|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
|
|
Integrating IIB with Oracle AQ using JMS |
« View previous topic :: View next topic » |
Author |
Message
|
ashu008 |
Posted: Thu Feb 14, 2019 11:12 pm Post subject: Integrating IIB with Oracle AQ using JMS |
|
|
Newbie
Joined: 14 Feb 2019 Posts: 4
|
Hi guys,
We are trying to read messages off a JMS queue implemented in ORACLE AQ, using IBM App connect enterprise.
Guide on IBM's website recommends to use OID ldap server to implement this, but source system currently is not capable of installing Oracle Internet Directory Server to achieve this connectivity.
Below are the details we have received from AQ team:
Provider URL : ormi://{host}:{port}
Initial context factory : oracle.j2ee.rmi.RMIInitialContextFactory
Security principal : username
Security creds : password
Datasource : jdbc/dsnname (not really sure what to do with this)
Topic name : somename
One more system (Hybris) is already consuming/publishing the messages from/to AQ jms queue/topic using ormi:// url and datasource name
Below is what i have tried so far to use JMSoutput nodes without success:
*importing oc4jclient.jar into shared classes
*mqsisetdbparms on integration server to set creds on jnd::oracle.j2ee.rmi.RMIInitialContextFactory.
* have tried multiple connection factory names, with all diffreent sorts of credentials set.
But i always get below exception:
Destination name not found. Unable to find destination in JNDI.
This issue has really become a showstopper for us.
|
|
Back to top |
|
|
fjb_saper |
Posted: Fri Feb 15, 2019 11:59 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003 Posts: 20729 Location: LI,NY
|
So make sure that ormi://host:port is reachable from the IIB server.
(Quick telnet to host port should prove the point.
Looking at the credentials you should use something like
Code: |
mqsisetdbparms -o jms::myoracle .... |
Hope it helps _________________ MQ & Broker admin |
|
Back to top |
|
|
ashu008 |
Posted: Fri Feb 15, 2019 8:25 pm Post subject: |
|
|
Newbie
Joined: 14 Feb 2019 Posts: 4
|
Telnet: works
mqsisetdbparms -w /home/aceuser/ace-server -n jndi::oracle.j2ee.rmi.RMIInitialContextFactory -u username -p password
Above creds work fine, as i tried to give incorrect username and password which resulted in Not Authorised exception.
My observation is, jndi lookup happens fine. Problem arises when it tries to look for a connection factory, and then the actual topic name. |
|
Back to top |
|
|
fjb_saper |
Posted: Sat Feb 16, 2019 9:14 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003 Posts: 20729 Location: LI,NY
|
ashu008 wrote: |
Telnet: works
mqsisetdbparms -w /home/aceuser/ace-server -n jndi::oracle.j2ee.rmi.RMIInitialContextFactory -u username -p password
Above creds work fine, as i tried to give incorrect username and password which resulted in Not Authorised exception.
My observation is, jndi lookup happens fine. Problem arises when it tries to look for a connection factory, and then the actual topic name. |
My meaning was that your -n for the credentials is all wrong.
You cannot have multiple credentials for the same type of ContextFactory...
you should have
Code: |
mqsisetdbparms -w /home/aceuser/ace-server -n jms::somename -u username -p pwd |
and then reference jms::somename in your configurable service / policy.
The jndi part should go into the InitialContextFactory....like
InitialContextFactory=oracle.j2ee.rmi.RMIInitialContextFactory _________________ MQ & Broker admin |
|
Back to top |
|
|
tumzkfa |
Posted: Sun Dec 22, 2019 10:42 pm Post subject: |
|
|
Newbie
Joined: 22 Dec 2019 Posts: 1
|
fjb_saper wrote: |
ashu008 wrote: |
Telnet: works
mqsisetdbparms -w /home/aceuser/ace-server -n jndi::oracle.j2ee.rmi.RMIInitialContextFactory -u username -p password
Above creds work fine, as i tried to give incorrect username and password which resulted in Not Authorised exception.
My observation is, jndi lookup happens fine. Problem arises when it tries to look for a connection factory, and then the actual topic name. |
My meaning was that your -n for the credentials is all wrong.
You cannot have multiple credentials for the same type of ContextFactory...
you should have
Code: |
mqsisetdbparms -w /home/aceuser/ace-server -n jms::somename -u username -p pwd |
and then reference jms::somename in your configurable service / policy.
The jndi part should go into the InitialContextFactory....like
InitialContextFactory=oracle.j2ee.rmi.RMIInitialContextFactory |
Has the connection problem been resolved? |
|
Back to top |
|
|
|
|
|
|
Page 1 of 1 |
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|
|
|