Network Deployment (Distributed operating systems), v8.0 > Applications > Messaging resources > Interoperation with WebSphere MQ > Interoperation using a WebSphere MQ link
Publish/subscribe messaging through a WebSphere MQ link
Overview
On a WebSphere MQ link, you can set up publish/subscribe messaging between WAS and...
- WebSphere MQ publish/subscribe function
- WebSphere Message Broker
- WebSphere Event Broker
The following products provide publish/subscribe capability for use with WAS over a WebSphere MQ link:
WebSphere MQ v7 Provides publish/subscribe function that is integrated into WebSphere MQ queue managers. This capability is called integrated publish/subscribe. The publish/subscribe capability for earlier versions of WebSphere MQ is called queued publish/subscribe, because you communicate with a separate publish/subscribe broker by means of messages placed on queues. WebSphere Message Broker v6 Provides a separate publish/subscribe broker for queued publish/subscribe. This version of queued publish/subscribe uses MQRFH2 message headers. If you are using WebSphere MQ v6, you can use WebSphere Message Broker v6 to provide publish/subscribe function that interoperates over a WebSphere MQ link with WAS. From WebSphere Message Broker v7, this product no longer provides a separate publish/subscribe broker, and all topic-based publish/subscribe operations made through the product use WebSphere MQ facilities. WebSphere Event Broker Provides a separate publish/subscribe broker for queued publish/subscribe. This version of queued publish/subscribe is the same as that in WebSphere Message Broker v6. WebSphere MQ v6 (except v6 of WebSphere MQ for z/OS) provides queued publish/subscribe that is implemented by a publish/subscribe broker within WebSphere MQ. However, the publish/subscribe function provided by WebSphere MQ v6 uses MQRFH message headers, also known as MQRFH1 message headers, and it does not support the MQRFH2 message headers that the WAS publish/subscribe bridge uses on the WebSphere MQ link. For WebSphere MQ v6 publish/subscribe to interoperate with WAS publish/subscribe over a WebSphere MQ link, use a separate message broker product that supports MQRFH2 message headers. Alternatively, instead of using a WebSphere MQ link, you can interoperate using the WebSphere MQ messaging provider, so that the applications use WebSphere MQ publish/subscribe function and do not use the service integration bus. This requirement also applies to earlier versions of WebSphere MQ where publish/subscribe function is provided by SupportPac MA0C.
Message headers and contents are mapped in the same way for both point-to-point messages and publish/subscribe messages. Message exchange through a WebSphere MQ link
Bus topology that links to WebSphere MQ networks
How service integration converts messages to and from WebSphere MQ format
Introduction to the WebSphere Message Broker global cache
Related
Information centers Publish/subscribe broker profiles [Settings]
Broker profile subscriptions [Collection]