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 Type

Partner Link Type

Create a standard BPEL activity, such as a receive, reply, or invoke. Add a partner link type definition to a new WSDL file or to an existing WSDL file.
A partner link type describes the kind of message exchange that two WSDL services intend to carry out. A partner link type characterizes this exchange by defining the roles played by each service and by specifying the port type provided by the service to receive messages appropriate to the exchange.
For an easy way to create and use partner link types and partner links, see
What are Participants?
.
A partner link type can include one role or two roles.
  • If a partner link type contains two roles, each of the services must implement its role by providing the specified port type. Using two roles indicates that there is a requirement for the calling service to receive some type of callback from the target service in the course of the conversation. For example, a service is invoked with a one-way operation (input message only). When it is ready to reply, it must send back a message to the process' receive activity.
  • If a partner link type contains only one role, no restriction exists on the calling web service regarding roles. The service described by the single role can complete the conversation simply by having its operation invoked without the need for issuing a callback.
The following illustration shows an example of a partner link type defining two roles.
For example, a partner link type named
AuctionHouse_Seller
describes two roles:
AuctionHouse
and
Seller
. The
AuctionHouse
role supports a port type of
Seller
that expects an input message of an item for sale. The
Seller
role supports a port type
Seller_Answer
that expects an input message from the auction house, regarding whether or not the item has sold. The output message is the name of the item for sale.
In this example, the port types are from the same service; however, port types can be from different services.
The partner link type is a WSDL extension. It can specify one or two roles. The port types can be from the same or from different WSDL files.
A partner link type definition can come from the following sources:
  • From a WSDL file where it is already defined, or where you can add a new definition.
  • From a separate WSDL file with its own namespace for the case where there are two port types, and they are from different services.
  • From a Process Developer BPEL process, where you create can a new definition and add it to a WSDL file.
You can add a new partner link type to a WSDL in the following ways:
  • From a Project Explorer WSDL
  • From a Service Reference
  • From an Interfaces View WSDL
These techniques are described in:
  • Adding a new Partner Link Type from a WSDL in Project Explorer
  • Adding a new Partner Link Type to a new WSDL using a Service Reference WSDL
  • Add a new Partner Link Type from Interfaces View


Updated March 30, 2020