WAS v8.0 > Migration and coexistence > Distributed operating systems > Migrate product configurations > Rolling back environments
Rolling back a WAS ND cell
We can use the restoreConfig and wsadmin commands to roll back a migrated WAS v8.0 WAS ND cell to Version 6.x or 7.x. This returns the configuration to the state that it was in before migration. After rolling back the WAS ND cell, you can restart the migration process.
Supported configurations:
This topic is about configuration migration, such as migrating dmgrs and federated nodes in a network deployment environment. The Application Migration Toolkit for WAS provides support for migrating applications from previous versions of WAS to the latest product version. For information about migrating applications, read more about the Application Migration Toolkit.
Best practice: When migrating a v6.x or 7.x WAS ND 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 v6.x or 7.x dmgr configuration.
Make sure that you note the exact name and location of this backed-up configuration.
Read the "backupConfig command" article in the information center for more information.
- Run the backupConfig command or your own preferred
utility to back up the v6.x or 7.x federated node configurations.
Make sure that you note the exact name and location of each of these backed-up configurations.
Read the "backupConfig command" article in the information center for more information.
- Run the backupConfig command or your own preferred
utility to back up the v6.x or 7.x dmgr configuration.
- Migrate the WAS ND cell.
Procedure
- Stop all of the servers and node agents that are currently
running in the v8.0 environment.
- If you chose to disable the previous dmgr
when you migrated to the v8.0 dmgr, perform one of the following actions.
Disablement is the default.
- If you backed up your previous dmgr configuration using the backupConfig command or your own preferred
backup utility, run the restoreConfig command or your own preferred utility to restore the v6.x or 7.x configuration for the dmgr.
Make sure that you restore the same backed-up configuration that you created just before you migrated the dmgr.
Read the "restoreConfig command" article in the information center for more information.
- If you did not back up your previous dmgr configuration, use the wsadmin command to run the migrationDisablementReversal.jacl script from the v6.x or 7.x PROFILE_ROOT/bin directory of the dmgr that roll back from v8.0.
In a Linux environment, for example, use the following parameters:
./wsadmin.sh -f migrationDisablementReversal.jacl -conntype NONE
Tip: If we 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 dmgr node 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.
- Go to the following directory:
- If you backed up your previous dmgr configuration using the backupConfig command or your own preferred
backup utility, run the restoreConfig command or your own preferred utility to restore the v6.x or 7.x configuration for the dmgr.
- Perform one of the following actions for each of the WAS ND cell's federated nodes that 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 v6.x or 7.x configuration for the federated node.
Make sure that you restore the same backed-up configuration that you created just before you migrated the federated node.
Read the "restoreConfig command" article in the information center for more information.
- If you did not back up your previous federated node configuration, use the wsadmin command to run the migrationDisablementReversal.jacl script from the v6.x or 7.x PROFILE_ROOT/bin directory of the federated node.
In a Linux environment,
for example, use the following parameters:
./wsadmin.sh -f migrationDisablementReversal.jacl -conntype NONE
Tip: If we 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 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.
- Go to the following directory:
- 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 v6.x or 7.x configuration for the federated node.
- Synchronize the federated nodes if they were ever running
when the v8.0 dmgr was running.
Read the "Synchronizing nodes with wsadmin.sh" article in the information center for more information.
- If you chose to keep the installed applications in the same location as the prior release during migration to v8.0 and any of the v8.0 applications are not compatible with the prior release, install applications that are compatible.
- Delete the v8.0 profiles.
Read the "Deleting a profile" article in the information center for more information.
- Start the rolled-back dmgr and its federated nodes in the v6.x or 7.x environment.
Results
The configuration should now be returned to the state that it was in before migration.
What to do next
We can now restart the migration process if you want to do so.