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

Designer

Designer

Fork Join

Fork Join

The notation for a fork join container is BPMN only. This control flow is equivalent to a BPEL Flow activity.
When you drag a fork join to the canvas, it contains two paths by default. You can add additional paths as needed. Each path contains one or more activities. Each path executes in parallel.
Required Properties
Optional Properties
none
Name.
Join Condition.
Suppress Join Failure.
Comment.
Documentation.
Setting Visual Properties and Using Your Own Library of Images
Execution State.
Extension Attributes and Extension Elements.
To build a Fork Join:
  1. From the
    Control Flow
    palette, drag a
    fork join
    to the Process Editor canvas.
  2. Drag an activity, such as Receive task, to one path.
  3. Continue dragging the other activities to the same or other path.
  4. Add a new path by right mouse clicking the Fork Join and selecting
    Add Path
    .
The following illustration shows an example of a Fork Join activity containing two invokes executing in parallel.

0 COMMENTS

We’d like to hear from you!