Database Reference
In-Depth Information
Some more OSB aspects shall be mentioned in relation to the Adapter framework—the
ability to support transactions. The JCA transport is transactional. If a JCA proxy service
is invoked in an EIS transaction, or if a JCA business service is invoked in a transaction,
the transport propagates the transaction. Sometime ago, Oracle had got in its arsenal,
which is one of the most powerful Transaction Coordinators, Tuxedo (
ht-
bwp-128150.pdf
)
, and if you need complete transactional support for your applications,
this could be the perfect choice. Still, the Oracle Service Bus can provide adequate trans-
actional support for our adapters. A transactional adapter has the potential to start or enlist
in a global transaction context when processing a message. The following examples from
Oracle documentation illustrate how transactional properties vary depending on the ad-
apter:
• A JMS proxy service that uses the XA connection factory is a transactional end-
point. When the message is received, the container ensures that a transaction is
started so that the message is processed in the context of a transaction.
• A Tuxedo proxy service may or may not be a transactional endpoint. A Tuxedo
proxy service is only transactional if a transaction was started by the Tuxedo cli-
ent application before the message is received.
• While an HTTP proxy service will not typically have an associated transaction
when invoked by an HTTP client, you can set an option in the HTTP proxy ser-
vice configuration that starts a transaction and executes the message flow in the
context of that transaction.
You can read more on these use cases at
http://docs.oracle.com/cd/E23943_01/dev.1111/
Search WWH ::
Custom Search