2.82 OnEvent Dialog
Use to indicate that the specified event waits for a message to arrive.
For example, assume you have a credit request process that is initiated by a customer's credit request message. The request may be completely processed without the need for further interaction, and the results submitted to the customer. In some cases, however, the customer may want to inquire about the status of the credit request, modify the request content, or cancel the request entirely while it is being processed. You cannot expect these interactions to occur only at specific points in the business order processing. An event handler such as an onEvent branch enables the business process to accept requests (such as status request, modification request, or cancellation request) to arrive in parallel to the primary business logic flow.
For more information about the onEvent activity, see the Web Services Business Process Execution Language Version 2.0 Specification at http://www.oasis-open.org
.
Note: This branch is supported in BPEL projects that support version 2.0 of the BPEL specification.
The OnEvent Dialog - General Tab is arranged in the following sections:
Name
The Name section enables you to name the OnEvent branch.
Element | Description |
---|---|
Name |
Enter a name or accept the default name of |
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. |
From Parts |
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. |
Variable |
Select the following details: |
Variable |
Enter a variable local to the event handler that contains the message received from the partner. |
Message Type |
Click the Search icon to select the variable type by referencing a message type definition using its QName. The variable type (as specified by the message type) must be the same as the input message type defined by the operation referenced by the operation attribute. |
Element |
Click the Search icon to select an element if the message to be received has a single part that is defined with an element type. That element type must be an exact match of the element type referenced by the element attribute. |
Namespace |
Click the Search icon to select the namespace. |
Local Part |
Displays a part value based on the selection you make in the Namespace field. |
Related Topics
Mapping WSDL Message Parts in BPEL 2.0 in Developing SOA Applications with Oracle SOA Suite
Specifying Events to Wait for Message Arrival with an OnEvent Branch in Developing SOA Applications with Oracle SOA Suite