BPEL Choreography Diagrams

Scope activites - provide the context which influences the execution behavior of their nested activities, and allow the definition of variables, partner, message exchanges, correlation sets, event handlers, fault handlers, a compensation handler, and a termination handler.

BPEL4WS 1.1 models scopes as standard composite processes.

Sequence activities - specify collections of activities that must be executed sequentially in lexical order. Use this tool if you need a "box" to gather your sequence activities.

BPEL4WS 1.1 can gather your sequence activities in a "box" modeled as a standard composite process with <<sequence>> stereotype.

Flow activities - specify a set of concurrent activities that must be executed concurrently. A link modeled as a flow with a link stereotype can express synchronization dependencies between activities. Use this tool if you need a "box" to gather your flow activities.

BPEL4WS 1.1 models flow activities as standard synchronizations with <<split>> or <<join>> stereotype. If you need to gather your flow activities in a "box", use a composite process with <<flow>> stereotype and create a nested flow activity.

While activities - specify that their nested activities must be repeated until their specified <condition> becomes true.

BPEL4WS 1.1 models while activities as standard composite processes with Loop implementation type and While loop type.

ForEach activities [WS-BPEL 2.0] - execute their scope for a specified count. The execution iterations can occur in parallel or in sequence.

RepeatUntil activities [WS-BPEL 2.0] - execute their contained activity at least once until their specified <condition> becomes true.

Wait activities - specify a delay for a certain period of time or until a certain deadline is reached.

BPEL4WS 1.1 models wait activities as standard processes with Generate event implementation type and Timer type event .

Compensate activities - cause all immediately enclosed scopes to be compensated in default order.

BPEL4WS 1.1 models compensate activities as standard processes with Generate event implementation type and Compensation type event.

Compensate scope activities [WS-BPEL 2.0] - cause one specified child scope to be compensated.

Throw activities - specify a business process which needs to signal an internal fault explicitly.

BPEL4WS 1.1 models throw activities as standard processes with Generate event implementation type and Fault type event.

Rethrow activities [WS-BPEL 2.0] - rethrow the fault that was originally caught by the immediately enclosing <catch> and <catchAll> elements within a <faultHandlers> element.

Receive activities - specify how the business process waits for a matching message to arrive.

BPEL4WS 1.1 models receive activities as standard processes with Execute operation implementation type and Receive request action type.

Reply activities - send responses to requests previously accepted through receive activities.

BPEL4WS 1.1 models reply activities as standard processes with Execute operation implementation type and Reply action type.

Reply fault activities - send faulted responses to requests previously accepted through receive activities.

BPEL4WS 1.1 models reply fault activities as standard processes with Execute operation implementation type and Reply fault action type.

Invoke activities - call Web Services offered by service providers.

BPEL4WS 1.1 models invoke activities as standard processes with Execute operation implementation type and Invoke operation action type.

Assign activities - update the values of variables with new data. The assign activity should be composed of at least one atomic assign task (see Process Properties).

BPEL4WS 1.1 models assign activities as standard processes with <<assign>> stereotype.

Validate activities [WS-BPEL 2.0] - validate the values of variables against their associated XML and WSDL data definition. Specify variables (see Variables (BPM)) in the ValidatedVariables tab.

Extension activities [WS-BPEL 2.0] - create activities, which are not defined by the specification.

Empty activities - specify activities that do nothing (for example a fault which needs to be caught and suppressed) or can provide a synchronization point in a flow activity. It is also used to model top-level processes in top-level diagrams (see Top-Level Diagrams

BPEL4WS 1.1 models empty activities as standard processes with no implementation type nor stereotype.

If activities - select exactly one activity to execute from a set of activities.

You can also use composite processes with <<if>> stereotype for modeling purposes.

BPEL4WS 1.1 models switch activities as standard decisions (see Decisions (BPM )) with <<switch>> stereotype.

Pick activities - wait for the occurrence of exactly one event from a set of events, then execute the activity associated with that event.

BPEL4WS 1.1 models pick activities as standard decisions (see Decisions (BPM )) with <<pick>> stereotype.

Exit activities - immediately end the business process instance.

BPEL4WS 1.1 models terminate activities as standard ends (see Ends (BPM )) with <<terminate>> stereotype.