Prepare a SecureWay Security Server

To use a SecureWay Security Server as an LDAP user registry, install and set up the server so that it communicates with IBM WebSphere Portal.

1. Install SecureWay Security Server. Refer to IBM SecureWay Security Server for z/OS and OS/390 for information.

2. Use the web administration tool to create the WebSphere Portal administrative user:
   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=myco,dc=com.

   4. Click Add.

   5. Click OK to save the changes.
   1. Open the appropriate LDIF file in the PORTAL_HOME/installer/wp.iim/ldif directory, with a text editor:

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

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

   2. Replace every dc=myco,dc=com with the suffix.

   3. Replace any prefixes and suffixes 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. Save the changes.

   6. Complete the instructions provided with our directory server to import the LDIF file.

3. To create the WebSphere Portal administrative user:
   To create a directory suffix:

   1. Go to IBM System i and IBM i Information Center, select the appropriate documentation version and go to Networking > TCP/IP applications, protocols, and services > IBM Directory Server for iSeries (LDAP) > Administering Directory Server > General administration tasks > Adding and Removing Directory Server suffixes for information.

   2. Stop and restart the LDAP server.
   1. Open the appropriate LDIF file in the PORTAL_HOME/installer/wp.iim/ldif directory, with a text editor:

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

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

   2. Replace every dc=myco,dc=com with the suffix.

   3. Replace any prefixes and suffixes 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. If we use IBM 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 the changes.

   7. Complete the instructions provided with our directory server to import the LDIF file.

Parent Prepare the user registry software