See information about the latest product version
Restoring components and resources to Version 6.1
Restore components and resources that you have migrated from Version 6.1 products to their original state.
If you have migrated from WebSphere® Message Broker Version 6.1 to Version 8.0, you can restore your installation to Version 6.1, subject to the following restrictions and procedures.
You can only restore brokers to the state they were in before you migrated them; changes that you have made to them after migration, such as updated properties, are lost.
You might want to restore components if you encounter a problem after you have migrated your brokers to Version 8.0. For example, if a message flow does not work as expected in Version 8.0, restore that broker until you can resolve the problem.
You can restore brokers to a previous version only if they were migrated from that version originally. You cannot create a new Version 8.0 broker, then restore it to a previous level. Nor can you create a Version 6.1 broker, migrate it to Version 8.0, then restore it to Version 7.0.
Because you do not migrate Configuration Manager or User Name Server components, you do not have to restore these. If you have not deleted them, they retain their existing configuration, and can be reused with brokers that you restore to a previous version.
When you use the mqsimigratecomponents command, you must be logged in to a Version 8.0 command environment.
See the mqsimigratecomponents command description for usage information and details of parameters and the format to use when specifying version numbers.
- Restrictions
Source files in the WebSphere Message Broker Toolkit Version 8.0 are maintained in a different format from that used in Version 6.1. The files are migrated to the new format when you save them in the WebSphere Message Broker Toolkit Version 8.0. After you have saved them, you can no longer use the resources with the WebSphere Message Broker Toolkit Version 6.1.
In Version 8.0, you can write CMP applications to modify message flows. You can use message flow files from Version 6.1 in these applications. When you save message flow files in a Version 8.0 CMP application, these files are stored in Version 8.0 format and cannot be used with earlier versions of the.WebSphere Message Broker Toolkit
Changes that you made to brokers after migration to Version 8.0 are not retained when you restore your resources back to Version 6.1.
- Migrating resources back to Version 6.1
- The following sections describe how to restore the WebSphere Message Broker Toolkit and your brokers to Version
6.1. You can reuse your original Version
6.1 Configuration Manager and User
Name Server components with the brokers that
you restore to Version
6.1.
- Restoring the WebSphere Message Broker Toolkit to Version 6.1
- Close all WebSphere Message Broker Toolkit Version 8.0 sessions.
- Restore the Version
6.1 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.
- Restart WebSphere Message Broker Toolkit Version 6.1.
- Restoring brokers to Version 6.1
- Use the -s and -t parameters
of the mqsimigratecomponents command
to migrate brokers from Version
8.0 to Version
6.1.
- Specify the installed level of Version 8.0 for the source version parameter (-s), for example 8.0.0.0 for the GA (general availability) level, or allow this to take the default value.
- Specify the appropriate level of Version 6.1 for the target version parameter (-t), for example 6.1.0.9 for Version 6.1, Fix Pack 9.
- Restoring brokers on distributed systems
- Stop the Version 8.0 broker by using the mqsistop command.
- Restore the broker to Version
6.1 using
the mqsimigratecomponents command,
as shown in the following example:
mqsimigratecomponents Broker -t 6.1.0.9
- Reverse the changes that you made to the ODBC definitions when you migrated to Version 8.0; for more details, see Updating ODBC definitions when migrating.
- Open a Version 6.1 command window, and restart the broker by using the mqsistart command.
If you migrate to Version 8.0, deploy a message set to the Version 8.0 broker, and then migrate back to Version 6.1, Version 6.1 is unable to recognize the message set that was deployed by Version 8.0. In this case, all message sets that Version 6.1 is unable to use are deleted and the warning message BIP8688W is displayed for each message set, prompting you to redeploy it to Version 6.1 following successful migration.
- Restoring brokers on z/OS®
- Stop the Version 8.0 broker by using one of the available options.
- Submit the BIPMGCMP job to call the mqsimigratecomponents command, specifying the -s and -t parameters, as described for distributed systems.
- Restore your Version 6.1 ENVFILE from a backup that you have made, or by resubmitting the Version 6.1 BIPGEN job.
- Replace the started task JCL file in USER.PROCLIB with the Version 6.1 copy that you backed up.