Completing the configuration for OMEGAMON AI for CICS TG

These are additional tasks required to complete the configuration of OMEGAMON AI for CICS TG.

Post installation configuration for transaction monitoring support
Depending on whether you are monitoring transactions through a Gateway daemon or through a WebSphere® Application Server with OMEGAMON AI for CICS TG, you must take specific steps to complete the configuration after installation.
Monitoring CICS TG daemons bound to a TCPIP stack other than the one OMEGAMON AI for CICS TG Agent is bound to
On the same z/OS® LPAR, when the OMEGAMON AI for CICS TG Agent is not bound to the same TCPIP stack as is the monitored Gateway daemon, the agent must be provided with the IP address or hostname where the Gateway daemon is active, so that a successful remote connection can be established and statistical information can be collected.
Defining a policy to periodically sweep away any orphaned transactions (optional)
The transaction monitoring component of OMEGAMON AI for CICS TG keeps a table of all currently active transactions to calculate average response times and identify long-running transactions.

Parent topic: Completing the configuration