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

Before you start

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

To migrate a broker domain from WebSphere MQ Event Broker Version 2.1 to WebSphere Business Integration Event Broker Version 5.0, do the following:

  1. Close all Control Center sessions.
  2. On each system where one or more 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 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 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, uninstall WebSphere MQ Event Broker. Follow 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. On each system, install the components of WebSphere Business Integration Event Broker that you require. For detailed instructions on how to perform this task, see:
  8. Recreate your broker domain. As part of this task, do the following using the information you recorded previously, where appropriate:
    1. Import the message flows you want to migrate by using the mqsimigratemsgflows command. For detailed instructions on how to perform this task, see Migrating a message flow.
    2. Using WebSphere Business Integration Event Broker commands, recreate and start the Configuration Manager, a User Name Server, and the brokers you want to migrate. For information about how to do this, see individual tasks in:
    3. 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:
    4. 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 delete any queue managers you no longer require.

Note that the migration does not preserve the subscriptions and retained publications at the 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
Installing on AIX
Installing on HP-UX
Installing on Solaris
Installing on Windows
Migrating a message flow
Configuring broker domain components
Administering the broker domain
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
mqsimigratemsgflows command
Supported migration and upgrade paths
Configuring a publish/subscribe topology