WAS v8.0 > Migration and coexistence > Distributed operating systems > Migrate product configurations > Rolling back environments

Rolling back stand-alone application servers

We can use the restoreConfig and wsadmin commands to roll back a migrated WAS v8.0 stand-alone application server to the state that it was in before migration.

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 stand-alone application server, the best practice is to perform the following actions to be able to roll it back to its previous state after migration:

1. Run the backupConfig command or your own preferred utility to back up the v6.x or 7.x stand-alone application server 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.

2. Migrate the stand-alone application server.

3. If necessary, you can now roll back the stand-alone application server that you just migrated.

Procedure

1. Stop all of the servers that are currently running in the v8.0 environment.
2. Perform one of the following actions to restore the Version 6.x or 7.x configuration for the stand-alone application server.
   • Run the restoreConfig command or your own preferred utility to restore the v6.x or 7.x configuration.

     Make sure that you restore the same backed-up configuration that you created just before you migrated this stand-alone application server.

     Read the "restoreConfig command" article in the information center for more information.

   • Use the wsadmin command to run the migrationDisablementReversal.jacl script from the v6.x or 7.x PROFILE_ROOT/bin directory of the stand-alone application server.

     In a Linux environment, for example, use the following parameters:

     ./wsadmin.sh -f migrationDisablementReversal.jacl -conntype NONE
     

3. 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.
4. Delete the v8.0 profile for the stand-alone application server.

   Read the "Deleting a profile" article in the information center for more information.

5. Start the rolled-back stand-alone application server in the v8.0 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 to do so.

+

Search Tips   |   Advanced Search