Troubleshoot Lotus Domino and the Extended Products

 

+

Search Tips   |   Advanced Search

 

 

Set debug parameters for the Domino Extended Products

We can set the following parameters in the NOTES.INI file of the two Domino servers running Lotus Sametime and Lotus QuickPlace : 

debug_sso_trace_level=2 
debug_outfile=debug.out

Name the Lotus Sametime debug file imdebug.out and Lotus QuickPlace file twdebug.out to distinguish between the two.

We can add these through the Domino console by typing: set config <parameter or by editing the NOTES.INI filemanually.

Restart the server to create the new debug out file in the domino_data/IBM _TECHNICAL_SUPPORT directory.

 

Troubleshoot IBM Lotus Domino

This section provides information about troubleshooting problems that might arise with Lotus Domino.

 

Problem: WebSphere Global Security with SSO-enabled Lotus Domino LDAP requires modification to the Lotus Domino Web Configuration document

If you enable single sign-on (SSO) between WebSphere Application Server and Lotus Domino servers in a portal environment that has applied WebSphere Global Security, edit the Lotus Domino Web Configuration document to correct an error that occurs in the LDAP Realm when Lotus Domino imports LTPA keys from WebSphere Application Server.

Solution: To correct the LDAP Server setting that is imported into Lotus Domino with the LTPA keys, open the Lotus Domino Web Configuration document and edit the LDAP Server value to include the backslash, for example, yourLDAPServer.yourdomain.com\:389. Restart the Lotus Domino LDAP server to initialize this change. Replicate the Domino Directory to all Lotus Domino LDAP servers, Lotus Sametime, and Lotus QuickPlace servers. Remember to start and stop the HTTP task on all Lotus Domino and Lotus QuickPlace servers.

 

Problem: SSO does not work after the portal is configured to use SSL

If you configure SSO for WebSphere Application Server and Lotus Domino servers in a portal environment, and then enable SSL for the portal, regenerate and then import a new LTPA key to reflect the new port number for the SSL configuration.

Solution: If you enable SSO between WebSphere Application Server and Lotus Domino servers, the default port number used is 389. This port number changes to 636 (by default) for an SSL configuration. In the WebSphere Administrative Console, regenerate the LTPA key, restart WebSphere Application Server, and then export the key from the WebSphere Administrative Console. Next, import the LTPA key into the Web SSO Configuration document on the Lotus Domino servers.

 

Problem: Database lists in some portlets fail to populate with database names

In the Lotus Notes View, Domino Web Access, and My Lotus QuickPlaces portlets, drop-down lists of database names may appear empty. There are several possible causes:

  • The Lotus Domino server configured for use with the portal does not have SSL set up correctly

  • The Lotus Domino server uses the setting Redirect to SSL instead of Enable SSL.

  • The Lotus Domino messaging/application server for the portlets does not actually contain databases of the correct type.

  • All Lotus Domino servers used with the portal do not have SSL certificates signed by the same certificate authority.

Solution:

  1. Perform the following steps to eliminate the possible problems:

  2. Ensure that the Lotus Domino server configured for use with the portal has SSL set up properly.

  3. Do one of the following:

    • If the Lotus Domino server uses HTTP, set HTTP to run on the default port of 80.

    • If the Lotus Domino server uses HTTPS, set HTTPS to run on the default port of 443, and enable DIIOP over SSL.

  4. In the Server document, select Internet Protocols > HTTP, and make sure that Allow HTTP clients to browse databases is set to Yes.

  5. While examining the Lotus Domino server, determine whether the server uses the Enable SSL or Redirect to SSL setting.

  6. Restart the Domino server.

  7. If the problem remains, check the Lotus Domino messaging/application servers and verify the databases users are attempting to view through the portlets exist, and are of the appropriate design for the portletType parameter configured in the portlets. For example, in a portlet configured with a portletType of NOTESDISCUSSION, the drop-down list shows only Notes
    databases with a discussion design. If no databases of the appropriate type exist, either inform users of this error, or make appropriate databases available.

  8. If the problem remains, examine the SSL certificates for each of the Lotus Domino servers that contain source databases for portlets in the portal, and make sure they are all signed by a single certificate authority (CA).

  9. From any of the Lotus Domino servers that has a properly signed SSL certificate, copy the TrustedCerts.class file from within the directory...

    domino_root/data/domino/java

  10. Navigate to the portal server's class directory...

    portal_server_root/shared/app/

    ...and paste the copied TrustedCerts.class file.

  11. If the problem remains, and you determined earlier that the Lotus Domino server uses the Redirect to SSL setting, locate and edit the CSEnvironment.properties file on the portal server.

  12. If the following property does not already exist and is not already set to this value, add it and set its value using the following line: 

    CS_SERVER_DOMINO_DIRECTORY_1.iiopport=63148

  13. Save the CSEnvironment.properties file.

  14. Restart the portal server.

 

Problem: The Domino Directory used for people awareness may cause delays or lack of awareness if it contains identical common user names

Solution: Modify names of any users who share a common name so that names become unique (for example, by including an initial).

 

Problem: For portlets that display people's names with online awareness, names containing commas do not display the correct online status when the Lotus Domino server is 6.5.4

If a person's common name contains a comma, for example, "Smith, Chris," and the Lotus QuickPlace server uses Lotus Domino 6.5.4 for its LDAP, the correct online status for the person will not be displayed in the portlet. This problem occurs in any of the Domino and Extended Products Portlets that display people's names with online awareness.

Workaround: There is a workaround that will fix the problem. However, if the portal also uses Lotus Domino for its LDAP directory, this workaround will disable awareness for the People Finder portlet entirely, even on names that do not contain commas.

Add the following content to the CSEnvironment.properties file: 

# The format of the name that will be added to the watch lists for awareness. 
CS_SERVER_SAMETIME_1.watchnameformat=dn

Solution: Check with IBM Support for an interim fix for the Domino LDAP server (release 6.5.4).

 

Troubleshoot IBM Lotus QuickPlace

This section provides information about troubleshooting problems that might arise with Lotus QuickPlace.

 

Problem: Team Workplace 6.5.1 ( Lotus QuickPlace ) requires an interim fix to work with Lotus Domino 6.5.x

Without this fix, Lotus Domino HTTP does not start, preventing the Team Workplace ( Lotus QuickPlace ) server software from operating.

For release 6.5.1 only, Lotus QuickPlace is called Team Workplace.

Solution: A required interim fix for Team Workplace release 6.5.1 is available on the IBM Support Web site. Refer to the following troubleshooting technote:

Technote 1198555: Required Team Workplace 6.5.1 Enabling Fixes for Domino 6.5.4 and 6.5.5
We can also use Search at IBM Support to find technotes by number.

 

Enable diagnostic tracing on the Lotus QuickPlace (QuickPlace) server

Perform the following steps to enable diagnostic tracing on the Lotus QuickPlace (QuickPlace) Server Console (when using any QuickPlace portlet, or any other portlet using the QPService APIs):

  1. Add the following lines in the notes.ini file of the Lotus QuickPlace server.

    • For Information: QuickPlaceJavaLogging=3

    • Details for other logging levels:

      • For Debug: QuickPlaceJavaLogging=5 or 4

      • For Error only: QuickPlaceJavaLogging=0 or 1

      • For Warnings: QuickPlaceJavaLogging=2

  2. Restart the Lotus QuickPlace server.

 

Parent Topic

Reference topics for collaboration

 

Related concepts

Reference topics for collaboration

 

Related reference

Troubleshoot Domino and Extended Products Portlets