You can use the restoreConfig and wsadmin commands
to roll back a migrated WebSphere® ESB version 6.2 deployment
cell to version 6.0.x or 6.1.x.
This returns the configuration to the state that it was in before
migration. After rolling back the deployment cell, you can restart
the migration process.
Before you begin
When migrating a
version 6.0.x or 6.1.x deployment
cell, you must complete the following if you want to be able to roll
it back to its previous state after migration:
- Back up the databases that support WebSphere ESB components.
- (Optional) Back up your existing configuration using the backupConfig command
or your own preferred backup utility.
- Run the backupConfig command or your
own preferred utility to back up the version 6.0.x or 6.1.x deployment
manager configuration.
Important: Make sure that you note
the exact name and location of this backed-up configuration.
See
the backupConfig command in
the WebSphere Application Server information
center.
- Run the backupConfig command or your
own preferred utility to back up the version 6.0.x or 6.1.x managed
node configurations.
Important: Make sure that you note
the exact name and location of each of these backed-up configurations.
See
the backupConfig command in
the WebSphere Application Server information
center.
- Migrate the deployment cell.
Procedure
- Stop all of the servers that are currently running in the WebSphere ESB version 6.2 environment.
- If you chose to disable the previous deployment manager
when you migrated to the version 6.2 deployment
manager, do one of the following:
- If you backed up your previous deployment manager configuration
using the backupConfig command or your own
preferred backup utility, run the restoreConfig command
or your own preferred utility to restore the version 6.0.x or 6.1.x configuration
for the deployment manager.
Important: Make
sure that you restore the same backed-up configuration that you created
just before you migrated the deployment manager.
See the restoreConfig command in
the WebSphere Application Server information
center.
- If you did not back up your previous
deployment manager configuration, use the wsadmin command
to run the migrationDisablementReversal.jacl script
from the Version 5.x or 6.0.x WAS_HOME/bin directory
of the deployment manager.
Use the following parameters:
./wsadmin.sh -f migrationDisablementReversal.jacl -conntype NONE
Tip: If you have trouble running the
migrationDisablementReversal.jacl script,
try to manually go through the steps in the script.
- Go to the following directory:
WAS_HOME/config/cells/cell_name/nodes/node_name
where node_name
is the name of the deployment manager node that you want to roll back.
- If you see a serverindex.xml_disabled file
in in this directory, do the following:
- Delete or rename the serverindex.xml file.
- Rename the serverindex.xml_disabled file
to serverindex.xml.
- For each of the deployment cell's managed nodes that you
need to roll back, do one of the following:
- If you backed up your previous managed node configuration
using the backupConfig command or your own
preferred backup utility, run the restoreConfig command
or your own preferred utility to restore the version 6.0.x or 6.1.x configuration
for the managed node.
Important: Make sure
that you restore the same backed-up configuration that you created
just before you migrated the managed node.
See the restoreConfig command in
the WebSphere Application Server information
center.
- If you did not back up your previous managed
node configuration, use the wsadmin command
to run the migrationDisablementReversal.jacl script
from the version 6.0.x or 6.1.x profile_root/bin directory
of the managed node.
Tip: If you have trouble running the
migrationDisablementReversal.jacl script,
try to manually go through the steps in the script.
- Go to the following directory:
profile_root/config/cells/cell_name/nodes/node_name
where node_name
is the name of the managed node that you want to roll back.
- If you see a serverindex.xml_disabled file
in in this directory, do the following:
- Delete or rename the serverindex.xml file.
- Rename the serverindex.xml_disabled file
to serverindex.xml.
- If you did not back up your previous
managed node configuration, use the wsadmin command
to run the migrationDisablementReversal.jacl script
from the version 6.0.x or 6.1.x install_root/bin directory
of the managed node.
Use the following parameters:
./wsadmin.sh -f migrationDisablementReversal.jacl -conntype NONE
Tip: If you have trouble running the
migrationDisablementReversal.jacl script,
try to manually go through the steps in the script.
- Go to the following directory:
install_root/config/cells/cell_name/nodes/node_name
where node_name
is the name of the managed node that you want to roll back.
- If you see a serverindex.xml_disabled file
in in this directory, perform the following actions:
- Delete or rename the serverindex.xml file.
- Rename the serverindex.xml_disabled file
to serverindex.xml.
- Synchronize the managed nodes if they were ever running
when the version 6.2 deployment
manager was running.
See Synchronizing nodes with the wsadmin tool in
the WebSphere Application Server information
center.
- If you chose to keep the installed applications in the
same location as the prior release during migration to version 6.2 and any
of the version 6.2 applications
are not compatible with the prior release, install applications that
are compatible.
- Delete the version 6.2 profiles.
See Deleting a profile in the WebSphere Application Server Information
Center.
- Roll back your databases. (For
any databases that support WebSphere ESB components
that were upgraded, either automatically with the migration tools
or manually, restore the backups that you made before you started
the migration process.)
- Start the rolled-back deployment manager and its managed
nodes in the version 6.0.x or 6.1.x environment.
Results
The configuration should now be returned to the state that
it was in before migration.
What to do next
You can now restart the migration process if you want to
do so.