| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| JMS Node with LDAP as JNDI |
« View previous topic :: View next topic » |
| Author |
Message
|
| Volvic |
 Posted: Fri Apr 13, 2012 12:22 am Post subject: JMS Node with LDAP as JNDI |
 |
|
Apprentice
Joined: 14 Oct 2009
Posts: 30
|
Hi there,
I am trying to force the JMS node into JNDI lookup on our LDAP but have several problems with that constellation (I was trying to achieve something similar to this http://publib.boulder.ibm.com/infocenter/wmbhelp/v8r0m0/index.jsp?topic=%2Fcom.ibm.etools.mft.doc%2Fbk52050_.htm). My configuration is as follows.
The message flow is simply MQ Input --> MQ JMS Transform --> JMS Output. The relevant JMS Output configuration is as follows.
In "Basic" tab the "Destination queue" is defined as "cn=TEST01.L,cn=project,cn=jms,ou=JNDI-D,ou=Applikationen,dc=domain,dc=DE".
In "JMS Connection" tab the fields are configured as follows.
"JMS provider name" = project_jms
"Initial context factory" = com.sun.jndi.ldap.LdapCtxFactory
"Location JNDI bindings" = ldap://ldapi.domain.de
"Connection factory name" = cn=project_jms_cf,cn=jms,ou=JNDI-D,ou=Applikationen,dc=domain,dc=DE"
The configurable service was created like this (I am not even sure if this is necessary and gets pulled for something).
mqsicreateconfigurableservice BROKER -c JMSProviders -o project_jms -n "initialContextFactory,jarsURL,jndiBindingsLocation" -v "com.sun.jndi.ldap.LdapCtxFactory,/opt/mqm/java/lib,ldap://ldapi.domain.de"
The message is consumed by the flow and then I get the following error.
| Code: |
| Apr 13 09:42:30 i11948 WebSphere Broker v7002[3571]: (BROKER.TEST)[9]BIP4640E: WMB JMSClient. 'JMS Output' There is a configuration problem with the JNDI Administered objects where: Initial Context Factory = 'com.sun.jndi.ldap.LdapCtxFactory'. Location of the bindings = 'ldap://ldapi.domain.de'. ConnectionFactory Name = 'cn=project_jms_cf,cn=jms,ou=JNDI-D,ou=Applikationen,dc=domain,dc=DE'. JMS destination = 'cn=TEST01.L,cn=project,cn=jms,ou=JNDI-D,ou=Applikationen,dc=domain,dc=DE'. The exception text is : '[LDAP: error code 32 - [DSA]:No such object:cn=TEST01.L,cn=project,cn=jms,ou=JNDI-D,ou=Applikationen,dc=domain,dc=DE]'. : BROKER.6d426d8a-3501-0000-0080-f303b87f2c97: /build/S700_P/src/DataFlowEngine/NativeTrace/ImbNativeTrace.cpp: 777: JMSClientOutputNode::lookUpJMSDestinations(): : |
However the object "cn=TEST01.L,cn=project,cn=jms,ou=JNDI-D,ou=Applikationen,dc=domain,dc=DE" does exist in our LDAP. I can confirm this with the "Apache Directory Studio". It shows me the DN which is "cn=TEST01.L,cn=project,cn=jms,ou=JNDI-D,ou=Applikationen,dc=domain,dc=DE".
1. Does any one have a clue what is wrong or how to debug this?
2. Is it possible to save all the configuration of the JNDI destination and connection factory in the configurable service and just link this information with the JMS node by the "JMS provider nam" field (project_jms in my case)?
Update:
Ok, I was stupid enough to forget to issue a "mqsichangebroker BROKER -y <user> -z <password>" to set LDAP credentials. Now it works.
But the question is now: Why can't I set the same LDAP credentials as follows?
mqsisetdbparms BROKER -n "ldap::LDAP" -u "cn=User,ou=Mitarbeiter,ou=LDAPWriters,ou=BLUB,dc=domain,dc=DE" -p "password"
If do this I get "no such object" from LDAP again. Setting the same credentials via "mqsichangebroker" however works fine.
_________________
Volvic |
|
| Back to top |
|
 |
| domoku_1 |
| Posted: Mon Sep 08, 2014 9:56 am Post subject: |
|
|
Newbie
Joined: 12 Jan 2012
Posts: 6
|
Hi,
I am getting the same error as well. Here are the steps I followed.
1. LDAP/OID and JMS topics/queues is setup on oracle server
2. Setup ldap user/password on broker
mqsichangebroker BROKER -y <user> -z <password>
3. Copied the following jar files into /opt/ibm/mqsi/8.0.0.2/JNDI
• orai18n.jar
• ojdbc6.jar
• aqapi.jar
4. Executed the following
mqsichangeproperties BROKER -c JMSProviders -o Oracle_AQ -n jarsURL -v /opt/ibm/mqsi/8.0.0.2/JNDI
mqsichangeproperties BROKER -c JMSProviders -o Oracle_AQ -n initialContextFactory -v com.sun.jndi.ldap.LdapCtxFactory
mqsichangeproperties BROKER -c JMSProviders -o Oracle_AQ -n jndiBindingsLocation -v ldap://<ldap_server>:3060
5. The JMSOutput Node is configured correctly with
source queue = cn=RIBAQ14.TEST,cn=OracleDBQueues,cn=oribadmin,cn=OracleContext, ,dc=<zzz>,<dc=xxx>,dc=<yyy>
JMSProvider = Oracle_AQ
Connection Factory Name = cn=RIBAQ14,cn=oracledbconnections,cn=oribadmin,cn=OracleContext,dc=<zzz>,<dc=xxx>,dc=<yyy>
Initial Context Factory = com.sun.jndi.ldap.LdapCtxFactory
Location JNDI = ldap://<ldap_server>:3060
Error:-
There is a configuration problem with the JNDI Administered objects where: Initial Context Factory = 'com.sun.jndi.ldap.LdapCtxFactory'. Location of the bindings = 'ldap://<ldap_server>:3060'. ConnectionFactory Name = 'cn=RIBAQ14,cn=oracledbconnections,cn=oribadmin,cn=OracleContext,dc=<zzz>,<dc=xxx>,dc=<yyy>'. JMS destination = 'cn=RIBAQ14.TEST,cn=OracleDBQueues,cn=oribadmin,cn=OracleContext, ,dc=<zzz>,<dc=xxx>,dc=<yyy>'. The exception text is : '[LDAP: error code 32 - No Such Object]'. : BROKER.7af260f0-4001-0000-0080-e006ec4ee911: /build/slot1/S800_P/src/DataFlowEngine/NativeTrace/ImbNativeTrace.cpp: 739: com.ibm.broker.jmsclientnodes.JMSClientErrors@7df17df1.JMSClientHelper::lookUpJMSDestinations(): :
Are there any other steps required here? |
|
| 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
|
|
|
|
