Substitute the names of your brokers for these examples wherever they are used.
All commands shown must be issued on the system on which the appropriate resource is defined. WebSphere MQ commands (for example, the command to define a queue) are shown in MQSC format. For more information about WebSphere MQ commands, refer to your WebSphere MQ documentation.
The following steps describe what you should do to add, as a leaf node within your MQSeries Publish/Subscribe broker network, a WebSphere Business Integration Message Broker broker that you have already created.
define qlocal(SYSTEM.BROKER.INTER.BROKER.COMMUNICATIONS) noshare
mqsistop WBRK_BROKER
mqsistart WBRK_BROKER
When the WebSphere Business Integration Message Broker broker is restarted, the presence of the interbroker queue (defined above) enables the broker to receive and process messages on this queue.
define qlocal(SYSTEM.BROKER.DEFAULT.STREAM) noshare
If you prefer, you can create your own message flow.
You can find full details of how to complete these steps in the online help for the workbench.
define qlocal(STREAM.X) noshare
You can use the supplied publish/subscribe message flow as the basis for each new message flow. Each MQInput node representing a non-default stream must have the property implicitStreamNaming set (this is the default setting).
strmqbrk MQPS_BROKER1
mqsijoinmqpubsub WBRK_BROKER -p MQPS_BROKER1
mqsilistmqpubsub WBRK_BROKER
BIP8090I: MQSeries Publish/Subscribe neighbor WBRK_BROKER is active BIP8091I: Common stream SYSTEM.BROKER.DEFAULT.STREAM BIP8091I: Common stream STREAM.X
Related tasks
Adding a broker as a parent node
Notices |
Trademarks |
Downloads |
Library |
Support |
Feedback
![]() ![]() |
aq18610_ |