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

What are Partner Link Types and Partner Links

What are Partner Link Types and Partner Links

Select partner links to include in a partner definition. A partner link can be used in only one partner definition.
For an easy way to create and use partner link types and partner links, see
What are Participants?
A BPEL process describes a flow of interactions between the process and services. Each interaction describes what role the process and services play at that step in the flow and what data can be manipulated by the parties in those roles.
BPEL defines constructs to identify roles and relationships used in interactions.
The constructs are partner link and partner link type. A partner link describes the roles that a process and service play as well as what data they can manipulate in that role. A partner link is defined by its partner link, as shown in the following diagram.
The partner definitions and usage in a BPEL process do not refer to the specifics of Web services. Since a BPEL process is a reusable definition that can be deployed in different ways, the definitions are abstract. The addressing, security, and other specifics of Web services are taken care of at deployment time. When a process is deployed, every partner role in a partner link for a BPEL process instance is assigned a unique endpoint reference.
For more details on each concept, see the following:
  • Partner Link Type
  • Partner Link


Updated March 30, 2020