Create BPEL Process Dialog

2.123 Create BPEL Process Dialog

Use to create a BPEL process service component in a service-oriented architecture (SOA) composite application.

A BPEL process service component integrates a series of business activities and services into an end-to-end process flow. After creation, double-click the BPEL process icon in the SOA Composite Editor to get started with designing your component. How?

Element	Description
BPEL 1.1 Specification	Select to create a BPEL process service component that conforms to BPEL 1.1 specifications.
BPEL 2.0 Specification	Select to create a BPEL process service component that conforms to BPEL 2.0 specifications. This is the default selection.
Name	Enter a name for the BPEL process or accept the default name of `BPELProcessnumber`. The name you enter here becomes the file name for the BPEL and Web Services Description Language (WSDL) files in the Applications window. Always use completely unique names when creating BPEL processes. Do not create: A non-ASCII process name (for example, `৉ŔBPELProcess1`). The BPEL process name is used in directory and file names of the SOA project, which can cause problems. A process name that begins with a number (for example, `1SayHello`). A process name that includes a dash (for example, `Say-Hello`). Two processes with the same name, but with different capitalization (for example, `SayHello` and `sayhello`).
Namespace	Use the default namespace path or enter a custom path.
Directory	Specify a directory in which to place BPEL process service component artifacts or accept the default directory of `project_root_directory/SOA/BPEL`. You can change the directory path, but ensure that the directory is beneath the `SOA` folder (that is, `project_root_directory/SOA`). If you specify a directory outside of `SOA`, an error message is displayed and the BPEL process is not created.
Template	Select a template based on the type of BPEL process service component you want to design. A template provides a basic set of default files (`process_name.wsdl` and `process_name.bpel`) with which to begin designing your BPEL process service component.
Asynchronous BPEL Process	Creates an asynchronous process with a default receive activity to initiate the BPEL process service component flow and an invoke activity to asynchronously call back the client. This type is selected by default. More
Synchronous BPEL Process	Creates a synchronous process with a default receive activity to initiate the BPEL process service component flow and a reply activity to return the results. More
One Way BPEL Process	Creates a process with a one-way call interface definition.
Define Service Later	Select to create an empty BPEL process service component with no activities.
Base on a WSDL	Creates a BPEL process with an interface defined by an existing WSDL file. You must specify the WSDL Uniform Resource Locator (URL), port type, and callback port type to use.
Subscribe to Events	Creates a BPEL process in which you can subscribe to a business event. After selecting this option, the dialog refreshes to display the Delivery list for selecting a transaction type and an event table. Click the Add icon to select an event to which to subscribe. Your selection is then displayed in the event table where you can perform additional configuration. Consistency: Click the table row to select an option. If you select one and only one, there is exactly one delivery guaranteed. The event delivery is conducted in a global transaction. If you select guaranteed, at least one delivery is guaranteed. Event delivery is conducted in a local transaction. Durable: If you select yes, events are retained even if the subscriber is not running. If you select no, events are dropped if the subscriber is not running. Run as publisher: If you select yes, the subscriber has the event publisher's security identity. If you select no, the subscriber does not have the event publisher's security identity. Filter: You can also click the Filter icon to create a filter expression for the selected event. This selection launches the Expression Builder dialog.
Service Name	Accept the default value of `BPEL_process_name_client` or enter the name of the service this process is exposing. When you open an invoke, receive, OnMessage, or reply activity, the service name appears by default in the Partner Link field. This name is the same name as the partner link.
Expose as a SOAP Service	Select this checkbox to create a BPEL process service component that is automatically connected (wired) to an inbound simple object access protocol (SOAP) web service binding component. If you do not select this checkbox, the BPEL process service component is created as a standalone component in the SOA Composite Editor. You can explicitly associate the BPEL process service component with a service at a later time. This checkbox is selected by default.
Delivery	Set the persistence policy of the process in the delivery layer. This list enables you to specify a value for the `oneWayDeliveryPolicy` deployment descriptor property. This field is displayed if you select an asynchronous or one-way BPEL process in the Template list. The possible values are as follows: async.persist: Messages into the system are saved in the delivery store before being picked up by the service engine. async.cache: Messages into the system are saved in memory before being picked up by the service engine. sync: The instance-initiating message is not temporarily saved in the delivery layer. The service engine uses the same thread to initiate the message. If you select sync, the Transaction field is displayed.
Transaction	Set the transaction behavior of the BPEL instance for initiating calls. This list enables you to specify a value for the `Transaction` deployment descriptor property. This field is displayed if you select a synchronous BPEL process in the Template list. requiresNew: A new transaction is created for the execution, and the existing transaction (if there is one) is suspended. This behavior is true for both request/response (initiating) environments and one-way, initiating environments in which the Delivery list value (`oneWayDeliveryPolicy` property) is set to sync. required: In request/response (initiating) environments, this setting joins a caller's transaction (if there is one) or creates a new transaction (if there is no transaction). In one-way, initiating environments in which the Delivery list value (`oneWayDeliveryPolicy` property) is set to sync, the invoke message is processed using the same thread in the same transaction. notSupported: Business process activities are executed without any transaction. Note: This property does not apply for midprocess receive activities. In those cases, another thread in another transaction is used to process the message. This is because a correlation is needed and it is always done asynchronously.
Input	Accept the default input XSD schema or click the Search icon to select a different XSD. If you click the Search icon, the Type Chooser dialog appears. Browse the imported schemas and select the input element (for example, a purchase order). You can also import an existing schema or WSDL in the Type Chooser dialog.
Output	Accept the default output XSD schema or click the Search icon to select a different XSD. If you click the Search icon, the Type Chooser dialog appears. Browse the imported schemas and select the output element (for example, a purchase order).