BPEL 1.1 Model
Enterprise Architect uses BPMN 1.1 as a graphical front-end to capture BPEL 1.1 Process description (as BPEL 1.1 does not have a standard graphical notation). Enterprise Architect uses the partial mapping specified in the OMG BPMN 1.1 Specification to map BPMN 1.1 constructs to BPEL 1.1.
Create a BPEL 1.1 Model
|
|
|
|
Create a BPEL 1.1 Package Structure.
Alternatively:
- Create a Package in the Project Browser
- Click on the 'New Diagram' icon in the Project Browser
- Select 'BPMN 1.1' in the 'Select From' field and 'BPEL' in the 'Diagram Types' field
- Click on the 'BPEL Process' icon from the BPMN 1.1 Core toolbox and drag it into the created BPEL diagram
|
BPEL 1.1 Package Structure
Project Browser Toolbar
|
|
Open the BPEL diagram under the <<BPELProcess>> stereotyped element.
|
|
|
Model the BPEL Process using the constructs in the BPMN 1.1 Core page of the Diagram Toolbox; use these constructs in each Toolbox page to model BPEL 1.1:
BPMN 1.1 - Core page:
- BPEL Process
- Activity
- Start Event
- Intermediate Event
- End Event
- Gateway
- Pool
BPMN 1.1 - Relationships page:
- Sequence Flow
- Message Flow
- Association
BPMN 1.1 Types page:
- Assignment
- Condition
- Message
- Participant
- Web Service
|
BPMN 1.1 Core Toolbox
Model BPEL 1.1 Process
|
|
Create Web Service for the BPEL Process and other related Pools, if required.
|
BPEL Web Service
|
|
Generate BPEL 1.1 code from the BPEL Process.
|
Generate BPEL 1.1
|
Notes
- Generating BPEL 1.1 from a BPMN 1.1 model is supported in the Unified and the Ultimate editions of Enterprise Architect
- Ensure that BPMN 1.1 Technology is enabled in the 'MDG Technologies' dialog ('Specialize > Technologies > Manage')
BPEL 1.1 Example
- The Enterprise Architect Example file (EAExample.EAP) has a sample BPMN 1.1 model from which BPEL 1.1 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 1.1 model Package is in: Example Model > Analysis and Business Modeling > BPEL Example > BPEL 1.1 Model
Modeling Restrictions
- Every BPEL Process and Sub-Process should start with a Start Event and end with an End Event
- A Start Event or an End Event should not be attached to the boundary of a Sub-Process
- Sequence Flow Looping is not supported - only Activity looping is supported; all Sequence Flows should flow downstream and not upstream
- Mapping of an Intermediate Event with multiple triggers to BPEL 1.1 is not supported
- Mapping of Multi-Instance Parallel While loops to BPEL 1.1 is not supported
- Mapping of Independent Sub-Process to BPEL 1.1 is not supported
- Pools are treated as black box (that is, they do not expose any details) and hence they cannot contain any child elements or have any incoming/outgoing Sequence Flow connectors