Migrating a Version 5.0 broker to Version 6.0 on distributed operating systems

You can migrate a Version 5.0 broker directly to Version 6.0. However, if the lack of availability of a broker during migration is an issue, move the Version 5.0 broker's application logic onto a Version 6.0 broker. Select the topic that is appropriate to your environment.

If you are using the Version 5.1 Message Brokers Toolkit, replace all references to "Version 5.0" with "Version 5.1".

Migrating a Version 5.0 broker to Version 6.0

To migrate a Version 5.0 broker on distributed operating systems to Version 6.0 at the same location, complete the following steps:
  1. Install WebSphere Event Broker Version 6.0 in the same location as WebSphere Business Integration Event Broker Version 5.0.
  2. Stop the Version 5.0 broker.
  3. Stop any channels to the Version 5.0 broker.
  4. Update the .odbc.ini file to Version 6.0 format by following the instructions in Updating your ODBC definitions when migrating.
  5. Launch a Version 6.0 Command Console and enter the mqsimigratecomponents command to migrate your Version 5.0 components.
  6. Start the Version 6.0 broker.

Migrating a Version 5.0 broker's application logic to another installation

Before you start

To complete this task you must have either a Version 5.0 or a Version 6.0 Message Brokers Toolkit available.

To migrate a Version 5.0 broker on distributed operating systems to Version 6.0 at a different location on the same computer, or to a different computer, complete the following steps:
  1. Install WebSphere Event Broker Version 6.0 either as a new instance on the computer where WebSphere Business Integration Event Broker Version 5.0 is installed, or on a different computer. For detailed instructions, see the Installation Guide.
  2. Update the .odbc.ini file to Version 6.0 format by following the instructions in Updating your ODBC definitions when migrating.
  3. Create a Version 6.0 broker and start it. Ensure that the Version 6.0 broker's name is different from the name of the Version 5.0 broker.

    Brokers cannot share queue managers. You cannot migrate a broker to a queue manager that is already being used by an existing broker.

  4. Add the new broker to the domain by completing the following tasks:
    1. Create a Configuration Manager on Windows
    2. Create a domain connection
    3. Connect to the broker domain
    4. Add a broker to a broker domain
  5. Write a list of the execution groups that you have on the Version 5.0 broker, and create these same execution groups on the new broker. Use either the Version 5.0 or Version 6.0 Message Brokers Toolkit to do this.
  6. Deploy the message flows of the Version 5.0 broker to the Version 6.0 broker. Use either the Version 5.0 or Version 6.0 Message Brokers Toolkit to do this.
  7. Configure any other relevant properties of the Version 5.0 broker on the Version 6.0 broker. For example, you might need to configure properties that you set using the mqsichangeproperties command, or as a result of using certain nodes, such as Publication or SCADA nodes.
  8. Stop the Version 5.0 broker.
  9. Remove the Version 5.0 broker from the workbench.
  10. Redeploy the topology.
  11. Delete the Version 5.0 broker.
When you have migrated the broker, ensure that you have migrated the rest of the components: then see the post-migration tasks for information about tasks that you might want to perform after migration.
Related concepts
Brokers