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.
Before you start:
Read the topics in the section Migrating the Version 7.0 WebSphere Message Broker component, and the topic Using a broker with an existing high availability manager.
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
- In MSCS bring the broker resource offline, keeping the cluster disk and WebSphere MQ resource online on your primary node.
- In a WebSphere Message Broker Version 8.0 command console
run the following command:
mqsimigratecomponents BROKER1 -s 8.0 -t 7.0
- 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.
- In a WebSphere Message
Broker Version 7.0 command console
run the following command:
mqsistop BROKER1
- With the broker resource offline, move the broker cluster group to the secondary node.
- In a WebSphere Message Broker Version 8.0 command console
run the following command:
mqsimigratecomponents BROKER1 -s 7 -t 8 -1
- In a WebSphere Message Broker Version 8.0 command console
run the following command:
mqsimigratecomponents BROKER1 -s 8.0 -t 7.0 -1
- 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
- In a WebSphere Message
Broker Version 7.0 command console
run the following command:
mqsistop BROKER1
- Bring the cluster disk and WebSphere MQ resource offline.
- 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.