# New BPEL Process File

The New BPEL Process File Wizard allows to create a BPEL process based on one of several templates defined by the wizard. The wizard assumes the new BPEL process is to be created in the currently selected project of the Project Explorer or Navigator view. If a BPEL process of the same name already exists within the project, a warning message will be displayed before any action is performed.

New BPEL Process

The first page includes the following options:

New BPEL Process file wizard. First page options.

Field | Description | Default
--- | --- | ---
Name | Enter the process name. | no default value
Namespace | Enter the namespace URL. All namespaces should follow the W3C recommendation (http://www.w3.org/1999/10/nsuri). | no default value

Template

Select one of the provided templates:

- Asynchronous BPEL Process - generates the basis of orchestration logic: receive and reply activities are included into the process; client WSDL is generated, service is defined in the class="property">parentlink of the process. The caller is notified asynchronously when the process completes.
- Empty BPEL Process - list of services participating in this BPEL process together with the one of messages used within the process is empty.There are no any orchestration logic.
- Synchronous BPEL Process - similar to Asynchronous BPEL Process template except the fact that here the caller is notified synchronously when the process completes.

Asynchronous BPEL Process

Abstract Process | Specifies the created process as an abstract one -partially specified processes that are not intended to be executed. | unchecked

The second page of the wizard defines the process interface (WSDL file) including the web service address, port definition and protocol. The wizard will populate all of these fields with appropriate default values based on the information provided on the previous page.

New BPEL Process

The second page includes the following options:

New BPEL process file wizard. Second page options.

Field | Description | Default
--- | --- | ---
Service Name | Enter a WDSL service name for the BPEL process. | The process name
Port Name | Enter a WDSL port name for the BPEL process. | The process name + 'Port'
Service Address | Enter an address of the WDSL service for the BPEL process. | http://localhost:8080/ + process name
Binding Protocol | Choose the binding protocol that you use in the WDSL: SOAP or HTTP | SOAP

The final page allows you to select the target project and folder for the new process artifacts. If a process with the name you provided already exists in that project and folder, the wizard will display an error message.

If the project is not a BPEL Project (does not define a BPEL facet) the wizard will display a warning message. You can still create the BPEL process, however it will not be deployable to a BPEL runtime engine until the BPEL facet has been added to the project (see the Help menu for more information about project facets).

## Important

BPEL artifacts must be contained somewhere within the `bpelContent` folder hierarchy if you intend to deploy the process. Complex projects may be organized into a folder hierarchy, but these folders must be contained within `bpelContent`.

The `Deployment Descriptor` file must be contained within the `bpelContent` folder and at the root of any folder hierarchy.

New BPEL Process

You will be asked if you wish for the BPEL perspective to be opened once this wizard completes.