Configuring the target IBM Business Process Manager V8.5.6

Configure the target IBM® Business Process Manager V8.5.6 for migrating from Teamworks 6.

Before you begin

You must have completed the following tasks:

Installed IBM Business Process Manager V8.5.6
Installed the required interim fixes if you are running V8.5.0.0 and have not upgraded to V8.5.0.1 or later
Configured the deployment environment in the target environment

If you applied Hot Fix 10 to your Teamworks Release 6.2 SP2 (6.2.2) installation, you must uninstall the fix (remove materialized views) before you migrate to IBM BPM.

The deployment environment administrator user must share the same name and password between Process Center and Process Server, or the password check fails when Process Designer connects with the migrated Process Server.

About this task

Upgrade the Teamworks 6 development environment to IBM BPM after you complete the analysis and planning phases of the migration project. Do not attempt to upgrade your development environment before you run the Upgrade Readiness Check tool and address the problems identified by that tool.

Procedure

If it is not already started, start the server for IBM BPM, which includes the Process Center Server and Performance Data Warehouse.
Verify that the Process Center console can be accessed by opening your web browser to http://[host_name]:[port]/ProcessCenter. Provide the name of the host on which the server is installed and the port that was designated for Process Center during installation.
Download IBM Process Designer from the Process Center console as described in Installing IBM Process Designer.

If you use an external LDAP security provider (such as Active Directory), complete configuration for your development environments as described in the following table.

Teamworks 6 security provider configuration	Required IBM BPM configuration
If you used the internal WebSphere® Lombardi Edition security provider in conjunction with an external LDAP security provider (such as Active Directory) in Teamworks 6	Configure LDAP as instructed in Configuring the user registry.
If you used only an external LDAP security provider in Teamworks 6	Configure LDAP as instructed in Configuring the user registry. Additionally, you must delete all default Teamworks users and groups from your external LDAP security provider in your Teamworks 6 environment to avoid conflicts with the IBM BPM security model. (Typically, default Teamworks users and groups begin with `tw_` like `tw_admin` and `tw_author`.) Note: Analyzing Teamworks 6 process assets with the Upgrade Readiness Check tool and then revising those assets as necessary before migration might take a few days or weeks, depending on your particular environment. You must keep your Teamworks 6 development environment up and running until your assets are ready for export. To do so, use the internal Teamworks security provider or a different external LDAP security provider in your Teamworks 6 environment until all assets are exported.

Teamworks 6 security provider configuration

Required IBM BPM configuration

If you used the internal WebSphere® Lombardi Edition security provider in conjunction with an external LDAP security provider (such as Active Directory) in Teamworks 6

Configure LDAP as instructed in Configuring the user registry.

If you used only an external LDAP security provider in Teamworks 6

Configure LDAP as instructed in Configuring the user registry. Additionally, you must delete all default Teamworks users and groups from your external LDAP security provider in your Teamworks 6 environment to avoid conflicts with the IBM BPM security model. (Typically, default Teamworks users and groups begin with tw_ like tw_admin and tw_author.)

Note: Analyzing Teamworks 6 process assets with the Upgrade Readiness Check tool and then revising those assets as necessary before migration might take a few days or weeks, depending on your particular environment. You must keep your Teamworks 6 development environment up and running until your assets are ready for export. To do so, use the internal Teamworks security provider or a different external LDAP security provider in your Teamworks 6 environment until all assets are exported.