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 Event Handling

What is Event Handling

Event handling is an activity that runs concurrently with a scope. Events can be one of two types: a message event or an alarm. When a message event or alarm occurs, the event handler associated with it invokes an activity.
Event handlers are especially helpful for events and requests that cannot be scheduled relative to the main activity, but may occur at unpredictable times. For example, a customer can cancel an order that is being processed.
Event handlers are considered part of the normal behavior of the scope, unlike fault and compensation handlers that take over normal processing.
An event handler can be attached to the process as a whole or to a scope. One or more events can occur and be handled at any time while the corresponding scope is active.
An event handler cannot be enabled until a process instance is created, meaning it cannot create the process instance itself.
Event Types
An event can be an incoming message that corresponds to a request/response or one-way operation in a WSDL. For example, a status query is likely to be a request/response operation, whereas a cancellation can be a one-way operation.
An event can also be an alarm that goes off after a set time or lasts for a specified time, and optionally repeats.
Examples of Event Handler Activities
When a message that triggers an event is received, one of the following can be the likely response by an event handler:
  • Send a reply.
  • Terminate the process instance. For example, an order is cancelled, so the process instance should be cancelled, and there is no ongoing work to be undone and compensated.
  • Throw a fault to cause the ongoing work to be undone and compensated.


Updated March 30, 2020