Migrating the development environment

IBM BPM, V8.0.1, All platforms > Migrating and upgrading your IBM BPM environment > Migrating from previous versions > Migrating from Teamworks 6 > Migrating from Teamworks 6 to IBM BPM V8.0.1
Migrating the development environment

Follow these detailed steps to migrate the Teamworks 6 development environment to IBM BPM V8.0.1.

If you have applied Hot Fix 10 to your Teamworks Release 6.2 SP2 (6.2.2) installation, you need to uninstall the hot fix (remove materialized views) before migrating to IBM BPM V8.0.1.
The tw_author user must share the same password between the Process Center and the Process Sever, or the password check will fail when Process Designer connects with the migrated Process Server. If necessary, change the password of the tw_author user on the Process Center to match that of the tw_author user on the Process Server after the migration.

Migrate the Teamworks 6 development environment to IBM BPM V8.0.1 after completing the analysis and planning phases of the migration project. Do not attempt to migrate your development environment before running the Upgrade Readiness Check tool and addressing the problems identified by that tool.

Procedure

If not already installed, install the new version of IBM Process Center, following installation instructions for the Advanced or Standard edition of IBM BPM in the IBM BPM Information Center. You must perform a custom installation when migrating. Only the custom installation option includes the upgrade utilities that you need; the typical installation option does not include the upgrade utilities.

Complete necessary post-installation configuration tasks such as creating profiles (stand-alone profiles or one or more dmgr and managed node profiles) and creating your deployment environment. See Configuring IBM BPM for the Advanced or Standard edition of IBM BPM in the IBM BPM Information Center.
If it is not already started, start the server for IBM Process Center V8.0.1, which includes the Process Center Server and Performance Data Warehouse. Use the First steps console to start the server as described in the installation instructions for the Advanced or Standard edition of IBM BPM in the IBM BPM Information Center.
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 designated for the Process Center during installation.
Download IBM Process Designer from the Process Center Console as described in Installing the Process Designer.
Export all process assets from the Teamworks 6 development server.
Before exporting process assets, be sure that you send definitions to the Performance Server. If not, queries of performance data might not work as expected after the migration. To send definitions, select File > Send Definitions to Performance Server from the main menu in Teamworks Authoring Environment.

In Teamworks Authoring Environment, right-click a folder in the Library view and then select Export from the menu. It is best to export the entire Teamworks 6 library and then import into IBM BPM V8.0.1 as a single process application. See Refactor process assets per application for more information.
The export window lists the items selected for export. Click Add Items to add any items you want to add to the export file, and then click Next.
The export window lists all of the items to be exported; that is, all of the items that were selected in the previous window in addition to the items that those items depend on.
Click Next to specify the name for your export file.
Click Finish. The selected items are exported to a compressed archive file (ZIP).

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

Teamworks 6 security provider configuration Required IBM BPM V8.0.1 configuration
If you used the internal Lombardi security provider in conjunction with an external LDAP security provider (such as Active Directory) in Teamworks 6 Configure LDAP as instructed in Configure an LDAP security provider in the post-installation configuration topics for your edition of IBM BPM (Advanced or Standard) in the IBM BPM Information Center.
If you used only an external LDAP security provider in Teamworks 6 Configure LDAP as instructed in Configure an LDAP security provider in the post-installation configuration topics for your edition of IBM BPM (Advanced or Standard) in the IBM BPM Information Center. Additionally, you must delete all default Teamworks users and groups from your external LDAP security provider in your Teamworks 6 environment in order to avoid conflicts with the V8.0.1 security model. (Typically, default Teamworks users and groups begin with tw_ like tw_admin and tw_author.)
Analyzing Teamworks 6 process assets with the Upgrade Readiness Check tool and then revising those assets as necessary before migrating may 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 have been exported.

Import the Teamworks 6 assets into the new version of IBM Process Center.

