Create connections between the Configuration Manager, the brokers, and the User Name Server.
Before you start:
The following steps describe how to make connections between the Configuration Manager, the brokers, and the User Name Server.
If the components in your broker domain are supported by different queue managers, you must establish WebSphere MQ connections between those queue managers to enable messages to be exchanged. Every broker must be able to exchange messages with the User Name Server that provides user name services for the broker.
If your broker domain components all run on the same system, and use a single queue manager, you do not need to create any WebSphere MQ connections between those components. If you have more than one broker, each broker must have its own queue manager; brokers cannot share a queue manager.
To achieve the required connection, complete the following steps. All of the steps are illustrated with MQSC examples. You can use any appropriate method for defining these resources. These examples assume that the queue managers are called COMP1 and COMP2.
In the following steps the value of 104857600 for maxmsgl is an example. Check the appropriate WebSphere MQ documentation to confirm the value for maxmsgl that you can use on your platforms.
You must set the maxmsgl attribute only on the transmission queue that sends messages from the queue manager associated with the Configuration Manager to the queue manager associated with the broker.
You can set up a single receiver channel on the queue manager that hosts the Configuration Manager to support all sender channels created for the brokers. Setting up a single receiver channel requires a single definition on the Configuration Manager and a single sender definition on each broker, the sender definitions on each broker must have the same name on each broker. You can also use this receiver channel on the Configuration Manager to support communications from the User Name Server.
All WebSphere MQ connections between WebSphere Message Broker components, and between clients and WebSphere Message Broker components, can be set up using any of the communications protocols supported by WebSphere MQ (TCP/IP and SNA on all operating systems; also, NetBIOS and SPX on Windows®).