Migrate a Version 5.0 Configuration Manager to Version 6.0 on the same system.
Before you start
Read about Coexistence with previous versions and other products.
If the Configuration Manager runs in a locale that is not listed in the Locales topic, check that the code page is one of the supported code pages and that the locale is set up correctly.
If you do not have additional hardware available, but you want to confirm the successful migration of the Configuration Manager before you remove the Version 5.0 Configuration Manager, migrate the Configuration Manager to a different location on the same computer. If you use this method, you can also change the name of the Configuration Manager.
You must specify a different name and a different queue manager name for the Version 6.0 Configuration Manager.
Use the -n parameter of the mqsicreateconfigmgr command to specify the Version 5.0 Configuration Manager database. This option initializes the Version 6.0 Configuration Manager with the domain configuration details from the Version 5.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 Message Brokers Toolkit Version 6.0. To resolve these problems, configure access control lists for users who are running the Message Brokers Toolkit Version 6.0. Follow the instructions in Considering security for the workbench.
When you have completed these tasks, see the post-migration tasks for information about tasks that you might want to perform after migration.