Designer > Participants > 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:

Using the Participants View

The Participants view is the key starting point for developing a BPEL process. It guides you to provide the key ingredients for a process: the roles that the process and partner services play and the interface for each role. Further, once you define an interface, you can drag its operation to the Process Editor canvas to create process activities. For example, a receive activity is created from the interface operation associated with a process service consumer.
The following illustration shows an example of participants and their interfaces:
The Participants view is empty unless a process is open. The view is process-based; that is, it shows participants only for the process in focus.
In this view, you can do the following (on-premises only):

Creating a New Process Service Consumer Interface

A Process Service Consumer is a participant Web service that is used in building a receive and/or reply activity. It consists of a name and an interface.
You can create a service consumer in stages:

Creating a New Partner Service Interface

A Partner Service Provider is a participant Web service that is used in building an invoke activity. It consists of a name and an interface.
You can create a partner service provider in stages:
  1. 1. Enter a name or accept the default name, Provider.
  2. 2. If interface resources are available, you can select the interface. If they are not, you can add them later, in the Properties view
When you complete the participant details, you are essentially creating all the elements needed for a process' invoke activity.

Creating a New Callback Interface

Select or create the port type and operation for a participant to call back.
Each Web service in a process, represented by receive, reply, and invoke activities, must have a service interface. The interface describes the operations provided by the service.
You can choose to add a callback interface, which allows the service provider to invoke operations on the service consumer. For example, in a service interface, the process sends an order and the partner replies with an order ID. In a callback interface, the partner can send an order shipment notice.
When you add a callback interface, Process Developer generates a standard BPEL partner link type for that participant and stores it in a WSDL. This makes the participant relationship clear for future users of the WSDL and allows new processes that use the service interface to automatically see the callback interface.
The details for creating a callback interface are the same as creating a service interface. See:
See also Creating New Activities from the Participants View

Clearing a Service Interface from a Participant

Remove a service interface from a participant.
You can clear a service interface from a participant from the Properties view.

Creating New Activities from the Participants View

After creating participants and their interfaces, you can drag an operation or task to the Process Editor to create activities. These activities contain the required participant name and operation. You can then use the activity's Properties view to provide data assignments.
The following table shows the activities that the Process Developer creates when you drop an operation onto the Process Editor canvas.
Drag an operation from this participant's interface
To create this activity or activity pair
Process Service Consumer one-way operation
Receive, onMessage (if Pick is selected), or onEvent (if event handler is selected)
Process Service Consumer two-way operation
Receive-Reply, onMessage-Reply, onEvent-Reply
Process Service Consumer Callback
Partner Service Provider
Partner Service Provider Callback
Same activities as process service consumer for one-way and two-way operations
Human Task Participant's task
People activity
See also:

Creating a New Variable From an Activities Property View

Create a new process variable for a receive or other activities.
Create a new process variable for a receive onMessage, onEvent, reply, or invoke activity as follows:
  1. 1. Select the Properties view of an activity.
  2. 2. Open the Data, Input or Output tab of the activity.
  3. 3. For the Assignment Type, select Single Variable.
  4. 4. In the Variable list, select New Variable.
The variable name suggested is one of the following:
In the Scope field, select the process or a scope to make the variable global or local.
The Variable Type is derived from the WSDL message definition.