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

Alarms

Alarms

Open a B-unit file in the B-unit editor, and select Alarms from the Outline view. To add an alarm, right-mouse click on BPEL Unit.
Alarms refer to the wait activity and the onAlarm events in picks and event handlers. You can assert on an alarm deadline or duration.
You can define an alarm for a B-unit test as follows:
  1. Select or add an alarm. Add an alarm by right-mouse clicking on BPEL Unit.
  2. Specify the Process and Location Path of the alarm-based activity.
    • Add the Simulated Duration of the alarm. This is the time the B-unit test will wait for the alarm to be triggered.
    • If this activity is within a loop (for example, a For Each), you can specify a Count for the expected number of times to execute the activity.
  3. Add a default alarm, and add the duration for the B-unit test to use.
  4. Add an Assert.
    • Assert Deadline. Specify the actual deadline, converted to a duration, for the B-unit test. Specify a Precision value that is the period of time within which the deadline should fire. This value is specified in seconds.
    • Assert Duration
      .
      Same as deadline.
  5. Add an assert iteration, if desired. If the alarm-based activity is within a loop, add an Index for this iteration. The index is the
    nth
    iteration within the count, specified for the alarm.


Updated March 30, 2020