This topic describes one of three ways to migrate
a Version 5.0 Configuration Manager to Version 6.0.
Before you start
To
complete this task you must have either a Version 5.0 or
a Version 6.0 broker available. Read about Coexistence with previous versions and other products.
If the lack of availability of a Configuration Manager during
migration is an issue, or if you do not have additional hardware available,
migrate the Configuration Manager to a different location
on the same computer. Complete the following steps:
- Install WebSphere
Message Broker Version
6.0 in a location
other than where WebSphere
Business Integration Message Broker Version 5.0 is installed.
- Stop the Version 5.0 Configuration Manager.
- Stop any channels to the Version 5.0 broker.
- Use the mqsimigratecomponents command
to migrate your Version 5.0 components.
- Start the Version 6.0 Configuration Manager.
If you have configured MCA users on the WebSphere MQ channels to the Configuration Manager,
you might encounter problems when you try to connect to the migrated Configuration Manager from
the Version 6.0 Message Brokers Toolkit.
To resolve this, configure access control lists (ACLs) for users who are running
the Version 6.0 Message Brokers Toolkit.
Follow the instructions in Considering security for the workbench.
When
you have migrated the
Configuration Manager, 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.