Introduction to Asynchronous Interactions with a Timeout

5-6 Oracle Fusion Middleware Developers Guide for Oracle SOA Suite Figure 5–5 Asynchronous Interaction with a Notification Time BPEL Process Service Component as the Client When the BPEL process service component is on the client side of this transaction, it needs a scope activity containing an invoke activity to send the request, and a receive activity to accept the reply. The onAlarm handler of the scope activity has a time limit and instructions on what to do when the timer expires. For example, wait 30 minutes, then send a warning indicating that the process is taking longer than expected. As with all partner activities, the WSDL file defines the interaction. BPEL Process Service Component as the Service The behavior for the BPEL process service component as the service matches the behavior with the asynchronous interaction with the BPEL process service component as the service.

5.6 Introduction to One Request, Multiple Responses

In this interaction type, the client sends a single request to a service and receives multiple responses in return. For example, the request can be to order a product online, and the first response can be the estimated delivery time, the second response a payment confirmation, and the third response a notification that the product has shipped. In this example, the number and types of responses are expected. Figure 5–6 provides an overview. BPEL Process WSDL PartnerLink d1 d2 Service BPEL Process receive invoke scope Call service invoke onAlarm Notify Someone Wait for Callback receive Introduction to Interaction Patterns in a BPEL Process 5-7 Figure 5–6 One Request, Multiple Responses BPEL Process Service Component as the Client When the BPEL process service component is on the client side of this transaction, it needs an invoke activity to send the request, and a sequence activity with three receive activities, one for each reply. As with all partner activities, the WSDL file defines the interaction. BPEL Process Service Component as the Service The BPEL service needs a receive activity to accept the message from the client, and a sequence attribute with three invoke activities, one for each reply.

5.7 Introduction to One Request, One of Two Possible Responses

In an interaction using one request and one of two possible responses, the client sends a single request to a service and receives one of two possible responses. For example, the request can be to order a product online, and the first response can be either an in-stock message or an out-of-stock message. Figure 5–7 provides an overview. Client BPEL Process Call service invoke sequence receive receive d1 d3 d2 d4 receive Service BPEL Process receive sequence sequence sequence invoke invoke invoke WSDL Client PartnerLink