Migrating a Version 2.1 broker to Version 5.0

Before you start this task, do the following:
  • Back up the database tables of the Version 2.1 broker you want to migrate. For information about how to do this, see the WebSphere MQ Integrator Broker Version 2.1 Administration Guide.
  • Record the following information for the broker, and for the associated assignments configuration data you want to preserve:
    • The name of the broker.
    • The name of each message set that is assigned to the broker.
    • The name of each execution group within the broker.
    • For each execution group within the broker, the name of each message flow that is assigned to the execution group.
    • For each message flow assigned to an execution group, the following properties:
      • Additional instances
      • Commit count
      • Commit interval
      • Coordinated transaction

    You can view this information in the workbench and record it manually.

  • The broker must run on the same system and use the same queue manager as it did before migration. You do not need to change the configuration of the queue manager, but you might need to ensure that the WebSphere MQ product code is at the required release and service level to support WebSphere Business Integration Message Broker. At the same time, you might want to ensure that you have installed the other software prerequisites. See Checking software prerequisites for the details.

When you migrate a broker domain from WebSphere MQ Integrator Broker Version 2.1 to WebSphere Business Integration Message Broker Version 5.0, you can preserve some or all of your brokers at the Version 2.1 level of code. These brokers can participate in the Version 5.0 broker domain but, at any time subsequently, you can migrate the brokers to the Version 5.0 level of code, and you can do this in stages if you wish. This topic describes how to migrate a Version 2.1 broker to the Version 5.0 level of code when the Version 2.1 broker is already participating in a Version 5.0 broker domain.

If two or more brokers run on the same UNIX or Windows system, you must migrate them all at the same time. See Coexistence with previous releases and other products for more information. If two or more brokers share the same set of database tables, you must migrate all of these brokers at the same time. If you do need to migrate multiple brokers, on the same system or on different systems, you can adapt the instructions that follow.

The information in this topic assumes that you are migrating a WebSphere MQ Integrator Broker Version 2.1 broker. The same information applies, however, if you are migrating a WebSphere MQ Integrator Version 2.1 broker. Simply replace all references to "WebSphere MQ Integrator Broker" with "WebSphere MQ Integrator" in the instructions that follow.

If you are migrating a WebSphere MQ Integrator Version 2.1 broker that is participating in a WebSphere Business Integration Message Broker with Rules and Formatter Extension Version 5.0 broker domain, replace all references to "WebSphere Business Integration Message Broker" with "WebSphere Business Integration Message Broker with Rules and Formatter Extension" in the instructions that follow. For instructions on how to migrate the New Era of Networks Rules and Formatter support for WebSphere MQ Integrator, see the New Era of Networks documentation.

To migrate a Version 2.1 broker to the Version 5.0 level of code, do the following:

  1. On the system where the broker is running, do the following:
    1. Stop the broker.

      On a UNIX or Windows system, you stop a broker by issuing the mqsistop command with the name of the broker. For information about how to use the mqsistop command, see the WebSphere MQ Integrator Broker Version 2.1 Administration Guide.

      On z/OS, you stop a broker by stopping the started task.

    2. Uninstall WebSphere MQ Integrator Broker by following the instructions in the appropriate book for your platform:
      • WebSphere MQ Integrator Broker for AIX Version 2.1 Installation Guide
      • WebSphere MQ Integrator Broker for HP-UX Version 2.1 Installation Guide
      • WebSphere MQ Integrator Broker for Solaris Version 2.1 Installation Guide
      • WebSphere MQ Integrator Broker for Windows NT and Windows 2000 Version 2.1 Installation Guide

      On a Windows system, do not select the option to uninstall WebSphere MQ Integrator Broker completely, including data.

      On z/OS, you do not need to remove the WebSphere MQ Integrator Broker product code.

    3. Install WebSphere Business Integration Message Broker. On a UNIX or Windows system, you need to install only the Broker component. For detailed instructions on how to perform this task, see:
    4. On a UNIX or Windows system, change the ODBC connection definition for each Oracle and Sybase database accessed by the broker. On AIX, also change the ODBC connection definition for each DB2 database accessed by the broker. Additionally, if a message flow running in the broker updates an Oracle or Sybase database within a global unit of work coordinated by the broker queue manager, change the XA resource manager definition for the database. To make these changes, follow the instructions in Changing the ODBC connection and XA resource manager definitions for a migrated broker.
    5. On a UNIX or Windows system, migrate the broker database tables by issuing the mqsimigratetables command with the name of the broker. If two or more brokers share the same set of database tables, you need to migrate the database tables only once. For information about how to use this command, see mqsimigratetables command. On z/OS, configure the broker by following the instructions in Configuring a migrated broker on z/OS. Configuring the broker includes migrating its database tables.
    6. Start the broker. On a UNIX or Windows system, you do this by issuing the mqsistart command with the name of the broker and, on z/OS, by starting the broker task. For detailed instructions on how to perform this task, see:
  2. On a system where the workbench runs, do the following:
    1. In the Domains view of the Broker Administration perspective, right-click the name of the broker and then click Remove Deployed Children. All the broker's execution groups, and their contents, are deleted and a new empty default execution group is created.
    2. Recreate the execution groups that were originally within the broker. Recreate only the execution groups you want to preserve. Use the information you recorded previously for this purpose. For detailed instructions on how to perform this task, see Adding an execution group to a broker.
    3. For each execution group that was originally within the broker, prepare a broker archive (bar) file. The bar file must contain the following:
      • The message flows that were originally assigned to the execution group
      • The message sets that were originally assigned to the broker
      For each assigned message flow, set the following properties:
      • Additional instances
      • Commit count
      • Commit interval
      • Coordinated transaction

      Recreate only the assignments configuration data you want to preserve. Use the information you recorded previously to prepare the broker archive file. When the broker archive file is ready, deploy it to the broker.

      For detailed instructions on how to perform this task, see Deploying message flow applications.

      Deploy migrated message flows and message sets 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 is ready for use.

Related concepts
Coexistence with previous releases and other products

Related tasks
Installing on AIX
Installing on HP-UX
Installing on Solaris
Installing on Windows
Installing on z/OS
Changing the ODBC connection and XA resource manager definitions for a migrated broker
Configuring a migrated broker on z/OS
Starting and stopping a broker on UNIX platforms
Starting and stopping a broker on Windows
Starting the broker
Adding an execution group to a broker
Deploying message flow applications
Deploying a topology configuration
Deploying a topics hierarchy

Related reference
mqsimigratetables command
mqsistart command