Rolling back stand-alone application servers

You can use the restoreConfig and wsadmin commands to roll back a migrated WebSphere® Application Server Version 9.0 stand-alone application server to the state that it was in before migration.

Before you begin

Supported configurations Supported configurations:

This article is about profile configuration migration. To migrate your applications to the latest version, use the WebSphere Application Server Migration Toolkit. For more information, see the Migration Toolkit on WASdev.

sptcfg
Best practice: When migrating a Version 7.0 or later stand-alone application server, 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:
  1. Run the backupConfig command or your own preferred utility to back up the Version 7.0 or later stand-alone application server configuration.
    Important: Make sure that you note the exact name and location of this backed-up configuration.

    See backupConfig command 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 Version 9.0 environment.
  2. Perform one of the following actions to restore the Version 7.0 or later configuration for the stand-alone application server.
    • Run the restoreConfig command or your own preferred utility to restore the Version 7.0 or later configuration.
      Important: Make sure that you restore the same backed-up configuration that you created just before you migrated this stand-alone application server.

      See restoreConfig command for more information.

    • Use the wsadmin command to run the migrationDisablementReversal.jacl script from the Version 7.0 or later WAS_HOME/bin directory of the stand-alone application server that you need to roll back from Version 9.0.
      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 Version 9.0 and any of the Version 9.0 applications are not compatible with the prior release, install applications that are compatible.
  4. Start the rolled-back stand-alone application server in the Version 9.0 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.

Icon that indicates the type of topic Task topic



Timestamp icon Last updated: March 6, 2017 0:04
File name: tmig_rollbacksa.html