Domino-WebSphere Portal Integration wizard overview
The Domino-WebSphere Portal Integration wizard configures IBMLotus DominoLDAP and messaging/application servers and IBM Lotus Sametimeserver to support messaging and Lotus Sametime portlets (Domino Web Access, Lotus Notes View, Sametime Contact List, and Who Is Here).
If environment is a dual directory-type site that uses Microsoft Active Directory as an LDAP user registry and Lotus Domino Directory for messaging, you can use the Lotus Domino Active Directory Synchronization Tool (ADSync) as a bridge to connect Active Directory and Domino. ADSync simplifies system administration by letting you keep Active Directory users and groups in synch with Domino Directory users and groups. Once you set up ADSync, you can run the Domino-WebSphere Portal Integration wizard.
The wizard does not work with any other LDAP directories, federated LDAP, or a portal configured with Computer Associates eTrust SiteMinder.
The wizard performs the following tasks on behalf, eliminating manual procedures:
Task that the wizard performs Server that is configured For information on the equivalent manual procedure, see the following topic Lotus Domino configuration task WebSphere Portal server Configure portal to recognize Lotus Domino and Collaborative Services Bind user configuration task WebSphere Portal server Configure a binding user ID for Collaborative Services Server task enablement: DIIOP Lotus Domino messaging/application server(s) Configure automatic DIIOP and HTTP tasks on the Lotus Domino server Single Sign-On (SSO) configuration All Lotus Domino servers Configure single sign-on between WebSphere Portal and Lotus Domino Lotus Sametime server trust configuration Lotus Sametime server Configure trust for the Sametime Contact List portlet
Prerequisites for the Domino-WebSphere Portal Integration wizard
Your existing Domino and portal configuration must fit the following description in order for organization to use the wizard. The wizard can identify all Lotus Domino servers in domain for integration, so you need to know all servers you want to include.
- You must already have installed and set up the Lotus Domino servers you want to use the wizard to integrate into the portal site. The features of Lotus Domino and Lotus Sametime to use in WebSphere Portal must also be working on the Lotus Domino servers before integration into the portal site. You must have a Lotus Domino LDAP directory working, mail databases in place and users with access to them, Lotus Sametime awareness, chatting, and conferencing working on Lotus Sametime server, and the Domino Web Access client also working with Lotus Sametime awareness.
CAUTION: If you already have a Web SSO configuration on Domino servers, be sure to see the section below on Considerations for existing Web SSO environments before running the wizard.
- All Lotus Domino servers (LDAP, messaging/application, and the underlying server on the Lotus Sametime server) must be at least release 7.0.1. WebSphere Portal must not be configured with clusters.
i: All Lotus Domino servers (LDAP, messaging/application, and the underlying server on the Lotus Sametime server) must be at least release 7.0.2 with Cumulative Fix Pack 1.
- To use Active Directory as an LDAP user registry while using Lotus Domino Directory for messaging, install and initialize ADSync before you run the Domino-WebSphere Portal Integration wizard.
ADSync is included with the IBM Lotus Domino Administrator client as an installation option but is not installed by default. For detailed instructions on installation and setup, see the developerWorks article, Integrate IBM Lotus Domino Directory with Microsoft Active Directory using ADSync.
- The LDAP task must be running on Lotus Domino Directory server.
- All servers must be behind the same Internet security firewall, in the same Internet domain, and if they are Lotus Domino servers, in the same Lotus Domino domain.
- Security must be enabled on the portal server with the Lotus Domino LDAP server. It is recommended that you enable security by running the WebSphere Portal configuration wizard. The portal configuration wizard is located on the portal server.
If you choose not to run the portal configuration wizard, verify security has been manually enabled on the portal server.
- All Lotus Domino servers on which you intend to run the wizard must be running the HTTP server task so that the wizard can communicate over HTTP. For more information, see the topic on starting the DIIOP and HTTP tasks automatically on the Lotus Domino server.
- The user who runs the wizard must provide an ID that is recognized as an Administrator in the Server document in the Domino Directory (NAMES.NSF) file on the Lotus Domino LDAP server. For details, see the topic on planning names for servers and users.
- If you plan to use the wizard to integrate a Lotus Sametime server, the server must have an HTTP port specified. Specifying an HTTPS port as well allows for secure transmission of the LTPA token that the wizard copies.
Considerations for existing Web SSO environments
The wizard creates a fresh Web SSO (Single Sign-On) environment for all the Lotus Domino servers in Lotus Domino domain that you choose to configure.If installation of Lotus Domino is new, or if existing Lotus Domino and Lotus Sametime servers have no Web SSO documents in their Domino Directory applications (NAMES.NSF files), no further action is needed and you are ready to run the wizard.
If you do have one or more existing Web SSO documents, refer to the following checklist to evaluate whether site is ready to run the wizard. Technote #1256149, listed below under Related information, explains how to locate and examine the Web SSO document.
- If you have an existing Web SSO document in Domino Directory (NAMES.NSF), check to see whether it has the name LtpaToken. If all Web SSO documents in domain have other names, no further action is needed and you are ready to run the wizard. The wizard creates a document with this exact name and will not affect existing documents with other names.
- If the document is called LtpaToken, check to see whether there are any copies of it on other Lotus Domino servers in Lotus Domino domain that have different content (for example, with different servers listed in the document). The Web SSO document should always be created by replication so that its content is identical on all Lotus Domino servers. If you have documents with differing content, you need to correct the configuration before you can run the wizard. For instructions, see the technote.
- If the document is called LtpaToken and has the same content on all servers, check to see whether it was created by the Lotus Sametime server. A document created by the Sametime server before Web SSO is configured in Lotus Domino cannot be used with the wizard, and you need to correct this configuration. For instructions, see the technote.
- If the document is called LtpaToken, has the same content on all servers, and was not created by Lotus Sametime, check to see whether it was created by a different Lotus Domino administrator than the one who will run the wizard. You need to correct this configuration; for instructions, see the technote.
- If the document meets all the conditions above, but you do not plan to configure all the Lotus Domino servers currently listed in it, you need to correct this configuration to list only the servers you plan to use with the wizard. For instructions, see the technote.
- Otherwise, environment is probably ready to run the wizard, but see the technote if you have concerns.