How to Trace and Analyze Events › How to Trace Cross-Process Transactions › Enable Cross-Process Transaction Tracing

Enable Cross-Process Transaction Tracing

The CA Cross-Enterprise APM component is designed to allow transaction tracing across the multiple tiers of an application that invokes transactions on the mainframe. The currently supported communications methods available out of the box are:

• CICS Transaction Gateway using Channels invoking the CICS transactions
• HTTP invocations from Java applications that extend HttpURLConnection which invoke CICS transactions
• HTTP invocations from Java applications that extend HttpURLConnection which invoke Java servlet applications extending HttpServlet
• Web Services Calls into CICS
• WebSphere MQ Series messages sent to CICS or IMS transactions which the mainframe transaction retrieves using function MQget()

When properly configured, traces can be generated from all instrumented tiers of an application. These traces are then shown in the Workstation together in the Trace View tab. The Trace View tab is accessible in the Workstation Investigator from the Transaction Trace Viewer launched during a Transaction Trace session. The Trace View tab is also accessible from the Agents tab of the Cross-Enterprise APM agent in the Investigator.

The Workstation can correlate the separate traces that run together into one view because the traces contain the same correlation ID. This correlation ID is generated in the first tier of the application. The ID is then passed to the agents instrumenting transactions invoked on subsequent tiers using the supported communications methods. In order for this process to work, each tier must be instrumented and every communications method that is used must be supported and instrumented.

To instrument the application tiers for the various communications methods, ensure that you have installed and enabled the CA APM Java agent components.