Index Changes
This is version 22. It is not the current version, and thus it cannot be edited.
[Back to current version]   [Restore this version]

Using the BPEL Designer and Service Engine

Contents


Features of the BPEL Designer and Service Engine


BPEL Service Engine Features

Following features are supported by the BPEL Service Engine:
  • Standard JBI 1.0 engine component
  • Supports BPEL 2.0
  • Provides and consumes web services defined by using WSDL 1.1
  • Exchanges messages in JBI-defined XML document format for wrapped WSDL 1.1 message parts
  • Implements endpoint status monitoring
  • Supports multiple-thread execution
  • Supports debugging of business processes
  • Supports database persistence of business process instances for reliable recovery from system failure
  • Supports load balancing and failover when clustered

Supported WS-BPEL 2.0 Constructs

The following table provides a list of WS-BPEL 2.0 language constructs that are implemented by the BPEL Service Engine.

NOTE: This table is a work in progress and has not been reviewed. Until it has been reviewed all support is pending.

FeatureSupported ElementsSupported AttributesAlso Supported
Process
- WS-BPEL 2.0 process root element
The Process element present in the
BPEL Designer diagram by default.
extensions
import
partnerLinks
variables
correlationSets
faultHandlers
eventHandlers
name
targetNamespace
empty (element)
invoke (element)
Invoke
- Invokes a one-way or request-response
operation on a portType offered by a
partner. It enables the business process
to send messages to partners. The
operation is defined in the partner's
WSDL file.
correlations
toPart
\ fromPart
partnerLink
portType
operation
inputVariable
outputVariable
CorrelationWithPattern
request (enumeration value)
response (enumeration value)
request-response (enumeration value)
Receive
- Allows the business process to do a
blocking wait for a particular message
to arrive.
correlations
fromPart
partnerLink
portType
operation
variable
createInstance
messageExchange
Reply
- Returns a message from the process
to the same partner that initiated the
operation. The combination of Receive
and Reply activities creates a
request-response operation.
correlations
toPart
partnerLink
portType
operation
variable
faultName
messageExchange
Assign
- Assigns values to variables. You
use the Assign element to copy data
from one variable to another, construct
and calculate the values of expressions,
and store new data in variables.
Expressions are required to perform
simple computation or operate message
selections, properties, and literal
constants to produce a new value for
variables.
copy (element ref)
From
- Indicates a source.
literal
variable
part
To
- Indicates a destination.
variable
part
Wait
- Waits for a specified time or until
a deadline is reached.
for
until
Throw
- Used to signal a specific internal
fault, and can provide a QName and
information for that fault.
faultName
faultVariable
exit (element)
Empty
- Used as a placeholder within a process
to catch and suppress faults or to
help synchronize actions within a flow
activity that are executed concurrently.
Sequence
- Used to nest a series of activities
in a process. Activities within a
sequence execute in strict sequential
order, completing when the last
activity within the nest has finished.
Flow
- Defines a set of activities that
will execute concurrently (in parallel).
This is a structured activity, containing
other activities separated into
individual control paths or branches.
You can embed as many paths in the
activity as you want, and they will
all be executed simultaneously.
activity (group ref)
If
- Supports conditional behavior of a
business process instance. The If activity
consists of conditional branches defined
by the If and Else If elements, followed
by an optional Else branch. The conditions
on If and Else If branches are evaluated in
the order they appear. During execution,
the first branch whose condition holds true
is taken and provides the activity specified
for the If activity. In other words, if there
are several Else If branches whose
conditions hold true, only the first
of them will be executed.
elseif
condition
activity (group ref)
While
- Repeatedly execute one or more activities
as long as specific conditions are in
place at the beginning of each iteration.
condition
activity (group ref)
RepeatUntil
- Repeatedly executes one or more
activities as long as specific conditions
are in place after the execution of
each iteration. This element contains
other elements that are repeated until
the success criteria you specify are
met. If the condition you specify leads
to true, the activities listed will be
executed once.
condition
activity (group ref)
Pick
- Blocks a process and waits until
a specified events occurs. After
one of the specific event occurs, the
activity associated with this event
is performed. The possible events are
the arrival of a message or a timer-based
alarm. The selected activity is dependent
upon which event occurs first.
onMessage
onAlarm
createInstance
OnMessage
variable
activity (group ref)
OnMsgCommon fromPart
correlations
partnerLink
portType
operation
messageExchange
OnAlarmPick
- Specifies an event that is triggered
when a given duration variable is
exceeded.
forOrUntilGroup (group ref)
activity (group ref)
Scope
- Essentially, this activity is a collection
of child activities that can have their
own Variables, Fault and Event Handlers,
and correlation sets. The Scope activity
provides the behavior context for the child
elements.
variables
faultHandlers
eventHandlers
activity (group ref)
ForEach
- Repeatedly execute its contained
scope activity exactly N+1 times
where N equals the Final Counter Value
minus the Start Counter Value.
startCounterValue
finalCounterValue
completionCondition
counterName
CompletionCondition countCompletedBranchesOnly
Import
- Used within a process to clearly express
dependency upon external XML Schema or
WSDL definitions. The Process element
can have any number of Import elements
as initial children, preceeding any other
child element.
namespace
location
importType
PartnerLink
- Identifies the parties that interact with
your business process. Each link is
defined by a partner link type and a
role name.
name
partnerLinkType
myRole
partnerRole
FaultHandlers
- Defines the activities that are executed
as a response to faults resulting from
invoked services.
catch
catchAll
Catch
- Used to intercept a specifically
defined type of fault.
faultName
faultVariable
faultMessageType
faultElement
EventHandlers
- Invokes a specific action concurrently
with a specified corresponding event.
onEvent
onAlarm
OnEvent
- Indicates that a specified event is
triggered when a message arrives.
messageType
variable
scope (element ref)
Variable
- Supplies the mechanism used to hold
messages that make up the state of a
business process.
name
messageType
type
element
Activity name
Correlation
- Tracks the multiple long-running
exchanges of messages that typically
take place between a BPEL process and
its partner services. The correlation
mechanism helps to route messages to
appropriate process instances.
yes (enumeration value)
join (enumeration value)
- Join is understood,
but is expected to be
in a receive that is
within a flow, and
that can create an instance.
no (enumeration value)
property
- Defines a unique name and associates
it with an XML Schema simple type.
name
type
element
propertyAlias
- Defines a globally named property as
an alias.
query
propertyName
messageType
part
PartnerLinkType
- Expresses the dependences between
services by defining each service's
role.
role
-
name
Role
- Specifies one WSDL portType.
name
portType


Previous Next

JSPWiki v2.4.100
[RSS]
« Home Index Changes Prefs
This particular version was published on 23-Mar-09 11:33 AM, -0700 by rjacobus