Deployment Oracle Fusion Middleware Online Documentation Library

7-12 Oracle Fusion Middleware Users Guide for Technology Adapters Most Common Mistakes The following are the two most common mistakes with deployment: ■ Not creating an adapter instance entry that matches the location attribute in your .jca file or not creating one at all. ■ Setting the location attribute in the .jca file to the name of the data source directly. For the latter, there is a level of indirection in that you give the name of the adapter instance eisAQ..., which itself points to the data source pool jdbc.... It is a common mistake to miss this indirection and give the name jdbc... directly in the location attribute. Additional Adapter Instance Properties There are additional properties in the AQ Adapter instance beyond xADataSourceName, dataSourceName. For information about the Oracle AQ Adapter instance properties, see Appendix A.3, Oracle AQ Adapter Properties.

7.4 Oracle AQ Adapter Use Cases

This section includes the following topics: ■ Section 7.4.1, Generic Use Case ■ Section 7.4.2, Oracle AQ Adapter ADT Queue ■ Section 7.4.3, Oracle AQ Adapter RAW Queue

7.4.1 Generic Use Case

The following use cases include a general walkthrough of the Adapter Configuration Wizard, followed by examples of how you can modify the general procedure in different situations. Each example shows relevant parts of the generated WSDL and JCA files. This section includes the following topics: ■ Section 7.4.1.1, The Adapter Configuration Wizard Walkthrough ■ Section 7.4.1.2, Dequeuing and Enqueuing Object and ADT Payloads ■ Section 7.4.1.3, Dequeuing One Column of the Object Payload ■ Section 7.4.1.4, Configuring the EnqueueDequeue Operation Type ■ Section 7.4.1.5, Using Correlation ID for Filtering Messages During Dequeue ■ Section 7.4.1.6, Enqueuing and Dequeuing from Multisubscriber Queues

7.4.1.1 The Adapter Configuration Wizard Walkthrough

In this example, you will create an Oracle AQ Adapter service that dequeues messages to the service_in_queue queue, with a payload that is one field within the service_type object, and with a user-defined schema. This section describes the tasks required to configure Oracle AQ Adapter by using the Adapter Configuration Wizard in JDeveloper. This section includes the following topics: Oracle JCA Adapter for AQ 7-13 ■ Section 7.4.1.1.1, Meeting Prerequisites ■ Section 7.4.1.1.2, Creating an Application and an SOA Project ■ Section 7.4.1.1.3, Defining an Oracle AQ Adapter Service ■ Section 7.4.1.1.4, Generated WSDL and JCA Files

7.4.1.1.1 Meeting Prerequisites

This example assumes that you are familiar with basic BPEL constructs, such as activities and partner links, and JDeveloper environment for creating and deploying BPEL composite. You must have access to a database with the SCOTT schema. To perform this use case, you require the following files from the artifacts.zip file contained in the adapters-aq-103-adtclobpayload sample: ■ artifactssqlsetup_user.sql ■ artifactssqlcreate_type_service.sql ■ artifactssqlcreate_queues.sql ■ artifactssqldequeue_service.sql ■ artifactssqlenqueue_service.sql To obtain the adapters-aq-103-adtclobpayload sample, access the Oracle Sample SOA Code site, and click on the Adapters tab.

7.4.1.1.2 Creating an Application and an SOA Project

You must create a JDeveloper application to contain the SOA composite. Perform the following steps to create a new application, 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 7–1 .

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

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

7-14 Oracle Fusion Middleware Users Guide for Technology Adapters Figure 7–1 The Create Generic Application Name your application Page

5. Click Next.

The Create Generic Application Name your project page is displayed, as shown in The Create Generic Application Name your Generic project Page on page 15 .

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

For example, SOAComposite.

7. In the Available list in the Project Technologies tab, double-click SOA to move it

to the Selected list.