If you are already using WebSphere MQ Publish/Subscribe,
you can migrate your applications to use the publish/subscribe functions
provided by WebSphere Message Broker.
You can also
migrate individual WebSphere MQ Publish/Subscribe brokers to create
replacement WebSphere Message Broker brokers, with support
for their client applications remaining intact.
These two possibilities
offer you a number of advantages:
- Publications from within the WebSphere MQ Publish/Subscribe network
can be targeted by WebSphere Message Broker subscribers.
This includes messages originating in environments not yet supported by WebSphere Message Broker.
- Message flows can be created and deployed on WebSphere Message Broker brokers
to:
- Analyze the information that is flowing around your enterprise.
- Create and execute additional business logic dependent upon
the content of the publications.
- Consolidate the information within your enterprise in the form of new
publications, that can then be republished as a series of additional topics
available to both WebSphere Message Broker and WebSphere MQ Publish/Subscribe clients.
There are three possible scenarios for exploiting the two networks:
Before you can make this choice, and create your migration plan,
you must be aware of the differences between the two products. These differences
are described in WebSphere MQ Publish/Subscribe.