This topic explains how to restore components and resources that you have migrated from Version 5.0 products back to their original state. You cannot restore components to Version 2.1 level.
Use the -s and -t parameters of the mqsimigratecomponents command to migrate components from Version 6.0 to Version 5.0. Specify Version 6.0 for the source version parameter (-s) and Version 5.0 for the target version parameter (-t). See the mqsimigratecomponents command topic for detailed information about these parameters and the format to use when specifying version numbers.
Version 5.0 and Version 5.1 Message Brokers Toolkit source files use a new format in the Version 6.0 Message Brokers Toolkit. The files are migrated to the new format when you save them using the Version 6.0 Message Brokers Toolkit. After this, you can no longer use the files with the Version 5.0 or Version 5.1 Message Brokers Toolkit. For detailed information, see Conditions for using migrated resources with previous versions of the Message Brokers Toolkit.
When you migrate a Configuration Manager from Version 5.0 to Version 6.0, the DB2 database that is associated with the Version 5.0 Configuration Manager is not modified. To restore the Configuration Manager to the Version 5.0 state, create a Version 5.0 Configuration Manager, specifying the DB2 database that is associated with the original Version 5.0 Configuration Manager. The restored Version 5.0 Configuration Manager reflects the state of the domain 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, specify the queue manager used by the Version 6.0 Configuration Manager when you create the Version 5.0 Configuration Manager. 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.
Restore a migrated broker to its Version 5.0 state by creating a Version 5.0 broker, specifying the backed-up database associated with the original Version 5.0 broker.
Broker databases are modified during migration to WebSphere Message Broker Version 6.0 when the BIP$DBM1 and BIP$DBM2 jobs are run. If you want to restore a broker that was migrated to WebSphere Message Broker Version 6.0 back to its Version 5.0 state, restore the broker database tables from backups. Broker databases used in Version 6.0 cannot be used in Version 5.0.
When you restore a broker database from backups, the Configuration Manager and the Broker Administration perspective are not updated automatically 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.
If you migrate to Version 6.0, deploy a message set to the Version 6.0 broker, then migrate back to Version 5.0, Version 5.0 is unable to recognize the message set that was deployed by Version 6.0. 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.
Notices |
Trademarks |
Downloads |
Library |
Support |
Feedback
![]() ![]() |
ah23890_ |