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 Participants

What are Participants

Participants are the people and services that the process interacts with over the course of its execution. Communication to or from a participant is always through a Web service interface.
Participants simplify the BPEL details you need to provide for an interface. By creating participants, you can skip over some technical details in BPEL as Process Developer generates details for you.
Here are the participant types:
  • Process service consumers
    Each process interacts with at least one participant: the participant that sends the service request message that starts the process. This participant is the first process service consumer. You can also create additional consumers if there are additional participants that use services provided by a process. Consumers can also provide callback service. These allow a process to request that the consumer perform operations. In BPEL, the process service consumer is equivalent to a partner link whose myRole property has been set.
  • Partner service providers
    If the process needs to invoke a service to do some work for the process, it calls a service that is provided by a partner service provider. The process can also make callback services available to a partner service provider. The interface for such a callback is listed with the partner service provider that can use it. In BPEL, this participant is the equivalent to a partner link whose
    partnerRole
    property has been set.
  • Human task participants
    (on-premises only)
    If the process needs people to accomplish some of its steps, it uses people activities. A human task participant represents the role of the person who will complete some of the activities of the process. Each human task participant lists the tasks that its role works on. In BPEL4People, a
    Logical People Group
    is created for each human task participant.
    For details, see Using the
    Participants View
    .
    For details on using the Participants view in conjunction with HTML form development, see
    Adding a New Service Operation for a Form or a Task
    .


Updated March 30, 2020