You can use the restoreConfig and wsadmin commands to roll back a migrated WebSphere® Application Server Version 8.5 WebSphere Application Server, Network Deployment cell to Version
6.1 or above. This returns the configuration to the state that it
was in before migration. After rolling back the WebSphere Application Server, Network Deployment cell, you can
restart the migration process.
Before you begin
Supported configurations: This
article is about configuration migration, such as migrating deployment
managers and federated nodes in a network deployment environment.
The Application Migration Toolkit for WebSphere Application Server
provides support for migrating applications from previous versions
of WebSphere Application Server to the latest product version. For
information about migrating applications, read more about the Application
Migration Toolkit.
sptcfg
Best practice: When migrating a Version 6.1
or above
WebSphere Application Server, Network 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.
- Run the backupConfig command or your own preferred
utility to back up the Version 6.1 or above deployment manager configuration.
- Run the backupConfig command or your own preferred
utility to back up the Version 6.1 or above federated node configurations.
Important: Make sure that you note the exact name
and location of each of these backed-up configurations.
For
more information, see backupConfig command.
- Migrate the WebSphere Application Server, Network Deployment cell.
Procedure
- Stop all of the servers and node agents that are currently
running in the Version 8.5 environment.
- If you chose to disable the previous deployment manager
when you migrated to the Version 8.5 deployment manager, perform one of the following actions.
Note: Disablement is the default.
- 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.1 or above 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.
For more
information, see restoreConfig command.
If you did not back up your previous
deployment manager configuration, use the wsadmin command to run the migrationDisablementReversal.jacl script from the Version 6.1 or above app_server_root/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:
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 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 WebSphere Application Server, Network Deployment cell's federated
nodes that you need to roll back.
- If you backed up your previous federated 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.1 or above configuration
for the federated node.
Important: Make sure
that you restore the same backed-up configuration that you created
just before you migrated the federated node.
For more information,
see restoreConfig command.
If you did not back up your previous
federated node configuration, use the wsadmin command
to run the migrationDisablementReversal.jacl script
from the Version 6.1 or above app_server_root/bin directory of the federated 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:
profile_root/config/cells/cell_name/nodes/node_name
where node_name is the name of the
federated node that you want to roll back.
- If you see a serverindex.xml_disabled file
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 federated nodes if they were ever running
when the Version 8.5 deployment
manager was running.
For more information, see Synchronizing nodes using the wsadmin scripting tool.
- If you chose to keep the installed applications in the
same location as the prior release during migration to Version 8.5 and any of the Version 8.5 applications are
not compatible with the prior release, install applications that are
compatible.
- Start the rolled-back deployment manager and its federated
nodes in the Version 6.1 or above 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.