Handling the Deployment Plan When Working on a Remote Oracle SOA Server

2-14 Oracle Fusion Middleware Users Guide for Technology Adapters The weblogic-ra.xml identifies the end point as a development EIS or testing EIS or production EIS. For example, consider that when running through the Database Adapter Service Wizard, you specify eisDBcustStore as the JNDI name for the createCustomer service. After modeling the composite by using this adapter service, you should deploy it to the development, test, or production environments without making any changes. But before you do this, ensure that you have a corresponding JNDI entry for eisDBcustStore in each of your various environments pointing to the right EIS instance. To summarize: ■ All JCA files reference the JNDI name as defined in the weblogic-ra.xml file ■ You must update the weblogic-ra.xml file to have the same JNDI name in all your environments in which it is deployed. ■ Use the weblogic-ra.xml deployment descriptor to specify values for deployment time properties, such as retry interval and retry count. This file also identifies the end point’s environment. ■ Before deployment, ensure you have a corresponding JNDI entry for the correct environment.

2.12 How Oracle JCA Adapters Ensure No Message Loss

This section describes how adapters ensure that messages are not lost. Transactional adapters allow the Enterprise Information System EIS to participate in one-phase or two-phase commits local transactions or globaldistributed transactions. Non-transactional adapters implement their own schemes to ensure delivery, without the use of transactional semantics. This section describes: ■ Section 2.12.2, Local Transactions and Global XA Transactions ■ Section 2.12.3, Basic Concepts of Transactions and Adapters ■ Section 2.12.5, Outbound Transactions For more information, see: ■ Section 2.13, Composite Availability and Inbound Adapters ■ Section 3.1.1, Oracle WebLogic Server Overview ■ Section 5.9.1.2 Oracle JCA Adapters Reliability and Transactional Behavior in the Oracle Fusion Middleware High Availability Guide.

2.12.1 XA Transaction Support

The goal of XA is to allow multiple resources such as databases, application servers, message queues, transactional caches to be accessed within the same transaction. XA uses a two-phase commit to ensure that all resources either commit or rollback any particular transaction consistently. The XA specification describes what a resource manager must do to support transactional access. Resource managers that follow this specification are said to be XA-compliant.