Configure automatic mail detection using a non-Domino LDAP directory

If WebSphere Portal authenticates with a non-Domino LDAP directory, you can configure Collaborative Services to use that LDAP directory to detect each user's mail server and mail file.

1. Configure portal to recognize Lotus Domino and Collaborative Services

   You configure the WebSphere Portal server to recognize the server (either an Lotus Domino or non-Lotus Domino server) running the LDAP service so that Lotus Collaborative Services can use that server to support features in Lotus Domino-based portlets. To configure the WebSphere Portal server, you update the CSEnvironment.properties file.

2. Configure a binding user ID for Collaborative Services

   The bind user ID is used by Lotus Collaborative Services to retrieve user attributes required for authentication from the selected LDAP directory. Setting the bind user ID to use the LDAP server for Collaborative Services supports automatic detection of users' mail files for any of the collaborative portlets that use a Lotus Domino back-end server for messaging (Lotus Notes View and Domino Web Access). If the server is a Lotus Domino LDAP, setting the bind user also supports the server or database drop-down lists that appear in Lotus Domino portlets.

3. Synchronizing mail server and mail file in a non-Domino LDAP for autodetection

   If user e-mail addresses are not consistent between the Domino LDAP server and the LDAP server that WebSphere Portal uses, configure Collaborative Services to query the Domino LDAP server for the mail file and mail server, and add the attributes to the person record in the non-Domino LDAP directory. Doing so enables the Domino Web Access portlet to retrieve the e-mail file and server information. Using this configuration option means that the server picker option in the Domino Web Access portlet will not be available.

Parent topic:

Configure e-mail integration

Related concepts

Automatic detection of mail files

---