Populating Data Objects with Real-time Data - Oracle BAM 11gR1 - page 60

form activity is used to initialize the BAM Adapter input variable, by using XSL
to transform the Database Adapter query result into an XML format.
As the design and implementation of SOA composites is beyond the scope of
this topic, we only discussed an overview of using the BAM Adapter in a SOA
composite in this section. To learn more about SOA development, refer to Oracle
SOA documentation or SOA development topics available on the market.
Enabling batching
By default, the Oracle BAM Adapter operates in the synchronous mode (non-
batching mode). As illustrated in the following diagram, the client thread T1 that
executes the BPEL Invoke activity also executes the BAM Adapter API, which
in turn performs a BAM operation, by invoking the remote API of the BAM Active
Data Cache. In this case, the BAM operation is performed synchronously, and
the Invoke activity in BPEL is blocked and waits for the completion of the BAM
Adapter operation. If a BAM Server is down or becomes unavailable, the client
(the Invoke activity) will be blocked until the JTA transaction time-out occurs.
With batching enabled, the BAM Adapter operates in the asynchronous mode.
As shown in the following diagram, after the XML payload that contains a BAM
operation (Insert, Update, Upsert , or Delete) request, is delivered
successfully to the BAM Adapter. The client thread T1 returns immediately
without waiting for the response from the BAM API call. In the meantime, instead
of transforming and sending the XML request to the BAM Active Data Cache in
real time, the BAM Adapter queues these requests, and sends a number of re-
quests as a batch, until certain conditions are met.