IBM BPM, V8.0.1, All platforms > Migrating and upgrading your IBM BPM environment > Migrating from previous versions > Migrating your IBM BPM Advanced V7.5.x or WebSphere Process Server V7.x or V6.2.x runtime > Runtime migration subprocedures > Rolling back your environment

Rolling back a managed node

You can use the restoreConfig and wsadmin commands to roll back a migrated IBM BPM V8.0.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 dmgr.

When you migrate a managed node, you must perform all of the backup steps below in sequence to successfully complete the rollback.

  1. Back up the databases that support IBM BPM components.

    If the purpose of the rollback is to fix a problem that occurred during migration and rerun profile migration, do not perform a database rollback. Databases should be rolled back only if you need to start the managed node servers once they have been restored to the previous version.

    Roll back the deployment target-scoped database, if applicable. Check whether the managed node has a server with Business Process Choreographer or Business Space components configured.

    • If the managed node does not have these components configured on any of the servers, go to Step 2.

    • If the managed node contains a server-scoped configuration for Business Process Choreographer or Business Space, roll back the database.

      If the managed node has a server that is a member of a cluster where Business Process Choreographer and Business Space are configured, verify that rolling back the managed node would not result in a mixed-version cluster, with some cluster members on V8.0.1 and some on a previous version. A database rollback would cause cluster members on V8.0.1 to fail. Databases should be rolled back only if you decide to roll back all the managed nodes that participate in the cluster, and you plan to run the cluster on the previous version.

  2. 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 earlier version of the dmgr configuration.

      Important: Make sure to note the exact name and location of this backed-up configuration.

      See backupConfig command in the WebSphere Application Server information center.

  3. Migrate the managed node.

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

If you do not have a backup copy of your V8.0.1 dmgr configuration as it was before you migrated the managed node that you want to roll back, you cannot use the procedure described in this topic and you must roll back your whole cell as described in Rolling back a deployment cell.

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


Procedure

  1. Roll back your databases. (For any databases that support IBM BPM components that were upgraded, either automatically with the migration tools or manually, restore the backups made before you started the migration process.)
  2. Stop all of the servers that are currently running in the V8.0.1 environment.
  3. Restore your previous configuration.

    1. Run the restoreConfig command or your own preferred utility to restore the V8.0.1 dmgr configuration.

      Important: Verify that you restore the same backed-up configuration created just before you migrated the managed node.

      See restoreConfig command in the WebSphere Application Server information center.

    2. Perform one of the following actions to restore the previous configuration for the managed node.

      • Run the restoreConfig command or your own preferred utility to restore the configuration of the earlier version.

        See restoreConfig command in the WebSphere Application Server information center.

      • Use the wsadmin command to run the migrationDisablementReversal.jacl script from the profile_root/bin directory of the earlier version of the managed node.

        In a Linux environment, for example, use the following parameters:

        ./wsadmin.sh -f migrationDisablementReversal.jacl -conntype NONE

        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 this directory, perform the following actions:
          1. Delete or rename the serverindex.xml file.
          2. Rename the serverindex.xml_disabled file to serverindex.xml.
      • Use the wsadmin command to run the migrationDisablementReversal.jacl script from the INSTALL_ROOT/bin directory of the earlier version of the managed node that you need to roll back from V8.0.1.

        Use the following parameters:

        ./wsadmin.sh -f migrationDisablementReversal.jacl -conntype NONE

        If you have trouble running the migrationDisablementReversal.jacl script, try to perform the steps in the script manually.

        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 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 V8.0.1 dmgr.
  5. Synchronize the managed node.

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

  6. If you chose to keep the installed applications in the same location as the prior release during migration to V8.0.1 and any of the V8.0.1 applications are not compatible with the prior release, install applications that are compatible.
  7. Delete the V8.0.1 managed profile.

    See Delete profiles in the WebSphere Application Server information center.

  8. Start the rolled-back managed node in the V8.0.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.

Rolling back your environment