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

Partner Link

Partner Link

For an easy way to create and use partner link types and partner links, see the key Process Developer feature,
What are Participants?
.
A partner link is a communication exchange between two partners. In the most basic form, the process is a partner link of an external service, receiving a request from it. A partner link defines the role that the process plays (if any) and the role that the partner service plays (if any) in the particular exchange. A partner link can be declared globally or within a scope.
A partner link definition consists of:
  • A name
  • A partner link type
  • At least one role and can include two roles
  • Role names of MyRole, which is the process role, and PartnerRole
  • Optional property called Initialize Partner Role
  • Optional properties for
    Adding Comments to a Process
    and
    Adding Documentation to a Process
  • Optional properties for
    Declaring Extension Elements and Attributes
In a BPEL process, you use the partner link when defining Web service interaction activities. For example, a receive activity specifies a partner link, its port type and operation. The port type comes from the associated partner link type. This means that the process can accept incoming message data from the service playing the partner role defined in the partner link.
At a minimum, a process must have one partner link for each particular communication exchange it is engaged in. BPEL allows for multiple partner links of the same partner link type to exist within a process.
By default, a partner link is declared at the process level. You can declare a partner link at a scope level. The partner link name must be unique among the set of partner links defined by the process or scope.
The
Initialize Partner Role property is provided as a hint to the deployer of a process. This property does not affect the runtime behavior of the process. If the process contains logic to initialize its partner links then it should set this property to No. This type of initialization would occur through the use of an assign activity. If the process requires its deployment environment to initialize its partner links, either through a static endpoint at deployment or perhaps through an endpoint reference scheme like WS-Addressing, then it should set this property to Yes. If the property is missing, then there is no information conveyed to the deployer as to how the partner links are initialized.
Add a partner link automatically to the process:
Partner links are automatically added to the process when you drop a WSDL operation onto the Process Editor canvas and complete a wizard to create a receive, invoke, reply, onMessage, or onEvent. If you must create a new operation, you can use the Operation Wizard. These are the recommended techniques for creating partner links. For more information, see
Creating an Activity by Starting with a WSDL Interface
.
Add a new partner link manually to the process:
  1. From the Outline view, right-mouse click on
    Participant Partner Link
    and select
    Add Process Service Consumer
    or
    Partner Service Provider
    .
  2. For further details, see
    Creating a New Partner Service Interface
    .
XML Syntax
<partnerLinks> <partnerLink name="NCName" partnerLinkType="QName" myRole="NCName"? partnerRole="NCName"? initializePartnerRole="yes|no"?>+ </partnerLink> </partnerLinks>
Example
<partnerLink name="seller" partnerLinkType="AuctionHouse_SellerLT" myRole="AuctionHouse" partnerRole="Seller" </partnerLink>


Updated March 30, 2020