Hi,
I am working with an SAP Enterprise Portal 6 SPS20. We have 4 stages (dev, test, preprod, prod). In our environment we are using an LDAP (IBM Tivoli Directory Manager) as our UME Datasource for the user, account and group objects. Everything is working fine so far. In defined intervals we are making backward copies, from preprod to test and dev (using the system copy utility from sap) to ensure consistency over all of our stages.
Now our problem starts, we have configured the UME to use the LDAP as the datasource for the user and account objects but SAP is not able to export all attributes (PasswordLastChanged, PasswordChangeRequired, ......) of the account object to the LDAP. Some attributes are held in a "shadow ume database" in the portal. When we now copy our preprod system back to the test stage, the user and user account objects in the LDAP datasource of the test stage are not synchronous with the "shadow ume database" of the copied portal. We cannot copy the LDAP of the preprod or prod system as it contains thousands of user and account objects of real life users and this data is protected by the privacy statement.
The inconsistency of the internal portal (ume) account data and the data stored in the LDAP datasource leads to Exceptions when searching users using account attributes (Show me all locked users). The system finds USER_ACCOUNT_OBJECTS with no existing USER_OBJECT. Is there a way to clean up the internal datastore of the portal?
Can anyone please help?
Regards
Edmund
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.