Start of Content Area

Function documentation Performance Trace Recordings  Locate the document in its SAP Library structure

Use

The performance trace writes duration information for actions, where actions are comparable to the transaction steps of an SAP System.If, for example, the Global Workload Monitor (transaction ST03G) shows that the average response time of an application is too high, you should activate the trace to find the cause.

 

Prerequisites

The performance trace must be activated and configured. For more information, see Activating the Performance Trace.

Features

The J2EE Engine is not transparent for the Distributed Statistics Records (DSRs). They can only measure the duration of the processing between the entry and exit points colored gray in the figure. The performance trace, on the other hand, writes duration information for the individual modules of the engine (HTTP, service, JMS, and so on) and therefore provides a higher granularity of information.

This graphic is explained in the accompanying text

 

The area between the entry and exit points is broken down in greater detail in the traces. The trace records the processing times within the modules, for example, the names of called significant methods are recorded for each module together with their duration. The methods that are displayed are predefined. These are method calls that are typical for the corresponding module. The method calls are displayed with class, method name, details of the duration in microseconds, and whether the method was completed normally or with an exception.

 

Example

For example, in the Global Workload Monitor (transaction ST03G), the service type displayed is always that of the last request. This means that if the request ran over multiple containers and finally to the EJB Container, the request is displayed as an EJB Request in the Global Workload Monitor. If the administrator wants to know exactly where the individual times are spent, he or she must activate the performance trace.

 

You can use the Visual Administrator of the J2EE Engine to configure, among other things, the modules of the Engine for which performance traces are to be written. For more information about this, see Activating the Performance Trace.

You can use the functional trace (transaction STATTRACE) to display the performance traces in the central monitoring system.

 

 

 

End of Content Area