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.
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.
Click Submit.
| Note: | This is a time intensive process. While you wait for results, you can continue with other monitoring tasks. |
|
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
|