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

Invokes

Invokes

Open a B-unit file in the B-unit editor, and select Invokes from the Outline view. To add an invoke, right-mouse click on BPEL Unit.
A common use case for an invoke is to provide a simulated response for a service that your process is invoking. When an invoke activity within the process executes, the B-unit engine looks for a matching invoke element within the B-unit file. If found, this invoke element provides the ability to do assertions on the input data passed to the invoke as well as provide a message that simulates the response from the service invoke.
B-unit invoke elements can be configured for one-way and two-way service invokes. Both styles of invokes can have assertions on the input data but only two-way service invokes are allowed to have a response.
You can define an invoke for a B-unit test as follows:
  1. Select or add an Invoke. Add an Invoke by right-mouse clicking on BPEL Unit.
  2. Specify the Name or
    L
    ocation Path of the invoke. 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. Specify a Delay if you want to delay before returning the response. The delay allows for better handling of onEvent and onAlarm events.
  3. Add a default iteration.
  4. Add the Response type expected:
    • Simulated Respons
      e. Specify the Output data.
    • Subprocess
      . The invoke is a BPEL process, deployed as a subprocess, making the main process eligible for termination and compensation handling.
    • Process
      . The invoke is a BPEL process, deployed as a "process" invoke handler.
    • Simulated Fault
      . The invoke returns a fault.
  5. Add Asserts.
    • Assert Match
      . Specify a Label that is documentation for this Assert, message part and query for the assert, and a Pattern to match on.
    • Assert Equals
      . Specify the input data passed to the invoke.
About Message Part Data
Some information about a message and its associated parts are generated automatically in the B-unit editor when you perform certain actions including:
  • Fill in values for process name, partner link and operation for a Send Message.
  • Select Simulated Response for an invoke assertion (or extension assertion).
  • Select a fault name for a Simulated Fault.


Updated March 30, 2020