Modeling for BPEL Languages

PowerDesigner supports the modeling of all the components required to deploy a BPEL solution in your environment.

  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 Other Models from a BPM) or reverse engineer BPEL files into a BPM (see Reverse Engineering Source Files into a BPM).
    A valid BPEL model must consist of 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 (BPM)) 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 Attaching Processes to Organization Units), 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 for BPEL Languages).
Parent topic: BPEL4WS and WS-BPEL