BPEL4WS 1.1 and WS-BPEL 2.0

BPEL4WS 1.1 (Business Process Execution Language for Web Services) and its successor WS-BPEL 2.0 (Web Services for Business Process Execution Language) are business process orchestration standards which let you describe your business processes under the form of Web services, and specify how they are connected to each other to accomplish specific tasks. PowerDesigner supports modeling for BPEL4WS 1.1 and WS-BPEL 2.0 and higher, including round-trip engineering.

1. Create a BPM with the process language set to BPEL4WS 1.1 or WS-BPEL 2.0.
   Note: You can generate a BPEL BPM from an analysis BPM (see Generating a BPEL Model from an Analysis Model) or reverse engineer BPEL files into a BPM (see Reverse Engineering BPEL Languages).

   A valid BPEL model must contain a top-level diagram with one or more top-level processes.
2. For each of your top-level processes, specify its partners and their interactions using organisation units (see Organization Units ( BPM)) and role associations (see Role Associations (BPEL)) respectively.
3. Import a WSDL file you own or one you have found published in a UDDI server (see Importing a Service Provider from a WSDL File) to retrieve service description objects (service providers, service interfaces, and operations). You can also create these objects from scratch (see Service Providers (BPM), Service Interfaces (BPM), and Operations (BPM)).
4. Drill down in the choreography diagram into which each of your top-level processes is decomposed.
5. For each process within each top-level process, assign a partner using an organisation unit (see s), and specify its implementation (see Process Properties).
6. Complete your process choreography by creating any appropriate additional processes (for example to catch a fault or compensate an error), and specify how you want to manage data in the exchanged messages using variables, data transformations and correlation keys.
7. [optional] Decompose one or more processes you want to analyze in more detail (see Decomposing Processes).
8. [optional] Generate BPEL code from your BPM objects to be interpreted by orchestration engine (see Generating BPEL Code).

• Top-Level Diagrams (BPEL)
  A top-level diagram is a special form of business process diagram required by BPEL models, which provides a high-level representation of a system and identifies its business partners in order to specify the scope of the system and its interactions with those partners.
• Choreography Diagrams (BPEL)
  BPEL choreography diagrams help you analyze the control flow between your activities when modeling a BPEL environment.
• Activities (WS-BPEL 2.0)
  PowerDesigner provides support for all the activities defined in WS-BPEL 2.0 and provides custom symbols and tools to create them.
• Activities (BPEL4WS 1.1)
  PowerDesigner provides support for all the activities defined in BPEL4WS 1.1.
• Messages (BPEL)
  The PowerDesigner BPM provides support for the following elements to build messages in a choreography diagram, when modeling a BPEL environment.
• WS-BPEL 2.0 Object Properties
  WS-BPEL 2.0 object property sheets contain additional properties on the WS-BPEL tab.
• BPEL4WS 1.1 Object Properties
  BPEL4WS 1.1 object property sheets contain additional properties on the BPEL4WS tab.
• Generating a BPEL Model from an Analysis Model
  You can generate from an analysis to a BPEL model in order to model the implementation of the processes. For example, once the Analysis team has designed the analysis model, the model can be submitted to the Development team for implementation. You can propagate subsequent changes made to the source model by repeating the generation and selecting the Update Existing Model option.
• Generating BPEL Code
  You can generate BPEL code from BPM objects that can be interpreted by any orchestration engine. A separate .BPEL file per each top-level process is generated, and contains the process descriptions. A .WSDL file (process language definition file) for the entire model is also generated.
• Reverse Engineering BPEL Languages
  You can reverse engineer .BPEL files, WSDL files, and .XML files containing a BPEL definition into a BPM. The WSDL definitions contained in the .BPEL files are reversed into service providers.