Database Reference
In-Depth Information
For asynchronous processes, there is no need to wait for a response before pro-
ceeding to the next step. The response can be received as part of a separate
process. While creating a BPEL process in JDeveloper, we select either the
Syn-
chronous BPEL Process
or
Asynchronous BPEL Process
template based on the
design of business process and logic. The following screenshot shows the
Design
view of JDeveloper for synchronous and asynchronous BPEL processes:
After completing the process, the synchronous BPEL process sends a response
back to the client using
replyOutput
. On the other hand, the asynchronous BPEL
process calls back the client with the response message using
callBackClient
. Syn-
chronous process provides a reply and the asynchronous process needs to imple-
ment a callback using the Invoke activity.
Oracle BPEL Process Manager uses the WS-Addressing technique for message
correlation between the sender and receiver. In order to correlate the response mes-
sages, Oracle BPEL Process Manager simply adds
Unique Identifier
(
UID
) in the
WS-Addressing headers on the initial request that floats with the
simple object ac-
cess protocol
(
SOAP
) packets. You're not required to take any action as Oracle
BPEL Process Manager automatically adds the UID and callback address to correl-
ate the response messages.
The following table explains the major differences between synchronous and asyn-
chronous BPEL processes:
