If you have migrated from Version 5.0 to Version 6.0, you can restore your installation to Version 5.0, subject to certain restrictions.
The following sections describe how to restore the Message Brokers Toolkit and your runtime components to Version 5.0.
If you did not create a backup of your Version 5.0 workspace, you cannot restore the Message Brokers Toolkit to this version.
Any changes that you made to resources in the Message Brokers Toolkit Version 6.0 cannot be restored to Version 5.0.
mqsimigratecomponents Broker -t 5.0.0.4
The User Name Server is unchanged between Version 5.0 and Version 6.0.
mqsimigratecomponents UserNameServer -t 5.0.0.4
When you migrate a Configuration Manager from Version 5.0 to Version 6.0, the DB2® database is neither changed nor deleted. Version 6.0 does not use DB2 for the configuration repository.
If you migrate from Version 6.0 back to Version 5.0, the original DB2 database is used again, so you must ensure that the database is available to the component. If you made any changes after migration to Version 6.0, these changes are not restored to Version 5.0. As a result, you will lose any domain changes that you made after migration to Version 6.0.
If you deployed any broker configuration changes after migration to Version 6.0, these changes are lost when you restore the Configuration Manager to Version 5.0. You must rebuild your brokers by deleting them and redeploying them to maintain a consistent state. Check carefully that your Configuration Manager works correctly before deploying for the first time after migration to Version 6.0.
If you changed the Configuration Manager queue manager during migration to Version 6.0, you must keep the new queue manager if you restore using the mqsimigratecomponents command. If the new queue manager is on an operating system other than Windows, you cannot use the mqsimigratecomponents command to restore; instead, you must restore from a backup.
mqsimigratecomponents ConfigMgr -t 5.0.0.4