Prev | Next |
BPEL 2.0 Model
Enterprise Architect uses BPMN 2.0 as a graphical front-end to capture BPEL 2.0 Process description (as BPEL 2.0 does not have a standard graphical notation). Enterprise Architect uses the partial mapping specified in the BPMN 2.0 specification to map BPMN 2.0 constructs to BPEL 2.0.
Map Constructs
Step |
Action |
See also |
---|---|---|
1 |
Create a BPEL 2.0 Package Structure. Alternatively:
|
Create BPEL 2.0 Model Structure Browser Header Bar |
2 |
Open the BPEL diagram under the <<BPELProcess>> stereotyped element. |
|
3 |
Model the BPEL 2.0 Process using the constructs on the 'BPMN 2.0 - Business Process' Toolbox pages. BPMN 2.0 - Business Process page:
BPMN 2.0 - Business Process Connectors page:
BPMN 2.0 Types page:
|
BPMN 2.0 Business Process Toolbox Pages Model a BPEL 2.0 Process |
4 |
Create Web Service Operations for the BPEL Process and other related Pools, if required. |
Create BPEL 2.0 Web Service Operation |
5 |
Generate BPEL 2.0 code from the BPEL Process. |
Generate BPEL 2.0 |
Notes
- Generating BPEL 2.0 from a BPMN 2.0 model is supported in the Unified and Ultimate editions of Enterprise Architect
- Enable the BPMN 2.0 Technology in the 'MDG Technologies' dialog ('Specialize > Technologies > Manage-Tech')
BPEL 2.0 Example
- The Enterprise Architect Example file (EAExample.EAP) has a sample BPMN 2.0 model from which BPEL 2.0 can be generated
- If you have installed Enterprise Architect at the default location, open this file: C:\Program Files\Sparx Systems\EA\EAExample.EAP
- The BPMN 2.0 model Package is in: Example Model > Analysis and Business Modeling > BPEL Example > BPEL 2.0 Model
Modeling Restrictions
- Every BPEL Process and Sub-Process should start with a Start Event and end with an End Event
- Boundary Start and End Events are not supported
- Sequence Flow Looping is not supported in both Normal and Exception Paths
- All Sequence Flows should flow downstream and not upstream
- Sub-Process cannot be a Loop node and have boundary Intermediate Events
- Event Sub-Process cannot act as a Loop Node
- Assignments are not supported on:
- Start Events on Event Sub-Processes
- End Events
- Sub-Processes
- Boundary Intermediate Events
- Gateways
- Tasks and Intermediate Events that immediately follow an XOR Event Gateway - Exception Path has to merge back into the Normal Path
- An exception to this rule is boundary Compensation Intermediate Event, which should have a BPMN 2.0 Association to a Compensation Activity (that has no incoming or outgoing Sequence Flows)
- Multiple Exception Paths from an Activity must join at the same location in the Normal Path
- An Exception Path should not cross another Exception Path
- Activities in an Exception Path cannot have boundary Intermediate Events
- Pools are treated as black boxes (that is, they do not expose any details) and hence they cannot contain any child elements or have any incoming/outgoing Sequence Flow connectors