BPEL Deployment Descriptor Editor

Before a BPEL project can be deployed to the runtime engine, you must create what is called a deployment descriptor. This is simply a manifest file, serialized as XML, that describes all of the BPEL processes and their interfaces to the BPEL engine. The deployment descriptor file must be created in the root folder of your project. See New BPEL Deployment Descriptor more information.

The deployment descriptor editor traverses the folder hierarchy in your project and searches for all BPEL files. Each process is then represented in a separate tab in the editor. The figure below shows two processes (HelloWorld and GoodbyeWorld). Each process must be configured before the project can be deployed.

Deployment descriptor editor example

Deployment descriptor editor example

  1. Process selection tabs: Click on these tabs to display the configuration page for each process.
  2. Initial process state: The process can be deployed in either an active, inactive or retired state.
  3. Inbound interfaces selection: Select the WSDL port type that clients will use to invoke this service.
  4. Output interfaces selection: Each invoked service (if any) will require you to select its port type.
  5. Process-level monitoring events: Allow you to select which events are generated by the BPEL engine. This is currently unused but will be used in future for debugging the process.
  6. Scope-level monitoring events: The BPEL engine can be configured to generate monitoring events for each Scope defined in the process.

The only action required to configure a processes is to select the interfaces for inbound and outbound services used by the process; all other settings are optional.