WebSphere

 

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

 

Checklist of tasks: LDAP server for Lotus Collaborative Services

 

+

Search Tips   |   Advanced Search

 

A server that runs the LDAP service is a requirement to support automatic mail detection in the following portlets...

  1. Lotus Notes View
  2. Domino Web Access
  3. Common Mail and Common Calendar

The Domino-WebSphere Portal Express Integration Wizard can do many parts of this task for you, except for...

The wizard always sets the bind user for authentication.

This task supports the following portlets:

An LDAP server supports two important features in the portlets.

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:

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, read and follow the instructions in the following tasks to set up a Lotus Domino Directory as your primary portal directory; then you have the option of using the same server for both purposes.

Perform the tasks in the checklist in the Information center in Set up Domino Directory.

 

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).

After you complete the following sequence of tasks, if users continue to experience problems with the server drop-down list or auto-detection of mail databases, see the following troubleshooting technotes:

Technote 1157029 Troubleshooting Automatic Detection of your Mail File with the Different Collaborative Portlets
Technote 1157249 Troubleshooting Pickers in Collaborative Portlets
You can also use Search at IBM Support to find technotes by number.

 

Checklist of tasks

  1. Starting the LDAP service automatically on a Lotus Domino server
  2. Configuring the WebSphere Portal Express server to recognize Lotus Domino and the Collaborative Services
  3. Specifying the Internet host name of the Lotus Domino server
  4. Collaborative Services and user authentication
  5. Supporting automatic mail detection with an LDAP directory other than Lotus Domino

 

Parent topic:

Integrating the Lotus Domino servers and portlets

 

Related concepts

Messaging: the Common PIM portlets
Domino-WebSphere Portal Express Integration wizard overview