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

Invoke

Invoke

BPMN Implementation: Send task, Service task, Rule task, Message throw event
The invoke activity directs a Web service to perform a one-way or request-response operation. It specifies the participant that provides the service and the operation to invoke. The invoke activity must specify the data for the message transmitted and may specify an output variable or variable part in the case of a synchronous request-response Web service invocation. See
Participants
for descriptions of concepts important to this activity.
An invoke activity can be compensated, or reversed. For more information, see
Compensation
.
An invoke activity can also include fault handling when the invoke is added to a scope. Alternately, any faults associated with the invoked service can be handled at the process level, if desired.
An invoke activity can also include fault handling when the invoke is added to a scope. Alternately, any faults associated with the invoked service can be handled at the process level, if desired. For more information, see
Fault Handling
.
Required Properties
Optional Properties
Participant (Partner Link)
Name. See
Selecting Activity Labels
Operation
Port Type
Input Variable
See
Input Variable
.
or
toPart fromVariable
See
From Variable to Part
.
Correlations. See
Correlation
.
 
Output Variable
See
Output Variable
and From
Part to Variable
.
 
Input and Output assignments
 
Join Condition.
See Creating a Join Condition for an Incoming Link
 
Suppress Join Failure. See
Process Properties
 
Comment. See
Adding Comments to a Process
 
Documentation. See
Adding Documentation to a Process
 
Setting Visual Properties and Using Your Own Library of Images
 
Execution State. See
Viewing the Execution State of an Activity or Link
 
Extension Attributes and Extension Elements. See
Declaring Extension Elements and Attributes
.
To add an invoke activity to the process manually:
  1. Drag a
    Send task
    (or other BPMN implementation mentioned above) to the Process Editor canvas.
  2. You can add a background color to the send, service, and rule tasks.
    In the Properties view, select the following values:
    1. Optionally type in a Name.
    2. In the Participant drop-down, select
      New Partner Service Provider
      . See
      Creating a New Partner Service Interface
      .
    3. Select a participant's Operation from the picklist.
  3. In the Input tab, do one of the following:
    • Select Single Variable from the
      Assignment Type
      and select a variable.
    • Select a
      XPaths
      or
      XQuery.
      For details, see
      From Part to Variable
      .
  4. Optionally, select an
    output variable
    or a
    to part
    . For details, see
    From Variable to Part
    .
  5. Select other optional properties as desired.
A simple example of using an invoke activity in a process is shown in the following illustration.
For another shortcut for creating an invoke activity, see
Creating an Activity by Starting with a WSDL Interface
.
XML Syntax
<invoke partnerLink="NCName" portType="QName"? operation="NCName" inputVariable="NCName"? outputVariable="NCName"? standard-attributes> standard-elements <correlations>? <correlation set="NCName" initiate="yes|join|no"? pattern="request|response|request-response"/>+ </correlations> <catch faultName="QName"? faultVariable="NCName"? faultMessageType="QName"? faultElement="QName"?>* activity </catch> <catchAll>? activity </catchAll> <compensationHandler>? activity </compensationHandler> <toParts>? <toPart part="NCName" fromVariable="BPELVariableName"/>+ </toParts> <fromParts>? <fromPart part="NCName" toVariable="BPELVariableName"/>+ </fromParts> </invoke>
Example:
<invoke name="invokeapprover" partnerLink="approver" portType="lns:loanApprovalPT" operation="approve" inputVariable="request" outputVariable="approval">


Updated March 30, 2020