Migrating from WebSphere MQ Event Broker Version 2.1 and WebSphere MQ Integrator Broker Version 2.1 to WebSphere Business Integration Message Broker Version 5.0

Before you start

Before you start this task, you must complete the task:

WebSphere MQ Event Broker and WebSphere MQ Integrator Broker might be installed on the same system, or there might be no system in the two domains on which both products are installed. You can use the procedure that follows in either case.

To migrate a WebSphere MQ Event Broker Version 2.1 broker domain and a WebSphere MQ Integrator Broker Version 2.1 broker domain into a single WebSphere Business Integration Message Broker Version 5.0 broker domain, do the following:

  1. Close all Control Center sessions for the WebSphere MQ Event Broker broker domain.
  2. On each system where one or more WebSphere MQ Event Broker brokers are running, do the following for each broker:
    1. Stop the broker by issuing the wmqpsstop command with the name of the broker.

      For information about how to use this and other WebSphere MQ Event Broker commands, see the WebSphere MQ Event Broker Version 2.1 Administration Guide.

    2. Delete the broker by issuing the wmqpsdeletebroker command with the name of the broker.
  3. Drop the database tables that were used by the brokers you have just deleted. If a set of broker database tables are in a database by themselves and you do not intend to use the database after migration, you can drop the whole database.

    The broker database tables are listed in the WebSphere MQ Event Broker Version 2.1 Administration Guide.

  4. On the system where the WebSphere MQ Event Broker Configuration Manager is running:
    1. Stop the Configuration Manager by issuing the wmqpsstop command for the component ConfigMgr.
    2. Delete the Configuration Manager by issuing the wmqpsdeleteconfigmgr command with the -n parameter. Using this parameter causes the configuration repository to be deleted.
  5. On a system where a WebSphere MQ Event Broker User Name Server is running:
    1. Stop the User Name Server by issuing the wmqpsstop command for the component UserNameServer.
    2. Delete the User Name Server by issuing the wmqpsdeleteusernameserver command.
  6. On each system where WebSphere MQ Event Broker is installed, uninstall WebSphere MQ Event Broker by following the instructions in the appropriate book for your platform:
    • WebSphere MQ Event Broker for AIX Version 2.1 Installation Guide
    • WebSphere MQ Event Broker for HP-UX Version 2.1 Installation Guide
    • WebSphere MQ Event Broker for Solaris Version 2.1 Installation Guide
    • WebSphere MQ Event Broker for Windows NT and Windows 2000 Version 2.1 Installation Guide

    On a Windows system, select the option to uninstall including data.

  7. Migrate the WebSphere MQ Integrator Broker broker domain to a WebSphere Business Integration Message Broker broker domain by following the instructions in Migrating from WebSphere MQ Integrator Broker Version 2.1 to WebSphere Business Integration Message Broker Version 5.0.

    At the point where you import the message flows that you exported from the WebSphere MQ Integrator Broker broker domain, import also the message flows that you exported from the WebSphere MQ Event Broker broker domain.

  8. Within the WebSphere Business Integration Message Broker broker domain, recreate those aspects of the WebSphere MQ Event Broker broker domain that you want to migrate. Use the information you recorded previously, where appropriate.
    1. Using WebSphere Business Integration Message Broker commands, recreate and start the brokers you want to migrate. For information about how to do this, see:
    2. Using the workbench, add each broker to the broker domain and recreate the execution groups that were originally within the broker. Recreate only the execution groups you want to preserve. For information about how to do this, see:
    3. Using the workbench, enter and deploy the assignments, topology, and topics configuration data you want to preserve. For information about how to do this, see individual tasks in:

      Deploy migrated message flows to a test environment first of all. When you are sure that they are working correctly, you can then deploy them to a production environment.

The migration is now complete and the broker domain is ready for use. You can drop any databases, and delete any queue managers, you no longer require.

Note that the migration does not preserve the subscriptions and retained publications at the WebSphere MQ Event Broker brokers. To recreate this information after migration, subscribers must renew their subscriptions and publishers must republish.

Related concepts
Coexistence with previous releases and other products
Related tasks
Preparing to migrate from WebSphere MQ Event Broker Version 2.1
Migrating from WebSphere MQ Integrator Broker Version 2.1 to WebSphere Business Integration Message Broker Version 5.0
Creating a broker
Starting and stopping a broker
Adding a broker to a broker domain
Adding an execution group to a broker
Deploying message flow applications
Issuing commands from a program after migration
Related reference
Supported migration and upgrade paths
Configuring a publish/subscribe topology