How can MQ configuration agent product discover only a subset of the queue managers present on a system?
For security purposes, when more than one WebSphere MQ environments coexist on the same system, you may be interested in configuring the MQ Configuration agent product (KMC) so that only some of the queue managers created on the system may be discovered and so managed by the product.
When you install and start the KMC agent on a system and you run the Discovery procedure on the Configuration view on TEP, all the queue managers present on the system are listed in the Discovery panel where you can choose the ones to be fully discovered and added to the Defined view.
If you need to restrict this list of available queue managers, you can leverage on the feature introduced with OMEGAMON XE for Messaging v7 to manage WebSphere MQ clustering on AIX with which you can specify which queue managers you want to work with for a specific instance of the KMC agent using the KMC_QUEUEMGRS variable.
To use this feature, you define a new .cfg file for KMC agent, copying the default mc.cfg file to <hostname>_mc_<instance_name>.cfg and specify the following variables in it:
KMC_QUEUEMGRS=[ <qmgr1_name>,<qmgr2_name> ]
Then start the KMC agent specifying the instance name as follows:
<ITMHome>/bin/itmcmd agent -o <instance_name> start mc
This way, when running the Discover procedure from TEP, you'll see listed for this KMC instance, only the queue managers you have specified in KMC_QUEUEMGRS.
For a complete description of these variables and how to use them, you can refer to the WebSphere MQ Configuration User's Guide, section "Configuring in a cluster environment on AIX systems" - "Configuring the WebSphere MQ Configuration agent", at the following link:
Subscribe and follow us for all the latest information directly on your social feeds: