Prepare a Novell eDirectory

To use a Novell eDirectory as an LDAP user registry, install and set up the server so that it communicates with HCL WebSphere Portal.

1. Install Novell eDirectory. Refer to eDirectory for information.

2. Complete the following steps with the web administration tool to create the HCL WebSphere Portal administrative user:

   1. Optional: Complete the following steps to create a directory suffix:

      1. Click the Server Administration folder in the directory server console navigation.

      2. Click the Manage Server Properties folder under the Server Administration folder and then select Suffixes on the main page.

      3. Type the Base DN name for the suffix; for example: dc=mycompany,dc=com.

      4. Click Add.

      5. Click OK to save changes.

   2. Open the appropriate LDIF file in the PortalServer_root/installer/wp.iim/ldif directory, with a text editor:

      • Use the PortalUsers.ldif file as a working example and adapt appropriately to work with the LDAP server.

      • Use the ContentUsers.ldif file for the HCL Content Manager group and user ID if we configured HCL Web Content Manager.

   3. Replace every dc=myco,dc=com with your suffix.
   4. Replace any prefixes and suffixes that are unique to the LDAP server.

   5. We can specify user names other than wpsadmin and wpsbind. For security reasons, specify nontrivial passwords for these administrator accounts.

   6. Save changes.

   7. Complete the instructions that are provided with your directory server to import the LDIF file.

3. Complete the following steps to create the HCL WebSphere Portal administrative user:

   1. Open the appropriate LDIF file in the PortalServer_root/installer/wp.iim/ldif directory, with a text editor:

      • Use the PortalUsers.ldif file as a working example and adapt appropriately to work with the LDAP server.

      • Use the ContentUsers.ldif file for the IBM Content Manager group and user ID if we configured HCL Web Content Manager.

   2. Replace every dc=myco,dc=com with your suffix.
   3. Replace any prefixes and suffixes that are unique to the LDAP server.

   4. We can specify user names other than wpsadmin and wpsbind. For security reasons, specify nontrivial passwords for these administrator accounts.

   5. Optional: If we use Security Access Manager Version 5.1, set the objectclasses to accessGroup. If we use Security Access Manager Version 6, set the objectclasses to groupOfNames.

   6. Save changes.

   7. Complete the instructions that are provided with your directory server to import the LDIF file.

Parent topic: Prepare the user registry software