Rolling back a federated node

Use the restoreConfig and wsadmin commands to roll back a migrated WebSphere Application Server v9.0 federated node to the state that it was in before migration. For each federated node to roll back, we must roll back the federated node itself and the corresponding changes made to the primary repository located on the deployment manager.

Best practice: When migrating a v7.0 or later federated node, 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.

   1. Run the backupConfig command or our own preferred utility to back up the v9.0 deployment manager configuration.

   2. Run the backupConfig command or our own preferred utility to back up the v7.0 or later federated node configuration.

   Important: Note the exact name and location of this backed-up configuration.

   See backupConfig command for more information.

2. Migrate the federated node.

3. If necessary, we can now roll back the federated node that we just migrated.

If we do not have a backup copy of our v9.0 deployment manager configuration as it was before migratingd the v7.0 or later federated node to roll back, we cannot use the procedure described in this article and we must roll back your whole cell.

We must perform all of the backup and rollback actions for each migrated federated node before proceeding to migrate another federated node.

Tasks

1. Run the backupConfig command or our own preferred utility to back up the v9.0 deployment manager configuration at the current state.

   Important: Note the exact name and location of this backed-up configuration.

   See backupConfig command for more information.

2. Stop all servers and the node agent on the v9.0 federated node to roll back.

3. Restore the previous configuration.

   1. Run the restoreConfig command or our own preferred utility to restore the previous v9.0 deployment manager configuration.

      Important:

      • Restore the same backed-up configuration that we created just before migratingd the federated node.

      • If we have made changes to the environment (application or configuration changes for example), these changes are rolled back at the same time and cause the other nodes to force synchronization with the deployment manager.

      See restoreConfig command for more information.

   2. Perform one of the following actions to restore the v7.0 or later configuration for the federated node.

      • Run the restoreConfig command or our own preferred utility to restore the v7.0 or later configuration.

        Important: Restore the same backed-up configuration that we created just before migratingd this federated node.

        See restoreConfig command for more information.

      • 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. Start the v9.0 deployment manager.

5. Perform any application maintenance required.
6. Synchronize the v7.0 or later federated node with the deployment manager.

   See Synchronize nodes using the wsadmin scripting tool for more information.

7. 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.

8. Start the rolled-back v7.0 or later federated node and servers.

9. Validate that the configuration is satisfactory.

   This is the last chance to undo the rollback action by restoring the deployment-manager configuration that you backed up in the first step.

10. Delete the v9.0 profile for the federated node that you rolled back to v7.0 or later.

    See Delete profiles for more information.

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

Delete profiles

Migration Toolkit on WASdev.

backupConfig command

restoreConfig command