Databases Reference
In-Depth Information
In SOA Suite 10.1.3, there was a partner link property
idempotentReply
that when set to true caused the transaction to be committed and the
response returned to the requestor immediately after the
reply
activity.
In 11
g
, this became a component property. The problem with this
approach is that it applies to all operations of a partner link (and in the
11
g
patch, set 1 to all partner links in the component). Patch set 3 of SOA
Suite 11
g
is expected to have a
checkpoint
activity which can be placed
after the
reply
to force the thread to return the result immediately. The
same effect can be achieved in patch set 1 and base 11
g
by using a Java
exec
activity with the
breakpoint()
call.
Oracle Service Bus (OSB) transactions
The OSB has a simpler transaction model than that of the BPEL engine. The way
transactions are handled depends on the nature of the incoming request and the
transaction characteristics of the partner service.
Transactional binding
If the incoming binding for the request to the Service Bus is transactional, then the
proxy service will participate in that transaction, and any proxy services, or business
services invoked by the proxy, will participate in the same transaction. Control of the
transaction, in this case, rests with the client. An example of this is the EJB binding or
the
Java Message Service
(
JMS
)
binding.
In the case that a flow within a proxy invokes several transactional proxies and
business services, they will all be enrolled in the initial inbound transaction and
committed or rolled back as part of that transaction. Hence any transactional
services invoked will all commit together or all roll back together.
Non-transactional binding
If the incoming binding for the request is not transactional, such as a SOAP request
or a file transport, then the transactional behavior of the proxy depends on the type
of proxy.
