Migrating the tooling

Before you start
Record the following information for the broker and for the associated assignments configuration data that 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.
View this information in the workbench and record it manually.
This topic describes the first step in migrating individual components from WebSphere MQ Integrator Broker Version 2.1 to WebSphere Message Broker Version 6.0.
  1. Use the Control Center to export all Version 2.1 resources, such as message flows, message sets, and user-defined nodes.
  2. Stop WebSphere MQ Integrator Broker Version 2.1.
  3. Uninstall the Version 2.1 Control Center.
  4. Install the Version 6.0 Message Brokers Toolkit in a different location to where the Version 2.1 Message Brokers Toolkit is installed.
  5. Import all Version 2.1 message flows, message sets, and user-defined extensions into Eclipse projects using the mqsimigratemsgflows and mqsimigratemsgsets commands.

Assignments data is not migrated automatically. After migration, if you want to deploy message flows with the same pre-migration parameters, compile the migrated message flows and message sets using the Version 6.0 Message Brokers Toolkit to create broker archive (bar) files, then update any configurable parameters to match the Version 2.1 settings that you recorded before migration. See the Deployment overview topic for more information.

After you have migrated the tooling, migrate your message flows and message sets and the Configuration Manager.

Related tasks
Backing up Version 2.1 resources
Planning for migration from Version 2.1
Migrating from WebSphere MQ Integrator Broker Version 2.1 to WebSphere Message Broker Version 6.0
Migrating from Version 2.1 to Version 6.0: Version 6.0 coexisting temporarily with Version 2.1
Migrating from Version 2.1 to Version 6.0: migrating applications and runtime components
Migrating a Configuration Manager from WebSphere MQ Integrator Broker Version 2.1 to WebSphere Message Broker Version 6.0
Migrating the broker
Migrating the User Name Server
Related reference
mqsimigratemsgflows command
mqsimigratemsgsets command