Pre-Requisites for Monitoring IBM WebSphere MQ Servers

1. To monitor the IBM WebSphere MQ server, the eG agent installed user should be within the MQM installed user group.
2. The eG agent should be bundled with JRE 1.7.

3. For monitoring IBM WebSphere MQ server version 6 and below, the following jar files need to be copied from the [WebSphere MQ install directory/java/lib] directory to the <EG_INSTALL_DIR>/lib directory:

   • com.ibm.mq.jar
   • connector.jar
   • com.ibm.mq.pcf.jar

4. For monitoring WebSphere MQ version 7.0, the following jar files need to be copied to the <EG_INSTALL_DIR>/lib directory:

   • com.ibm.mq.jar
   • com.ibm.mq.jmqi.jar
   • com.ibm.mq.headers.jar
   • com.ibm.mq.pcf.jar
   • com.ibm.mq.commonservices.jar
   • connector.jar

   After copying the jar files, remember to restart the eG agent. If MQ monitoring is done in an agentless manner, these jar files should be available on the remote agent that will perform the monitoring.

5. For monitoring WebSphere MQ version 8.0, the following jar files need to be copied to the <EG_INSTALL_DIR>/lib directory:

   • com.ibm.mq.jar
   • com.ibm.mq.jmqi.jar
   • com.ibm.mq.headers.jar
   • com.ibm.mq.pcf.jar
   • com.ibm.mq.commonservices.jar

   After copying the jar files, remember to restart the eG agent. If MQ monitoring is done in an agentless manner, these jar files should be available on the remote agent that will perform the monitoring.

6. For monitoring WebSphere MQ version 9.0 and above, only the following jar file need to be copied to the <EG_INSTALL_DIR>/lib directory:

   • com.ibm.mq.allclient.jar

   After copying the jar file, remember to restart the eG agent. If MQ monitoring is done in an agentless manner, these jar file should be available on the remote agent that will perform the monitoring.

7. Configure the eG agent to monitor the queue manager and its queues and topics.