MQ Monitoring agent: remote monitoring on the MQ Appliance environment
WalterPietroni 2000000AEC Visits (8123)
The general approach to monitor a queue manager in MQ Appliance is to configure an ITCAM for WebSphere MQ monitoring agent on another Linux, AIX or Windows system to remotely connect to the queue manager and gather information. ITCAM for WebSphere MQ Monitoring does not currently run on MQ Appliance.
Prerequisites for system where ITCAM agent will be running:
1. ITCAM Agents for WebSphere Messaging Version 07.30.00.00 or above installed
See the link below for details about the latest installation level, v07.30.01.00:
2. WebSphere MQ Client
See the link below for details:
Setup on system where agent will be running:
For each queue manager to be monitored:
2) Modify the configuration file of the agent instance to enable remote monitoring by setting the following parameters:
SET MANAGER NAME(<qmgr_name>) REMOTE(YES)
On Windows, configuration file is mq_<
Setup on queue manager to be monitored:
SVRCONN channel and listener definitions
For each queue manager to be monitored, there must be SVRCONN channel and listener defined and started. For example,
Note that for agent to be able to access remote queue manager, the listener must be started. CONTROL(QMGR) will ensure that listener is started when queue manager starts.
Create CCDT (Client Channel Definition Table File):
The CCDT must reside on the system where ITCAM agent is running and must have a CLNTCONN definition for EACH queue manager that an agent instance will be monitoring. The CCDT can be created on any system where WebSphere MQ is installed and then transferred (in binary mode) to the system where the agent is going to run. To remotely monitor multiple queue managers from the same system with multiple agent instances, you must create one CCDT (AMQCLCHL.TAB) that has all CLNTCONN definitions needed. Note that the CCDT must be at a version less than, or equal to that of the client. For example, if CCDT was created using WebSphere MQ V8, then you must be running WebSphere MQ V8 client on the system where the agent is running and using the client connection.
1) Use "runmqsc -n" or "runmqsc <any active qmgr> to generate CCDT and transfer to system where agent is going to run (if different system)
If WebSphere MQ 126.96.36.199 or above is installed on a system that can be used, you can create the client channel definition table file (AMQCLCHL.TAB) for remote
Otherwise, issue ""runmqsc <any active qmgr>".
2) Once runmqsc issued, for EACH queue manager that is going to be monitored, i.e. each agent instance, issue a DEFINE CHANNEL,
3) If this is not on the system that the agents are going to run on, then transfer the CCDT (AMQCLCHL.TAB) to agent system in binary mode.
If transferring from MQ Appliance you can use File Management in IBM MQ Console UI to manipulate/copy files. Or for linux/unix:
The AMQCLCHL.TAB location may vary based on version, MQ configuration, etc, but default location is:
Refer to the WebSphere MQ documentation for more details on CCDT and location if needed:
4) Place AMQCLCHL.TAB in directory where agent is running.
On Windows: <ITMHOME>\TMAITM6 on Win32
Special Considerations for HA queue managers in MQ Appliance environment
If monitoring HA queue managers in MQ Appliance environment, you have 2 options:
OPTION 1 - One ITCAM for WebSphere MQ Monitoring Agent Instance that connects to whichever system that has the active queue manager
The steps outlined above should be followed, with one change. In step (2) of "Create CCDT" section, create 2 definitions for the HA queue manager, one for each host_IP:
DEFINE CHANNEL(<chl_name>) CHLTYPE(CLNTCONN) TRPTYPE(TCP) CONN
OPTION 2 - Separate ITCAM for WebSphere MQ Monitoring Agent Instance for each appliance that the queue manager can be running on.
At this time, with ITCAM V730, the inactive/standby queue manager will not have any data but "Queue Manager Not Available" in queue manager status. However, users will be able to see which appliance the queue manager is active on.
To run remote agents on Unix, one for each appliance/qmgr in HA group:
To set up this option, the steps outlined above should be done for each appliance/qmgr. The CCDT that is used for the different appliances must only contain the CLNTCONN for that appliance. So separate installation and CCDT must be created for each one.
To run remote agents on Windows, one for each appliance/qmgr in HA group:
To set up this option, the steps outlined above should be done for each appliance/qmgr. Only one installation is needed, with one agent instance for each appliance/qmgr. The following differences apply when creating CCDT table:
2) Copy both APPL1.TAB and APPL2 TAB to agent directory:
For example, after you create two WebSphere MQ Agent instances, which are instance1 and instance2, two files, kmqc
where , instance1 and instance2 are the two WebSphere MQ Agent instance names.
Configure Channel Authentication Settings
Make sure that channel authentication settings are configured properly for the user ID that is used to start the agent instance. This will vary depending on queue manager settings for CONNAUTH and CHLAUTH. A few things to consider:
1) With WebSphere MQ version 8.0.0, the default channel authentication specifies CONNAUTH of SYST
Note that setmqaut is not available on MQ Appliance so IBM MQ Console or SET AUTHREC in runmqsc can be used to grant this authorization.
2) If queue manager has CHLAUTH(DISABLED), then MCAUSER of authorized user can be specified in the SVRCONN definition that is used for client connection.
3) Our agent client connection does not currently pass any password, so CHCKCLNT(REQUIRED) will not work properly.
Subscribe and follow us for all the latest information directly on your social feeds: