Start of change
WebSphere Message Brokers
File: ah61110_
Writer: Kate Hostler

Task topic

This build: July 31, 2007 21:30:51

Restoring components and resources to Version 6.0

Restore components and resources that you have migrated from Version 6.0 products to their original state.

If you have migrated from WebSphere® Message Broker Version 6.0 to Version 6.1, you can restore your installation to Version 6.0, subject to the following restrictions and procedures.

When you use the mqsimigratecomponents command, you must be logged in to a Version 6.1 environment.

See the mqsimigratecomponents command description for usage information and details of parameters and the format to use when specifying version numbers.

Restrictions
When you revert a broker from Version 6.1 to Version 6.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 6.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 6.0. The files are migrated to the new format when you save them using the Message Broker Toolkit Version 6.1. After you have saved them, you can no longer use the resources in Message Broker ToolkitVersion 6.0.

If you have created message flows in Version 6.1, you cannot revert them to Version 6.0. For detailed information, see Conditions for using migrated resources with previous versions of the Message Broker Toolkit.

Migrating resources back to Version 6.0
The following sections describe how to restore the Message Broker Toolkit and your runtime components to Version 6.0.
Restoring the Message Broker Toolkit to Version 6.0
To restore the Message Broker Toolkit to Version 6.0, perform the following steps:
  1. Stop the Message Broker Toolkit Version 6.1.
  2. Restore the Version 6.0 workspace from the backup that you took before migration.

    Ensure that the workspace directories include the .metadata directory, which contains information that is specific to the release of Eclipse on which the toolkit is based.

  3. Restart Message Broker Toolkit Version 6.0.

Any changes that you made in Message Broker Toolkit Version 6.1 cannot be restored to Version 6.0.

Restoring runtime components to Version 6.0
Use the -s and -t parameters of the mqsimigratecomponents command to migrate components from Version 6.1 to Version 6.0. Specify the appropriate release of Version 6.0 for the target version parameter (-t). Specify Version 6.1 for the source version parameter (-s), or allow this to take the default value.
Restoring components on z/OS®
To revert z/OS runtime components to Version 6.0, perform the following steps:
  1. Submit the BIPMGCMP job to call the mqsimigratecomponents command, specifying the -s and -t parameters as described above.
  2. Replace the started task JCL in USER.PROCLIB with the Version 6.0 copy that you backed up.
Reverting a broker on distributed systems
To revert a migrated broker to its Version 6.0 state, perform the following steps:
  1. Stop the Version 6.1 broker.
  2. Revert the broker to Version 6.0 using the mqsimigratecomponents command, as shown in the following example:
    mqsimigratecomponents Broker -t 6.0.0.4
    Message BIP8688 might be displayed, warning you to redeploy your message sets.
  3. Reverse the changes that you made to the ODBC definitions when you migrated to Version 6.1.
    • On UNIX, reset the ODBCINI environment variable to point to the previous version of the odbc.ini file.
    • On Windows, use the Control Panel to adjust the ODBC settings.
  4. Restart the broker using a Version 6.0 command window.

If you migrate to Version 6.1, deploy a message set to the Version 6.1 broker, and then migrate back to Version 6.0, Version 6.0 is unable to recognize the message set that was deployed by Version 6.1. In this case, any message sets that Version 6.0 is unable to use are deleted and a warning message is displayed for each message set, prompting you to redeploy it to Version 6.0 following successful migration.

Restoring a Configuration Manager on distributed systems
If you changed its queue manager when you migrated the Configuration Manager, you must keep the new queue manager if you restore using the mqsimigratecomponents command.
To revert a migrated Configuration Manager to its Version 6.0 state, perform the following steps:
  1. Stop the Version 6.1 Configuration Manager.
  2. Revert the Configuration Manager to Version 6.0 using the mqsimigratecomponents command, as shown in the following example:
    mqsimigratecomponents ConfigMgr -t 6.0.0.4
  3. Restart the Configuration Manager using a Version 6.0 command window.
Restoring a User Name Server on distributed systems
The User Name Server is unchanged between Version 6.0 and Version 6.1, therefore you do not have to revert this component.
To restore a User Name Server to Version 6.0, issue the mqsimigratecomponents command, as shown in the following example:
mqsimigratecomponents UserNameServer -t 6.0.0.4
Related concepts
Conditions for using migrated resources with previous versions of the Message Broker Toolkit
Related tasks
Migrating and upgrading
Backing up WebSphere Message Broker Version 6.0 resources
Uninstalling
Related reference
mqsimigratecomponents command
Notices | Trademarks | Downloads | Library | Support | Feedback

Copyright IBM Corporation 1999, 2007Copyright IBM Corporation 1999, 2007. All Rights Reserved.
This build: July 31, 2007 21:30:51

ah61110_ This topic's URL is:
End of change