Evaluating Activity Tracing 
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.
The trace file is displayed in the Log Viewer. The calls from requests (red name), components (blue name) and actions (gray name) are written record-by-record sequentially to the trace file together with the corresponding performance data (columns) of the individual users.
You can configure
the display of the performance data by hiding or showing columns. You can also
define the order of the individual columns. For more information see the
Administration Guide for the Log
Viewer.
The following data
is available:
(click with the alternate mouse button on one of the default columns; the list
is displayed in alphabetic order)
Column Header |
Meaning for |
||
Requests (red) |
Components (blue) |
Actions (gray) |
|
ClassName |
N/A = not available (planned for a later release) |
||
classVersion |
N/A = not available (planned for a later release) |
||
Datasource |
Storage path of the trace file as <servername>:<path> |
||
Date |
Time when this data record was written |
||
Description |
N/A = not available |
Description of the
action performed. |
|
GrossTime |
Total time of the request or component (including time for all subcomponents) |
-1 = not available |
|
Level |
-1 = not applicable |
Nesting Level 0 = main
component |
-1 = not applicable |
Location |
Source of the data record, normally the class name |
||
Message |
SATRecord = ID of the activity trace file |
||
Message ID |
ID of the message permitting unique cross references to messages in different log files |
||
Name |
Request name (red) |
Component name (blue) |
N/A = not available |
The name is defined
according to the convention: |
|||
NetTime |
Net time of the request or component (computed from its gross time less the gross time of the subcomponents). |
-1 = not available |
|
Number Of Sub Rec |
Number of components contained |
Number of actions contained |
-1 = not applicable |
outData |
Amount of outbound data for a request |
-1 = not available |
|
Properties |
Specific properties, displayed in square brackets [ ] |
||
Provider |
Source of the trace information 1 = JARM |
||
RecType |
Data record type 10 = JARM
request |
||
SequenceNumber |
-1 = not applicable |
Position in the call sequence within a request (starting with 0 = first call) |
|
Severity |
Degree of severity assigned to the trace data record |
||
Source Name |
Name of the log controller from which the data record origins |
||
startTS |
Time when the request, component or action was started |
||
State |
0 = OK |
-1 = not available |
|
Thread |
Technical name of the thread (thread ID) in which the request, component or action is running |
||
Username |
ID of the portal user |
N/A = not available |
N/A = not available |