Invoke Operation
The Invoke Operation task enables you to invoke an operation of an interface in the target interface list during processing of an input, output, or fault path. The operation can be one-way or request-reply. If the operation is request-reply, the reply message is stored in the mediation exchange for use by subsequent tasks in the mediation path.
General Tab
See Invoking an Operation for more information about the Invoke Operation task.
Use the General tab to specify a name and description for the task. This tab is useful for providing documentation for tasks in your mediation flows.
| Field | Description |
|---|---|
| Name | Assign a name to the task, to identify the task in the mediation flow. This name appears in the tooltip that opens when you hover the cursor over the task icon in the mediation flow. |
| Description | Describe the task briefly. This description appears in the tooltip that opens when you hover the cursor over the task icon in the mediation flow. |
| Target Operation | The operation to invoke. The drop-down list is populated with all operations from the interfaces in the target interface list of the mediation flow. |
Input Tab
The Input tab is a mapping panel for mapping data from the mediation exchange to the input fields of this task. See Transforming Tasks for more information about using a mapping panel.
Output Tab
The Output tab contains a static tree representation of the reply message schema for the invoked operation. Subsequent tasks in the mediation flow will have access to the reply message. The reply message is stored in an element within the mediation exchange whose root is named the same as the Invoke Operation task name specified on the General tab.
Subsequent tasks also have access to the message context properties in the reply message. See Working with Message Context Properties.
If the message exchange pattern for the operation is one-way, the output is null.