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

Signal

Signal

A signal is an event that you create that throws information within a process and which can be received anywhere within the process. Catching a signal event is equivalent to catching a message or alarm event except that only the name of the signal needs to be specified. This means it could be caught inline (like a wait), as an alternative in a pick (like onAlarm), as a handler (like onAlarm), or using a boundary event.
This is a Process Developer extension activity.
Unlike a message (which a signal resembles), a signal can be received by more than one activity. It also differs in that a message must know the activity to which the message is directed. In contrast, a catch signal is broadcast and the signal decides which of the signals being broadcast it should process.
To add signals to your process, drag a Signal icon to the Process Editor canvas. Signal resides in the Throw and Catch event palettes.
After dragging a throw signal to the canvas, you must assign it a
Signal Name
. Do not confuse this with an
Activity Name
. When you define the properties of the catch signal, you will identify the signal it catches by this name. It needs this name because a process can have more than one signal.
When a signal is thrown, all signal handlers that are active and waiting a signal of that name execute and they do this before the end of the current transaction.
For information on defining a signal's properties, see
Defining an Activity and Its Properties
.
If you are using an existing workspace and have customized your palette, signal events may not show in it. If you run into this problem, copy the signal events entries over into the workspace or remove the workspace's customized palette. This does not occur when you create a new workspace signal events show in the palette.


Updated March 30, 2020