Oracle SOA JMS Queue configuration

JMS Adapter Validation Prerequisites

In this release of Oracle Application Server ProcessConnect, there are no automated or user interface-based means for verifying and validating the correctness of the delivery channel configuration, except when starting the JMS adapter in runtime.

Typical values for the JNDI locations for an OJMS-based setup are as follows:

• For the JMS Connection Factory:

   java:comp/resource/Ojms/QueueConnectionFactories/qcf   

• Vendor properties:

  blank

  where blank indicates to leave the field blank.

• For the JMS Destination:

  java:comp/resource/Ojms/Queues/$[DestinationName]   

• Vendor properties:

  blank

  where the Ojms substring must match the resource provider instance name (See "Instructions for Oracle JMS ".) and blank indicates to leave the field blank.

For an MQSeries JMS-based setup, the same two settings are as follows:

• JMS Connection Factory:

  com.ibm.mq.jms.MQQueueConnectionFactory   

• Vendor properties:

  QueueManager=my.queue.manager;TransportType=1;Host=... 

• JMS Destination:

  queue:///$[DestinationName]  

• Vendor properties:

  ?targetClient=1  

8.8.9 JMS Adapter Additional Setup Tasks

This section describes setup tasks to perform in addition to the delivery channel parameter and interaction question tasks that you perform with the Oracle Application Server ProcessConnect user interface tool.

Depending on the method used for locating JMS administrative objects (connection factories and destinations), the following tasks must be performed:

• Vendor- and user-specific JAR files must be appended to the adapter class path.

• Objects must be bound in a JNDI namespace through pertinent deployment descriptors.

Queues, topics, or both must also be created and enabled in the third-party queuing system. Pertinent third-party listeners, channels, daemons, and so on must also be started.

8.8.9.1 Instructions for Oracle JMS

Add an OJMS resource provider instance through Oracle Enterprise Manager 10g.

Note: Do not add an OJMS resource provider instance by editing the application.xml file. Use Oracle Enterprise Manager 10g to add a provider.

1. Log in to the Oracle Enterprise Manager 10g Application Server Control Console.

2. Select the Oracle Application Server ProcessConnect middle tier instance in which to add the JMS resource provider.

3. Click OC4J_ProcessConnect in the System Components section of the Application Server : middle_tier_instance page.

4. Click Administration.

   The OC4J: OC4J_ProcessConnect page appears.

   
   

   
   

   Important Links:

   http://otndnld.oracle.co.jp/document/products/as10g/1012/doc_v3/integrate.1012/B14448-01/html/adptr_jms.htm

   http://download-east.oracle.com/docs/cd/B10464_05/integrate.904/b12121/adapters.htm#i1010356