When to
Use the Different Performance Tools
Performance Tool |
When to Use |
Tools for problem detection |
|
Distributed Statistics Records (DSRs) |
The statistics are used to constantly monitor the J2EE Engine and to provide a good overview of the J2EE Engine system performance. |
Java Application Response Time Measurement (JARM) |
A method for collecting response time data from Java applications. It is used in productive systems to detect problems in Java applications. |
Tools for problem analysis |
|
Performance Trace |
Use it to analyze problems in the J2EE Engine performance. It is used in case a performance problem is detected with the DSRs. |
Single Activity Trace (SAT) |
Use in productive systems to analyze problems with a certain application at runtime. |
SQL Trace |
If an application uses a database, use this trace to analyze the database selects or problems with the database connections, for example. |
Application Trace |
Used in non-productive systems to analyze problems with a certain application. |
Session Trace |
Use it to activate the Performance Trace, SAT and SQL Trace at once for a certain application for one session or request. |
The SAP Web AS (Java) performance tools do not duplicate their work. As shown in the figure below, the SAP Web AS (Java) statistics are handled by the DSRs and the application statistics are handled by JARM. The SAP Web AS (Java) tracing in a productive environment is handled by the Performance Trace and the tracing of applications in a productive environment is handled by the Single Activity Trace (SAT). For monitoring the performance of a database in a productive system, you can use the SQL Trace.
To monitor and improve the performance of an application in a development (non-productive) environment, as you need to restart the application anyway, you can use the Application Trace service.
