Single Activity Trace 

Use

The Single Activity Trace (SAT) is used to track a single activity running over multiple components (Cross Component Trace). If there are performance problems, the SAT is used to analyze a component in detail. To allow for single activity tracing, a component must be instrumented with JARM. The JARM data for each request and component is written automatically in a trace file using the SAP Logging API. This file can be viewed in the LogViewer. For more information, see Log Types → SAT Trace Format.

The J2EE Engine is instrumented with JARM, therefore even if you want to trace an application that is not instrumented with JARM, you still can use the JARM Viewer in the Visual Administrator to browse the JARM data generated by some of the J2EE Engine components that can be related to the traced application.

 

Using JARM implementation, you can analyze a single (user's) request to find performance problems in an application, or to understand the logical processing steps inside an application. The difference between SAT and JARM is that with JARM you will get only the top-value data, while with SAT you will receive all the trace data generated for the selected request.

For more information how to start the SAT, see Activating the Single Activity Trace.