Remotely monitoring queue managers on MQ Appliance

You can use the WebSphere® MQ agent to monitor remote queue manager on MQ Appliance environment.

1. Set up connection to the remote queue manager. On the remote queue manager, define a server connection channel and a listener that is used for communication with the monitoring agent. Run the following command:

   M2000# mqcli
   M2000(mqcli)#runmqsc qmgr_remote
   > DEFINE LISTENER(listener) TRPTYPE(TCP) PORT(port_NO) 
   > DEFINE CHANNEL(chl_name)CHLTYPE(SVRCONN) TRPTYPE(TCP)
   CONNAME('host_IP(port_NO)') QMNAME(Qmgr_remote)
   > END

   where:

   • qmgr_remote is the name of the remote queue manager.
   • listener is the name of the listener on the remote queue manager.
   • port_NO is the port number to be used for the listener.
   • chl_name is the name that you assign to both the server channel and the client channel.
   • host_IP is the IP address of the remote system.
2. Configure the listener to start automatically and then start the listener on the remote queue manager by running the following commands on the remote system:

   M2000# mqcli
   M2000(mqcli)#runmqsc qmgr_remote
   > ALTER LISTENER(listener) TRPTYPE(tcp) CONTROL(qmgr_remote) 
   > START LISTENER(listener) 
   > END

3. Make sure that channel authentication settings are configured appropriately for the user ID that is used to start the MQ agent instance. For more information, see Setting up a queue manager to accept client connections in IBM MQ Appliance Knowledge Center.
4. Create an instance of the WebSphere MQ agent for remote monitoring by following instructions in Configuring the WebSphere MQ agent and provide remote queue manager connection information in prompts following Remote Monitoring Settings.

   Remote Monitoring Settings (For a local queue manager, just press Enter in
   this section) :
   Connection name for remote monitoring, for example: 192.168.1.1(1415)
   Connection Name (default is: null):
   Channel name for remote monitoring, SYSTEM.DEF.SVRCONN is as default.
   Channels (default is: null):

5. Start the WebSphere MQ agent instance.