Importing an Existing BPEL Process

ActiveVOS Designer User’s Guide

Importing an Existing BPEL Process

If you have created a BPEL process outside of ActiveVOS, you can import the BPEL and related files into your orchestration project. If your BPEL process in already in an Eclipse project, see Adding or Removing a Project Orchestration Nature.

Tips:

If your project was created prior to Version 7, it will be imported with classic ActiveVOS activity icons and will use the classic Process Editor. To work in the newer environment, BPMN modeling style, see BPMN and ActiveVOS Classic Edit Styles.
If you want to save a BPEL 1.1 process as a BPEL 2.0 process, see Migrating Processes from BPEL4WS 1.1 to WS-BPEL 2.0.

Select File>New>Orchestration Project, and click Next.
Type in a project name, and click Finish.
If you have xsd files, select the schema folder, and right-mouse click to select Import.
Select General>File System.
Browse to the directory where your XSD files reside. Import your xsd files into the schema folder.
Import your WSDL into the wsdl folder, or alternately use Service References, as described in Importing a Service Reference.
Import your BPEL into the bpel folder.
Double-click the BPEL file to open it in the Process Editor.

The file opens in the mode associated with the BPEL version: WS-BPEL 2.0 or BPEL4WS 1.1. It is opened in the modeling style, either BPMN or ActiveVOS classic, associated with the .vbpel file. For details on saving your file with a different stylesheet, see BPMN and ActiveVOS Classic Edit Styles.

Use the Problems view to correct any validation errors that occurred.

Note: If you import your BPEL process before you add the referenced WSDL and schemas, ActiveVOS reports validation errors until it locates an appropriate namespace for your process.

Note: If your WS-BPEL 2.0 process contains elements and attributes that are extensions to the WS-BPEL 2.0 specification, they are automatically declared. See Declaring Extension Elements and Attributes for details.