If you plan to use an Oracle Directory Server as an LDAP user registry, you must install
and set up the server so that it communicates with HCL Digital Experience.
Procedure
-
Install Oracle Directory Server. Refer to Oracle software for information.
-
Complete the following steps with the web administration tool to create the HCL Portal
administrative user:
- Optional:
Complete the following steps to create a directory suffix:
- Click the Server Administration folder in the directory server console
navigation.
- Click the Manage Server Properties folder under the Server Administration
folder and then select Suffixes on the main page.
- Type the Base DN name for the suffix; for example: dc=yourcompany,dc=com.
- Click Add.
- Click OK to save your changes.
-
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 your LDAP server.
- Use the ContentUsers.ldif file for the IBM® Content
Manager group and user ID if you configured HCL Web Content Manager.
-
Replace every dc=yourco,dc=com with your suffix.
-
Replace any prefixes and suffixes that are unique to your LDAP server.
-
You can specify user names other than wpsadmin and
wpsbind. For security reasons, specify nontrivial passwords
for these administrator accounts.
-
Save your changes.
-
Complete the instructions that are provided with your directory server to import the LDIF
file.
-
Complete the following steps to create the HCL Portal administrative user:
-
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 your LDAP server.
- Use the ContentUsers.ldif file for the IBM® Content
Manager group and user ID if you configured HCL Web Content Manager.
-
Replace every dc=yourco,dc=com with your suffix.
-
Replace any prefixes and suffixes that are unique to your LDAP server.
-
You can specify user names other than wpsadmin and
wpsbind. For security reasons, specify nontrivial passwords
for these administrator accounts.
- Optional:
If you use IBM® Security Access Manager Version 5.1, set the objectclasses to accessGroup. If you
use Security Access Manager Version 6, set the objectclasses to groupOfNames.
-
Save your changes.
-
Complete the instructions that are provided with your directory server to import the LDIF
file.