Message Broker agent: multi-instance broker configuration

Body

This is a blog entry create to clarify the configuration needed for the Message Broker agent to monitor a multi-instance broker installed on two systems.

Environment

Let's assume that you have 2 systems system1 and system2.
Then you have the following IIB configuration as reported by the output of mqsilist

user@system1 bin# mqsilist
BIP1295I: Integration node 'BRK1' is an active multi-instance or High Availability integration node that is running on queue manager 'QMGR1'.
BIP1293I: Integration node 'BRK2' is a multi-instance integration node running in standby mode on queue manager 'QMGR2'.
BIP8071I: Successful command completion.

user@system2 bin# mqsilist
BIP1295I: Integration node 'BRK2' is an active multi-instance or High Availability integration node that is running on queue manager 'QMGR2'.
BIP1293I: Integration node 'BRK1' is a multi-instance integration node running in standby mode on queue manager 'QMGR1'.
BIP8071I: Successful command completion.

Instructions

First of all you need to create a QI agent instance on system1 and a QI agent instance on system2.
They have their own xml configuration file and the important point is to have 2 different AgentId.
In case you use the same AgentId by mistake, the subnode names will be duplicated because there is no hostname info in the subnode MSN <BrokerName>:<AgentId>:KQIB
So the xml files should look like below (in case of IIB 10 you need to explicitly define the defaultWMBInstallDirectory).

*qi*.xml on system1 should contain:
<KqiAgent version="730"
          agentId="SYS1"
...
          defaultTakeActionAuthUsers="*"
          defaultWMBInstallDirectory="/app/IBM/iib-10.0.0.9">
</KqiAgent>

*qi*.xml on system2 should contain:
<KqiAgent version="730"
          agentId="SYS2"
...
          defaultTakeActionAuthUsers="*"
          defaultWMBInstallDirectory="/app/IBM/iib-10.0.0.9">
</KqiAgent>

With these xml files, the two QI agent instances should discover the 2 brokers BRK1 and BRK2 that are on both system1 and system2 (with different status).

Hope this helps
Walter

Subscribe and follow us for all the latest information directly on your social feeds: