Transaction Tracking with TrackingToken
For the CICS transactions that are being called through CICS Transaction Gateway, CICS TG provides a mechanism by which monitoring products, also referred to as stakeholders, can track the requests in processing system of record.
For each API or service request, CICS TG generates a unique correlator to identify the request. This correlator is embedded in a tracking token together with stakeholder tokens. The tracking token is sent with the request to the system of record, where the token can be programmatically inspected by the monitoring product's agent (RequestExits). A stakeholder token contains a monitoring product's stakeholder identifier, which is a single character in the range A-Z or a-z.
The flow diagram depicted in Figure 1 describes the TrackingToken generation at the application side based on the registered StakeholderIdentifier. The generated token is propagated to the CICS region through CICS Transaction Gateway using origin data with IPIC protocol.
Flow Diagram for Transaction tracking with Tracking Token
Request monitoring exits can be configured on CICS Transaction Gateway client applications as well as gateway daemon. Transaction tracking facility is enabled by implementing TrackingTokenInterface in request monitoring exit.
If Transaction tracking facility is enabled for CICS Transaction Gateway client applications, then tracking tokens are generated. If Transaction tracking facility is enabled on gateway, then CICS Transaction Gateway will not acknowledge it and treat as if the TrackingTokenInterface is not implemented.