Instrumenting application environment

Z APM Connect IMS Data Producer expects a correlation token known as tracking ID, such as the AppDynamics Singularity Header, to be passed as part of the user message and in a specific fashion.

This tracking ID can be used to show the components which a transaction involves, the order in which the components communicate with each other, and the time it takes a transaction to traverse each component.

The tracking ID is set by the Z APM Connect client and returned in the HTTP response message for each transaction. By default, transaction tracking is disabled. To use a tracking ID, transaction tracking must be enabled.

A tracking ID can be set in the following ways:

• By using a client such as AppDynamics on Websphere Application Server (WAS) that uses IMSInteractionSpec Class methods to directly set the tracking ID. This process is described in Optional IMS TM resource adapter plug-in support. For more information, see Optional IMS TM resource adapter plug-in support.
  
• By using the Z APM Connect Interceptor on z/OS Connect EE to set the tracking ID for the IMS Service Provider. This process is described in Z APM Connect Interceptor. For more information, see Installing and configuring Z APM Connect Interceptor.
  Note: the incoming requests to z/OS Connect EE must already contain an AppDynamics Singularity Header.
  
• By specifying the tracking ID manually in the transactions IMS IRM control block as described in the Optional IMS Connect User Message Exit. For more information, see Optional IMS Connect user message exit.
  
• By using an IMS Service Provider to initiate an IMS MQ transaction passing an AppDynamics header in an MQRFH2 header, as described in the Optional IMS MQ Bridge Configuration. For more information, see Optional IMS MQ Bridge Configuration.