Activity Tracing 

Use

You can sequentially record the activities of individual requests and their components for a defined period of time, and then analyze their performance and errors in the Log Viewer of the J2EE Engine. Technically, activity tracing is based on Java Application Response Time Measurement (JARM).

If you want to record the activities of custom components, you must follow the example of the interfaces provided for this purpose so that the data can be transferred correctly to the Monitoring Service. 

You can find further documentation and examples in the SAP Enterprise Portal Development Kit (PDK) section of the Help for the SAP NetWeaver Developer Studio.

Integration

Activity tracing is activated and deactivated in the Visual Administrator of the J2EE Engine for a given user or for all users.. In a cluster environment, activity tracing is activated automatically for all cluster nodes.

All the trace data is written to file sat.trc.0 in the path ...\usr\sap\<SAP_System ID>\JC<J2EE Engine Instance>\j2ee\cluster\server<n>\log. New trace data is constantly added to this file.

For details about the configuration see the Administration Guide for the J2EE Engine.

Activities

For more information about activating and deactivating single activity tracing, see the documentation for the Visual Administrator at Single Activity Trace.

For more information about the data that is available during activity tracing, see Evaluating Activity Tracing.