Configuring Message Header Properties for Oracle JCA Adapters

2-6 Oracle Fusion Middleware Users Guide for Technology Adapters

2.5 Describing XML Data Structure

The record implementation for Oracle JCA Adapters is XMLRecord. All adapter interactions are started with XMLRecord. Each JCA record must be an implementation of oracle.tip.adapter.api.record.XMLRecord. Each instance of XMLRecord contains the RecordElement. RecordElements payload that contains data. In addition, each RecordElement contains one BLOB of data, which can either be a UTF-8-encoded XML string or a binary opaque byte stream. XMLRecord consists of the following methods: ■ getPayloadRecordElement: Retrieves the payload RecordElement. ■ setPayloadRecordElement: Sets the payload record element of the XMLRecord.

2.6 Physically Deploying Oracle JCA Adapters

Oracle JCA Adapters are deployed as JCA 1.5 resource adapters in an Oracle WebLogic Server container. Adapters are packaged as Resource Adapter Archive RAR files using the Java Archive JAR format. The physical deployment of adapters involves using the RAR file to register the adapters as connectors with the underlying Oracle WebLogic Server or the middle tier platform.

2.6.1 The RAR Deployment Descriptor File and the weblogic-ra.xml Template File

The RAR file contains the ra.xml file, which is the deployment descriptor XML file containing deployment-specific information about the resource adapter. In addition, the RAR file contains declarative information about the contract between Oracle WebLogic Server and the resource adapter. In addition to the ra.xml file in the.rar file, adapters package the weblogic-ra.xml template file. The weblogic-ra.xml file is used to define resource adapter ConnectorFactory objects logical deployment. The weblogic-ra.xml file is the Oracle WebLogic Server-specific deployment descriptor for a resource adapter. It contains deployment configurations for deploying resource adapters to Oracle WebLogic Server, which includes the back-end application connection information as specified in the deployment descriptor of the resource adapter, Java Naming and Directory Interface JNDI name to be used, connection pooling parameters, resource principal mapping mechanism, and configurations. For more information, see: ■ Section 2.7, Creating an Application Server Connection for Oracle JCA Adapters ■ Section 2.8, Deploying Oracle JCA Adapter Applications from JDeveloper ■ Section 2.9, Manually Deploying an Adapter RAR File that Does Not Have a Jar File Associated With It ■ Section 2.10, Handling the Deployment Plan When Working on a Remote Oracle SOA Server ■ Section 2.11, Migrating Repositories from Different Environments ■ Section 2.19, Adding an Adapter Connection Factory ADAPTER Life-Cycle Management 2-7 ■ Section 2.21, Recommended Setting for Data Sources Used by Oracle JCA Adapters ■ Oracle Fusion Middleware Installation Guide for Oracle WebLogic Server.

2.7 Creating an Application Server Connection for Oracle JCA Adapters

You must establish connectivity between the design-time environment and the server to which you want to deploy. To establish such connectivity, you must create an application server connection. The following are the steps to create an application server connection:

1. In the File menu, click New.

The New Gallery page is displayed, as shown in Figure 2–3 . Figure 2–3 The New Gallery Page This figure shows the New Gallery page.

2. In the All Technologies tab, under General categories, select Connections.

A list of the different connections that you can make is displayed in the Items pane on the right side of the New Gallery page.

3. Select Application Server Connection, and then click OK.

The Create Application Server Connection page is displayed, as shown in Figure 2–4 .