Oracle Database Adapter Integration with Oracle BPEL PM

9-4 Oracle Fusion Middleware Users Guide for Technology Adapters However weblogic-ra.xml entries occasionally have more than simply the name of the underlying data source. These properties are detailed further under Section 9.5, Deployment . While at run time you have Oracle Database Adapter instances, at design time you have the Adapter Configuration Wizard link. You can run it once to generate a single adapter service end point, and then multiple times in edit mode to make incremental changes to each. It generates all the adapter related artifacts needed when deploying a SOA composite as Table 9–1 lists.

9.2 Complete Walkthrough of the Adapter Configuration Wizard

This section describes the Adapter Configuration Wizard and how you can define an Oracle Database Adapter by using the Adapter Configuration Wizard. This section describes the various Oracle Database Adapter concepts through a use case, which is, a complete walkthrough of the Adapter Configuration Wizard. In addition, this use case also describes how by using the Adapter Configuration Wizard, you can import tables from the database, specify relationships spanning multiple tables, generate corresponding XML schema definitions, and create services to expose the necessary SQL or database operations. These services are consumed to define partner links that are used in the BPEL process. You use the Adapter Configuration Wizard to both create and edit adapter services. ■ Section 9.2.1, Creating an Application and an SOA Project ■ Section 9.2.2, Defining an Oracle Database Adapter ■ Section 9.2.3, Connecting to a Database ■ Section 9.2.4, Selecting the Operation Type ■ Section 9.2.5, Selecting and Importing Tables Table 9–1 Adapter Configuration Wizard Generated SOA Composite Adapter Artifacts File Description serviceName.wsdl This is an abstract WSDL, which defines the service end point in terms of the name of the operations and the input and output XML elements. serviceName_table.xsd This contains the XML file schema for these input and output XML elements. Both these files form the interface to the rest of the SOA project. serviceName_or-mappings.xml This is an internal file. It is a TopLink specific file, which is used to describe the mapping between a relational schema and the XML schema. It is used at run time. serviceName_db.jca This contains the internal implementation details of the abstract WSDL. It has two main sections, location and operations. Location is the JNDI name of an adapter instance, that is, eisDBSOADemo. Operations describe the action to take against that end point, such as INSERT, UPDATE, SELECT, and POLL. The contents of the db.jca file are wholly determined by choices made while running the Adapter Configuration Wizard. serviceName.properties This is also an internal file. It is created when tables are imported, and information about them is saved. It is used only at design time. At run time, the location is used to look up the adapter instance which executes the service. Based on the properties in the db.jca file and the linked or-mappings.xml file, seviceName.properties file generates the correct SQL to execute, parses the input XML, and builds an output XML file matching the XSD file. To execute the SQL, it obtains a pooled SQL connection from the underlying data source. Oracle JCA Adapter for Database 9-5 ■ Section 9.2.6, Defining Primary Keys ■ Section 9.2.7, Creating Relationships ■ Section 9.2.8, Creating the Attribute Filter ■ Section 9.2.9, Defining a WHERE Clause ■ Section 9.2.10, Choosing an After-Read Strategy ■ Section 9.2.11, Specifying Polling Options ■ Section 9.2.12, Specifying Advanced Options ■ Section 9.2.13, Entering the SQL String for the Pure SQL Operation

9.2.1 Creating an Application and an SOA Project

You must create an Oracle JDeveloper JDeveloper application to contain the SOA composite. Perform the following steps to create a new application, and an SOA project: 1. Open JDeveloper.

2. In the Application Navigator, click New Application.

The Create Generic Application - Name your application page is displayed, as shown in Figure 9–2 .

3. Enter a name for the application in the Application Name field.

4. In the Application Template list, choose Generic Application.

Figure 9–2 The Create Generic Application - Name your application Page

5. Click Next.

The Create Generic Application - Name your project page is displayed, as shown in Figure 9–3 .

6. In the Project Name field, enter a descriptive name.