Documente Academic
Documente Profesional
Documente Cultură
Prerequisites
To generate trace files that are required for the detailed performance analysis you need to download and unpack the file IEMon.zip. This file can be found at http://service.sap.com/bw Performance.
Installation of IEMon.exe
In order to use the IEMon.exe analysis tool, unpack the archive IEMon.exe into a separate directory. IEMon.exe can be executed without any further installation steps.
Usage of IEMon.exe
IEMon.exe is a simple Web browser with enhanced protocol logging facilities. You can enter any URL in the address bar and press the Navigate button to load and display the Web page. IEMon creates a log file iemon.txt in the TEMP directory %TEMP which contains information about various browser events. To display the progress of the protocol logging, activate the check box Display Progress. With the Open Log File button you can conveniently load the log file into notepad.
For our response time analysis we need to look at only three types of events: Before Navigate: The HTTP request is being sent to the Web server. Navigate Complete: The Web server responds with an HTML stream. Document Complete: The browser has finished rendering the Web page. In our example above, the HTTP request was sent at 11:57:06.533 and the response arrived at 11:57:07.144. This is equivalent to a load time of 581 ms. Between 11:57:07.144 and 11:57:08.095 the browser was rendering the HTML code, so the rendering time was 951 ms. The total query response time sums up to 1.562 ms.
If IEMon.exe is used to trace Web pages in a portal environment, multiple URLs are called and logged in the trace file. For these cases, the three events carry the corresponding URL, so the proper log file entries have to be matched according to those URLs.
Important note: we recommend deleting the contents of the log file before starting a new analysis. This also applies for queries with multiple navigation steps. You should start a new trace before immediately before each navigation step. To get rid of old trace information, open the log file of IEMon by pressing the Open Log File button, mark all its contents, delete it, and save the file to its original location (Temp directory). After the query has executed, open the log file again, and store it into a trace file directory. You can find further information on IEMon.zip. in the file ReadMe.html which is included in the archive.
been established. If you have an open Web browser (or IEMon) please shut the browser down and restart it before you start tracing the ABAP calls.
An incoming HTTP request causes a trace file to be generated. This trace file can be analyzed with transaction SE30. If multiple HTTP requests are processed (e.g. a selection screen, or multiple Web queries from a Web template) each request generates an individual trace file. Note: On systems with multiple application servers make sure to call transaction SE30 on the server that has handled the HTTP request and produced the trace file. Open transaction SE30, select Other file , specify the user SAPSYS and choose the proper trace file from the list. To find all relevant trace files, we recommend deleting all previous trace files before executing the Web query analysis. Double click the trace file to get an overview screen, then press the Hit List button (F5) to see the detailed trace information. Download this trace information into a local file onto your PC (System List Save Local File) as unconverted file.