How to force ldap synchronization

, ,
1

I have a role in My webMethods portal that is defined by LDAP Query Role Provider.
I have a user of my Active Directory that need to have urgently this role.
But my problem is that LDAP sincronization that apply the role to this user takes more than 15 minutes to apply.
In ldap configuration I have:
[b]- cache capacity = 1000

  • cache timeout = 1 minute
  • search timeout = 60[/b]

I have to reconfigure this parameters to apply the query role providers more quickly?

Thanks.

2

Alejandro:

Make a java service to clear the role cache.


ICacheManager cacheManager = (ICacheManager) PortalSystem.getComponentProvider(IComponentNames.CACHE);
RoleCache roleCache = (RoleCache)cacheManager.getCache(com.webmethods.portal.service.cache.impl.RoleCache.ROLE_CACHE_NAME);
roleCache.flushAll(true);

Best regards.
Norberto.

3

And what “imports” I have to add?
I can’t locate the classes ICacheManager and RoleCache.
I have to copy any file to \SoftwareAG\IntegrationServer\lib\jars?

4

Alejandro:

Add the following imports:

java.util.Iterator
java.util.List
java.util.Map
com.webMethods.caf.faces.data.dir.IPrincipalProvider
com.webMethods.caf.faces.data.dir.PrincipalModelFactory
com.webMethods.portal.service.cache.ICacheManager
com.webMethods.portal.service.cache.impl.RoleCache
com.webMethods.portal.system.IComponentNames
com.webMethods.portal.system.PortalSystem
com.webMethods.sc.directory.DirectorySystemFactory
com.webMethods.sc.directory.IDirectoryGroup
com.webMethods.sc.directory.IDirectoryRole
com.webMethods.sc.directory.IDirectorySession

You don’t need to copy any jars to \lib.

Best Regards.
Norberto.

5

I can import this classes:
java.util.Iterator
java.util.List
java.util.Map
, but don’t locate the following namespace (the classes cannot be resolved):
com.webMethods.caf.*
com.webMethods.portal.*
com.webMethods.sc.*
I have WM 8.2.2.

6

Alejandro:

I’ve 8.0.1. You have to locate the appropriate jar/s and put them into IS common libraries path.

Regards.

7

I think, the code above should be executed in the context of MWS, not IS. I.e. you could create a portlet (or a web app) and create an action there which would execute the code. Then all the necessary libraries should already be in place (as they are available to all MWS components).

I can’t tell what will happen if you copy all the CAF libraries to the common dir. The code might compile, but will it work? The cache “lives” in MWS, so even if the call succeeds, I doubt it will bring the desired effect.

If you try it out please report back.

8

Yes, agree to the above.

MWS should provide a way to clear the LDAP Cache - why is it not there? Presumably instead you have to do a restart of the service - does this fix it?