Plan integration of Portal and Domino

 

+

Search Tips   |   Advanced Search

 


Single directory: Non-Domino LDAP Decisions

You have WebSphere Portal installed and in active use.

Your portal site is configured with an LDAP directory other than Domino with a substantial user repository in active use.

You intend to integrate collaborative portlets

You want the 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 Domino server you intend to integrate, make sure that 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 Domino server before you can use it with the portal.

Set up a Sametime server to support awareness. IBM recommends configuring 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: Domino LDAP Decisions

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 Domino integration. Install and configure Domino as your 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.

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 Sametime as the directory configured for the portal, and Domino LDAP is the best choice for Sametime; therefore, in a new site IBM recommends using Domino LDAP as the single directory.


Dual directory-type site: Non-Domino LDAP for portal with Domino LDAP for Sametime Decisions
You already have a mature installation of Domino servers including Sametime or Domino Web Access (iNotes). Your 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 your Domino installations.

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

You want the portlets to have online awareness features (your Domino users are accustomed to 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...


Multiple directory-type site: Non-Domino LDAP for portal, other directories for Sametime Decisions

You already have a mature installation of Domino servers including Sametime or Domino Web Access (iNotes). Your 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 your Domino installations.

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

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

You want the portlets to have online awareness features (your users are accustomed to 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 Domino installations and an investment in an extensive native 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 your native Domino directory and the portal LDAP directory. See the following topics for tasks specific to reconciling directories:


Parent topic:

Plan for collaborative servers and portlets