Online Help for Oracle SOA Suite

2.80 Invoke Dialog - General Tab

Use to specify an operation that you want to invoke for the service (identified by its partner link).

The operation can be an asynchronous one-way operation or synchronous request-response operation on a port provided by the service. You can also automatically create variables in this activity. An asynchronous invocation requires only the input variable of the operation because it does not expect a response as part of the operation. A synchronous invocation requires both an input variable and an output variable.

For more information about the invoke activity, see the Business Process Execution Language for Web Services Specification (for BPEL 1.1) or the Web Services Business Process Execution Language Version 2.0 Specification at http://www.oasis-open.org.

The Invoke Dialog - General Tab is arranged in the following sections:

Name

The Name section enables you to name the invoke activity and specify optional conversation ID and master and detail process information.

Element	Description
Name	Enter a name or accept the default name of `Invokenumber`. This becomes the name for this activity in the designer.
Conversation ID	Enter a unique value. This value is used for identifying a process instance during an asynchronous conversation. By default, the BPEL process service engine generates a unique ID for each conversation (which can span multiple invoke and receive activities), as specified by WSA addressing. If you want, you can specify your own value for the engine to use.
Detail Label	Enter a detail instance name for coordinating master and detail processes in a BPEL process. This field is enabled when you select the Invoke As Detail checkbox
Invoke As Detail	Select to create the partner process instance as a detail instance when coordinating master and detail processes in a BPEL process. This coordination enables you to specify the tasks performed by a master BPEL process and its related detail BPEL processes.

Interaction Type - Event

The Interaction Type -Event section enables you to select the web service partner or business event with which to interact.

Element	Description
Event	Select to publish a business event.
Event	Click the Search icon to select the business event.
Variable	Click the Add icon to automatically create a variable. The variable is automatically assigned a message type. Click the Search icon to browse a list of existing variables to assign.

Interaction Type - Partner Link

The Interaction Type - Partner Link section enables you to select the web service partner with which to interact.

Element	Description
Partner Link	Select the partner link to invoke with this activity.
Port Type	Select the port type for this activity. This field only displays in BPEL 2.0 projects.
Operation	Select the operation to be performed
Input	Select Argument Mapping or Input Variable.
Argument Mapping	Select to set the message parts for the selected operation.
Operation Parts Table	Displays the message parts, message types, and values of the selected operation.
Parts	Displays the message part.
Type	Displays the message type.
Value	Click to set the value for the message part. Select the variable in which to retrieve the value and store in the message part.
Input Variable	Select to specify a variable.
Input	Select one of the following options: Click the Add icon to automatically create a variable for this activity. The variable follows a naming convention of `activity_name_operation_InputVariable`. For example, if the activity name is `invokeCredit` and the operation is `initiate`, the variable is named `invokeCredit_initiate_InputVariable`. A message type is automatically assigned to this variable (for example, request message). Click the Search icon to browse a list of existing variables to assign to this activity.
Output Variable	Select to specify a variable.
Output	Select one of the following options: Click the Add icon to automatically create a variable for this activity. The variable is automatically assigned a message type. The variable follows a naming convention of `activity_name_operation_OutputVariable`. For example, if the activity name is `receiveCredit` and the operation is `process`, the variable is named `receiveCredit_process_OutputVariable`. A message type is automatically assigned to this variable (for example, response message). Click the Search icon to browse a list of existing variables to assign to this activity.