You can integrate your existing WebSphere MQ Publish/Subscribe broker network with a WebSphere Message Broker broker network to create a mixed, heterogeneous network. This enables publications and subscriptions to be propagated through one logical network, made up of two or more physical networks. As a result, subscribers to the WebSphere MQ Publish/Subscribe brokers can target information being published to the WebSphere Message Broker broker network, and subscribers to the WebSphere Message Broker brokers can target information being published to the WebSphere MQ Publish/Subscribe broker network.
In a heterogeneous network, any new stream that is created for a WebSphere MQ Publish/Subscribe broker is supported by any WebSphere MQ Publish/Subscribe brokers that are connected to it. However, the new stream is not supported by WebSphere MQ Publish/Subscribe brokers that are separated by a WebSphere Message Broker broker from the WebSphere MQ Publish/Subscribe broker where the new stream was created.
WebSphere MQ Publish/Subscribe brokers and WebSphere Message Broker brokers can be running on Windows or other platforms.
There are two ways in which a WebSphere Message Broker broker can be joined to the WebSphere MQ Publish/Subscribe network; it can be joined either as a leaf node (that is, as a child of an existing WebSphere MQ Publish/Subscribe broker) or as a parent node (that is, as the parent of an existing WebSphere MQ Publish/Subscribe broker).
This queue supports the default publication stream. You must create this queue on every broker. You must also create and deploy a message flow that services this stream queue.
This queue is used by the broker to communicate with neighboring WebSphere MQ Publish/Subscribe brokers. You must create this queue on every broker, however the message flow for this queue is created internally by the broker.
Notices |
Trademarks |
Downloads |
Library |
Support |
Feedback
![]() ![]() |
aq18600_ |