WebSphere Portal Express and Express Plus V5 for the IBM eServer iSeries Server

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.

QuickPlace configuration

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

the

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:

http://www.lotus.com/support

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

mapping.

6.1.4 Summary

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

running.

212 WebSphere Portal Express and Express Plus V5 for the IBM Eserver iSeries Server

6.2.1 Creating a new WebSphere Portal instance

Follow these steps to create a new WebSphere Portal instance with the Lotus collaboration

components enabled:

1. Make sure that your HTTP Admin instance is running. If it is stopped, start it by entering

the following OS/400 command:

STRTCPSVR SERVER(*HTTP) HTTPSVR(*ADMIN)

2. Point your browser to:

http://systemName:2001

Here systemName is the host name of your iSeries.

3. In the pop-up window, type your user ID and password. Press Enter.

4. Click the IBM HTTP Server for iSeries link.

5. On the next page, click Create WebSphere Portal in the navigation pane.

6. The wizard starts. Click the Next button.

Attention: During the course of the residency to write this book, the iSeries development

lab made several changes to the WebSphere Portal wizard. As a result, the sequence and

the look of the windows have changed. The remaining information is still valid.

For current information about the WebSphere Portal wizard, see Appendix C, “WebSphere

Portal wizard updates” on page 511.

Note: For a more expanded discussion that covers all the WebSphere Portal wizard steps,

except for the ones related to the Lotus components, see Chapter 4, “Advanced

configuration” on page 81.

Tip: Make sure that you resize or maximize your browser window before you start the

wizard. If you resize or maximize the browser window while running the wizard, the

page reloads so that you lose all of the data that you entered in the wizard. If this

happens, you must start the wizard from the beginning.