You can use the restoreConfig and wsadmin commands
to roll back a migrated WebSphere Application Server Version 6.1 deployment
cell to Version 5.x or 6.0.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
Best practice: When migrating a Version
5.x or 6.0.x deployment cell, the best practice is to perform the following
actions if you want to be able to roll it back to its previous state after
migration:
- 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 5.x or 6.0.x deployment manager configuration.
Important: Make sure that you note the exact name and location of this
backed-up configuration.
- Run the backupConfig command or your own preferred
utility to back up the Version 5.x or 6.0.x managed node configurations.
Important: Make sure that you note the exact name and location of each
of these backed-up configurations.
- Migrate the deployment cell.
Procedure
- Stop all of the servers that are currently running in the Version
6.1 environment.
- If you chose to disable the previous deployment manager when you
migrated to the Version 6.1 deployment manager, perform one of the following
actions.
- 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 5.x or 6.0.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.
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 profile_root/bin directory
of the deployment manager that you need to roll back from Version 6.1.
![[Linux]](../../linux.gif)
In a Linux environment, for example, use the following
parameters:
./wsadmin.sh -f migrationDisablementReversal.jacl -conntype NONE
![[iSeries]](../../iseries.gif)
Use the following parameters:
app_server_root/bin/wsadmin -instance instance -conntype NONE
-f profile_root/bin/migrationDisablementReversal.jacl
![[iSeries]](../../iseries.gif)
To restore the Version 5.1 default deployment manager,
for example, you might use the following command:
/QIBM/ProdData/WebAS51/ND/bin/wsadmin -instance default -conntype NONE -f
/QIBM/UserData/WebAS51/ND/default/bin/migrationDisablementReversal.jacl
Tip: If you have trouble running the
migrationDisablementReversal.jacl script,
try to manually perform 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 deployment
manager 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.
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 perform 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, perform the following actions:
- Delete or rename the serverindex.xml file.
- Rename the serverindex.xml_disabled file to serverindex.xml.
- Perform one of the following actions for each of the deployment
cell's managed nodes that you need to roll back.
- 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 5.x or 6.0.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.
If you did not back up your previous
managed node configuration, use the wsadmin command
to run the migrationDisablementReversal.jacl script from
the Version 5.x or 6.0.x profile_root/bin directory
of the managed node. ![[Linux]](../../linux.gif)
In a Linux environment,
for example, use the following parameters:
./wsadmin.sh -f migrationDisablementReversal.jacl -conntype NONE
![[iSeries]](../../iseries.gif)
Use the following parameters:
app_server_root/bin/wsadmin -instance instance -conntype NONE
-f profile_root/bin/migrationDisablementReversal.jacl
Tip: If you have trouble running the
migrationDisablementReversal.jacl script,
try to manually perform 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, perform the following actions:
- 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 5.x or 6.0.x WAS_HOME/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 perform 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 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.1 deployment manager was running.
- If you chose to keep the installed applications in the same location
as the prior release during migration to Version 6.1 and any of the Version
6.1 applications are not compatible with the prior release, install applications
that are compatible.
Delete the Version 6.1 profiles.
- Start the rolled-back deployment manager and its managed nodes
in the Version 5.x or 6.0.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.