Configuring transaction tracking for the WebSphere MQ agent

Edit online

Transaction tracking data for IBM® MQ (WebSphere® MQ) can be displayed in the middleware and topology dashboards after you enable the data collection on the Agent Configuration page for the WebSphere MQ agent.

Before you begin

  • Make sure that MQI application activity trace information collection is enabled at the queue manager. If you have not done it before the WebSphere MQ agent is configured and started, follow the instructions in Enabling MQI application activity trace and then restart the agent.
  • Make sure that the version of IBM MQ (WebSphere MQ) that you are using is supported by the transaction tracking feature. For the up-to-date information about supported IBM MQ (WebSphere MQ), see the prerequisites statement in the Detailed System Requirements Report for the WebSphere MQ agent.
  • Make sure that the WebSphere MQ agent is configured to monitor the queue manager. For instructions, see Configuring the WebSphere MQ agent.
Remember: Ensure that you have upgraded the WebSphere MQ agent to the latest version. For Cloud APM, Private, you need V8.1.2 or later. You must upgrade the agent, and configure and enable transaction tracking to see data in some of the widgets, such as the Message Volume widget.

Procedure

To configure transaction tracking for the WebSphere MQ agent, complete the following steps:

  1. From the navigation bar, click Configure icon System Configuration > Agent Configuration.
    The Agent Configuration page is displayed.
  2. Click the WebSphere MQ tab.
  3. Select the check boxes for the queue managers that you want to monitor and take one of the following actions from the Actions list:
    • To enable transaction tracking, click Set Transaction Tracking > Enabled. The status in the Transaction Tracking column is updated to Enabled.
      Tip: Tracking alias queues and remote queues is enabled by default. To reduce the volume of data that is being tracked, you can disable the tracking of alias and remote queues by clicking Set Alias Queue Tracking > Disabled from the Actions list. After tracking alias and remote queues is disabled, alias queues and remote queues are eliminated from the Transaction Topology view.
    • To disable transaction tracking, click Set Transaction Tracking > Disabled. The status in the Transaction Tracking column is updated to Disabled.

Results

You have configured the WebSphere MQ agent for tracking the selected queue managers. Transaction tracking data can be displayed in the middleware and topology dashboards. For more information, see Adding middleware applications to the Application Performance Dashboard.