Rolling back a WAS ND cell

Use the restoreConfig and wsadmin commands to roll back a migrated WebSphere Application Server v9.0 cell to the previous version . This returns the configuration to the state that it was in before migration. After rolling back the WAS ND cell, we can restart the migration process.

Best practice: When migrating a WAS ND cell, the best practice is to perform the following actions to be able to roll it back to its previous state after migration:

1. Back up our existing configuration.

   • Run the backupConfig command or our own preferred utility to back up the source deployment manager configuration.

   • Run the backupConfig command or our own preferred utility to back up the source federated node configurations.

   Important: Note the exact name and location of each of these backed-up configurations.

   See backupConfig command.

2. Migrate the WAS ND cell.

Tasks

1. Stop all of the servers and node agents that are currently running in the v9.0 environment.

2. If we chose to disable the previous deployment manager when we migrated to the v9.0 deployment manager, perform one of the following actions.

   Disablement is the default.

   1. If we backed up the previous deployment manager configuration using the backupConfig command or our own preferred backup utility, run the restoreConfig command or our own preferred utility to restore the previous version configuration for the deployment manager.

      Important: Make sure that we restore the same backed-up configuration that we created just before migratingd the deployment manager.

      See restoreConfig command.

   2. If we did not back up the previous deployment manager configuration, use the wsadmin command to run the migrationDisablementReversal.jacl script from the v7.0 or later profile_root/bin directory of the deployment manager needed to roll back from v9.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.

      1. Go to the following directory:

         profile_root/config/cells/cell/nodes/node
         

         where node is the name of the deployment manager node to roll back.

      2. If we see a serverindex.xml_disabled file in this directory, perform the following actions:

         1. Delete or rename the serverindex.xml file.
         2. Rename the serverindex.xml_disabled file to serverindex.xml.

3. Perform one of the following actions for each of the WAS ND cell's federated nodes needed to roll back.

   1. If we backed up the previous federated node configuration using the backupConfig command or our own preferred backup utility, run the restoreConfig command or our own preferred utility to restore the v7.0 or later configuration for the federated node.

      Important: Make sure that we restore the same backed-up configuration that we created just before migratingd the federated node.

      For more information, see restoreConfig command.

   2. If we did not back up the previous federated node configuration, use the wsadmin command to run the migrationDisablementReversal.jacl script from the v7.0 or later profile_root/bin directory of the federated node.

      (Linux) 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.

      1. Go to the following directory:

         profile_root/config/cells/cell/nodes/node
         

         where node is the name of the federated node to roll back.

      2. If we see a serverindex.xml_disabled file in this directory, perform the following actions:

         1. Delete or rename the serverindex.xml file.
         2. Rename the serverindex.xml_disabled file to serverindex.xml.

4. Synchronize the federated nodes if they were ever running when the v9.0 deployment manager was running.

   See Synchronizing nodes using the wsadmin scripting tool.

5. If we chose to keep the installed applications in the same location as the prior release during migration to v9.0 and any of the v9.0 applications are not compatible with the prior release, install applications that are compatible.

6. Delete the v9.0 profiles.

   See Delete profiles.

7. Start the rolled-back deployment manager and its federated nodes in the v7.0 or later environment.

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 to do so.

Synchronize nodes

Migration Toolkit on WASdev.

Delete profiles

backupConfig command

restoreConfig command