Rolling back a federated node

You can use the restoreConfig and wsadmin commands to roll back a migrated WebSphere® Application Server Version 9.0 federated node to the state that it was in before migration. For each federated node that you want to roll back, you must roll back the federated node itself and the corresponding changes made to the primary repository located on the deployment manager.

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 federated node, 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.
    1. Run the backupConfig command or your own preferred utility to back up the Version 9.0 deployment manager configuration.
    2. Run the backupConfig command or your own preferred utility to back up the Version 7.0 or later federated node 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 federated node.
  3. If necessary, you can now roll back the federated node that you just migrated.
Important: If you do not have a backup copy of your Version 9.0 deployment manager configuration as it was before you migrated the Version 7.0 or later federated node that you want to roll back, you cannot use the procedure described in this article and you must roll back your whole cell.

About this task

You must perform all of the backup and rollback actions for each migrated federated node before you proceed to migrate another federated node.

Procedure

  1. Run the backupConfig command or your own preferred utility to back up the Version 9.0 deployment manager configuration at the current state.
    Important: Make sure that you 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 Version 9.0 federated node that you want to roll back.
  3. Restore your previous configuration.
    1. Run the restoreConfig command or your own preferred utility to restore the previous Version 9.0 deployment manager configuration.
      Important:
      • Make sure that you restore the same backed-up configuration that you created just before you migrated the federated node.
      • If you have made changes to your 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 Version 7.0 or later configuration for the federated node.
      • 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 federated node.

        See restoreConfig command for more information.

      • Use the wsadmin command to run the migrationDisablementReversal.jacl script from the Version 7.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 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 federated node that you want to roll back.
        2. If you 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 Version 9.0 deployment manager.
  5. Perform any application maintenance that is required.
  6. Synchronize the Version 7.0 or later federated node with the deployment manager.

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

  7. 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.
  8. Start the rolled-back Version 7.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 Version 9.0 profile for the federated node that you rolled back to Version 7.0 or later.

    See Deleting profiles for more information.

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:01
File name: tmig_rollbackmn.html