Siebel Performance Tuning Guide > Analyzing Siebel ARM Data > Analyzing Siebel ARM Files Using the Siebel ARM Analyzer Tool >
About User Session Trace Analysis and Data
This topic is part of Analyzing Siebel ARM Files Using the Siebel ARM Analyzer Tool. Running a user session trace analysis using Siebel ARM files from the Web server and the Siebel Server results in an extensible markup language (XML) output file. The XML output file contains detailed information about each of the SWE requests made by the user identified when running the Siebel ARM file conversion. If the user logs onto the system multiple times, then the output shows that there are multiple sessions. The SWE requests are grouped into specific login sessions and sorted by the time the requests were made. For more information about the Siebel ARM architecture, see About Siebel Application Response Measurement. For more information about creating this format of Siebel ARM output, see Running User Session Trace. The XML output file contains the following tag schema, which records the details of user session trace. The user session trace data also contains the tag schema of the performance aggregation analysis. For more information about those tags, see About Performance Aggregation Analysis and Data. <UserID>
<Session> <SessionID> <UserActionID> <ID>
<SWERequest> <ReqID> <TotalServerTime> <WebServerTime> <NetworkTime> <SiebServerTime> <DatabaseTime> <DatabaseCalls> +<SiebsrvrDetail>
For descriptions on each of the tags specific to the user session trace analysis, see Table 26. For descriptions of the tags that are also a part of the performance aggregation analysis, see Table 24.
Table 26. User Session Trace Tag Descriptions
|
|
UserID |
User login name. For example, SADMIN. |
Session |
Specifies performance data captured for a specific user session contained within this tag. |
SessionID
|
Refers to a unique user session ID in hexadecimal format. The first component of the session ID refers to the server ID, the second refers to the process ID, and the last section to the task ID. For example: !1.2b40.182b Server ID = !1 Process ID = 2b40 (2b40 is 11072 in decimal format and represents the operating system process ID number.) Task ID = 182b (182b is 6187 in decimal format and represents the task ID number.) |
UserActionID |
Data contained within this tag represents a specific individual action or request of the user. |
ID |
Number that identifies the specific user action or request in sequence for that particular user session. |
SWERequest |
Specifies performance timing data for the specific user action or request. |
ReqID
|
An incremental numeric ID number corresponding to a Siebel Web Server Extension (SWSE) plug-in request. |
TotalServerTime |
Total request time on the servers (includes Web server, Siebel Server, and network time). |
WebServerTime |
Total time spent on the Web server for a given request. |
NetworkTime |
Total time spent between the Web server and the Siebel Server. This time can also include some Siebel infrastructure time routing the request to the handling Siebel Server task. |
SiebServerTime
|
Time spent on the Siebel Server. |
DatabaseTime
|
The time spent on the network when communicating to the database. |
DatabaseCalls
|
Number of calls to the Siebel Server database connector layer. |
+<SiebsrvrDetail>
|
Response time and execution time for each of the architectural areas of instrumentation for a given session. For more information about these tags, see About Performance Aggregation Analysis and Data and About Call Graph Generation Analysis and Data. |
|