Write in the access manager cache

Question

Hi,
I use AM 2004Q2 with the portal server. I also use IDM to manage portal identites. From IDM, I want to change portal LDAP attributes. Precisely, I want to change the value of the attribute of sunPortalDesktopDpDocumentUser.
So from IDM, I make a call to a java class that does the change of the sunPortalDesktopDpDocumentUser attribute which is stored in the portal LDAP.
At first I used jndi to make my changes directly in the ldap. My change was stored in the ldap but since access manager uses a cache, the change I had made in the ldap was, in some cases, overwritten by the cache.
So I was advised not to make my change to the ldap but directly to the cache.
here is the piece of code that does the job.
          AMStoreConnection conn = new AMStoreConnection(adminToken);
          AMUser user = conn.getUser(userdn);
          String attribXML = user.getStringAttribute("sunPortalDesktopDpDocumentUser");
          ModifyDP mdp = new ModifyDP();
          String newAttribXML = mdp.changeDP(attribXML);   // here I make the change I need on the attribute
          user.setStringAttribute("sunPortalDesktopDpDocumentUser", newAttribXML);
          user.store();  // valide les changementsWith this code I still have a cache problem. In some case the new value is overwritten by the old one.
Does anyone have any idea how I should proceed to make permanent changes to the ldap/cache?
any help appreciated :)

Answer 1

Actually Access Manager has an Event Mechism which is used to udpate the caches if data is changed in the directory server. This is used in multinode deployments. It�s also used by Portal (which relies on amSDK).
Unfortunately i�m not sure if this is perfectly working in AM 2004Q1 (AKA AM6.1). At least you need the latest patch.
Unfortunately i can not remember if AM6.1 already had an amEventService debug log.
Is there some FW/LB between AM and DS?
-Bernhard