Importing files from Teamworks 6

You can import files from Teamworks 6 using the Process Center console.

About this task

When you import files from Teamworks 6, be aware of the following:

You can import Teamworks 6 export files with any extension such as .zip, .export, and so on.
You must import the files using the Process Center console, as described in the following procedure. Command-line import is not supported.
Teamworks 6.2 (and earlier) exports can be imported.
All library items within a single export file are placed into a new process application, as described in the following procedure.
Each imported library item is tagged with the folder name in which it was stored in Teamworks 6. The tags enable you to easily find library items by clicking a category in the library and then using the drop-down menu to switch to the Tag option.
Before importing large export files, ensure that the log level for the Process Designer is set to error and not debug. By default, the log level is set to error. You can change the log level in the SystemOut.log file. Use the WebSphere Application Server administrative console to modify the log file settings (as described in "Log and trace settings").
If you experience problems importing large exports from Teamworks 6 and the error log file contains Out Of Memory error messages, switching from a 32-bit JVM to 64-bit JVM can resolve this problem. Contact IBM Customer Support for further assistance.

Procedure

To import files from Teamworks 6:

In the Process Center console, select the Process Apps tab.
Click Import Process App.
In the Import Process App window, click the Browse button to locate the export file that you want to import.
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. The acronym is used 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. You can grant access to other users by managing access to process applications and toolkits as described in Managing access to the Process Center repository.

Administrators can see a log of all imports by clicking the Admin option at the upper right of the Process Center console and then clicking Import and Export Log.
Click the Open in Designer option to view and edit the imported assets.

What to do next

When you import files from Teamworks 6, all library items are placed into a single process application. For larger imports, examine the resulting process application and move groups of related items to other process applications and toolkits, according to an organization that makes sense for your development efforts. For example, if the imported file includes multiple library items to be shared across projects, move those library items to a toolkit, following the directions provided in Copying or moving library items.

When you are finished organizing library items in individual process applications and toolkits, verify the implementation and data mappings of activities and services to ensure that all required implementations have been properly updated to reflect their new location.