Table of Contents

Search

  1. Preface
  2. Welcome to Informatica Process Developer
  3. Using Guide Developer for the First Time
  4. Getting Started with Informatica Process Developer
  5. About Interfaces Service References and Local WSDL
  6. Planning Your BPEL Process
  7. Participants
  8. Implementing a BPMN Task or Event in BPEL
  9. Implementing a BPMN Gateway or Control Flow
  10. Using Variables
  11. Attachments
  12. Using Links
  13. Data Manipulation
  14. Compensation
  15. Correlation
  16. What is Correlation
  17. What is a Correlation Set
  18. Creating Message Properties and Property Aliases
  19. Adding a Correlation Set
  20. Deleting a Correlation Set
  21. Adding Correlations to an Activity
  22. Rules for Declaring and Using Correlation Sets
  23. Correlation Sets and Engine-Managed Correlation
  24. Event Handling
  25. Fault Handling
  26. Simulating and Debugging
  27. Deploying Your Processes
  28. BPEL Unit Testing
  29. Creating POJO and XQuery Custom Functions
  30. Custom Service Interactions
  31. Process Exception Management
  32. Creating Reports for Process Server and Central
  33. Business Event Processing
  34. Process Central Forms and Configuration
  35. Building a Process with a System Service
  36. Human Tasks
  37. BPEL Faults and Reports

2. Designer

2. Designer

What is BPEL-Centric Style

What is BPEL-Centric Style

BPEL-Centric style includes BPMN graphical notation to represent BPEL constructs. The BPEL palette contains the following notation:
  • Each BPEL construct is in the palette, except flow and sequence. These constructs are represented implicitly on the canvas for efficient process design. For example, if you drag a receive to the canvas, it is automatically enclosed in a sequence. When you add the next activity, it is automatically linked.
  • Some BPMN elements are included. To add visual clarity to a process, you can use the start, end, and none events and the fork-join and gateway control flows.
  • Some BPEL activities, such as a receive, can be shown in more than one BPMN construct. For example, a receive can be shown as a message catch event or a receive task. In the receive's Properties view, from the Show As list, select the BPMN display style.
Special Usage of BPEL and BPMN Constructs
The following table shows the BPEL constructs hidden and BPMN constructs used in BPEL edit style.
BPEL Construct Hidden in BPMN
BPMN Construct (not part of BPEL terminology)
Flow
(automatically embedded in a process design as applicable)
Fork Join
Sequence
(automatically embedded to structure a group of activities)
Gateway
Opaque (not used)
Start/End/None
See also:
  • Comparing the BPMN-Centric and BPEL-Centric Tool Palettes
  • Which Edit Style to Choose: BPMN-Centric or BPEL-Centric?


Updated March 30, 2020