Checklist of tasks: LDAP server for Lotus Collaborative Services
An LDAP server is required to support automatic mail detection in...
- Lotus Notes View portlet
- Lotus Domino Web Access portlet
The Lotus Domino-WebSphere Portal Integration Wizard can do many parts of this task for you, except for...
- Set the Domino server to run the LDAP task, which must be running before you run the wizard.
- Configure automatic detection for an LDAP other than Domino. The wizard integrates only the Domino LDAP server.
The wizard sets the bind user for authentication.
This topic provides information for configuring a server in your Domino domain to run the LDAP service to support portlets and the Collaborative Services in the portal. A Domino LDAP server is recommended, because it also supports drop-down selection lists of servers and databases in these portlets. Use an LDAP server other than Domino for automatic mail detection if it better fits the needs of your site.
An LDAP server supports two features in the portlets.
- Automatic detection of mail database file for the logged-in user
- The drop-down list of servers (supported only by a 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 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 Domino server with the DIIOP service running.
If your site is already configured with a Domino server running LDAP as its primary directory, use the same server to support Collaborative Services.
If your site is already configured with a non-Domino LDAP directory, you can do one of two things:
- Configure a Domino server.
Perhaps one of your 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,
- Use the portal non-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 Domino Directory (LDAP) server as the portal user directory is a good choice for later extensibility, and use it to support Collaborative Services. Before configuring a 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 Domino server, you can skip to the task on configuring the WebSphere Portal server to recognize Domino and the Collaborative Services, and enter a placeholder host.name for the...
CS_SERVER_DOMINO_DIRECTORY_1.hostnameThis 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 Domino-based messaging portlets 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-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
Checklist of tasks
- Start the LDAP service automatically on a Domino server
- Map VMM attributes to LDAP user attributes
- Configure the WebSphere Portal server to recognize Domino and the Collaborative Services
- Specify the Internet host name of the Domino server
- Collaborative Services and user authentication
- Support automatic mail detection with an LDAP directory other than Domino
Parent topic
Integrating the Domino servers and portlets
Related concepts
Configure the Common Mail portlet
Domino-WebSphere Portal Integration wizard overview
Related tasks
Configure the WebSphere Portal server to recognize Domino and the Collaborative Services
Related information
Technote 1157029
Technote 1157249