In the Process Center Console, select the Process Apps tab.
Click the Import Process App option in the right margin of the Process Center Console interface.
In the Import Process App window, click the Browse button to locate the Teamworks 6 export file that you want to import. It is best to export the entire Teamworks 6 library and then import into IBM BPM V8.0.1 as a single process application. See Refactor process assets per application for more information.
Click the Next button to continue. The Process Center Console requests the information required to create the new process application to contain the imported assets.
Enter a name and an acronym for the new process application. The acronym for a process application must be unique and is limited to seven characters. IBM BPM uses the acronym as an identifier for this process application and the library items that it contains.
For example, when manipulating the items within the process application using the IBM BPM JavaScript API, you can use the acronym to specify the namespace of the items. Providing a description is optional. When you enter a description, you can view it in the Process Center Console by clicking the question mark next to the process application name.
Click the Import button to import the selected file. When the import completes, you can see the new process application listed in the Process Apps tab.
Click the Open in Designer option to view and refactor the imported assets.

When you import Teamworks 6 assets that contain ad hoc reports to the Process Center, you must add the tw_adhoc_report_authors Teamworks group manually and assign users and groups as needed. If you do not perform this step, you will receive an error when you try to view ad hoc reports from Process Portal, because no such group exists in the current repository.
Refactor the imported Teamworks 6 assets into process applications and toolkits by moving assets. (See Refactor process assets per application for recommendations regarding this task.)

Organize all assets required for a particular application into a single process application, ensuring that all necessary services, nested processes, and other items are available to the top-level BPDs that rely on those assets to run the implementations.
Move the process assets that were organized for re-use across applications in Teamworks 6 to toolkits. When you move items, those changes can affect existing implementations and other references.
For example, if the implementation for an activity is a nested process and you move the nested process without moving the BPD that contains the activity, whether the activity's implementation (reference to the nested process) is good or is broken depends upon where you move the nested process as described in the following table:

If you move the nested process to... The reference...
A new toolkit Is good because IBM BPM automatically creates a new dependency on the new toolkit.
An existing toolkit that the source process application is not currently using Is good because IBM BPM automatically creates a new dependency on the existing toolkit.
An existing toolkit that the source process application is currently using If there have been no changes to the destination toolkit since the most recent snapshot was created, the reference is good because Process Designer automatically creates a new snapshot of the toolkit and updates the existing toolkit dependency to the new snapshot. If there have been changes to the destination toolkit since the most recent snapshot was created, the reference is broken until you update the existing toolkit dependency to the new snapshot of the toolkit that Process Designer automatically creates.
A new or existing process application Is broken because process applications cannot depend upon each other. When moving assets to process applications, be sure to move all related items to avoid broken references. IBM BPM automatically resolves broken references when related items are not moved simultaneously.

By default, Process Designer moves all related items. If you analyze dependent items and choose to move only some of them, ensure that you understand all relationships before completing such an operation. In such cases, you should check both the source and destination process application or toolkit for validation errors.
When you have finished moving assets, test each process application by running it from beginning to end on the Process Center Server to ensure that all processes and services actually work. If you refactor in a way that breaks your implementations, the assets stored in the Process Center repository will not match the assets that you migrate in each runtime environment, making future fixes and enhancements to your processes extremely problematic.
Fix any broken implementations before starting to migrate your runtime environments.
Fix and test any issues that were identified by the Upgrade Readiness Check tool that were planned to be addressed after migrating the process assets.

Run your regression test suite to identify any issues that may have been introduced during this process.

: Migrating from Teamworks 6 to IBM BPM V8.0.1

Related tasks:
Migrating the runtime environments

Related information:
Changing the default password for tw_admin and tw_user

If you move the nested process to...	The reference...
A new toolkit	Is good because IBM BPM automatically creates a new dependency on the new toolkit.
An existing toolkit that the source process application is not currently using	Is good because IBM BPM automatically creates a new dependency on the existing toolkit.
An existing toolkit that the source process application is currently using	If there have been no changes to the destination toolkit since the most recent snapshot was created, the reference is good because Process Designer automatically creates a new snapshot of the toolkit and updates the existing toolkit dependency to the new snapshot. If there have been changes to the destination toolkit since the most recent snapshot was created, the reference is broken until you update the existing toolkit dependency to the new snapshot of the toolkit that Process Designer automatically creates.
A new or existing process application	Is broken because process applications cannot depend upon each other. When moving assets to process applications, be sure to move all related items to avoid broken references. IBM BPM automatically resolves broken references when related items are not moved simultaneously.