WebSphere Enterprise Service Bus for z/OS, Version 6.2.0 Operating Systems: z/OS


Rolling back a deployment cell

You can use the restoreConfig and wsadmin commands to roll back a migrated WebSphere® ESB version 6.2 deployment cell to version 6.0.x or 6.1.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.

Before you begin

When migrating a version 6.0.x or 6.1.x deployment cell, you must complete the following if you want to be able to roll it back to its previous state after migration:
  1. Back up the databases that support WebSphere ESB components.
  2. (Optional) 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.0.x or 6.1.x deployment manager configuration.
      Important: Make sure that you note the exact name and location of this backed-up configuration.

      See the backupConfig command in the WebSphere Application Server information center.

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

      See the backupConfig command in the WebSphere Application Server information center.

  3. Migrate the deployment cell.
Procedure
  1. Stop all of the servers that are currently running in the WebSphere ESB version 6.2 environment.
  2. If you chose to disable the previous deployment manager when you migrated to the version 6.2 deployment manager, do one of the following:
    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 6.0.x or 6.1.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.

      See the restoreConfig command in the WebSphere Application Server information center.

    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.x or 6.0.x WAS_HOME/bin directory of the deployment manager.
      Use the following parameters:
      ./wsadmin.sh -f migrationDisablementReversal.jacl -conntype NONE
      Tip: If you have trouble running the migrationDisablementReversal.jacl script, try to manually go through 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 deployment manager node that you want to roll back.
      2. If you see a serverindex.xml_disabled file in in this directory, do the following:
        1. Delete or rename the serverindex.xml file.
        2. Rename the serverindex.xml_disabled file to serverindex.xml.
  3. For each of the deployment cell's managed nodes that you need to roll back, do one of the following:
    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 version 6.0.x or 6.1.x configuration for the managed node.
      Important: Make sure that you restore the same backed-up configuration that you created just before you migrated the managed node.

      See the restoreConfig command in the WebSphere Application Server information center.

    2. If you did not back up your previous managed node configuration, use the wsadmin command to run the migrationDisablementReversal.jacl script from the version 6.0.x or 6.1.x profile_root/bin directory of the managed node.
      Tip: If you have trouble running the migrationDisablementReversal.jacl script, try to manually go through 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, do the following:
        1. Delete or rename the serverindex.xml file.
        2. Rename the serverindex.xml_disabled file to serverindex.xml.
    3. If you did not back up your previous managed node configuration, use the wsadmin command to run the migrationDisablementReversal.jacl script from the version 6.0.x or 6.1.x install_root/bin directory of the managed node.
      Use the following parameters:
      ./wsadmin.sh -f migrationDisablementReversal.jacl -conntype NONE
      Tip: If you have trouble running the migrationDisablementReversal.jacl script, try to manually go through the steps in the script.
      1. Go to the following directory:
        install_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.
  4. Synchronize the managed nodes if they were ever running when the version 6.2 deployment manager was running.

    See Synchronizing nodes with the wsadmin tool in the WebSphere Application Server information center.

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

    See Deleting a profile in the WebSphere Application Server Information Center.

  7. Roll back your databases. (For any databases that support WebSphere ESB components that were upgraded, either automatically with the migration tools or manually, restore the backups that you made before you started the migration process.)
  8. Start the rolled-back deployment manager and its managed nodes in the version 6.0.x or 6.1.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 Task topic

Terms of use | Feedback


Timestamp icon Last updated: 21 June 2010


http://publib.boulder.ibm.com/infocenter/dmndhelp/v6r2mx/topic//com.ibm.websphere.wesb620.zseries.doc/doc/tmig_vtv_rollbackdm.html
Copyright IBM Corporation 2005, 2010. All Rights Reserved.
This information center is powered by Eclipse technology (http://www.eclipse.org).