Instrumenting application environment
Depending on your IMS application usage, there are a few ways to instrument your
application environment to pass Instana Header to track IMS transactions via Z APM Connect.
About this task
Z APM Connect IMS Data Producer expects a correlation token known as tracking ID, such as the Instana 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 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 Instana singularity header.
- By using a client such as Websphere Application Server (WAS) that uses IMS TMRA and Instana Java
Agent to directly set the tracking ID. For more information, see Optional IMS TM Resource adapter support.Note: The incoming requests to WebSphere® Application Server must already contain an Instana header.
- By using an IMS Service Provider to initiate an IMS MQ transaction passing an Instana header in an MQRFH2 header, as described in the Optional IMS MQ Bridge Configuration. For more information, see Optional IMS MQ Bridge Configuration.