6.1.2 Monitoring Initiator

A "monitoring initiator" is a process that "initiates" tracking a call path tree. The process can be a Tuxedo client, application server, client proxy server (WSH/JSH), the Tuxedo domain gateway server or web service gateway server GWWS. A typical scenario is when a tpcall/tpacall/tpconnect is invoked by the monitoring initiator; call path monitoring begins. All the back-end services involved in this call are displayed on the call path tree representation in the Oracle TSAM Plus Console.

Note:

Currently only tpcall/tpacall/tpconnect can trigger a call path monitoring. Other communication models are not supported.

For tpconnect, there are limitations in the different scenarios:

• For common usage scenarios, only service in and return call segment are supported. The response call path is missed if the client issues disconnect and the call is handled by a bridge.
• When a client invokes tpdiscon, the time stamp is later than the last call path segment.
• If tpconnect fails, nothing is recorded in Oracle TSAM Plus manager, that is, no information is displayed for the call.

A Tuxedo application server performs two functions:

• All sub-calls made in the service implementation are a part of the call path tree started by the original monitoring initiator (if the incoming request is already monitored).
• It is a monitoring initiator with calls made in the service routine according to the monitoring policy definition.