Portal Express, Version 6.0
Operating systems: i5/OS, Linux, Windows
Set up the Common PIM portlets and Lotus Domino to work together
To prepare a IBM® Lotus® Domino® server to work with the Common Mail and Common Calendar portlets, make sure that some required settings exist on the server.
You must first install the Lotus Domino Update for CPP that corresponds to your Lotus Domino release. For more information, see the Known limitations for Common PIM portlets section of the WebSphere Portal Express release notes. These portlets also require the following settings:
- Domino XML services must be enabled on the Lotus Domino messaging/application server. These services are not run by default, so perform one of the following tasks: (1) For Lotus Domino 6.5.3, add the line HTTPDomWSAppSpace=1 to the NOTES.INI file on the Lotus Domino server, and then restart the server. (2) For Lotus Domino 6.5.4, 6.5.5, 7.0, or 7.0.1, open the server document from the Domino Administrator client, click the Internet Protocols - Domino Web Engine tab, and enable Domino XML services. If Domino XML services are not running, users see the following error when trying to use the portlets: Unknown error (CLHAG0017E: Internal error sending http request: 404 - Not Found).
Wait! The Domino-WebSphere Portal Express Integration Wizard can enable XML Services for you (on Lotus Domino releases compatible with the wizard).
- The LDAP Lookaside property in the wpconfig.properties file should be set to true (Lookaside=true) if certain user mail preferences, such as signatures and the default text style for composing mail, will be saved in the Member Manager lookaside database. This saves user mail preferences across mail portlet instances.
That is, if users have a Common Mail portlet on more than one portal page, they can use the same mail preferences (for example, add the same signature to messages) regardless of the mail portlet instance they use.
If you do not want to enable Lookaside, the Email signature feature will not be shown, and the default text style setting will apply only to the current portal session. An alternative would be to extend the LDAP schema of the directory used by the portal server to contain the necessary attributes. For more information, see the Known limitations for Common PIM portlets section of the WebSphere Portal Express release notes.
- HTTP must be enabled on the Lotus Domino messaging/application server and users must have an HTTP password set. The Common Mail and Common Calendar portlets use HTTP to retrieve mail and calendar information from the server.
- If you are running WebSphere Portal Express and Lotus Domino on the same machine, set the Lotus Domino HTTP port to a non-conflicting port (such as 8080).
- When you configure a Lotus Domino server for use with these portlets, leave the Organization field blank when you create the Web SSO Configuration document so that the configuration is available to server documents (instead of Web site documents only). For more information on the Web SSO Configuration document, see Retrieving the WebSphere LTPA key.
- For users to search their Lotus Domino mail using the Common Mail portlet, they must first create a full-text index of their mail using either IBM Lotus Notes or IBM Domino Web Access, or a Lotus Domino administrator must create a full-text index of their mail for them.
Tip: To read an IBM developerWorks article that describes setting up WebSphere Portal Express, Lotus Domino, and the Common PIM portlets to work together, see Configuring WebSphere Portal and Lotus Domino for the Common PIM Portlets.
Parent topic:
Using the Common PIM portlets with Domino
Previous topic
Checklist of tasks: Lotus Domino messaging/application servers and portlets
Next topic
Enabling SSL connections to a Domino serverRelated concepts
Domino-WebSphere Portal Express Integration wizard overview