Portal, Express Beta Version 6.1 Operating systems: i5/OS, Linux,Windows

Adding the RDN to the entity type on i5/OS

After creating your LDAP user registry, you may find that your entity type is not correct or you created a new entity type to your LDAP user registry. You can add a relative distinguished name (RDN) to an existing entity type in your LDAP user registry configuration.

1. Optional: Run the ConfigEngine.sh -profileName profile_root wp-query-repository task, located in the profiles/wp_profile/ConfigEngine directory to list the names and types of configured repositories. Note: profile_root is the name of the WebSphere Application Server profile where WebSphere Portal Express is installed; for example, wp_profile.
2. Use a text editor to open the wkplc.properties file, located in the profiles/wp_profile/ConfigEngine/properties directory.
3. Enter the following parameters in the wkplc.properties file under VMM LDAP entity type configuration:

   1. For et.ldap.id, type the name of the LDAP server.
   2. For et.entityTypeName, type the name of the LDAP entity type.
   3. For et.objectClass, type the name of the object class.
   4. For et.searchFilter, type the search filter that you want to use to search the entity type.
   5. For et.objectClassesForCreate, type the name of the object class to use when creating an entity type. If this value is the same as et.objectClass, leave this parameter blank.
   6. For et.searchBase, type the search base or bases to use when searching the entity type.
   7. For et.rdnName, type the attribute name that is used to build the relative distinguished name (RDN) for the entity type.
4. Save your changes to the wkplc.properties file.
5. Run the ConfigEngine.sh -profileName profile_root wp-add-ldap-entitytype-rdn task, located in the profiles/wp_profile/ConfigEngine directory to add an LDAP entity type with a relative distinguished name. Note: profile_root is the name of the WebSphere Application Server profile where WebSphere Portal Express is installed; for example, wp_profile.
6. Perform the following steps to stop and restart the server1 and WebSphere_Portal servers:

   1. Open a command prompt and change to the wp_profile_root/bin directory.
   2. Enter the stopServer server1 -profileName profile_root -user admin_userid -password admin_password command to stop the WebSphere Application Server. Note: profile_root is the name of the WebSphere Application Server profile where WebSphere Portal Express is installed; for example, wp_profile.
   3. Enter the stopServer WebSphere_Portal -profileName profile_root -user admin_userid -password admin_password command to stop the WebSphere Portal Express server.
   4. Enter the startServer server1 -profileName profile_root command.
   5. Enter the startServer WebSphere_Portal -profileName profile_root command.