WebSphere Application Server Network Deployment, Version 6.1
             Operating Systems: AIX, HP-UX, i5/OS, Linux, Solaris, Windows, z/OS

             Personalize the table of contents and search results

Rolling back a managed node

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

Before you begin

Best practice: When migrating a Version 5.x or 6.0.x managed 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 using the backupConfig command or your own preferred backup utility.
    • Run the backupConfig command or your own preferred utility to back up the Version 6.1 deployment manager configuration.
      Important: Make sure that you note the exact name and location of this backed-up configuration.
    • Run the backupConfig command or your own preferred utility to back up the Version 5.x or 6.0.x managed node configuration.
      Important: Make sure that you note the exact name and location of this backed-up configuration.
  2. Migrate the managed node.

If necessary, you can now roll back the managed node that you just migrated.

Important: If you do not have a backup copy of your Version 6.1 deployment manager configuration as it was before you migrated the Version 5.x or 6.0.x managed node that you want to roll back, you cannot use the procedure described in this article and you must roll back your whole cell as described in Rolling back a deployment cell.

About this task

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

Procedure

  1. Stop all of the servers that are currently running in the Version 6.1 environment.
  2. Restore your previous configuration.
    1. Run the restoreConfig command or your own preferred utility to restore the Version 6.1 deployment manager configuration.
      Important: Make sure that you restore the same backed-up configuration that you created just before you migrated the managed node.
    2. Perform one of the following actions to restore the Version 5.x or 6.0.x configuration for the managed node.
      • Run the restoreConfig command or your own preferred utility to restore the Version 5.x or 6.0.x configuration.
        Important: Make sure that you restore the same backed-up configuration that you created just before you migrated this managed node.
      • [AIX HP-UX Linux Solaris Windows] [i5/OS] Use the wsadmin command to run the migrationDisablementReversal.jacl script from the Version 5.x or 6.0.x profile_root/bin directory of the managed node.
        [Linux] In a Linux environment, for example, use the following parameters:
        ./wsadmin.sh -f migrationDisablementReversal.jacl -conntype NONE
        [i5/OS] Use the following parameters:
        app_server_root/bin/wsadmin -instance instance -conntype NONE 
        -f profile_root/bin/migrationDisablementReversal.jacl
        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 managed node that you want 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.
      • [z/OS] Use the wsadmin command to run the migrationDisablementReversal.jacl script from the Version 5.x or 6.0.x WAS_HOME/bin directory of the managed node that you need to roll back from Version 6.1.
        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:
          WAS_HOME/config/cells/cell_name/nodes/node_name
          where node_name is the name of the managed node that you want 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. Start the Version 6.1 deployment manager.
  4. Synchronize the managed node.
  5. If you chose to keep the installed applications in the same location as the prior release during migration to Version 6.1 and any of the Version 6.1 applications are not compatible with the prior release, install applications that are compatible.
  6. [AIX HP-UX Linux Solaris Windows] [i5/OS] Delete the Version 6.1 managed profile.
  7. Start the rolled-back managed node in the Version 6.1 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: Feb 25, 2009 9:32:38 AM CST
http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/index.jsp?topic=/com.ibm.websphere.nd.multiplatform.doc/info/ae/ae/tmig_rollbackmn.html