Configure IBM Lotus Domino Enterprise Server LDAP server with WebSphere Portal

 

+
Search Tips   |   Advanced Search

 

Contents

  1. Overview
  2. Understanding the use of the Domino LDAP with Collaborative Services
  3. Load the LDAP task
  4. Configure http-hostname for Domino LDAP (optional)
  5. Configure Collaborative Services to use Domino Directory
  6. Configure Collaborative Services to bind to Domino LDAP

 

Overview

If you plan to use any of the following portlets, configure the Collaborative Services to work with a Domino server running the LDAP task in your Notes domain:

  • Notes and Domino
  • Inline Team Workplaces
  • Domino Web Access

This is an additional and completely different task from configuring the portal server with LDAP. Even if portal is configured with an LDAP directory other than Domino, this task is still necessary. Furthermore, if the portal server is configured with a Domino LDAP server, you still must complete this step, and the Domino LDAP server used with the Collaborative Services can be the same or a different Domino LDAP server in your Notes domain.

Note that there is some debate about this, with some people saying that you can only one run flavor of LDAP in your Portal. For example, you cannot run Domino LDAP for collaborative portlets, and Novell eDirectory for the rest of the Portal. Contact your IBM representative for clarification

 

Understanding the use of the Domino LDAP with Collaborative Services

The Domino LDAP server is used for two features of the Collaborative portlets.

  1. The drop-down list of servers.

    The Notes and Domino, Inline Team Workplaces and Domino Web Access portlets, in edit mode, all provide a drop-down list of servers. The tasks below are requirements to support this drop-down server list; if they are not completed, users who edit the properties of these portlets must manually enter a server name in a field.

  2. Automatic detection of mail database file.

    The Notes and Domino and Domino Web Access portlets are configured by default to detect a user's mail file based on the login name with which the users signs into the portal. The tasks below are requirements to support the automatic detection of users' mail files.

If you do not wish to take advantage of either of the features above, and you do not wish to run the LDAP task on one of your Domino servers, you can skip to the task Configure Collaborative Services to use Domino Directory, and enter a placeholder hostname for the LCC.DominoDirectory.Server. This placeholder host.name should not be the default value for this field (yourServer.yourDomain.com) and should not be a machine currently in your environment. The Notes and Domino, Inline Team Workplaces and Domino Web Access portlets will work only if you complete Configure Collaborative Services to use Domino Directory.

 

Load the LDAP task

For the Domino portlets and Lotus Team Workplace inline portlet to work, Collaborative Services must be able to communicate with a Domino server over LDAP. To enable the LDAP task in Domino, issue the following command on the Domino server: 

load ldap

To enable the LDAP task to load automatically every time the Domino server starts, peform the following steps:

  1. Open the notes.ini in the Domino Program directory.

  2. Locate the line ServerTasks= and add ,ldap to the end of the line.

  3. Save and close the file.

For more information on the LDAP task, refer to the Domino Administration Help.

 

Configure http-hostname for Domino LDAP (optional)

This task enhances how users connect to their Mail or Application server through portlets. Specifically, the Domino portlets and Lotus Team Workplace Inline portlets require the ability to query specific fields from the Domino LDAP server. Perform the following steps:

  1. Start the Domino administrative console.

  2. Open the address book (names.nsf) from the LDAP server.

  3. Navigate to the Server - Servers view

  4. Double click on the server that you want to appear in the drop-down list, or the users Domino Mail server.

  5. Click the Internet Protocols tab.

  6. On the HTTP tab, check the Host(s) Name field to add the host.name for this server.

  7. Click Save and Close.

In addition to populating the http-hostname field, also configure the Collaborative Services to bind to the Domino LDAP. Perform this step after configuring Collaborative Services to use Domino Directory.

 

Configure Collaborative Services to use Domino Directory

To perform the configuration task, do the following:

  1. Stop WebSphere Portal. 

    stopServer WebSphere_Portal

  2. Edit...

    <wp_root>/config/wpconfig.properties

    ...and, in the Collaborative Services properties section, enter the values appropriate for your environment.

    Property Value
    LCC.DominoDirectory.Enabled

    Determines whether Lotus Domino Directory is enabled.

    Recommended: true

    Default: false

    LCC.DominoDirectory.Server

    Name of the Lotus Domino Directory.

    Recommended: my.server.com

    Default: my.server.com

    LCC.DominoDirectory.Port

    Port number for the Lotus Domino Directory.

    Recommended: 389

    Default: 80

    LCC.DominoDirectory.SSL

    Determines whether Lotus Domino Directory is enabled to communicate over SSL.

    Recommended (SSL): true

    Recommended (non-SSL): false

    Default: false

  3. Save the file.

  4. Type the following command to run the appropriate configuration task: 

    cd <wp_root>/config 
 ./WPSconfig.sh lcc-configure-dominodirectory -DDBPassword=password -DWmmDbPassword=password

    To configure all Lotus collaborative services values, edit appropriate values in wpconfig.properties, and then run... 

    WPSconfig.sh lcc-configure-all

  5. If you encounter an error, check the logs

  6. Start WebSphere Portal. 

    startServer.sh WebSphere_Portal

  7. Advanced configurations for using Collaborative Services and Domino Directory are available.

 

Configure Collaborative Services to bind to Domino LDAP

  1. Stop WebSphere Portal.

  2. Edit... 

    <wp_root>/shared/app/config/CSEnvironment.properties

  3. Remove the comment tag (#) from the beginning of the line that contains...

    CS_SERVER_DOMINO_DIRECTORY_1.userid=

  4. At the end of the line, add a user ID that has at least reader access to the address book (names.nsf) of your Domino LDAP server. Type the Domino LDAP canonical name for the user.

  5. Go to the line that contains...

    CS_SERVER_DOMINO_DIRECTORY_1.encryptedpwd=.

  6. Remove the comment tag (#) from the beginning of this line.

  7. Copy the line that contains...

    CS_SERVER_DOMINO_DIRECTORY_1.encryptedpwd=

    ...and paste it into a new file.

  8. In the new file, at the end of the line, add the internet password for the user ID (CS_SERVER_DOMINO_DIRECTORY_1.userid=).

  9. Save this new file as...

    $WAS_HOME/bin/dominobind.txt

  10. Encrypt the file... 

    cd $WAS_HOME/bin
PropFilePasswordEncoder dominobind.txt CS_SERVER_DOMINO_DIRECTORY_1.encryptedpwd

  11. Open the dominobind.txt file, and copy the encrypted password after...

    CS_SERVER_DOMINO_DIRECTORY_1.encryptedpwd=

  12. Go back to the CSEnvironment.properties file.

  13. Paste the encrypted password after CS_SERVER_DOMINO_DIRECTORY_1.encryptedpwd=.

  14. Save and close the CSEnvironment.properties file.

  15. Close the dominobind.txt file

  16. Delete dominobind.txt and dominobind.txt.bak from $WAS_HOME/bin.

  17. Restart WebSphere Portal.

Now Domino server names should appear in the server drop-down list and users should be able to automatically detect mail database for the Domino Web Access (iNotes) and Notes Mail portlets. If you continue to experience problems with the drop-down (picker) list or auto detection of mail database see the following troubleshooting technotes:

  • Troubleshooting Pickers in Collaborative Portlets, technote number 1157249.

  • Troubleshooting Automatic Detection of your Mail File with the Different Collaborative Portlets, technote number 1157029.

 

See also

Home | Support | Terms of use | Feedback

 

WebSphere is a trademark of the IBM Corporation in the United States, other countries, or both.

 

IBM is a trademark of the IBM Corporation in the United States, other countries, or both.