[rkuruba]

Why after OTM installation intg_queue table is empty it is supposed to have 5 queues?
inbound_aq, ack_aq, exception_aq, xml_stage_aq, query_reply_aq

[chrisplough]

Hello!

I don't know why, but I've verified on 2 OTM v5.5 CU3 systems that the
INTG_QUEUE table is empty. So, at least, it seems that you're not alone.

--Chris

[rkuruba]

I am told by oracle that these will appear when a message is enqueued. I am going to test it out and see.

[rkuruba]

Chris!!.

How to expose inbound_aq to outside clients. Documentation talks about directly connecting to OTM database but doesn't give much details. I have created all the configuration that need to be done.

Thanks,
RK.

[chrisplough]

Hello

I haven't seen OAQ exposed over the Internet before - usually the integration engine or ESB (Enterprise Service Bus) is exposed and then does the translation of documents into the OTM or OAQ format and posts internally to the OAQ queue -- so I'd recommend looking into your security and translation needs to ensure this model best fits.

That being said, usually OAQ connects in using the Oracle OCI or JDBC drivers. For instance, when configuring Mule (an open-source ESB) to connect to OAQ, you define your connection as follows:

<mule-configuration id="TestConfiguration" version="1.0"> 
<connector name="oracleJmsConnector" 
className="org.mule.providers.oracle.jms.OracleJmsConnector"> 
<properties> 
<property name="url" value="jdbc:oracle:oci:@myhost" /> 
<property name="username" value="scott" /> 
<property name="password" value="tiger" /> 
</properties> 
</connector> 
<transformers> 
<transformer name="StringToXMLMessage" 
className="org.mule.providers.oracle.jms.transformers.StringToXMLMessage" 
returnClass="oracle.jms.AdtMessage" /> 
<transformer name="XMLMessageToString" 
className="org.mule.providers.oracle.jms.transformers.XMLMessageToString" 
returnClass="java.lang.String" /> 
</transformers> 
<global-endpoints> 
<endpoint name="XmlQueue" address="oaq://XML_QUEUE" transformers="StringToXMLMessage" /> 
</global-endpoints> 
<model name="Test Model"> 
<mule-descriptor name="XML-Driven UMO" implementation="com.foo.MyUMO"> 
<inbound-router> 
<endpoint address="oaq://XML_QUEUE" transformers="XMLMessageToString"> 
<properties> 
<property name="payloadFactory" value="oracle.xdb.XMLTypeFactory" /> 
</properties> 
</endpoint> 
</inbound-router> 
</mule-descriptor> 
</model> 
</mule-configuration>

or - you can use a one-line connection string like:

oaq://XML_QUEUE?url=jdbc:oracle:oci:scott/tiger@myhost

The connection is then made using the default db port.

(as a side note, some additional information for anyone using Mule can be found here:
Oracle AQ Integration - Mule - Mule--Open Source ESB (Enterprise Service Bus) and Integration Platform)

Thanks!
--Chris

[rkuruba]

Thanks Cris!!

From what you are saying if I understand correctly I can use JMS API and "oaq://XML_QUEUE?url=jdbcracleci:scott/tiger@myhost" connection string while making database connection to OTM and push JMS messages to this queue.

Is this right?

[chrisplough]

Correct - you can make a connection to OTM's Oracle DB (which has OAQ enabled) and post directly to it. The transactions will have to be formatted for OAQ and (I believe) need to be in G-Log XML format. You're able to use JMS as your central integration protocol, however, between your integration server (like Mule in my previous post) and external systems.

--Chris

[chrisplough]

I ran across another Open Source ESB recently, that looks very promising - Open ESB.

https://open-esb.dev.java.net/

It's also integrated with the Netbeans IDE, making development easier.

--Chris