Developer Guide to BPEL Designer
The following sections describe, in order of their appearance:
In this release of the BPEL Designer, you can add Fault Handlers and Event Handlers to your BPEL process. Compensation and Termination Handlers are not supported.
The BPEL language provides the ability to catch and manage exceptions using fault handlers. For example, exceptions occur when web services return data different from what was expected. If faults are not handled, the entire BPEL process can be thrown into a faulted state. Therefore, to prevent the entire process from faulting, you can add fault handlers to catch and manage exceptions within particular scopes.
Each fault handler contains an activity that runs when there is an error. For example, a partner service is notified if an error has occurred. Fault handlers can be added to the entire process or to individual Scope elements.
You can attach one Fault Handler container to either the Process or the Scope element. Inside the Fault Handlers container, you can create several Catch activities configured to catch specific kinds of faults, or one Catch All handler element to catch all the exceptions not caught by specific handlers.
Use this element to intercept and deal with a specific kind of fault.
This element is used within an appropriate Fault Handlers container element.
The properties of the Catch element are defined in the Properties window. You can also right-click the element on the diagram and choose Properties. The available properties are:
Use the Catch All element to intercept and deal with all faults that are not caught by an associated catch element.
The Catch All element is used within a fault handler window along with one or more catch elements. It is defined within a Fault Handlers container element along with one or more catch elements.
There are no properties for the Catch All element. Its behavior is pre-defined and requires no property configuration.
There are no specific properties for the Fault Handlers container element. It is an element that provides containment for a collection or group of Catch and Catch All elements.
The whole Process as well as each individual Scope can be associated with a set of Event Handlers that are invoked concurrently if the corresponding event occurs. The actions taken within an Event Handler can be any type of activity, such as Sequence or Flow. The only immediate child of an Event Handler is Scope, so when you drag an element from the Palette into an Event Handler, it is automatically wrapped in Scope.
There are two types of events. First, events can be incoming messages that correspond to a request/response or one-way operation in WSDL. For instance, a status query is likely to be a request/response operation, whereas a cancellation may be a one-way operation. Second, events can be alarms that go off after user-set times.
The OnEvent element indicates that the specified event waits for a message to arrive. The interpretation of this tag and its attributes is very similar to a Receive activity.
A Correlations tab on the OnEvent element property editor enables you to examine or specify a correlation set.
The tab shows:
You can add a correlation set by clicking the Add button. For more information, refer to Defining a Correlation Set and Adding a Correlation Set to an Element.
The OnAlarm element specifies the deadline for or the duration of the nested Scope.
The properties of the OnAlarm element are defined in the Properties window, invoked by right-clicking the element on the diagram and choosing Properties. The available properties are:
There are no specific properties for the Event Handlers container element. It is an element that provides containment for a collection or group of OnEvent and OnAlarm elements.