Modern applications are often multi-tier with processes running in the differing tiers calling each other. Often performance problems happening in the front-end application process are due to problems happening on the back-end process it uses. Tracing the front-end process is not sufficient to determine the cause of the issue. And it is often impossible to tell which back-end processes it is calling.
Cross-process transaction tracing solves this problem by correlating the trace events of the front-end applications with the corresponding trace events from back-end processes. Use the CA Introscope Workstation to diagnose back-end processes problems by viewing a problematic front-end transaction trace event. Then use the trace event to find the corresponding back-end trace events.
That back-end trace provides the “when, where, and why” of information that determines the cause of the problem. The Information provided includes server name, transaction processor, unit of work ID, transaction ID, and internal transaction timings.
Cross-Process tracing is enabled when the appropriate front-end and back-end Agents and tracers are installed. For more information about installing the tracers, see Install and Configure the Extension.
Back ends are external systems, such as a:
Front ends are the component of an application that first handles an incoming request such as a:
When a front-end transaction invokes a back-end transaction, two trace events are created and sent to the CA Introscope EM. One from the front-end agent and the other from the back-end CA APM Cross-Enterprise Agent. Additional back-end traces are generated for each additional back-end call that the front-end application makes. The CA Introscope Workstation can display all these traces together on the Trace View tab. Selecting the front-end trace event allows the CA Introscope Workstation to fetch and display all correlated back-end traces on the same pane. Also, selecting a back-end trace event causes the front-end and all correlated back-end traces to display together.
The front-end tracers for CTG and web services insert a unique correlation identifier in the front-end traces. This identifier decorates the back-end calls into CICS with the same correlation identifier. This decoration flags the back-end transaction call as originating from a monitored front-end transaction and provides a unique identifier. CA APM Cross-Enterprise adds the same correlation identifier to the corresponding CICS back-end trace. The CA Introscope Workstation uses the unique identifier in the front-end and back-end trace events to fetch corresponding front-end or back-end traces for display. Only the CICS transactions can be invoked using CTG, and web services.
The front-end tracer for the MQ flags and MQ messages come from a monitored application. The MQ trace is correlated with MQ message ID, correlation ID, or both. The MQ message ID or correlation ID provides a unique identifier for the correlation between both the front-end MQ traces and back-end traces. The back-end traces from both CICS and IMS transactions have this correlation ID when MQ is the communication method that is used to invoke the transaction.
|
Copyright © 2013 CA.
All rights reserved.
|
|