Create the entity type on AIX

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 the 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.
   cd WP_PROFILE/ConfigEngine
   ./ConfigEngine.sh wp-query-repository -DWasPassword=foo

2. Edit...
   WP_PROFILE/ConfigEngine/properties/wkplc.properties

3. Enter the following parameters...
   • et.ldap.id
   • et.entityTypeName
   • et.objectClass
   • et.searchFilter
   • et.objectClassesForCreate
   • et.searchBases

4. Save changes wkplc.properties

5. Create an LDAP entity type...
   cd WP_PROFILE/ConfigEngine
   ./ConfigEngine.sh wp-create-ldap-entitytype -DWasPassword=foo

6. Stop and restart the appropriate servers to propagate the changes.

7. Edit wkplc.properties and set...
   • et.ldap.id
   • et.entityTypeName
   • et.objectClass
   • et.searchFilter
   • et.objectClassesForCreate
   • et.searchBases
   • et.rdnName

8. Save changes

9. To add an LDAP entity type with a relative DN...
   cd WP_PROFILE/ConfigEngine
   ./ConfigEngine.sh wp-add-ldap-entitytype-rdn -DWasPassword=foo

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

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

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