WebSphere Message Broker, Version 8.0.0.7 Operating Systems: AIX, HP-Itanium, Linux, Solaris, Windows, z/OS

See information about the latest product version

Performing parallel broker migration for a Version 7.0 broker

Parallel broker migration allows a staged migration process by creating a new Version 8.0 broker to run in parallel with your existing Version 7.0 broker, to which you can migrate your application logic.

Before you start:

For the latest details of all supported levels of hardware and software, visit the WebSphere® Message Broker Requirements website.

Migrating application logic to a Version 8.0 broker

To migrate application logic from a Version 7.0 broker on a distributed operating system to a different Version 8.0 broker on the same computer, or on a different computer, complete the following steps:
  1. Install WebSphere Message Broker Version 8.0 on the same computer as Version 7.0, or on a different computer. Install at least the Broker component; other components are optional. If you are installing on the same computer, you must specify a different location.
  2. Optional: If your message flows access databases by using ODBC connections, update the ODBC definitions to Version 8.0 format by following the instructions in Updating ODBC definitions when migrating.
  3. Set up the correct Version 8.0 command environment:
    • Linux platformUNIX platformOn Linux and UNIX systems, open a new shell and run the environment profile mqsiprofile for this Version 8.0 installation.
    • Windows platformOn Windows, click Start, and open the Command Console that is associated with this Version 8.0 installation.

      On Windows 7 and Windows Server 2008 systems, you must open a command console with elevated privileges. To open a command console with elevated privileges, use the mqsicommandconsole command. For more information, see mqsicommandconsole command.

  4. Create a Version 8.0 broker by using the mqsicreatebroker command; give it a name and a queue manager name that are different from the names of the Version 7.0 broker and queue manager. If you installed one or both of these components on this computer, you can also create a local broker by using the WebSphere Message Broker Explorer or the WebSphere Message Broker Toolkit.
  5. Start the Version 8.0 broker by using the mqsistart command. If you installed one or both of these components on this computer, you can also start a local broker by using the WebSphere Message Broker Explorer or the WebSphere Message Broker Toolkit.
  6. Write a list of the execution groups that you have on the Version 7.0 broker, and create these same execution groups on the Version 8.0 broker. Use the WebSphere Message Broker Explorer, the WebSphere Message Broker Toolkit Version 8.0, or the mqsicreateexecutiongroup command to complete this step. On the AIX®, Linux on x86-64, and Solaris on SPARC platforms, you can create only 64-bit execution groups.
  7. Deploy the message flows and message sets that are in use by the Version 7.0 broker to the Version 8.0 broker from the WebSphere Message Broker Toolkit Version 8.0. You cannot complete this step unless you migrated the WebSphere Message Broker Toolkit resources, as described in Migrating development resources to WebSphere Message Broker Toolkit Version 8.0.
  8. Configure all other relevant properties of the Version 7.0 broker on the Version 8.0 broker.
  9. If you want to delete your Version 7.0 broker, complete the following steps:
    1. In a Version 7.0 command environment, stop the Version 7.0 broker by using the mqsistop command.
    2. Remove the Version 7.0 broker from the Version 7.0 WebSphere Message Broker Toolkit.
    3. In a Version 7.0 command environment, delete the Version 7.0 broker by using the mqsideletebroker command.

When you have completed migration, see the tasks in Perform post-migration tasks for information about tasks that you might want to complete after migration.

Notices | Trademarks | Downloads | Library | Support | Feedback

Copyright IBM Corporation 1999, 2016Copyright IBM Corporation 1999, 2016.

        
        Last updated:
        
        Last updated: 2016-05-23 14:48:08


Task topicTask topic | Version 8.0.0.7 | bh19460_