Create the entity type on Solaris

If an entity type exists within IBM WebSphere Portal to use but it does not exist within the LDAP user registry, we can create the entity type within the LDAP user registry and then add the relative distinguished name (RDN) to the entity type to map it between WebSphere Portal and your LDAP user registry.

In a clustered environment, start the dmgr and nodeagent and verify they are able to synchronize.

Create entity types in the LDAP user registry:

1. List the names and types of configured repositories...
   ./ConfigEngine.sh wp-query-repository

2. Edit wkplc.properties

3. Enter the following parameters under VMM LDAP entity type configuration heading:
   • et.ldap.id
   • et.entityTypeName
   • et.objectClass
   • et.searchFilter
   • et.objectClassesForCreate
   • et.searchBases

4. Save changes to wkplc.properties.

5. ./ConfigEngine.sh wp-create-ldap-entitytype -DWasPassword=foo task, from WP_PROFILE/ConfigEngine, to create an LDAP entity type.

6. Stop and restart servers, dmgrs, and node agents.

7. Edit wkplc.properties

8. Set parameters under the VMM LDAP entity type configuration heading:
   • et.ldap.id
   • et.entityTypeName
   • et.objectClass
   • et.searchFilter
   • et.objectClassesForCreate
   • et.searchBases
   • et.rdnName

9. Save changes to wkplc.properties.

10. ./ConfigEngine.sh wp-add-ldap-entitytype-rdn -DWasPassword=foo task, from WP_PROFILE/ConfigEngine, to add an LDAP entity type with a relative DN.

11. Stop and restart servers, dmgrs, and node agents.

If you created the clustered environment, including the additional nodes, and then completed the steps in this task, run update-jcr-admin on the secondary nodes.

Parent: Update the user registry on Solaris
Related:
Start and stop servers, dmgrs, and node agents
Enable LDAP security after cluster creation