About this task
If you migrated from a previous version of IBM® Integration Bus or
WebSphere® Message Broker to IBM Integration Bus Version 10.0, you can restore your
installation to the previous version, subject to the following restrictions and
procedures.
When you restore integration nodes to a previous version, changes that you made that
are compatible with the previous version are kept. Changes that you made that are
not compatible with the previous version are not reflected in your integration
node's state, which might cause errors.
You might want to restore components if you encounter a problem after you migrate
your integration nodes to Version 10.0. For
example, if a message flow does not work as expected in Version 10.0, restore that integration node until
you can resolve the problem.
You can restore integration nodes to a previous version only if they were migrated
from that version originally. You cannot create a new Version 10.0 integration node, then restore it to
a previous level.
When you use the mqsimigratecomponents command, you must be logged
in to a Version 10.0 command environment.
See the mqsimigratecomponents command
description for usage information and details of parameters and the format to use
when you specify version numbers.
- Restrictions
-
Message flows that you deploy to an integration node after you migrate to
Version 10.0 might no longer work
when you restore that integration node to its original version; always
check logs to search for errors or warnings about message flows that the
integration node cannot start.
Source files in the IBM Integration Toolkit
Version 10.0 might be maintained in a
different format from that used in your original version. The files are
migrated to the new format when you save them in the IBM Integration Toolkit
Version 10.0. After you save a
resource with the IBM Integration Toolkit
Version 10.0, you might not be able to
use the resources with the IBM Integration Toolkit or
WebSphere Message Broker Toolkit from the previous
version .
- Migrating resources back to the previous version
- The following sections describe how to restore the IBM Integration Toolkit and your integration nodes to the previous version. You can reuse your
original Configuration Manager and User Name Server components with the integration node
that you restore to the original version.
- Restoring the IBM Integration Toolkit
Version 10.0 to the previous
version
-
- Close all IBM Integration Toolkit
Version 10.0
sessions.
- Restore the workspace from the backup that you took
before you started the migration.
Ensure that the workspace
directories include the
.metadata directory, which
contains information that is specific to the release
of Eclipse on which the previous IBM Integration Toolkit or WebSphere Message Broker Toolkit is
based.
- Restart the previous IBM Integration Toolkit or WebSphere Message Broker Toolkit .
- Restoring integration nodes to the previous version
- Use the -s and -t
parameters of the mqsimigratecomponents command
to migrate integration nodes from Version 10.0 to the previous
version.
- Specify the installed level of Version 10.0 for the
source version parameter (-s), for
example
10.0.0.n
for the GA (general availability) level,
or allow this to take the default value.
- Specify the appropriate level for the target version
parameter (-t), for example
8.0.0.2
for Version
8.0, Fix Pack 2.
See the mqsimigratecomponents command
for detailed information about these parameters and the format
to use when you specify version numbers.
- Restoring integration nodes on distributed
systems
-
- Stop the Version 10.0
integration node by using the mqsistop
command.
- Restore the integration node to the previous
version by using the mqsimigratecomponents command, as shown in the following
example:
mqsimigratecomponents integration_node -t 8.0.0.2
- Reverse the changes that you made to the ODBC
definitions when you migrated to Version 10.0; for
more information, see Updating ODBC definitions when you migrate to IBM Integration Bus Version 10.0.
- Open a command window by using the previous
version of IBM Integration Bus
or WebSphere Message Broker,
and restart the integration node by using the
mqsistart
command.
If you migrate to Version 10.0, deploy
a message set to the Version 10.0
integration node, and then migrate back to the
previous version, the previous version might be
unable to recognize the message set that was
deployed by Version 10.0. In
this case, all message sets that the previous
version is unable to use are deleted and the
warning message BIP8688W is
displayed for each message set, prompting you to
redeploy it to the previous version following
successful migration.
- Restoring integration nodes on z/OS®
-
- Stop the Version 10.0
integration node 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 the ENVFILE from backup, or by
resubmitting the BIPGEN job for the original
version.
- Replace the started task JCL file in
USER.PROCLIB with the backup copy from the
previous version.