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

Adding an onEvent Event Handler

Adding an onEvent Event Handler

The
onEvent
element indicates that the event specified waits for a message to arrive. This element is very similar to a receive activity, except that a message event cannot create a new process instance. Also, an
onEvent
must contain a scope activity and optionally uses a variable local to the event handler that contains the message received from a partner.
An incoming message can correspond to a request/response or one-way operation in a WSDL. When the operation is a request/response type, the event handler is expected to use a reply to send back the response.
Required Properties
Optional Properties
Participant
Variable
Operation
Port Type
Correlations.
Comment.
Documentation.
Setting Visual Properties and Using Your Own Library of Images.
Execution State
Message Exchange.
Extension Attributes and Extension Elements.
To add an onEvent event handler for the process:
Ensure that you have added a participant for the event handler before you can complete the properties for it.
  1. Click on the Event Handlers tab of the Process Editor.
  2. Drag a
    Message catch event
    to the Event Handlers canvas.
  3. From the Properties view, select a participant, operation, and optionally select a Variable Definition and type in a Variable name. This variable is an implicit scope variable that can be used by other activities.
  4. Drag an activity into the
    onEven
    t's scope to respond to the event, such as a reply or exit.
  5. Fill in the properties for the activity that handles the event.
The following illustration shows an example of an onEvent event handler added for the process. If you collapse the event handler, you can add a background color in the Properties view.
Example of an onMessage event handler
To add an onEvent event handler for a scope:
  1. Ensure that you have added a WSDL file to Project Explorer containing the participant information needed.
  2. Display a BPEL file in the Process Editor, and select a scope.
  3. Drag a
    Message catch event
    to the scope.
  4. Fill in the properties of the
    onEvent
    , including the participant, operation and optionally type in a variable. This variable is an implicit scope variable that can be used by other activities.
  5. Drag an activity into the
    onEven
    t's scope to respond to the event, such as a reply or exit.
  6. Fill in the properties for the activity that handles the event.
The following illustration shows an example of an
onEvent
and an
onAlarm
event handler added for a scope. The activity responding to each event is a reply.
Example of scope with an onMessage and an onAlarm event handler, with callouts


Updated March 30, 2020