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

Which Edit Style to Choose BPMN-Centric or BPEL-Centric

Which Edit Style to Choose BPMN-Centric or BPEL-Centric

Which Edit Style to Choose: BPMN-Centric or BPEL-Centric?
Both BPMN and BPEL edit styles generate 100% validated, executable BPEL XML code. Both styles are diagramming notations for process descriptions. You can choose which visual style is easier for you and your team.
Highlights of BPMN-Centric
  • The edit style uses standard BPMN terminology.
  • The Process Developer
    break
    extension activity can be implemented with a
    terminate
    activity within a scope,
    for Each
    or
    while
    structured activity. The
    break
    implementation allows breaking out of the closest scope or loop.
  • The Process Developer
    continue
    extension activity is not supported because no notation in BPMN has the exact Continue semantics.
  • The error catch event is used for the
    catch
    and
    catch all
    fault handlers.
  • The
    error
    throw event is used for the
    throw
    and
    rethrow
    activities.
  • Annotations include icons for data objects, collections and stores.
  • An annotation can be linked to an activity.
  • A control flow structure, like a Conditional Pattern or Repeat Pattern, can be ungrouped into separate activities.
Highlights of BPEL-Centric
  • The style uses BPEL terminology for constructs and includes some common BPMN constructs. Not all BPEL constructs are visible. Some are hidden in order to produce a cleaner, clearer diagram.
  • The style includes the Process Developer extension activities break and continue
  • Catch
    and
    catch all
    fault handlers are represented separately
  • Throw
    and
    rethrow
    activities are represented separately


Updated March 30, 2020