Before you start:
Complete the steps below to make connections between the Configuration Manager, brokers, and the User Name Server.
If components in your broker domain are supported by different queue managers, establish WebSphere MQ connections between those queue managers to enable messages to be exchanged. It is important that each broker is 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 your brokers.
To achieve the required connection, complete the following steps. All the steps here 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.
The value of 104857600 for maxmsgl in the following steps is merely an example. You are recommended to check the appropriate WebSphere MQ documentation to confirm the value for maxmsgl that you can use on your particular platforms.
In addition, note that you have to set the maxmsgl attribute only on the transmission queue that sends messages from the Configuration Manager's queue manager to the broker's queue manager.
You can set up a single receiver channel on the Configuration Manager's queue manager to support all sender channels created for the brokers. This requires a single definition on the Configuration Manager and a single sender definition on each broker, which 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 Event Broker components, and between clients and WebSphere Event 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).
Notices |
Trademarks |
Downloads |
Library |
Support |
Feedback
![]() ![]() |
ae18060_ |