Oracle SOA BPEL Transaction Option in Asynchronous BPEL

Asynchronous BPEL process is helpful in achieving higher performance of the system. While connecting the ASynch Webservice to the BPEL process we have  following transaction options

By default, incoming requests are saved in the following delivery service database tables: dlv_message

• async.persist: Messages are persisted in the database.

• sync.cache: Messages are stored in memory.

• sync: Direct invocation occurs on the same thread.

We need to select the transaction option based on requirement mainly based on recovery process.

If the process failed in the Asyncronus process then we can resubmit that process instead of restarted from the beginning.