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

Overview of BPEL Activities

Overview of BPEL Activities

In the default (BPMN) Process Developer editing style, basic activities are organized according to BPMN types: activities and events. In BPEL, there is no distinction: both activities and events are considered activities.
The following table provides brief definitions and links to more details.
Activity Name
Description
Invoke
Directs a Web service to perform an operation
Assign
Manipulates process variables and partner link endpoint references by creating Copy From/To operations for them
Empty
An activity that does nothing when it executes. Useful for situations where you need an activity but do not want anything to really happen, for example, suppressing a fault by having the empty be the child of the catch.
Suspen
Suspends the process. Useful in a catch or catchAll event to catch unexpected errors.
Validate
Validates the values of variables against their associated XML and WSDL data definition
Opaque
(For Process Developer Classic only). For abstract processes. Stands as a placeholder for an activity that would be used in an executable process.
Receive
Accepts message data from a service partner. Optionally begins a process by creating an instance of the process.
Reply
Sends a response to a partner identified in a matching Receive activity
Signal
Signals are similar to a throw, differing in that there isn't a fault. A signal throws information that is received by a signal that waits for this information.
Throw
Signals a fault. Specifies a standard or custom fault
Rethrow
Passes the fault that was originally caught by the immediately enclosing fault handler to the parent scope
Exit
Stops an executable process immediately, resulting in a faulted process.
Wait
Stops process execution for a specified amount of time or until a deadline is reached
Compensate Scope
Starts compensation on a specified inner scope that has already completed successfully
Compensate
Executes the compensation handler on a named scope or executes the default compensation if no scope is named
Break
Breaks out of a scope or a loop in a while or for each activity. Processing continues normally with the next activity.
Continue
For BPEL-Centric palette only.) Continues with the next iteration in a loop (while, repeat until, or for each). A convenience activity that simplifies processing without the need of specifying all the conditions that may be required to continue normal processing when a certain condition is met.
Start/End/None
Equivalent to the BPEL empty or assign activity, described above.
For information on structured activities, see
Different Ways of Structuring Activities
.


Updated March 30, 2020