### Call Pattern

Each Tuxedo call triggers a set of service invocations. The back-end service operation is transparent to the caller. It may be a local service, remote host, and even a remote domain. A challenge for application monitoring is figuring out the exact call path tree (focusing on services). One type of service invocation tree is called a pattern. TSAM provides the capability to summarize a call pattern using collected performance data.

#### Define the Query Conditions

The call pattern statistics is a computing and database intensive task. TSAM gives query conditions as many as possible to limit the time used on pattern computing.

Table 1-20 Items in Filter
Name | Description
Root Service | The service name of the first service invoked by the monitored request. It can only be selected when Domain is selected of Initiator panel.
Minimum Request Number | The minimum number of requests that form a pattern. Usually a call pattern contains a large number of calls. This threshold prevents listing a pattern with small number of calls. The default value is 100.
Request Only | The pattern is decided by the request message. The reply messages can be dropped to reduce the time used. Reply transportation statistics are lost.
Time Window | The From and To enable the query window to second level. The default setting is the last day

Click Submit.

Note: | This is a time intensive process. While you wait for results, you can continue with other monitoring tasks.

Table 1-21 Initiator Items
Name | Description
Domain | Select the domain in which the initial request started
Machine | Select the machine in which the initial request started.
Server | If a monitored request is started from a server, the server name can be selected to limit the query scope.
Client | If a monitored request is started from a client, the client name can be selected to limit the query scope. For more information, see Using TSAM Agent in the Tuxedo System and Application Monitor (TSAM) User's Guide

#### Pattern Query Result

Table 1-22 Pattern Result
Name | Description
Number of Patterns | How many patterns were found
Pattern Description | A simple string indicates the pattern. By clicking it can see the pattern tree.
Number of Requests | How many requests contained in this call pattern
Pattern Tree | The pattern tree is service focus and the nodes are the services name involved in this pattern. The root node is always "INITIATOR". Click the Expand Tree button to expand the tree node.
Service on Pattern Tree | Click each service on pattern tree the transportation statistics to this service will be displayed
Average Transportation Time | The time (millisecond) is computed with all the requests contained in this pattern
Transportation Description | The transportation to a service might have following type: IPC Queue (Request) IPC Queue(Reply) Network (Request) Network (Reply)

##### Get Pattern with Selected Conditions

1. Input Filter conditions, such as root service, time window etc.
2. Limit Initiator scope. Select the wanted domain, machine, server or client.
3. Click the Submit button to get pattern information.
4. When the pattern tree is generated click Initiator to expand all tree nodes.
5. Click each service to see service transportation statistics.

#### See Also

- Call Path Tree