Rolling back a WebSphere Application Server, Network Deployment cell

You can use the restoreConfig and wsadmin commands to roll back a migrated WebSphere® Application Server, Network Deployment cell to Version 5.1.x or Version 6.x. This returns the configuration to the state that it was in before migration. After rolling back the WebSphere Application Server, Network Deployment cell, you can restart the migration process.

Before you begin

Best practice: When migrating a Version 5.1.x or Version 6.x WebSphere Application Server, Network 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.
    • Run the backupConfig command or your own preferred utility to back up the Version 5.1.x or Version 6.x deployment manager configuration.
      Important: Make sure that you note the exact name and location of this backed-up configuration.

      Read the "backupConfig command" article in the information center for more information.

    • Run the backupConfig command or your own preferred utility to back up the Version 5.1.x or Version 6.x federated node configurations.
      Important: Make sure that you note the exact name and location of each of these backed-up configurations.

      Read the "backupConfig command" article in the information center for more information.

  2. Migrate the WebSphere Application Server, Network Deployment cell.

Procedure

  1. Stop all of the servers and node agents that are currently running in the Version 7.0 environment.
  2. If you chose to disable the previous deployment manager when you migrated to the Version 7.0 deployment manager, perform one of the following actions.
    Note: Disablement is the default.
    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 Version 5.1.x or Version 6.x configuration for the deployment manager.
      Important: Make sure that you restore the same backed-up configuration that you created just before you migrated the deployment manager.

      Read the "restoreConfig command" article in the information center for more information.

    2. If you did not back up your previous deployment manager configuration, use the wsadmin command to run the migrationDisablementReversal.jacl script from the Version 5.1.x or Version 6.x profile_root/bin directory of the deployment manager that you need to roll back from Version 7.0.
      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 deployment manager 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.
  3. Perform one of the following actions for each of the WebSphere Application Server, Network Deployment cell's federated nodes that you need to roll back.
    1. If you backed up your previous federated node configuration using the backupConfig command or your own preferred backup utility, run the restoreConfig command or your own preferred utility to restore the Version 5.1.x or Version 6.x configuration for the federated node.
      Important: Make sure that you restore the same backed-up configuration that you created just before you migrated the federated node.

      Read the "restoreConfig command" article in the information center for more information.

    2. If you did not back up your previous federated node configuration, use the wsadmin command to run the migrationDisablementReversal.jacl script from the Version 5.1.x or Version 6.x 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. Synchronize the federated nodes if they were ever running when the Version 7.0 deployment manager was running.

    Read the "Synchronizing nodes with the wsadmin tool" article in the information center for more information.

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

    Read the "Deleting a profile" article in the information center for more information.

  7. Start the rolled-back deployment manager and its federated nodes in the Version 5.1.x or Version 6.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.

Task topic    

Terms of Use | Feedback

Last updated: Oct 22, 2010 2:38:49 AM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=compass&product=was-nd-dist&topic=tmig_rollbackdm
File name: tmig_rollbackdm.html