### Call Path Tree

The Call Path Tree Page displays Tuxedo call path application request information when Application Monitoring is turned on.

When Application Monitoring is turned on, Tuxedo associates each call path request with a unique ID name (Correlation ID). The Correlation ID denotes where the request originated and remains unchanged when the request travels across Tuxedo.

A Correlation ID consists of the following field values separated by a space:

- Tuxedo domain ID: `<DOMAINID>:<master machine name>:<IPCKEY>` in the`` UBBCONFIG `*RESOURCE` section. For more information, see Table 1-12.
- Logical Machine ID: `LMID` in the UBBCONFIG `*MACHINES` section
- Process Name:

"client": used for native clients

"WSH": used for /WS clients

<server name>: used for the server name

- Process ID (pid)
- Thread ID
- A counter in range of 1..99999999 (starting from 1)

#### Correlation ID Example

`TUXEDO SITE1 client 13753 1 145`.

Table 1-15 lists the Call Path Tree page properties.

Table 1-15 Call Path Tree
Name | Description
--- | ---
Query By Correlation ID | Searches call path information for given complete Correlation ID.
Filter | Selects specific search criteria.
Enable Paging | Lists found Correlation IDs.
Rows per page | Enter number of rows to display per page.
Initiator | Performs search based on domain, node, server, or client name.

#### Display Correlation ID Call Path Information

To display correlation ID call path information, do the following steps:

1. Fill in the Correlation ID under Query By Correlation ID.
2. Click the Query button to the right of the Correlation ID field.

The Correlation ID table appears.

#### Display Calls from an Initiator with Conditions

To display calls from an initiator with conditions, do the following steps:

1. Clear Correlation ID if it is not empty
2. (Optional) Fill in the Initiator information under "Initiator" (Domain, Node and the Process Name)
3. Fill in Filter information if you want to limit the scope of the result. You can:

1. specify Root Service to display calls for a particular service
2. specify Min Active Time to display calls started for the time the service is active
3. Specify the search scope by using:

Notes: | Active Call Path: search for unfinished call paths

Notes: | Call Path for latest: search for call paths started no earlier than `<n>` minutes ago. A 0 value indicates search all call paths.

Notes: | Call Path during: search for call path started during a time period.

4. Click the Query button to the left of Enable Paging field.

The Correlation ID table appears.

Table 1-16 lists the Correlation ID Table properties

Table 1-16 Correlation ID Table
Name | Description
--- | ---
No. | Sequence number. Starts at 1.
Correlation ID | The Correlation ID associated with the request.
Service | The service name invoked by the initiator.
Start Time | The time the request starts. The format is `YY/MM/DD hh:mm:ss:SSS' (SSS is millisecond).
Execution Time | Time elapsed (in seconds) since the request is sent out and the reply is returned.
Status | Indicates finished request. Indicates pending request. Indicates failed request.
Return Code | Displays a string representation and the `tperrno` value for the finished request. The display content is "`TPOK/0`" when there is no error.
GTRID | Displays the Global Transaction ID associated with the request, if any.

Clicking on the table column header will sort the table according to the selected column.

Clicking a Correlation ID displays more detailed request processing information. This detailed information is displayed in three sections:

- Call Path Tree
- Transport Detail Table
- Service Summary Table

##### Call Path Tree

Tuxedo request and reply are sent by the IPC message queue, or the network when the source and target are on different machine. The Call Path Tree lists the request originator (process name and PID), the Correlation ID (as its root), and the invoked service as its only child.

When you click on a Call Path Tree child, the Transport Detail table appears. Table 1-17 lists the Transport Detail table properties.

You can also display the server name, the physical message queue ID and logical queue name, and/or the server location information by clicking the corresponding check box (show server name, show queue info, show location).

Note: | A Call Path Tree child may also contain children if it makes calls when handling the request.

##### Transport Detail Table

A sequence number is displayed at the beginning of the service node of the Call Path Tree. Table 1-17 lists the Transport Detail table properties.

Table 1-17 Transport Detail Table
Name | Description
--- | ---
No. | Sequence number. Starts at 1.
From | The requesting application. It consists of following fields separated by a space: `DOMAINID:<hostname>:<IPCKEY>, LMID, Process Name, Server ID` (SRVID in UBBCONFIG if it is a server), and PID
To | The sending application. It has the same format as "From" column.
Start Time | The time when this transport is begin in `YY/MM/DD hh:mm:ss:SSS' format. (SSS is millisecond)
Elapsed Time | Seconds spent on this transport.
Description | Description about the transport. It denotes the type of this transport (IPC queue or network) and the type of message (request or reply).

##### Service Summary Table

A sequence number is displayed at the beginning of the service node of the Call Path Tree. Table 1-18 lists the Service Summary table properties.

Table 1-18 Service Summary Table
Name | Description
--- | ---
No. | Sequence number. The number is also shown in the beginning of invoked service in the Call Path Tree.
From | The requesting application. It consists of following fields separated by space: DOMAINID, LMID, Process Name, Server ID (SRVID in UBBCONFIG) if it's server, and PID. DOMAINID is not shown for simplicity if its value is the same as of the initiator's.
To | The sending application. It has the same format as "From" column.
Status | Indicates finished requests. Indicates pending requests.
Wait Time | Time elapsed (in seconds) from the time the request is sent until the time when it starts to be processed.
Exec Time | Time elapsed (in seconds) from the time the request is sent until the time the reply is returned.
GTRID | Global Transaction ID associated when the request is processed, if called in transaction mode or if AUTOTRAN is enabled.

Clicking the GTRID field in displays the Transaction Query page.

##### Configure Call Information Cache

All Calls Information started after TSAM booted is cached with 100000 (tsam.config.maxappsize) as the default cache size (call path number of). A call path will be removed from cache if it is not finished within 600 seconds (tsam.config.maxappactive); otherwise it stays in cache for another 300 seconds (tsam.config.maxappdone).

The parameters are configurable in the TSAM `web.xml` file.

Table 1-19 list the Call Information Cache configuration parameters.

Table 1-19 Call Information Cache Configuration Parameters
Name | Description
--- | ---
tsam.config.maxappsize | Max number in cache for a monitored application request. Default value: 10000.
tsam.config.maxappactive | Max cache time (in seconds) for monitored application request in active status. Default value: 3600.
tsam.config.maxappdone | Max cache time (in seconds) for monitored application request in done status. Default value: 3600.

#### See Also

- Query