Portal, V6.1

---

 

Prepare a SecureWay Security Server

If you plan to use a SecureWay Security Server as an LDAP user registry, install and set up the server so that it will communicate with IBM WebSphere Portal.

To prepare SecureWay Security Server:

1. Install SecureWay Security Server; refer to the IBM SecureWay Security Server for z/OS and OS/390^® for information.

2. To create the WebSphere Portal administrative user:

   1. Optional

      To create a new directory suffix:

      1. Click the Server Administration folder, located in the left-hand navigation of the directory server console.

      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=setgetweb,dc=com

      4. Click Add.

      5. Click OK to save your changes.

      6. Stop and restart the LDAP server.

   2. Open the appropriate LDIF located in root directory of the CD setup, with a text editor:

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

      • Use the ContentUsers.ldif file for the IBM DB2 Content Manager group and user IDs if you configured DB2 Content Manager.

   3. Replace every dc=yourco,dc=com with your suffix.

   4. Replace any prefixes and suffixes that are unique to your LDAP server.

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

   6. Optional

      If using IBM Tivoli Access Manager for e-business Version 5.1, set the objectclasses to accessGroup. If using Tivoli Access Manager V6 set the objectclasses to groupOfNames.

   7. Save changes.

   8. Follow the instructions provided with your directory server to import the LDIF file.

   9. Stop and restart the LDAP server.

 

Parent topic

Preparing user registries on AIX

---