Stream Payload Support Oracle AQ Adapter Inbound Retries

Oracle JCA Adapter for AQ 7-11 1. Search fmwhome for AqAdapter.rar. 2. Unzip the file. 3. Edit META-INFweblogic-ra.xml and possibly ra.xml. 4. Jar the file again. 5. Restart the application server. The following is a sample adapter instance in weblogic-ra.xml: connection-instance jndi-nameeisAQaqSamplejndi-name connection-properties properties property nameXADataSourceNamename valuejdbcaqSamplevalue property property nameDataSourceNamename valuevalue property property nameConnectionStringname valuevalue property property nameUserNamename valuevalue property property namePasswordname valuevalue property property nameDefaultNCharname valuefalsevalue property property nameUseDefaultConnectionManagername valuefalsevalue property properties connection-properties connection-instance The mandatory properties are: jndi-name, XADataSourceName or DataSourceName. The jndi-name property must match the location attribute in the .jca file, and is the name of the adapter instance. The XADataSourceName or DataSourceName property is the name of the underlying data source which has the connection information. Only one of the properties XADataSourceName or DataSourceName needs to be specified. The usage depends on if the scenario involves and would require adapter to participate in global transaction or if local transaction semantics are sufficient. In the former case XADataSourceName must be specified while in the latter case DataSourceName must be specified. When specifying XADataSourceName property ensure that the physical data source it refers to is XA enabled while when specifying DataSourceName property the physical data source it refers to may or may not be XA enabled. 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: