Chapter 6. Integrating Lotus products with WebSphere Portal 211
The specific example is the use of the NotesView portlet. If People Awareness is turned on for
a column that contains the common name of a user, you can use either directory (LDAP or
Native Domino). If the column contains the full canonical name of the user, and if Sametime is
using the LDAP directory, Sametime cannot determine the online status.
Unlike QuickPlace, which makes LDAP calls to the directory server, Sametime uses Directory
Assistance when authenticating against LDAP. Since Directory Assistance is necessary for
Sametime to operate, you must configure Directory Assistance on the Sametime server.
However, this is the only server where you should configure it. Although Sametime awareness
works, you will have the problems discussed earlier when authenticating to Domino
applications running on the Sametime server.
When using QuickPlace 2.08, you should configure the server to use Domino as the directory.
When configuring the underlying Domino server for SSO, you must use a special version of
domcfg.nsf file. This file contains an updated default domain login document that performs
additional processing to maintain the LTPA cookie. The special version of the domcfg.nsf file
is available from Lotus Support at:
If you use the default domcfg.nsf file that is provided with Domino, the LTPA cookie is
overwritten when you access QuickPlace. Then, when you return to WebSphere Portal, you
need to log in again.
Configure QuickPlace 3.0 to access the same LDAP directory as the WebSphere Portal. If
you are accessing an existing QuickPlace environment that has migrated from an earlier
version, this may be a problem. You may need to use the changemember command to update
the user names in QuickPlace to their LDAP version. This allows users to maintain their
current QuickPlace capabilities in the environment.
If you have a requirement that you must use either the Native Domino directory or Domino
Directory through LDAP, then you must obtain a patch that supports the appropriate name
Taking advantage of the core capability of SSO between WebSphere Portal and Domino
environments greatly enhances the user experience as well as increases user productivity.
With this information, you should be armed with the knowledge of how best to implement
SSO and understand better the underlying the details behind this core capability. In addition,
the methods outlined in this document allow you to configure your WebSphere Portal and
Domino environments to leverage their respective strengths. In more complex environments,
it may be desirable to consider taking advantage of Tivoli Access Manager.
6.2 Configuring Lotus components in WebSphere Portal
This section takes you through the steps to implement the integration scenarios described in
6.1, “Integration scenarios” on page 204. We configure LDAP and Lotus components through
the wizard. Prior to reading this section, you must have completed steps in Appendix A,
“Installing, configuring Lotus Instant Messaging and Web Conferencing, Lotus Team
Workplace” on page 383. You must also ensure that your Lotus components are up and