This topic explains how you can restore components and resources that you migrated from Version 2.1 or Version 5.0 products to WebSphere Business Integration Message Broker Version 6.0 back to their Version 2.1 or Version 5.0 state.
Message Brokers Toolkit Version 5.0 and Version 5.1 source files use a new format in Message Brokers Toolkit Version 6.0. The files are migrated to the new format when you save them using Message Brokers Toolkit Version 6.0. After this, you can no longer use the files with Message Brokers Toolkit Version 5.0 or Version 5.1. For detailed information, see Conditions for using migrated resources with previous versions of the Message Brokers Toolkit.
This means that if you want to return to using such files in Message Brokers Toolkit Version 5.0 or Version 5.1, this is possible only if the files have not been saved using Message Brokers Toolkit Version 6.0. If you backed up the files before you saved them in Message Brokers Toolkit Version 6.0, you can revert to using the backed up versions of the files.
When you migrate a Configuration Manager from Version 5.0 to Version 6.0, the DB2 database associated with the Version 5.0 Configuration Manager is not modified. To restore the Configuration Manager to the Version 5.0 state, you create a Version 5.0 Configuration Manager specifying the DB2 database associated with the original Version 5.0 Configuration Manager. The restored Version 5.0 Configuration Manager reflects the state the domain was in when you migrated the Version 5.0 Configuration Manager to Version 6.0.
If during migration from Version 5.0 to Version 6.0 you changed the queue manager on which the Configuration Manager runs, you must create the Version 5.0 Configuration Manager specifying the queue manager used by the Version 6.0 Configuration Manager. When you change the queue manager during migration, the brokers in the domain are associated with the Version 6.0 Configuration Manager, and it is not possible to re-associate brokers with a Version 5.0 Configuration Manager. Creating the Version 5.0 Configuration Manager on the queue manager used by the Version 6.0 Configuration Manager also means that you need to structure the WebSphere MQ network.
You can restore a migrated broker to its Version 5.0 state by creating a Version 5.0 broker specifying the backed up database associated with original Version 5.0 broker.
Broker databases are modified during migration to WebSphere Business Integration Message Broker Version 6.0 when the mqsimigratetables command or the BIP$DBM1 and BIP$DBM2 jobs are run. If you want to restore a broker that was migrated to WebSphere Business Integration Message Broker Version 6.0 back to its Version 5.0 state, you need to restore the broker database tables from backups. Broker databases used in WebSphere Business Integration Message Broker Version 6.0 cannot be used in WebSphere Business Integration Message Broker Version 5.0.
When you restore a broker database from backups, the Configuration Manager and the Broker Administration perspective are not automatically updated to reflect the restored state of the broker. This is because the broker does not reveal its set of deployed resources to the Configuration Manager. As a result, you might want to delete any message flows that have been deployed after the initial migration so that their status is no longer reported and options to manipulate them are no longer displayed in the Broker Administration perspective.
[LINKS TO UNINSTALLING, AND UNINSTALLING SERVICE, AND TO BACKING UP V2.1 RESOURCES]
Notices |
Trademarks |
Downloads |
Library |
Support |
Feedback
![]() ![]() |
ah23890_ |