Portal, Express Beta Version 6.1 Operating systems: i5/OS, Linux,Windows

Checklist of tasks: LDAP server for Lotus Collaborative Services

A server that runs the LDAP service is a requirement to support automatic mail detection in the Lotus Notes View portlet and the Domino Web Access portlet.

Wait! The Domino-WebSphere Portal Express Integration Wizard can do many parts of this task for you, except for setting the Lotus Domino server to run the LDAP task (which must be running before you run the wizard), and configuring automatic detection for an LDAP other than Lotus Domino (the wizard integrates only the Lotus Domino LDAP server). Also, the wizard always sets the bind user for authentication.

This topic provides information for configuring a server in your Lotus Domino domain to run the LDAP service to support portlets and the Collaborative Services in the portal. A Lotus Domino LDAP server is recommended, because it also supports drop-down selection lists of servers and databases in these portlets, but you can use an LDAP server other than Lotus Domino for automatic mail detection if it better fits the needs of your site. This task supports the following portlets:

• Lotus Notes View
• Domino Web Access

Understanding the use of an LDAP server with Collaborative Services

• Automatic detection of mail database file for the logged-in user. For more information, see About automatic detection of mail files.
• The drop-down list of servers (supported only by a Lotus Domino LDAP). When users personalize the Lotus Notes View and Domino Web Access portlets, the portlets provide a drop-down list of back-end messaging/application servers. If this feature is not enabled, users must manually enter a server name in a field to point a portlet to its back-end Domino server. Support for this feature in these portlets is provided when the LDAP directory for Collaborative Services is a Lotus Domino server with the DIIOP service running.

How many LDAP servers do you need?

• If your site is already configured with a Lotus Domino server running LDAP as its primary directory, you can use the same server to support Collaborative Services.
• If your site is already configured with a non-Lotus Domino LDAP directory, you can do one of two things: configure a Lotus Domino server (perhaps one of your Lotus Domino back-end messaging and application servers) with LDAP to support auto-detection and server/database lists in the Collaborative Services and the Domino and Extended Products Portlets, or use the portal non-Lotus Domino LDAP to support auto-detection only.
• If your site is not yet configured with an LDAP directory (for example, it is a brand new site), a Lotus Domino Directory (LDAP) server as the portal user directory is a good choice for later extensibility, and you can use it to support Collaborative Services. Before configuring a Lotus Domino server with LDAP for Collaborative Services, install and configure your LDAP user registry.

Collaborative Services without LDAP

If you do not want to take advantage of either of the features above, and you do not want to run the LDAP service on any Lotus Domino server, you can skip to the task Configuring the WebSphere Portal Express server to recognize Lotus Domino and the Collaborative Services, and enter a placeholder host name 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 server currently in your environment. The Lotus Domino-based messaging portlets and the Inline QuickPlace will work, but will not be able to take advantage of the features above.

Overview of tasks

Perform all the following procedures to enable LDAP and to configure these portlets, except those that state they are specific only to the type of LDAP you are not configuring (Lotus Domino LDAP or non-Lotus Domino LDAP).

• Technote 1157029 Troubleshooting Automatic Detection of your Mail File with the Different Collaborative Portlets
• Technote 1157249 Troubleshooting Pickers in Collaborative Portlets

Checklist of tasks

1. Starting the LDAP service automatically on a Lotus Domino server
   You configure an IBM Lotus Domino LDAP server to support IBM Lotus Domino and the Lotus Domino portlets by adding a setting to the NOTES.INI file that causes the server to start the LDAP service (server task) each time the server starts.
2. Configuring the WebSphere Portal Express server to recognize Lotus Domino and the Collaborative Services
   You run the Lotus Domino configuration task on the IBM WebSphere Portal Express server. Running the task allows the portal to recognize the presence of the server (either an IBM Lotus Domino or non-Lotus Domino server) running the LDAP service, so that Lotus Collaborative Services can use the server to support features in Lotus Domino-based portlets, primarily auto-detection of mail files.
3. Specifying the Internet host name of the Lotus Domino server
   In the Server document of the Lotus Domino Directory (NAMES.NSF) database on the Lotus Domino server, you specify the fully qualified Internet host name for the Lotus Domino server and Internet security options. These settings are part of the support for the server drop-down list that appears when users of the Lotus Notes View and Domino Web Access portlets edit portlet defaults, and automatic detection of users' mail files for any of these portlets that use a Lotus Domino back-end server for messaging.
4. Collaborative Services and user authentication
   The Lotus Collaborative Services search an LDAP directory for user information. You can enable the Collaborative Services to get the required information in two different ways: by setting up a bind user for authenticated LDAP, or by enabling anonymous user access to attributes in the directory.
5. Supporting automatic mail detection with an LDAP directory other than Lotus Domino
   If the LDAP directory configured for the portal and for Lotus Collaborative Services is not IBM Lotus Domino, and you want the automatic mail detection feature in Lotus Domino messaging portlets, you can modify the CSenvironment.properties file to support the feature.