Restoring components and resources to Version 5.0

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.

Restrictions
  • Source files in Message Brokers Toolkit Version 6.0 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 Brokers Toolkit Version 6.0. After you have saved them, you can no longer use the resources in 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.
  • When you have restored a broker, you must redeploy the BAR files that you had previously deployed at Version 6.0. If you do not redeploy, the deployed resources are not compatible with the Version 5.0 broker, and errors are generated when you restart the broker; always check logs to search for errors or warnings about message flows that the broker cannot start.
Restoring resources to Version 5.0

The following sections describe how to restore the Message Brokers Toolkit and your runtime components to Version 5.0.

Restoring the Message Brokers Toolkit to Version 5.0
To restore the Message Brokers Toolkit to Version 5.0:
  1. Stop the Message Brokers Toolkit Version 6.0.
  2. Restore the Version 5.0 workspace from the backup that you took before migration.

    If you did not create a backup of your Version 5.0 workspace, you cannot restore the Message Brokers Toolkit to this version.

  3. Restart Message Brokers Toolkit Version 5.0 with your Version 5.0 workspace.

Any changes that you made to resources in the Message Brokers Toolkit Version 6.0 cannot be restored to Version 5.0.

Restoring runtime components to Version 5.0
Use the -s and -t parameters of the mqsimigratecomponents command to restore components from Version 6.0 to Version 5.0.
  • Specify the installed level of Version 6.0 for the source version parameter (-s), for example 6.0.0.2 for Version 6.0, Fix Pack 2, or allow this to take the default value.
  • Specify the appropriate level of Version 5.0 for the target version parameter (-t), for example 5.0.0.8 for Version 5.0, Fix Pack 8.
See the mqsimigratecomponents command for detailed information about these parameters and the format to use when specifying version numbers.
z/OS platform To restore z/OS® runtime components to Version 5.0:
  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 5.0 backup that you took before migration.
Restoring a broker to Version 5.0
To restore a migrated broker to its Version 5.0 state:
  1. Stop the Version 6.0 broker.
  2. Restore the broker to Version 5.0 using the mqsimigratecomponents command, as shown in the following example:
    mqsimigratecomponents Broker -t 5.0.0.4
  3. Reverse the changes that you made to the ODBC definitions when you migrated to Version 6.0.
    • UNIX platform On Linux and UNIX®, reset the ODBCINI environment variable to point to the previous version of the odbc.ini file.
    • Windows platform On Windows®, use the Control Panel to adjust the ODBC settings.
  4. Restart the broker using a Version 5.0 command window.
Restoring a User Name Server to Version 5.0

The User Name Server is unchanged between Version 5.0 and Version 6.0.

If you choose to restore a User Name Server to Version 5.0, issue the mqsimigratecomponents command, as shown in the following example:
mqsimigratecomponents UserNameServer -t 5.0.0.4
Restoring a Configuration Manager to Version 5.0

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.

The following example shows the command used to restore the Configuration Manager to Version 5.0 state on a Windows system:
mqsimigratecomponents ConfigMgr -t 5.0.0.4
Related concepts
Conditions for using migrated resources with previous versions of the Message Brokers Toolkit
Related tasks
Migrating and upgrading
Backing up WebSphere Business Integration Event Broker Version 5.0 resources
Uninstalling
Related reference
mqsimigratecomponents command
Notices | Trademarks | Downloads | Library | Support | Feedback

Copyright IBM Corporation 1999, 2009Copyright IBM Corporation 1999, 2009. All Rights Reserved.
Last updated : 2009-01-07 15:40:36

ah23891_