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

Migrating a WebSphere Message Broker Version 7.0 broker that is configured on Microsoft Cluster Services (MSCS)

You must complete a specific set of steps to migrate a broker in an MSCS cluster to WebSphere® Message Broker Version 8.0.

Use the following procedure to migrate a broker that is configured on MSCS.

Migrating from WebSphere Message Broker Version 7.0 to WebSphere Message Broker Version 8.0

  1. Install WebSphere Message Broker Version 8.0 onto each node. You must specify a new location for this installation.
  2. Stop all channels that are connected to the WebSphere Message Broker Version 7.0 broker.
  3. In MSCS bring the broker resource offline, keeping the cluster disk and WebSphere MQ resource online on your primary node
  4. In a WebSphere Message Broker Version 8.0 command console run the following command: .
    mqsimigratecomponents BROKER1
    where BROKER1 is the name of your broker
  5. With the broker resource offline, move the broker cluster group to the secondary node.
  6. In a WebSphere Message Broker Version 8.0 command console run the following command:
    mqsimigratecomponents BROKER1 -1
  7. Copy all additional custom environment settings from your previous environment into your WebSphere Message Broker Version 8.0 environment; for example: MQSI_FILENODES_ROOT_DIRECTORY.
  8. Bring the cluster disk and WebSphere MQ resource offline.
  9. Start the broker cluster group on its primary node.
Migrating from WebSphere Message Broker Version 8.0 to WebSphere Message Broker Version 7.0
  1. In MSCS bring the broker resource offline, keeping the cluster disk and WebSphere MQ resource online on your primary node.
  2. In a WebSphere Message Broker Version 8.0 command console run the following command:
    mqsimigratecomponents BROKER1 -s 8.0 -t 7.0
  3. In a WebSphere Message Broker Version 7.0 command console run the following command:
    mqsistart BROKER1

    This step is required to update the Windows service to point at the WebSphere Message Broker Version 7.0 binary files.

  4. In a WebSphere Message Broker Version 7.0 command console run the following command:
    mqsistop BROKER1
  5. With the broker resource offline, move the broker cluster group to the secondary node.
  6. In a WebSphere Message Broker Version 8.0 command console run the following command:
    mqsimigratecomponents BROKER1 -s 7 -t 8 -1
  7. In a WebSphere Message Broker Version 8.0 command console run the following command:
    mqsimigratecomponents BROKER1 -s 8.0 -t 7.0 -1
  8. In a WebSphere Message Broker Version 7.0 command console run the following command:
    mqsistart BROKER1

    This is required to update the Windows service to point at the WebSphere Message Broker Version 7.0 binary files

  9. In a WebSphere Message Broker Version 7.0 command console run the following command:
    mqsistop BROKER1
  10. Bring the cluster disk and WebSphere MQ resource offline.
  11. Start the broker cluster group on its primary node.

Note, that, because of changes in the file security model that is used in WebSphere Message Broker Version 8.0, you might need to alter the file permissions of the shared resource.

If necessary, create a domain group, add the userID of your broker to this group, and give the group full access to the shared files.

Notices | Trademarks | Downloads | Library | Support | Feedback

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

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


Task topicTask topic | Version 8.0.0.7 | bh23480_