In an WebSphere MQ Publish/Subscribe network a broker might not support the same set of streams as its neighbors. If a broker does not support a stream that is supported by one of its neighboring brokers, publications associated with that stream are not available to clients at that broker.
When a WebSphere Event Broker broker is added to the network, it supports all the streams that are supported by its neighboring WebSphere MQ Publish/Subscribe brokers. This means that clients of the WebSphere Event Broker broker can target publications for any stream supported by any of its WebSphere MQ Publish/Subscribe neighbors.
However, to make these publications available, you must define the stream queues, and define and deploy the message flows that support them, to the WebSphere Event Broker broker.
The default stream queue SYSTEM.BROKER.DEFAULT.STREAM is always supported by every broker in a WebSphere MQ Publish/Subscribe network, and must be defined for every WebSphere Event Broker broker in a heterogeneous network. At each broker, you must also define and deploy a message flow to service this queue.
When a WebSphere Event Broker broker is integrated into a WebSphere MQ Publish/Subscribe network, and links two or more WebSphere MQ Publish/Subscribe brokers that share common streams, you must define the common stream queues, and define and deploy the message flows that service them, to the WebSphere Event Broker broker.
For example, the WebSphere Event Broker broker NEWBROKER shown in the previous figure must have a stream queue defined for BULLETIN.STREAM. It must also have a message flow defined and deployed to provide a publication service for that queue.
Notices |
Trademarks |
Downloads |
Library |
Support |
Feedback
![]() ![]() |
aq19800_ |