Setting up Sun ONE

WebSphere Portal has been tested to support the LDAP server provided with Sun ONE Directory Server (Formerly iPlanet). See the WebSphere Portal requirements for supported versions.

Use the IBM Web Administration for iSeries tool when configuring WebSphere Portal instances. The wizard creates the necessary servers (HTTP and WAS), configures the server for Portal, configures the database for Portal, configures security (LDAP) for Portal, and deploys the portlets installed with the WebSphere Portal product. You can edit the Portal instance configuration manually after you have used the WebSphere Portal wizard.

 

Create a new user as the portal administrator

The following steps can be used if the portal administrative user does not exist in the directory.

  1. If you choose to use the LDIF file, locate PortalUsers.ldif in the root directory on the WebSphere Portal disc, and open it in a text editor.
    Note: The PortalUsers.ldif file is provided as a working example and needs to be adapted appropriately to work with the ldap.

  2. Replace all occurences of o=yourco.com with the suffix that you are using. Also, replace any prefixes and suffixes that are unique to the LDAP directory. You can specify user names other than wpsadmin and wpsbind. For security reasons, specify non-trivial passwords for these administrator accounts because it is easier to specify them now than to change them after installation. Save the changes.

  3. Follow the instructions provided with Sun ONE to import PortalUsers.ldif.

    Importing the PortalUsers.ldif file could overwrite existing user data.

  4. Stop and restart the LDAP server.

  5. After the portal installation, if you did not specify non-trivial passwords for the administrator IDs in the LDIF file, it is recommended that you change the passwords for these user IDs. See Changing passwords in the WebSphere Portal Information Center for instructions.

 

Example of the Sun ONE LDAP structure

The following schema is an example for Sun ONE and is referenced throughout the documentation for consistancy. The example below is designed to help you determine the appropriate values when configuring WebSphere Portal to work with the specific directory layout. The values shown match the default values for this LDAP. If you have an existing schema that varies from this example, replace the example values with the values. For instance, cn is shown as the group prefix; replace cn with the group prefix for the schema.

Sun ONE LDAP structure

  • LDAP suffix="o=yourco.com"
  • user prefix="uid"
  • user suffix="ou=people"
  • group prefix="cn"
  • group suffix="ou=groups"
  • Portal administrator DN="uid=wpsadmin,ou=people,ou=yourco.com"
  • Portal administrator group="cn=wpsadmins,ou=groups,o=yourco.com"

 

Next steps

You have completed this step. Continue to the next step by choosing one of the following topics:

 

See also