For the latest details of all supported levels of hardware and software, visit the 
IBM® Integration Bus Requirements website.
- You want to migrate publish/subscribe collectives from WebSphere Message Broker Version 6.1 to WebSphere MQ queue manager clusters.
- On distributed systems, you have set up and initialized a command environment in which WebSphere MQ and WebSphere Message Broker commands can run.
- You have installed a version of WebSphere MQ that supports IBM Integration Bus and you have migrated your Version 6.1 broker's queue manager.
- You have not migrated your Version 6.1 broker to Version 9.0 and the broker's database definitions are still valid for WebSphere Message Broker Version 6.1.
- Your Version 6.1 broker is stopped.
This process is for migration only. You cannot administer new IBM Integration Bus Version 9.0 brokers or update, for example, publish/subscribe topologies, or Access Control Lists
If you inadvertently initiate the deployment of a publish/subscribe topology, any brokers that are already migrated to IBM Integration Bus Version 9.0 ignore this part of the deployment and issue a BIP2082 warning message to the system log.
If you use this mixed environment, you must use the migmbbrk command as part of the migration for each broker. For information about the migmbbrk command, see the WebSphere MQ information center.
- Remove each broker from the collective. For more information, see the WebSphere Message Broker Version 6.1 information center.
- Migrate the publish/subscribe information from each broker, as described in Migrating publish/subscribe from WebSphere Message Broker Version 6.1 to WebSphere MQ.
Next:
When you have migrated all the brokers, you can
place the brokers in a queue manager cluster. For information about
setting up a new queue manager cluster, see the WebSphere MQ Version 7.5 product documentation online
Last updated Friday, 21 July 2017