Planning for migration

If you are already using WebSphere MQ Publish/Subscribe, you can migrate your applications to use the publish/subscribe functions provided by WebSphere Event Broker.

You can also migrate individual WebSphere MQ Publish/Subscribe brokers to create replacement WebSphere Event 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 Event Broker subscribers. This includes messages originating in environments not yet supported by WebSphere Event Broker.
  • Message flows can be created and deployed on WebSphere Event 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 Event Broker and WebSphere MQ Publish/Subscribe clients.

There are three possible scenarios for exploiting the two networks:

  1. You can choose to have two independent broker networks, and therefore have two separate broker domains for publish/subscribe applications. See Running two independent broker networks.
  2. You can connect the two networks to allow publications and subscriptions to flow throughout the integrated network. Further details are provided in Creating and operating a heterogeneous network.
  3. You can selectively and gradually migrate individual brokers from WebSphere MQ Publish/Subscribe to WebSphere Event Broker. For more guidance on this option, see Migrating WebSphere MQ brokers and Migrating a WebSphere MQ broker network.

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.