|
Home > Archive > WebSphere Portal Server > May 2007 > WPS 6 Multiple LDAP Repository Configuration Active Directory &
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
WPS 6 Multiple LDAP Repository Configuration Active Directory &
|
|
| Dinesh Subramanian 2007-03-02, 7:22 am |
| Hi,
I have been trying out this multiple LDAP configuration with WPS6 for quite sometime. I have problem when configuring portal server for ADS and ADAM(Active Directory Application Mode)
I have configured AD 2003 to be my primary LDAP server. I have run enable-security-wmmur-ldap task to achieve the same.
Now I am trying to add one more <ldapRepository></ldapRepository> for ADAM using wmm.xml
I have set horizontalPartitioning=true.
I have also added <federationRepository> which points to the right datasource of my wmm database on DB2 server.
I have added the new realm in wmmur.xml file and set the default property to false.
When I try to start my WebSphere_Portal server, it gives me a wierd error.
ocm.ibm.wps.engine.Servlet init EJPFD0016E: Initialization of service failed.
java.lang.IllegalArgumentException: Parameter externalID must not be null.
at com.ibm.wps.services.identification.IdentificationService.CreateObjectID(Unknown Source)
at com.ibm.wps.services.puma.AbstractURManager.convertPerson(AbstractURManager.java)
Servlet Portal is currently unavailabe: Initialization of one or more services failed.
As I understand, the wmm system is trying to create a new object id for my external id.
I have mapped the "extID" attribute in wmmLDAPAttributes_AD.xml/wmmLDAPServerAttributes.xml to objectGUID
As we are aware that AD and ADAM automatically generates the objectGUID,I have set wmmGenerateExternalId=false in wmm.xml file so that wmm does generate extID.
I have also removed unwanted samAccount attributes from wmmLDAPAttributes_AD.xml of ADAM ldap.
After trying with several permutations/combinations, the error still appears.
Can anybody get me out of this problem.
Thanks Dinesh
| |
| Dinesh Subramanian 2007-03-16, 7:29 am |
| Herez the solution for those who had been struggling like me ....
All you have to do is FlagOn LookAside repository in your wmm.xml file if your main repository does not support some of the attributes of other repositories.
Cheers Dinesh
| |
| Harisankar Gopalan 2007-05-26, 7:22 am |
| Hi Dinesh,
As per my requirements I have to keep some custom attributes in lookaside db. I have used attibuteloader and created custom attribute in lookaside db.
I am using PUMA user for getting user attributes. I am not able to set value to custom atribute which is available in lookaside database.
Its giving error like
com.ibm.portal.puma.AttributeNotDefinedException: EJPSG0007E: One of the attribute specified is not defined for this member type.DefaultPage.
DefaultPage is custom attribute available in lookaside db.
Do you have any idea about this to fix?
Thanks.
|
|
|
|
|