Rolling back a deployment cell

 

You can use the restoreConfig and wsadmin commands to roll back a migrated WAS V6.1 deployment cell to V5.x or 6.0.x. This returns the configuration to the state that it was in before migration. After rolling back the deployment cell, you can restart the migration process. Best practice: When migrating a Version 5.x or 6.0.x 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:

1. Back up your existing configuration using the backupConfig command or your own preferred backup utility.

   • Run the backupConfig command or your own preferred utility to back up the V5.x or 6.0.x deployment manager configuration.

     Verify you note the exact name and location of this backed-up configuration.

     See backupConfig command.

   • Run the backupConfig command or your own preferred utility to back up the V5.x or 6.0.x managed node configurations.

     Verify you note the exact name and location of each of these backed-up configurations.

     See backupConfig command.

2. Migrate the deployment cell.

 

Procedure

1. Stop all of the servers that are currently running in the Version 6.1 environment.

2. If you chose to disable the previous deployment manager when you migrated to the V6.1 deployment manager, perform one of the following actions.

   1. 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 V5.x or 6.0.x configuration for the deployment manager.

      Make sure that you restore the same backed-up configuration that you created just before you migrated the deployment manager.

      See restoreConfig command.

   2. If you did not back up your previous deployment manager configuration, use the wsadmin command to run the migrationDisablementReversal.jacl script from the V5.x or 6.0.x profile_root/bin directory of the deployment manager that roll back from V6.1. In a Linux environment, for example, use the following parameters:

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

      If you 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_name/nodes/node_name
         

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

      2. If you see a serverindex.xml_disabled file in 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 deployment cell's managed nodes that roll back.

   1. If you backed up your previous managed node configuration using the backupConfig command or your own preferred backup utility, run the restoreConfig command or your own preferred utility to restore the V5.x or 6.0.x configuration for the managed node.

      Verify you restore the same backed-up configuration that you created just before you migrated the managed node.

      See restoreConfig command.

   2. If you did not back up your previous managed node configuration, use the wsadmin command to run the migrationDisablementReversal.jacl script from the V5.x or 6.0.x profile_root/bin directory of the managed node. In a Linux environment, for example, use the following parameters:

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

      If you 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_name/nodes/node_name
         

         where node_name is the name of the managed node to roll back.

      2. If you see a serverindex.xml_disabled file in 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 managed nodes if they were ever running when the V6.1 deployment manager was running.

   See Synchronizing nodes with the wsadmin tool.

5. If you chose to keep the installed applications in the same location as the prior release during migration to V6.1 and any of the Version 6.1 applications are not compatible with the prior release, install applications that are compatible.

6. Delete the V6.1 profiles.

   See Deleting a profile.

7. Start the rolled-back deployment manager and its managed nodes in the V5.x or 6.0.x 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.