Migrating from WebSphere MQ Event Broker Version 2.1 to WebSphere Event Broker Version 6.0

Before you start

To migrate a broker domain from WebSphere MQ Event Broker Version 2.1 to WebSphere Event Broker Version 6.0:

  1. Close all Control Center sessions.
  2. On each system where one or more brokers are running, perform the following steps for each broker:
    1. Stop the broker by issuing the wmqpsstop command with the name of the broker.
    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 that 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, 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 operating system:
    • 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 Event Broker that you require. For detailed instructions on how to perform this task, see the Installation Guide.
  8. Re-create your broker domain. As part of this task, perform the following steps, using the information that you recorded previously, where appropriate:
    1. Import the message flows that you want to migrate by issuing the mqsimigratemsgflows command.
    2. Using WebSphere Event Broker commands, re-create and start the Configuration Manager, a User Name Server, and the brokers that you want to migrate.
    3. Using the workbench, add each broker to the broker domain and re-create the execution groups that were originally within the broker. Re-create only the execution groups that you want to preserve.
    4. Using the workbench, enter and deploy the assignments, topology, and topics configuration data that you want to preserve.

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

The migration is now complete and the broker domain is ready for use. Delete any queue managers that you no longer need.

Note that the migration does not preserve the subscriptions and retained publications at the brokers. To re-create this information after migration, subscribers must renew their subscriptions and publishers must republish.

Related tasks
Preparing to migrate from WebSphere MQ Event Broker Version 2.1
Configuring broker domain components
Administering the broker domain
Adding a broker to a broker domain
Adding an execution group to a broker
Deploying
Issuing commands from a program after migration
Related reference
Installation Guide
mqsimigratemsgflows command
Supported migration and upgrade paths
Configuring a publish/subscribe topology