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

Configure the Process Server and Performance Data Warehouse

You can configure your migrated environment with the Process Server and the Performance Data Warehouse components that form part of IBM BPM V8.0.1.

Before you begin

Important: If you are using a version of DB2 earlier than 9.5.0.7, you must upgrade to version 9.5.0.7 or later. Once you have created a database, make sure the utilities in db2ubind.lst and db2cli.lst bind to that database.

Procedure

1. Create the Process Server database, Performance Data Warehouse database, and Business Space database. Refer to Creating databases and database design files.

   1. If the source version is 6.2.x or 7.0.x, you must create the Process Server database and Performance Data Warehouse database.

   2. If the source version is 7.5, it is not necessary to create the Process Server database or Performance Data Warehouse database.

   3. If Business Space is not configured in the source environment, you must create the Business Space database.

2. Create the database design file by using the database design tool (DBDesignGenerator) in the install_root/util/dbUtils location. Refer to Creating databases and database design files.

   1. Select the bpm.standard.standalone or bpm.standard.nd database pattern for configuring database components of the Process Server, Business Space, and Performance Data Warehouse.

   2. If the source version is 6.2.x or 7.0.x, ensure that the database design file contains the Process Server and Performance Data Warehouse database information.

   3. If Business Space is not configured in the source environment, ensure that the database design file contains the Business Space database information.

3. Configure the Process Server, Performance Data Warehouse, and Process Portal using the BPMConfigureProcessServer command from the install_root/profiles/profileName/bin directory.

   Use the following syntax to configure the Process Server, Performance Data Warehouse, and Process Portal on a server or in a cluster:

   • 

     BPMConfigureProcessServer.sh -dbDesign /opt/bpm.standard.standalone.dbDesign

   • BPMConfigureProcessServer.bat -dbDesign C:\bpm.standard.standalone.dbDesign

   The default deployment targets for the Process Server, Performance Data Warehouse, and Process Portal components in a ND environment are as follows:

   • One Cluster - Process Server, Performance Data Warehouse, and Process Portal are deployed to the only cluster: the application cluster.

   • Two Clusters - Process Server, Process Portal, and Performance Data Warehouse are deployed to the application cluster; all the bus members are deployed to the messaging engine cluster.

   • Three Clusters - Process Server is deployed to the application cluster; Process Portal and Performance Data Warehouse are deployed to the support cluster; all the bus members are deployed to the messaging engine cluster.

   • Four Clusters - Process Server is deployed to the application cluster; Performance Data Warehouse is deployed to the support cluster; Process Portal is deployed to the web cluster; all the bus members are deployed to the messaging engine cluster.

   For a detailed description of the command, see BPMConfigureProcessServer in the reference documentation.

4. If the source version is WebSphere Process Server V6.2.x or V7.0.x, run the bootstrapProcessServerData command from the profileName/bin directory to load configuration data into the Process Server database. This data is required in order for the BPM applications to run correctly.

   1. To bootstrap data into a cluster:

      • 

        bootstrapProcessServerData.sh -clusterName myAppCluster

      • bootstrapProcessServerData.bat -clusterName myAppCluster

   2. To bootstrap data into a standalone default profile server:

      • 

        bootstrapProcessServerData.sh

      • bootstrapProcessServerData.bat

Parent topic: Runtime migration subprocedures

Related tasks:
Creating database design files for DB2
Creating database design files for Oracle
Creating database design files for DB2 for z/OS
Creating database design files for SQL Server
Migrating an ND environment with full downtime
Migrating an ND environment with minimal downtime
Migrating a stand-alone environment

Related reference:

BPMConfigureProcessServer command