Migrating from WebSphere MQ Event Broker Version 2.1 and WebSphere MQ Integrator Broker Version 2.1 to WebSphere Message Broker Version 6.0

Before you start

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. 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 Message Broker Version 6.0 broker domain, perform the following steps:

  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, 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 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 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. Migrate the WebSphere MQ Integrator Broker broker domain to a WebSphere Message Broker broker domain by following the instructions in Migrating from WebSphere MQ Integrator Broker Version 2.1 to WebSphere Message Broker Version 6.0.

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

  8. Within the WebSphere Message Broker broker domain, re-create 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 Message Broker commands, re-create and start the brokers that you want to migrate.
    2. 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.
    3. 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. Drop any databases and delete any queue managers that you no longer need.

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

Related concepts
Conditions for a Version 2.1 broker participating in a Version 6.0 broker domain
Related tasks
Preparing to migrate from WebSphere MQ Event Broker Version 2.1
Migrating from WebSphere MQ Integrator Broker Version 2.1 to WebSphere Message Broker Version 6.0
Creating a broker
Starting and stopping a broker
Adding a broker to a broker domain
Adding an execution group to a broker
Deploying
Issuing commands from a program after migration
Related reference
Supported migration and upgrade paths
Configuring a publish/subscribe topology