Create the entity type on Windows

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

In single server environments, you do not have to start or stop the WebSphere_Portal and server1 servers to complete the following steps. In clustered environments, stop all application servers on system, including WebSphere_Portal, then start the nodeagent and dmgr servers before you begin any of the following steps.

Create entity types in LDAP user registry:

  1. Optional. Run the ConfigEngine.bat wp-query-repository -DWasPassword=foo task, from the WP_PROFILE/ConfigEngine, to list the names and types of configured repositories.

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

  3. Enter the following parameters in wkplc.properties under the 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. Run the ConfigEngine.bat wp-create-ldap-entitytype -DWasPassword=foo task, from the WP_PROFILE/ConfigEngine, to create an LDAP entity type.

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

  7. Edit WP_PROFILE/ConfigEngine/properties/wkplc.properties

  8. Enter a value 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. Run the ConfigEngine.bat wp-add-ldap-entitytype-rdn -DWasPassword=foo task, from the WP_PROFILE/ConfigEngine, to add an LDAP entity type with a relative distinguished name (DN).

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

If you created clustered environment then performed the steps in this task, now run the update-jcr-admin task on the secondary node. See Enable LDAP security after cluster creation for instructions.


Parent

Update user registry on Windows


Related tasks


Start and stop servers, dmgrs, and node agents
Enable LDAP security after cluster creation

 


+

Search Tips   |   Advanced Search