![]()
Portal Express, Version 6.0
Operating systems: i5/OS, Linux, Windows
About automatic detection of mail files
Messaging portlets are configured by default to detect a user's source mail file (a Notes database) based on the identity with which the user signs into the portal. The LDAP server for Lotus® Collaborative Services, and Single Sign-On configuration for the portal site, are requirements to support this feature.
The messaging portlets that use automatic detection are:
- Lotus Notes View
- Domino Web Access
- Common Mail or Common Calendar (when set to use Domino as a back-end messaging server)
In all cases described below, the automatic detection feature requires that the portal site is configured for multi-server Single Sign-On (SSO) authentication as described in Configuring single sign-on between WebSphere Portal Express and Lotus Domino.
Automatic detection when both the portal and Collaborative Services authenticate to an IBM Lotus Domino LDAPTip: The Domino-WebSphere Portal Express Integration Wizard can configure automatic detection for you when the portal uses a Lotus Domino LDAP user directory.
Automatic detection works in these portlets whether both directories are Lotus Domino LDAP, or they are the same Lotus Domino LDAP directory.
Automatic detection when the portal authenticates to an LDAP directory that is not Lotus Domino, and Collaborative Services authenticate to a Lotus Domino LDAP
This case requires the following tasks:
- Extend the LDAP schema on the LDAP directory that is not Lotus Domino, by adding the following attributes:
mailserver=mailserver.domain.com mailfile=mail/usermail.nsfThe forward slash in the specification for the mailfile attribute is required.
- On the Lotus Domino LDAP directory, take one of the following actions:
- Extend the schema as above.
- If your organization prefers not to extend the schema, populate the directory with a separate Person document for each user. The document must specify the name the person uses for logging in to the portal in either the Short Name or Common Name field. You can run an agent to create the documents.
- In addition, if you use the Common PIM portlets, modify the CSEnvironment.properties file on the portal server to include settings that will work for both the Common PIM portlets and the Domino and Extended Products Portlets, if your site uses both. Follow the procedure in Supporting automatic mail detection with an LDAP directory other than Lotus Domino. If you use only the Domino and Extended Products Portlets portlets such as Domino Web Access or Lotus Notes View, these settings are unnecessary.
Automatic detection when both the portal and Collaborative Services authenticate to an LDAP directory that is not Lotus Domino
Automatic detection also works when neither directory is a Lotus Domino LDAP, but extend the schema in both directories as described above.
Parent topic:
Integrating the Lotus Domino servers and portletsRelated tasks
Checklist of tasks: LDAP server for Lotus Collaborative Services Configuring single sign-on between WebSphere Portal Express and Lotus Domino