- 17.9K All Categories
- 3.4K Industry Applications
- 3.3K Intelligent Advisor
- 63 Insurance
- 536.4K On-Premises Infrastructure
- 138.3K Analytics Software
- 38.6K Application Development Software
- 5.8K Cloud Platform
- 109.5K Database Software
- 17.5K Enterprise Manager
- 8.8K Hardware
- 71.1K Infrastructure Software
- 105.3K Integration
- 41.6K Security Software
Using the Oracle AQ JMS java api (aqapi.jar) library to create JMS Provider on generic application s
Is the provided Oracle AQ JMS java api (aqapi.jar) library enough to configure a functioning JMS provider (and associated connection factories and queues)? I've managed to create a JMS Provider, and a connection factory. However I'm running into obscure issues configure and retrieving a queue via JNDI in my container.
I tried to use the Oracle AQ RAR file provided (ojms.rar) in WebSphere however it seems to be custom build for WebLogic and runs into all kinds of class loading issues that I tried to resolve. When it started looking for Oracle specific MBean configuration I gave up on it.
I'm working with:
Oracle Database 18.104.22.168
WebSphere Application Server 8.5
Frustration comment: I've had to get this far by sweat and tears because there is next to no specific documentation on HOW to use Oracle's provided RAR and Jar libraries on this topic. To me this seems to be a vendor war type situation where Oracle documents how to use their "generic" resource adapter in WebLogic. However good luck figuring out how to use it in WebSphere or Jboss.