Home

 

Adding a broker to a network

You are recommended to define the broker topology from the root down.

Before we can add a broker to the network, channels in both directions must exist between the queue manager that hosts the new broker and the queue manager that hosts the parent. Brokers use explicit addressing when sending messages to queues that reside on another queue manager. When the queue is opened by the broker, both the queue and queue manager names are specified. To facilitate multi-broker operation, this queue manager name must resolve to the appropriate transmission queue. The simplest method of achieving this is for the transmission queue to have the same name as the remote queue manager name.

If you do not adopt this naming scheme, queue manager alias definition can be used to ensure that messages get placed on the appropriate transmission queue. For example, to specify that messages sent to queue manager PARENT are placed on transmission queue, PARENT.XMITQ:

DEFINE QREMOTE (PARENT) RNAME() RQMNAME(PARENT) XMITQ(PARENT.XMITQ)

To specify that messages sent to queue manager PARENT are placed on transmission queue, PARENT.XMITQ on iSeries:

CRTMQMQ QNAME(PARENT) QTYPE(*RMT) RMTMQMNAME(PARENT) TMQMNAME(PARENT.XMITQ)

To add a broker to the network, start the broker with the strmqbrk command (STRMQMBRK on iSeries), specifying the name of the parent broker if appropriate. When the broker has been started with a parent named we cannot change the name of its parent, even when the broker is restarted. We cannot change the parent of a broker as part of normal operational procedures without disrupting service. This command is described in strmqbrk (Start broker function).

 

Home