Using the Process Import Wizard for ARIS Imports
The Process Import Wizard works in a particular way for ARIS imports; there are a few considerations specific to the ARIS integration. If you are importing XPDL in the course of an ARIS import, follow these instructions.
To use the Process Import Wizard for an ARIS import
1. From the Select process project list, select an existing project into which to import the XPDL file. If you want to create a new process project for the XPDL file, click New Project to open the New Process Project dialog box.
2. From the Select an Integration Server list, select an Integration Server that will be the server for the steps in the imported process, and where the imported XPDL that refers to data will be located. If you need to configure Integration Servers, click the Configure Integration Server s link to open the Integration Servers preferences page.
3. If the XPDL file you are importing contains multiple WorkflowProcess constructs, Designer combines them all into a single process by default. The Create a single process model from multiple XPDL WorkflowProcess constructs check box is automatically selected. Clear the check box if you do not want Designer to create a single process from multiple WorkflowProcess constructs (see the notes below for more information).
Tip: | For processes coming from ARIS, you typically want to use the default values, since the WorkflowProcess constructs generally represent pools. |
Note: | To create a single process design for multiple XPDL WorkflowProcess constructs, each WorkflowProcess must be mapped to a pool in the XPDL file with a valid Process attribute (Process ID). Additionally, each pool must have specified size and coordinates. If these conditions are not satisfied, Designer creates multiple .process files as the default behavior. When this situation occurs, the event is recorded in the Import Log. |
Note: | If you clear the Create a single process model from multiple XPDL WorkflowProcess constructs check box, importing XPDL files containing multiple WorkflowProcess constructs results in multiple Designer processes (.process files). Multiple imported processes are automatically named based on identifying information (Name or ID) of the WorkflowProcess constructs in the XPDL file. |
4. Designer checks for duplicate step names during the import process, automatically incrementing each duplicate by 1 (Step, Step1, Step2, and so on). This protects against build errors due to duplicate step names. If you do not want your duplicate step names changed, clear the Enforce Step Name Uniqueness check box, which is selected by default. Click Next.
5. If the XPDL file being imported contains call activities that refer to child processes, Designer checks for the presence of these child processes in the Designer workspace. If they exist, the log reflects this fact and the import continues. If the referenced child processes do not exist in the workspace, Designer alerts you of this and lists these child processes. You must import them before importing the parent process. Click Cancel to stop the import wizard, then Accept implementation and Import new process for each child process listed.
6. When all referenced child processes of the parent call activity exist in the Designer workspace, Accept implementation and Import the parent process. Designer sets the Implementation of the call activity.
7. CentraSite is required for Web service exchange. If your database does not use CentraSite, skip to step 13.
8. If your database uses CentraSite and the XPDL file being imported contains references to Web services that implement activities, Designer displays the Web Service Descriptors page of the wizard. For each Web Service Descriptor (WSD) you want to use, click to select the browse button in the Run WSC wizard column in the row that contains it.
9. On the Web Service Descriptors page, select the Create Default Web Service Descriptors at <Project>.<Process> check box to automatically create and assign Web service connectors at the default location in the Integration Server namespace.
Designer searches for pre-existing matching Web Service Descriptors automatically. If a WSDL has already been imported as a part of this or another process, Designer locates it. If Designer finds any WSDs, it displays the Select Web Service Connector page of the wizard.
10. On the Select Web Service Connector page, do one of the following:
If you find a Web service connector (WSC) you want to use, click to select it and then click
OK to return to the Web Service Descriptors page.
If you do not find a WSC you want to use, click
Cancel to create a new Web Service Descriptor (WSD).
11. If you click Cancel to create a new Web Service Descriptor (WSD), Designer displays the New Web Service Descriptor page of the wizard. Provide the following information to create a new WSD:
Server | Integration Server Name, or Default for the defined default Integration Server |
URL | Integration Server URL |
Package | Integration Server package name |
Namespace | Select the parent namespace from the Integration Server tree |
Element name | New Web Service Descriptor (WSD) name |
12. Click Finish to create the new WSD. If you click Cancel, no WSD is created, and no WSC is assigned to the XPDL activity.
13. Click Finish to start the import.
