Bookshelf v7.5: About Call Graph Generation Data

Running a call graph generation analysis of a Siebel ARM file results in an extensible markup language (XML) output file. For a given Siebel ARM file, the Siebel ARM post-processing tool constructs a map with call references. Each node in the call map represents an instrumentation instance. Using this option generates an XML file containing all the calls made by each component (if that component captures response time data).

The XML output file contains the following tag schema, which records the details of the calls. For descriptions on each of the tags, see Table 9.

Table 9. Call Graph Generation Analysis Tags
Tag	Description
Node	Each instance of an instrumented area is a node. Each node can have zero to many nodes as its descendants.
SarmID	A unique number representing a Siebel ARM instrumentation point.
ParentID	A unique number representing the caller of an instrumentation point within the same request. The caller is another instrumented area.
RootID	A unique number assigned to a request submitted from the SWSE to the Siebel Server. RootID is also known as Request ID.
SenderSrvID	Reserved for future use.
SenderProcID	Reserved for future use.
Area	Instrumentation element within the Siebel architecture. The seven elements that collect response time information are: SarmIO, SWSE, Server Thread (SMI), SWE, Workflow, Scripting Engine, and Database Connector.
SubArea	Detailed instrumentation within an area of the Siebel architecture. For example, Siebel ARM captures response time for invoking a method (Invoke Method) or executing a step (Step Execution) within a Workflow execution.
StartTime	Internal representation of the Siebel ARM record timestamp.
Duration	Total time to execute the instrumented area.
UserInt1	Context information captured at the point of instrumentation. The value depends on the instrumented area.
UserInt2	Context information captured at the point of instrumentation. The value depends on the instrumented area.
UserString	Context information captured at the point of instrumentation. The value depends on the instrumented area. For example, name of the method invoked or workflow process initialized.