If you already have an WebSphere MQ Publish/Subscribe broker network, you can continue to use this network unchanged. The introduction of WebSphere Event Broker Version 6.0 to your environment, and the creation of brokers in that broker domain, does not affect your WebSphere MQ Publish/Subscribe broker domain until you take specific action to connect the two networks.
If you want to run in this mode with two separate, independent networks, you do not have to take any specific actions. You can retain your existing WebSphere MQ Publish/Subscribe network, and install and configure a WebSphere Event Broker Version 6.0 network, without any interaction.
Your existing applications can continue to work unchanged. However, there can be no interchange of publications in this scenario.
You must be aware that a single queue manager cannot support both a WebSphere MQ Publish/Subscribe broker and a WebSphere Event Broker Version 6.0 broker. If you have brokers of both types on the same system, each broker must have its own dedicated queue manager.
You can implement this scenario while you assess the new product and the extra functions contained within the publish/subscribe support. It also lets you plan for the extent of integration or migration, or both, that you require, without affecting your current environment.
However, you must ensure that you have the required level of WebSphere MQ for your WebSphere MQ Publish/Subscribe system. WebSphere Event Broker Version 6.0 requires WebSphere MQ to be at least Version 5.3.
Notices |
Trademarks |
Downloads |
Library |
Support |
Feedback
![]() ![]() |
aq18590_ |