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 a stand-alone environment

The procedure for migrating stand-alone environments includes backing up the environment, migrating the stand-alone profile, and upgrading the product databases configured for the profile. The procedure contains variants for the different supported mechanisms of migrating a stand-alone environment, including side-by-side migration, remote migration, and operating system upgrade migration. Before migrating a stand-alone environment, determine which of these variants fits your requirements best.

Review Plan the runtime migration and the BPM runtime premigration checklist.


Procedure

Follow these steps to migrate a stand-alone environment.

  1. Install the migration target products.

    • For a side-by-side migration, install the target product and latest fix packs on the same system as the source product of the migration.

    • For a remote migration, install the target product and latest fix packs on the system that will serve as the target for the migration.

    • For an operating system upgrade migration, defer the installation until after the operating system is upgraded.

    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.

    Important: 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 V7 and V8.

    If you use DB2 for z/OS V7 or V8, and have not yet upgraded the database to a supported version of DB2 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.

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

    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. To do this, use the following procedure.
      1. Check the value for the ORACLE_JDBC_DRIVER_PATH variable in the previous environment. Use one of the following methods to do this:

        • In the administrative console, select Environment > WebSphere variables, then select the scope that matches the node of the source profile.
        • Navigate to the variables.xml file in the following directory: source_profile_root\config\cells\ cell_name\nodes\ node_name\.

        The cell name and node name must match the source profile information.

      2. Install the new ojdbc6.jar driver in the directory that is pointed to by the ORACLE_JDBC_DRIVER_PATH WebSphere variable. Use one of the following steps, depending on the location pointed to by the variable.

        • If the variable points to a directory outside of the IBM BPM installation, copy the odbc6.jar file into the same folder where the ojdbc14.jar or ojdbc5.jar file resides.

        • If the variable points to a directory within the IBM BPM installation, create the same directory structure in the IBM BPM V8.0.1 installation, and then copy the odbc6.jar file into that directory.

  4. Stop the migration source server.

    Stop the migration source server using the stopServer command from the profile_root/bin directory on the migration source system or from the profile's First steps console. Use the following syntax:

    • stopServer.sh server_name -username user_name -password password

    • stopServer.bat server_name -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, the -username and -password parameters do not have to be specified 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 not necessary.

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

  5. Back up the migration source profile.

    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.

  6. Back up the migration source product databases.

    Back up the following databases that are configured by the stand-alone profile according to the documentation for your database:

  7. Migrate the stand-alone server 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 9 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 12 to upgrade the Process Server (or Process Center) and Performance Data Warehouse databases.

    • Common Event Infrastructure and Messaging Engine databases:

  9. Migrate the instance data for Business Space if it is configured in the source environment. Perform the following step to update the data in the databases to work with V8.0.1.

  10. Update the data source configuration. If you have data sources using the 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. Start the migration target server.

      Start the migration target server using the startServer command from the profile_root/bin directory of the migration target server or from the target 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.

    2. Log in to the administrative console.
    3. Update the data source configuration using the following steps:

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

      3. Use the Test Connection option to check that the data source configuration works.
      4. Stop the migration target server.

        Stop the migration target server using the stopServer command from the profile_root/bin directory on the migration source system or from the profile's First steps console. Use the following syntax:

        • stopServer.sh server_name -username user_name -password password

        • stopServer.bat server_name -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, the -username and -password parameters do not have to be specified 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 not necessary.

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

  11. 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 WebSphere Process Server 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 IBM BPM 7.5 and have not configured Business Space, configure Process Portal using the procedure described in the section Configure the Process Server and Performance Data Warehouse.

    3. If you are migrating from IBM BPM 7.5 and have configured Business Space, configure Process Portal using the BPMConfigureProcessServer command from the profileName/bin directory. Use the following syntax:

      • BPMConfigureProcessServer.sh

      • BPMConfigureProcessServer.bat

  12. 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:

  13. Start the migration target server.

    Start the migration target server using the startServer command from the profile_root/bin directory of the migration target server or from the target 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.

  14. 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.
  15. Check the migration status.

    Use the BPMMigrationStatus command to verify the current state of the migration.

    For more information about the BPMMigrationStatus command, see the BPMMigrationStatus command.


Results

The stand-alone 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 concepts:

System requirements


Related tasks:

Plan the runtime migration
Migrating a profile using the profile migration wizard
Migrating a profile using the command-line utilities
Migrating a profile to a remote system
Migrating a server while upgrading an operating system
Manually upgrading the product databases
Migrating the Business Space V7.0.x database and data
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
Running SQL upgrade scripts


Related reference:

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