Create the entity type

If an entity type exists within portal, but not within LDAP...

1. Create the entity type within the LDAP user registry.
2. Add the relative distinguished name (RDN) to the entity type to map it portal and LDAP.

In a stand-alone server environment, complete the following task when the servers are either stopped or started. In a clustered environment, start the deployment manager and node agent. Then, verify they are able to synchronize.

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

   ...and under VMM LDAP entity type configuration heading, set...

   • et.ldap.id
   • et.entityTypeName
   • et.objectClass
   • et.searchFilter
   • et.objectClassesForCreate
   • et.searchBases

   For example...

   et.ldap.id=MyCo_LDAP1
   et.entityTypeName=PersonAccount
   et.objectClass=inetOrgPerson;Person;mycoPerson
   et.searchFilter=
   et.objectClassesForCreate=mycoPerson
   et.searchBases=
   et.ldap.host=prdtds1.myco.com

3. Save the changes to wkplc.properties.

4. Update a realm configuration:
   ./ConfigEngine.sh wp-update-realm -DWasPassword=foo

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

6. Open wkplc.properties.

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

8. Save the changes to wkplc.properties.

9. Add an LDAP entity type with a relative distinguished name (DN):
   ./ConfigEngine.sh wp-add-ldap-entitytype-rdn -DWasPassword=foo

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

Parent Update the user registry