Configuring the WebSphere MQ agent
The WebSphere® MQ agent supports only WebSphere MQ 7.1 or later. Before you can start the agent, you must assign an instance name to the agent and complete the several configuration tasks for the user ID, managed system names, or transaction tracking optionally.
Procedure
- Authorize the user ID that is used to configure, start, and stop the agent to access IBM® MQ (WebSphere MQ) objects. See Authorizing the user IDs to run the agent.
- Configure the agent by providing an agent instance name, a queue manager name, and optionally
an agent name. See Configuring the WebSphere MQ agent. Tip: If you want configure the WebSphere MQ agent for remote monitoring, you must do some manual configuration after you create an agent instance. For instructions, see the following topics:
- Optional: When a unique managed system name is required to distinguish different monitoring agents, use the Agent Name option in the mq-agent.sh config command to specify the middle qualifier of the managed system name if you did not do so when you configured the agent for the first time. See Specifying unique managed system names for multiple queue managers.
- Optional: To configure the agent to collect transaction tracking data of the monitored queue manager, use the Agent Configuration page. For instructions, see Configuring transaction tracking for the WebSphere MQ agent.
- Optional: By default, the queue manager does not generate several types of events. Thus, these events are not monitored by the WebSphere MQ agent. For these events to be monitored displayed in the Queue Manager Events group widget, enable the queue manager to generate the related events by using the ALTER QMGR command. For instructions, see Enabling the queue manager to generate specific events.
- Authorizing the user IDs to run the agent
For a user ID to configure, start, and stop the WebSphere MQ agent, the user ID must belong to the mqm group. Also, for a non-root user or a non-administrator user, you must grant users the access to the IBM MQ (WebSphere MQ) objects by using the IBM MQ (WebSphere MQ) control command. - Configuring the WebSphere MQ agent
You must assign an instance name to the WebSphere MQ agent and configure the agent before it can start monitoring your WebSphere MQ) environment. - Specifying unique managed system names for multiple queue managers
Unique managed system names are required sometimes to distinguish different monitoring agents that connect to the same monitoring server. Use the AGTNAME parameter in the silent response file or the Agent Name option in the mq-agent.sh config command to specify the middle qualifier that is used in the managed system name. - Configuring transaction tracking for the WebSphere MQ agent
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. - Enabling the queue manager to generate specific events
Several types of queue manager events are not generated by the queue manager by default. You must first enable the queue manager to emit these events, so they can be monitored by the WebSphere MQ agent. - Remotely monitoring queue managers on MQ Appliance
You can use the WebSphere MQ agent to monitor remote queue manager on MQ Appliance environment. To do it, you must configure an agent instance and set up connections between the agent and the queue manager. - Remotely monitoring HA queue managers on MQ Appliance
To remotely monitor HA queue manager on MQ Appliance, you have two options. One is to use a single agent instance to connect to whichever system that has the active queue manager. The other option is to use separate agent instance for each appliance that the queue manager might be running on.