Prior to Oracle's acquisition of BEA, the underlying application server for Oracle SOA Suite and many Oracle applications such as E-Business Suite, JD Edwards was Oracle Internet Application Server (aka OC4J).
As a result, it is a common requirement for Oracle Service Bus to consume messages that have been published to OC4J. In this recipe, we will configure a proxy service on Oracle Service Bus to consume messages published to a JMS provider running on OC4J.
The core of this recipe requires us to configure Oracle Service Bus and its Java Naming and Directory Interface (JNDI) provider in the WebLogic server to access a remote JNDI provider (on OC4J). Once configured, we can then implement a proxy service to consume JMS messages as if it was on a local queue.