Hi
In CQ 5.5 we connected to the ldap jmx bean via:
javax.management.MBeanServer.getClassLoaderFor("com.adobe.granite.ldap:host=localhost,port=10389,type=Tools")
e.g. for the operation syncAllExternalUsers(), which worked fine.
Now with AEM 6.1 I try to use the new JMX Bean via:
javax.management.MBeanServer.getClassLoaderFor("org.apache.jackrabbit.oak:handler=mySyncHandler,idp=ldap")
but I get the following exception:
javax.management.InstanceNotFoundException:org.apache.jackrabbit.oak.spi.security.authentication.external.impl.jmx.SynchronizationMBean:handler=mySyncHandler,idp=ldap
If I run the syncAllExternalUsers() manually via AEM Web Console, the function works fine. I also tried to connect to the bean with org.apache.jackrabbit.oak.spi.security.authentication.external.impl.jmx.SynchronizationMBean:handler=mySyncHandler,idp=ldap .
Does anyone have an idea, how I an call the new bean in AEM 6.1?
Thanks alot
Reto
Solved! Go to Solution.
Views
Replies
Total Likes
Try this:
connect to your cq jmx port via jconsole. (jconsole is located at $jdk_home/bin/jconsole). open jconsole. connect to your CQ instance from the available process. then in the Mbeans tab see if your MBean is registered there. it will also help determine if anything is wrong with the objectname string. whatever objectname is listed there is what should be provided in the code.
this should look something like that in the attached shreenshot.
Views
Replies
Total Likes
Have you configured the properties for 'Apache Jackrabbit Oak Default Sync Handler' in the configMgr ?
can you give the steps you have followed to configure the ldap
Views
Replies
Total Likes
Hi,
Why do you need the ClassLoader? I would suggest just calling MBeanServer.invoke().
Regards,
Justin
Views
Replies
Total Likes
Hi justin_at_adobe
I also tried it with MBeanServer.invoke() but I get the same exception.
Best regards,
Reto
Views
Replies
Total Likes
Hi bsloki
Thank you for your quick response. Yes, I configured the the properties for 'Apache Jackrabbit Oak Default Sync Handler' in the configMgr, otherwise none of the LDAP function would work. I followed this instruction for the configuration: http://docs.adobe.com/docs/en/aem/6-1/administer/security/ldap-config.html. In fact that the LDAP function works fine, I think I'm doing something wrong in calling the JMX bean.
Views
Replies
Total Likes
are you using the default Handler or a custom handler ? if So can you share your handler ..
Views
Replies
Total Likes
I'm using the default handler.
Views
Replies
Total Likes
Interesting !! I did setup locally and it is working for me.. Do you mind sharing the screenshot of your configurations ?
Views
Replies
Total Likes
How does your MBeanServer.invoke() look like? My configuration is attached.
Views
Replies
Total Likes
try this (not sure if this would work) -
javax.management.MBeanServer.getClassLoaderFor(new ObjectName("org.apache.jackrabbit.oak:handler=mySyncHandler,idp=ldap"));
Views
Replies
Total Likes
This is what I'm already doing, without luck:
final ObjectName targetObjectName = new ObjectName(ldapJmxObjectName);final ClassLoader tmpClassLoader = mBeanServer.getClassLoaderFor(targetObjectName);
Views
Replies
Total Likes
Try this:
connect to your cq jmx port via jconsole. (jconsole is located at $jdk_home/bin/jconsole). open jconsole. connect to your CQ instance from the available process. then in the Mbeans tab see if your MBean is registered there. it will also help determine if anything is wrong with the objectname string. whatever objectname is listed there is what should be provided in the code.
this should look something like that in the attached shreenshot.
Views
Replies
Total Likes
Hi awadheshv
Thanks alot for your hint with the jconsole. This solved my problem. I figured out that my objectname was wrong. I have to use the following objectname: org.apache.jackrabbit.oak:name=External Identity Synchronization Management,handler="mySyncHandler",type=UserManagement,idp="ldap"
Views
Replies
Total Likes
Views
Likes
Replies
Views
Likes
Replies