Migrating a Version 2.1 broker to Version 6.0 on distributed systems

Before you start

Before migrating a broker, ensure that you do not have any aggregations in progress. When you migrate a broker to Version 6.0 any live data being stored for aggregations in progress will be lost.

If the broker runs in a locale that is not listed in the Locales topic, check that the code page is one of the supported code pages and that the locale is set up correctly.

To migrate a Version 2.1 broker to Version 6.0 on distributed operating systems, complete the following steps:
  1. Install WebSphere Message Broker Version 6.0 in a different location from Version 2.1.
  2. Stop Version 2.1.
  3. Issue the mqsimigratecomponents command for the broker.
  4. Start of changeUpdate the .odbc.ini file to Version 6.0 format by following the instructions in Updating the ODBC.ini file.End of change
  5. Start the Version 6.0 broker.
  6. Start of changeOptional: Uninstall the Version 2.1 product.End of change
  7. Repeat these steps for all remaining brokers.

After you have migrated the broker, go to Migrating the User Name Server.

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 replacing Version 2.1
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 components on different computers
Migrating the tooling
Migrating a Configuration Manager from WebSphere MQ Integrator Broker Version 2.1 to WebSphere Message Broker Version 6.0
Migrating the User Name Server
Changing your locale on UNIX and Linux systems
Changing your locale on Windows
Related reference
mqsimigratecomponents command