IBM i stand-alone: Prepare a Tivoli Directory Server

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

To prepare Tivoli Directory Server:

1. Customize the LDAP directory servers settings using the Directory Services Configuration Wizard.

   You must have *ALLOBJ and *IOSYSCFG special authority to use the wizard. Go to IBM System i and IBM i Information Center, select the appropriate Information Center version and navigate to...

   e-business and Web serving -> Security and IBM Tivoli Directory Server for i5/OS (LDAP) -> IBM Tivoli Directory Server for i5/OS (LDAP)
   Due to a restriction in Tivoli Directory Server, users or groups must not contain a Turkish uppercase dotted I or lowercase dotted i in the DN as this will prevent correct retrieval of that user or group.

2. Create the WebSphere Portal administrative user:

   1. Optional. Create a new directory suffix:

      1. Go to IBM System i and IBM i Information Center, select the appropriate Information Center version and navigate to...
         Networking -> TCP/IP applications, protocols, and services -> IBM Directory Server for iSeries (LDAP) -> Administer Directory Server -> General administration tasks -> Add and Removing Directory Server suffixes

      2. Stop and restart the LDAP server.

   2. Open the appropriate LDIF file, located in the root directory of the CD setup, with a text editor:
      Use PortalUsers.ldif as a working example and adapted appropriately to work with LDAP server.

      Use ContentUsers.ldif for the IBM DB2Content 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 LDAP server.

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

   6. If using IBM Tivoli Access Manager Version 5.1, set the objectclasses to accessGroup. If using Tivoli Access Manager Version 6, set the objectclasses to groupOfNames.

   7. Save changes.

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

Parent

Configure WebSphere Portal to use a user registry

Next topic

Choose the user registry model

 

+

Search Tips   |   Advanced Search