Restore components and resources that you have migrated from Version 5.0 products back to their original state.
If you have migrated from Version 5.0 to Version 6.1, you can restore your installation to Version 5.0, subject to the following restrictions and procedures.
When you revert a broker from Version 6.1 to Version 5.0, message sets are deleted, therefore you must redeploy them. You are reminded to do this by warning message BIP8688, which appears when you run the mqsimigratecomponents command.
After migration to Version 6.1, if you have deployed any message flows that use new Version 6.1 functions, such as new nodes or new ESQL syntax, those message flows will not start if your broker is reverted to Version 5.0. Other message flows in your broker that do not use new functions will continue to run.
Source files in Message Broker Toolkit Version 6.1 are maintained in a different format to that used in Version 5.0 and Version 5.1. The files are migrated to the new format when you save them using the Message Broker ToolkitVersion 6.1. After you have saved them, you can no longer use the resources in Message Broker ToolkitVersion 5.0 or Version 5.1.
If you have created message flows in Version 6.1, you cannot revert them to Version 5.0. For detailed information, see Conditions for using migrated resources with previous versions of the Message Broker Toolkit.
The following sections describe how to restore the Message Broker Toolkit and your runtime components to Version 5.0.
Any changes that you made in Message Broker ToolkitVersion 6.1 cannot be restored to Version 5.0.
Use the -s and -t parameters of the mqsimigratecomponents command to migrate components from Version 6.1 to Version 5.0. Specify Version 6.1 for the source version parameter (-s) and Version 5.0 for the target version parameter (-t). See the mqsimigratecomponents command for detailed information about these parameters and the format to use when specifying version numbers.
mqsimigratecomponents Broker -t 5.0.0.4Warning message BIP8688 might be displayed, warning you to redeploy your message sets.
If you migrate to Version 6.1, deploy a message set to the Version 6.1 broker, and then migrate back to Version 5.0, Version 5.0 is unable to recognize the message set that was deployed by Version 6.1. In this case, any message sets that Version 5.0 is unable to use are deleted and a warning message is displayed for each message set, prompting you to redeploy it to Version 5.0 following successful migration.
mqsimigratecomponents UserNameServer -t 5.0.0.4
When you migrate a Configuration Manager from Version 5.0 to Version 6.1, the DB2 database is neither changed nor deleted. Version 6.1 does not use DB2 to store data.
If you migrate from Version 6.1 back to Version 5.0, the original DB2 database is used again, and if you made any changes after migration to Version 6.1, these changes are not reverted to Version 5.0. As a result, you will lose any domain changes that you made after migration to Version 6.1.
If you deployed any broker configuration changes after migration to Version 6.1, 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 in order to maintain a consistent state. Check carefully that your Configuration Manager works correctly before deploying for the first time after migration to Version 6.1.
If you changed the Configuration Manager's queue manager during migration to Version 6.1, 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