Importing and refactoring artifacts into the target environment

After you export the artifacts from Teamworks 6, import them into the IBM® Business Process Manager V8.5.6 environment.

About this task

In general, you should import the entire Teamworks 6 library into IBM BPM as a single process application. The folder hierarchy from the Teamworks 6 import is reproduced in tags in the resulting process application. You can then use these tags to quickly move process assets to appropriate process applications and toolkits.

After you import Teamworks 6 assets into IBM BPM, refactor process assets carefully. For example, organize all assets that are required for a Billing Disputes process 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. Process assets that were organized for reuse across processes in Teamworks 6 can be moved to toolkits in IBM BPM.

When you import the illustrated Teamworks 6 library into a single process application in IBM BPM, the folder hierarchy from Teamworks 6 is reproduced in tags. These tags make it easy to move items to new process applications or toolkits. For the example Teamworks 6 library, start by moving the common components to a new toolkit in IBM BPM. To do so, open your single imported process application in IBM Process Designer, click the All category, and sort by Tag. Click the Acme Common group header to highlight everything in that tag, right-click, select the Move items to menu option, and then select New toolkit. IBM BPM automatically creates a reference to the new toolkit, and all references to these items from the original process application remain intact. Then, when you move the items for the processes (Billing Disputes and Vendor Inquiry) to new process applications by using the available tags, the new process applications also include the necessary references to this toolkit.

When you choose one or more items to move, IBM Process Designer displays all dependencies for the selected items. For example, if you choose a BPD that you want to move and that BPD depends upon several participant groups, services, and business objects for its implementations, Process Designer displays all the items that the BPD depends upon so that you can easily see all items to be included in the move operation. You also have the option of choosing the specific items to include in the move operation. Moving dependent items together ensures that you have a functional implementation in the destination process application or toolkit.

Procedure

Import the Teamworks 6 assets into the new version of IBM Process Center.
1. In the Process Center console, select the Process Apps tab.
2. Click the Import Process App option in the right margin of the Process Center console interface.
3. In the Import Process App window, click Browse 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 as a single process application.
4. Click Next to continue. The Process Center console requests the information that is required to create the new process application to contain the imported assets.
5. Enter a name and an acronym for the new process application. The acronym for a process application must be unique and is limited to 7 characters. IBM BPM uses the acronym as an identifier for this process application and the library items that it contains. For example, when you are 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.
6. Click Import to import the selected file. When the import completes, you can see the new process application listed in the Process Apps tab.
7. 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. Otherwise, you 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.

Organize all assets that are 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 reuse 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 Process Designer automatically creates a new dependency on the new toolkit.
An existing toolkit that the source process application is not currently using	Is good because Process Designer automatically creates a new dependency on the existing toolkit.
An existing toolkit that the source process application is 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 you are moving assets to process applications, be sure to move all related items to avoid broken references. Process Designer automatically resolves broken references when related items are not moved simultaneously.

Note: 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 you complete 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 work. If you refactor in a way that breaks your implementations, the assets that are 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 difficult.
Fix any broken implementations before you start 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 were introduced during this process.