Creating a JMS queue for SOA consumption

This post will move permanently to here: http://blog.ipnweb.com/2009/03/creating-jms-queue-for-soa-consumption.html

This post describes how to create a JMS queue in the Oracle database to use within your BPEL processes and/or ESB services.

Create a JMS queue

Log on to the Oracle Database and create a queue table called JMS_ABC_QUEUETABLE. Afterwards, create a queue called JMS_ABC_QUEUE on this queue table. Finally, start the queue.

begin sys.dbms_aqadm.create_queue_table( queue_table => 'JMS_ABC_QUEUETABLE', queue_payload_type => 'SYS.AQ$_JMS_MESSAGE', sort_list => 'PRIORITY, ENQ_TIME', compatible => '10.0.0', primary_instance => 0, secondary_instance => 0, storage_clause => 'tablespace pctfree 10 initrans 1 maxtrans 255 storage ( initial 64K minextents 1 maxextents unlimited )'); end; / begin sys.dbms_aqadm.create_queue( queue_name => 'JMS_ABC_QUEUE', queue_table => 'JMS_ABC_QUEUETABLE', queue_type => sys.dbms_aqadm.normal_queue); end; / EXECUTE dbms_aqadm.start_queue (queue_name => 'JMS_ABC_QUEUE');

Configure the Oracle SOA Suite server

Edit the $ORACLE_HOME/j2ee/oc4j_soa/config/application.xml file and add the "myjms" resource provider.

<resource-provider class="oracle.jms.OjmsContext" name="myjms"> <description>oc4j-jms loop back resource provider</description> <property name="url" value="jdbc:oracle:thin:<user>/<password>@<dbhost>:<dbport>:<dbsid>"/> </resource-provider>"/>

Edit the $ORACLE_HOME/j2ee/oc4j_soa/application-deployments/default/JmsAdapter/oc4j-ra.xml file and add the "myconnfac" connector factory.

<connector-factory location="eis/Jms/myconnfac" connector-name="Jms Adapter"> <config-property name="connectionFactoryLocation" value="java:comp/resource/myjms/QueueConnectionFactories/myQCF"/> <config-property name="factoryProperties" value=""/> <config-property name="acknowledgeMode" value="AUTO_ACKNOWLEDGE"/> <config-property name="isTopic" value="false"/> <config-property name="isTransacted" value="false"/> <config-property name="username" value="<user>"/> <config-property name="password" value="<password>"/> <connection-pooling use="none"></connection-pooling> <security-config use="none"></security-config> </connector-factory>

Enqueing via PL/SQL

For testing purposes, you may decide to enqueue a payload via PL/SQL.

declare l_message clob := ''; v_enqueue_options dbms_aq.enqueue_options_t; v_msg_props dbms_aq.message_properties_t; v_msg_id RAW(16); v_message SYS.AQ$_JMS_MESSAGE := SYS.AQ$_JMS_MESSAGE.construct(DBMS_AQ.JMS_TEXT_MESSAGE); begin l_message := '<ns4:elements xmlns:ns4="http://ns.thisisahmed.com/MyMessage/20080702"><ns4:element><ns4:firstname>Ahmed</ns4:firstname><ns4:lastname>Naga</ns4:lastname></ns4:element></ns4:elements>'; v_message.set_text(xmltype(l_message).getstringval()); dbms_aq.enqueue(queue_name => 'JMS_ABC_QUEUE', enqueue_options => v_enqueue_options, message_properties => v_msg_props, payload => v_message, msgid => v_msg_id); commit; end; /

When configuring the JMS Adapter within JDeveloper, here are the settings you will want to use:

Service Name: (whatever name you choose; e.g., JMSQueue)
OEMS: Database
JNDI Name: (whatever your JNDI name is; e.g., eis/Jms/LocalDB)
Operation Type: Consume Message
Resource Provider: myjms
Destination Name: JMS_ABC_QUEUE
Schema Location: (whatever schema you want)

This is how my final BPEL process looked like.

Good luck.