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 procedures

Migrating an ND environment with full downtime

Use this procedure to migrate an ND environment while incurring full downtime. This procedure is simpler than the minimal downtime procedure, and is recommended if you can accommodate the downtime.

Review the Migration overview and BPM runtime premigration checklist.


Procedure

Follow these steps to migrate an ND environment while incurring full downtime.

  1. Install the migration target product(s).

    Install the target product and the latest fix packs on the same system as the source product of the migration.

    You must either install the target version with the same user ID as that used for installing the source version, or have permission to access the configuration and data on the source installation.

    To migrate from source profiles augmented by multiple products, the new version of those products must be installed into the same target installation directory.

    For example, if the source profile is augmented by IBM BPM and IBM Business Monitor, both of those products must be installed into the same target installation directory.

  2. Upgrade DB2 for z/OS and OS/390 Version 7.

    If you use DB2 for z/OS and OS/390 Version 7, and have not yet upgraded the database to DB2 for z/OS Version 8 or DB2 9 for z/OS, perform the upgrade now, as described in the DB2 for z/OS documentation.

  3. Upgrade Oracle 9i and the Oracle JDBC driver.

    If you are using an Oracle database, check the following:

    1. If you are using Oracle 9i, and have not yet upgraded your database to 10g or 11g, perform the upgrade now, as described in the Oracle documentation.

    2. If you are using the ojdbc14.jar or the ojdbc5.jar driver, install the new ojdbc6.jar driver in the directory that is pointed to by the ORACLE_JDBC_DRIVER_PATH WebSphere variable.

    You must do this on all IBM BPM installations that access the Oracle database.

  4. To prepare to stop all Java Virtual Machines (JVMs) in the cell, identify all clusters, node agents, non-clustered servers, and the dmgr.

    For example, in the topology illustrated, you would need to stop the following.

    • The three clusters

    • The node agents for nodes one and two

    • The non-clustered server in node three

    • The dmgr for the cell

    Figure 1. Example topology with three clusters across two nodes plus a third node for non-clustered servers

  5. Stop the clusters, node agents, non-clustered servers, and dmgr.

    1. Stop all cluster members.
    2. Stop all node agents.
    3. Stop all non-clustered servers.
    4. Stop the dmgr.

      Stop the source dmgr using the stopManager command from the profile_root/bin directory on the migration source system or from the profile's First steps console.

      Use the following syntax:

      • stopManager.sh -username user_name -password password

      • stopManager.bat -username user_name -password password

      If the profile has security enabled, the user name provided must be a member of the operator or administrator role.

      If security is enabled, you do not have to specify the -username and -password parameters if the server is running as a Windows service. In this case, the parameters are automatically passed into the script that the Windows service uses to shut down the server.

      If the profile does not have security enabled, the -username and -password parameters are unnecessary.

      For more information about the stopManager command, see stopManager command in the WebSphere Application Server information center.

  6. Back up the migration source profiles and the migration source product databases.

    1. Back up the migration source profiles.

      Repeat this step for each profile that will be migrated, including the dmgr, each non-clustered managed node, and each managed node.

      Back up the profile configuration on the migration source server using the backupConfig command.

      Use the following syntax to back up a profile named profile1 to /ProfileBackups/profile1.zip:

      • backupConfig.sh /ProfileBackups/profile1.zip -profileName profile1

      • backupConfig.bat c:\ProfileBackups\profile1.zip -profileName profile1

      For more information about the backupConfig command, see backupConfig command in the WebSphere Application Server information center.

    2. Back up the migration source product databases.

      Back up the following databases that are configured by any of the migration source profiles according to the documentation for your database:

      • Business Process Choreographer Database
      • Business Space database
      • Common database
      • Common Event Infrastructure Database

      • Messaging Engine Database

      • Performance Data Warehouse database

      • Process Server or Process Center database

  7. Migrate the dmgr profile.

  8. Upgrade the product databases.

    • Common database:

      • If you are migrating from WebSphere Process Server 6.2 or 7.0, upgrade the Common database schema following the instructions in Migrating the Common database.
      • If you are migrating from IBM BPM 7.5, it is not necessary to perform a schema upgrade for the Common database.

    • Business Process Choreographer:

    • Business Space database:

      • If you are migrating from WebSphere Process Server 6.2 or 7.0, see step 17 to migrate the Business Space database schema. Business Space combines the schema upgrade and data migration into one procedure.
      • If you are migrating from IBM BPM 7.5, upgrade the Business Space database schema following the instructions in Migrating the Business Space database.

    • Process Server (or Process Center) and Performance Data Warehouse databases:

      • If you are migrating from WebSphere Process Server 6.2 or 7.0, these databases do not exist and no action is required.
      • If you are migrating from IBM BPM 7.5, see step 16 to upgrade the Process Server (or Process Center) and Performance Data Warehouse databases.

    • Common Event Infrastructure and Messaging Engine databases:

  9. Start the target dmgr.

    Start the target dmgr using the startManager command from the profile_root/bin directory on the dmgr system or from the First steps console for the dmgr profile.

    Use the following syntax:

    • startManager.sh

    • startManager.bat

    For more information about the startManager command, see startManager command in the WebSphere Application Server information center.

  10. Update the data source configuration. If you have data sources that are using embedded data direct driver and you did not update them in the source environment to use a licensed Data Direct JDBC driver or Microsoft JDBC driver, update the Data Source configuration. To do this, use the following procedure.

    Attention: The SystemOut.log file might reflect errors because some components could not establish connection to the database.

    1. Log in to the administrative console.

    2. Create a new Data Source with the correct JDBC Provider Type, and set the following properties: JNDI Name, statementCacheSize, releationalResourceAdapter, authMechanismPreference, authDataAlias, databaseName, serverName, portNumber, and URL that match with the existing Data Source.
    3. Delete the existing Data Source that uses embedded driver.

    4. Use the Test Connection option to check if the data source configuration works.
    5. Restart the dmgr.

  11. Perform the following actions for all nodes that are federated under the dmgr.

    1. Migrate the managed nodes.

    2. Start the node agent of the target managed nodes.

      Repeat this step for each non-clustered managed node that was migrated and each clustered managed node for each cluster that was migrated.

      Start the migration target node agent using the startNode command from the profile_root/bin directory of the migration target server.

      Use the following syntax:

      • startNode.sh

      • startNode.bat

      For more information about the startNode command, see startNode command in the WebSphere Application Server information center.

  12. Migrate the cluster configuration for clustered nodes.

    1. Migrate the cluster-scoped configuration.

      Migrate the cluster-scoped configuration using the BPMMigrateCluster command from the target_INSTALL_ROOT/bin directory on the system containing the dmgr.

      Use the following syntax to migrate all clusters found on the dmgr:

      Use the following syntax to migrate a cluster named applicationCluster1 with a dmgr profile named dmgrProfile copied in the /MigrationSnapshots/ProcServer directory:

      For more information about the BPMMigrateCluster command, see the BPMMigrateCluster command-line utility topic.

  13. Check the data sources to make sure that they point to the correct database server.

  14. Configure the additional features for IBM BPM V8.0.1 (for example, Business Process Definitions), because these are not configured during the runtime migration procedure.

    1. If you are migrating from version 6.2 or 7.0, configure Process Server and Performance Data Warehouse using the procedure described in the section Configure the Process Server and Performance Data Warehouse.

    2. If you are migrating from version 7.5, configure Process Portal using the BPMConfigureProcessServer command from the dmgrProfile/bin directory. Use the following syntax:

      • BPMConfigureProcessServer.sh

      • BPMConfigureProcessServer.bat

  15. Synchronize all the clustered nodes that participate in the clusters migrated in previous steps to update the cluster configuration.

    1. Stop the migration target node agent using the stopNode command from the profile_root/bin directory of the migration target system. Use the following syntax:

      • stopNode.sh -username user_name -password password

      • stopNode.bat -username user_name -password password

      For more information about the stopNode command, see stopNode command in the WebSphere Application Server information center.

    2. Secure the changes made up to this point by making a new back up of your managed profiles. Back up the profile configuration on the clustered managed node using the backupConfig command. Use the following syntax to back up a profile named profile1 to /ProfileBackups/profile1.zip:

      • backupConfig.sh /ProfileBackups/profile1.zip -profileName profile1

      • backupConfig.bat c:\ProfileBackups\profile1.zip -profileName profile1

      For more information about the backupConfig command, see backupConfig command in the WebSphere Application Server information center.

    3. Synchronize the managed nodes. Synchronize the node with the target dmgr using the syncNode command from the profile_root/bin directory of the migration target profile or from the target profile's First steps console. Use the following syntax:

      • syncNode.sh deployment_manager_machine_name_or_ip_address deployment_manager_port_no

      • syncNode.bat deployment_manager_machine_name_or_ip_address deployment_manager_port_no

      For more information about the syncNode command, see syncNode command in the WebSphere Application Server information center.

    4. If the syncNode command did not complete successfully, perform the following actions.
      1. Resolve the issues reported by the syncNode command.

      2. If necessary, restore the managed profiles that you backed up before running the syncNode command.

      3. Run the syncNode command again.

    5. Start the migration target node agent.

  16. If the source version is 7.5.x, update the Process Server and Performance Data Warehouse databases following the instructions in Upgrading existing databases, using the UpgradeProcessData command from the target_INSTALL_ROOT/BPM/Lombardi/tools/upgrade/UpgradeProcessData directory.

    For example:

  17. Migrate the instance data for Business Space if it is configured in the source environment. Perform the following steps to update the data in the database to work with V8.0.1:

  18. Start the migration target servers.

    Repeat this step for each server configured for each non-clustered managed node that was migrated and for each clustered managed node that was migrated.

    Start the migration target server using the startServer command from the profile_root/bin directory of the migration target server or from the profile's First steps console.

    Use the following syntax:

    • startServer.sh server_name

    • startServer.bat server_name

    For more information about the startServer command, see startServer command in the WebSphere Application Server information center.

  19. If you are using a three-cluster or four-cluster configuration, and you have not yet configured a routing server for Business Space:

    1. To ensure that requests for Process Portal are redirected to the correct cluster, complete the steps in Configure a proxy server for Process Portal.

    2. If you want users to be able to access Process Portal using HTTP rather than the Business Space default of HTTPS, complete the steps in Designating HTTP or HTTPS settings for Business Space.

      Restriction: Be aware that not all of the Process Portal functionality is available if you change the access settings to HTTP.

  20. Optionally configure Process Center to create process applications and use the features of version 8.0.1. Refer to Roadmap for install IBM BPM Advanced.

  21. Optional: Uninstall the source dmgr.

    Once the migration is complete, the migration source dmgr can be uninstalled.

  22. Remove Compatibility Mode.

    If you chose the compatibility option (which is the default), and if all your nodes are completely migrated to the target version, run the convertScriptCompatibility script from the target_INSTALL_ROOT/bin directory on the dmgr to remove compatibility.

    Use the following syntax:

    • convertScriptCompatibility.sh

    • convertScriptCompatibility.bat

    For more information about the convertScriptCompatibility command, see convertScriptCompatibility command in the WebSphere Application Server information center.


Results

The ND environment is migrated to the target version.


What to do next

Verify that the migration was successful. For instructions, see Verifying migration.

If your source version is 7.5.x, there are no additional or specific steps required to migrate Business Space data after you are finished with manually upgrading the product databases.

If you have an IBM Forms Server configured with your Business Space in the earlier releases, you must manually deploy the BSpaceForms.ear after the migration. Deploy the BSpaceForms.ear from the WASHome\installableApps\BusinessSpace directory to the application server.

Runtime migration procedures


Related tasks:

Plan the runtime migration
Migrating a profile using the profile migration wizard
Migrating a profile using the command-line utilities
Manually upgrading the product databases
Verifying migration
Configure a Process Server
Configure the Business Performance Data Warehouse component on a server or cluster
Configure the Process Server and Performance Data Warehouse
Upgrading existing databases
Start and stop individual resources


Related reference:

Runtime premigration checklist
BPMMigrateCluster command-line utility
installBRManager command-line utility
BPMConfigureProcessServer


Related information:

Configure external security providers