Determine the needs of the portal site

The following general use cases are intended only to provide some recommendations for decisions about directories when integrating the Dominoand Extended Products Portlets.

To identify use case, ask yourself two questions about site:

  1. What directory are you already using, or do you want to use, for the user directory for WebSphere Portal? Possible answers are:

      A: LDAP directory other than Lotus Domino

      B: Lotus Domino LDAP directory

  2. What directory are you already using, or do you want to use, for the user directories for IBMLotus Sametime®? Possible answers are:

Table 1. Use case: 1A+2A

Single directory (LDAP other than Lotus Domino) site Your decisions about Lotus Domino integration

  • You have WebSphere Portal installed and in active use.

  • Your portal site is configured with an LDAP directory other than Lotus Domino (for the purposes of these scenarios, assume IBM Tivoli Directory Server, but any other LDAP has the same considerations) with a substantial user repository in active use.

  • You intend to integrate collaborative portlets

  • You want the Lotus Domino portlets to have online awareness features.

  • You want users to be able to work in portlets without authentication other than logging into the portal (that is, you need the single sign-on feature). In fact, you may already have single sign-on enabled on the portal server.

  • You do not yet have any Domino and Extended Products or servers installed, or if you have them, they are not yet configured for use with the portal.

      If you have an existing Lotus Domino server you intend to integrate, verify its release is supported before you attempt to use it with the portal. See the Software for collaboration section in the WebSphere Portal hardware and sofware requirements. If the release is not supported, upgrade the Lotus Domino server before you can use it with the portal.
Your environment is typical of most portal customers. Follow the instructions for installation and integration in the rest of the Domino Integration and Messaging section of the Information center.

You must install and set up a Lotus Sametime server to support awareness. We recommend that you configure the server to authenticate against the LDAP directory already configured with the portal site.

To enable single sign-on, configure it as a last task after installing and configuring new servers for Domino and Extended Products, to include all the new servers.

Support for key features in the collaborative portlets such as auto-detection of users' mail files requires additional configuration in this environment.

Single directory (Lotus Domino LDAP) site Your decisions about Lotus Domino integration

  • You have installed WebSphere Portal

  • You have no LDAP user directory configured yet.

  • You intend to integrate collaborative portlets

  • You want the portlets to have online awareness features, and you want users to be able to work in portlets without authentication other than logging into the portal (that is, you need the single sign-on feature)

Your environment is recommended, especially for new portal sites, if you intend to make full use of Lotus Domino integration. Install and configure Lotus Domino as LDAP directory for the portal, and then follow the instructions for installation and integration in the rest of the Domino Integration and Messaging section of the Information center.
Fastpath: This is the environment most suited to configuration with the Domino-WebSphere Portal Integration Wizard.

It is a best practice to use the directory configured for Lotus Sametime as the directory configured for the portal, and Lotus Domino LDAP is the best choice for Lotus Sametime; therefore, in a new site we recommend using Lotus Domino LDAP as the single directory.

Dual directory-type site (LDAP other than Lotus Domino for portal with Lotus Domino LDAP for Lotus Sametime user directory) Your decisions about Lotus Domino integration

  • You already have a mature installation of Lotus Domino servers including Lotus Sametime or iNotes. Your Lotus Domino servers are upgraded to a release supported by WebSphere Portal.

  • You have newly installed WebSphere Portal or have the intention to deploy it. You may even have a mature portal site, but have not yet attempted to integrate it with Lotus Domino installations.

  • You intend to integrate collaborative portlets, especially messaging portlets to support existing Lotus Domino mail and calendar users.

  • You want the portlets to have online awareness features (your Lotus Domino users are accustomed to Lotus Sametime instant messaging), and you want users to be able to work in portlets without authentication other than logging into the portal (that is, you need the single sign-on feature).

Your environment is typical of many portal customers who have investments in both directories that must be maintained.

Follow the instructions for installation and integration in the rest of the Domino Integration and Messaging section of the Information center.

See the following topics for tasks specific to reconciling directories:

Multiple directory-type site (LDAP other than Lotus Domino for portal with a combination of other directories, most likely native Lotus Domino directory for Lotus Sametime Your decisions about Lotus Domino integration

  • You already have a mature installation of Lotus Domino servers including Lotus Sametime or iNotes. Your Lotus Domino servers are upgraded to a release supported by WebSphere Portal.

  • You have newly installed WebSphere Portal or have the intention to deploy it. You may even have a mature portal site, but have not yet attempted to integrate it with Lotus Domino installations.

  • You have a native Lotus Domino Directory (non-LDAP) in active use. Lotus Sametime uses a native Lotus Domino Directory.

  • You intend to integrate collaborative portlets, especially messaging portlets, to support existing Lotus Domino mail and calendar users.

  • You want the portlets to have online awareness features (your users are accustomed to Lotus Sametime instant messaging), and you want users to be able to work in portlets without authentication other than logging into the portal (that is, you need the single sign-on feature).

Your environment is typical of many customers with mature Lotus Domino installations and an investment in an extensive native Lotus Domino directory who want to integrate portal.

Follow the instructions for installation and integration in the rest of the Domino Integration and Messaging section of the Information center.

To support SSO, reconcile authentication between user identifications in native Lotus Domino directory and the portal LDAP directory.

See the following topics for tasks specific to reconciling directories:


Parent

Plan for collaborative servers and portlets

 


+

Search Tips   |   Advanced Search