Troubleshoot Domino and the Extended Products

 

+
Search Tips   |   Advanced Search

 

  1. Set debug parameters for IM and Team Workplace
  2. WebSphere Global Security with SSO-enabled Domino LDAP requires modification to the Domino Web Configuration document
  3. SSO does not work after the portal is configured to use SSL
  4. Troubleshoot awareness in WebSphere Portal
  5. Change name formats so that names in the Notes view show up as being online
  6. Set up QuickPlace 3.0 to use IBM Tivoli Directory Server
  7. Enable diagnostic tracing on the QuickPlace server

 

Set debug parameters for IM and Team Workplace

Set the following parameters in the notes.ini file of the two Domino servers running Lotus Instant Messaging and Web Conferencing and Lotus Team Workplace: 

debug_sso_trace_level=2 
debug_outfile=debug.out

Two distinguish between the IM debug and the Team Workplace files, name them imdebug.log and twdebug.log respectively.

Create the new debug log files in...

Lotus\Domino\Data\IBM_TECHNICAL_SUPPORT directory.

You can add these through the Domino console by typing:

set config parameter

...or by editing the notes.ini manually and then restarting the Domino server.

 

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

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

 

Solution

Open the Domino Web Configuration document and edit the LDAP Server value to include the backslash, for example...

yourLDAPServer.mydomain.com\:389

Restart the Domino LDAP server to initialize this change.

Replicate the Domino Directory to all Domino LDAP servers, including servers that host Lotus Software companion products (for example, Lotus Instant Messaging and Web Conferencing, Lotus Team Workplace, and Lotus Discovery Server).

Start and stop the HTTP task on all Domino and Lotus Team Workplace servers.

If you have enabled Lotus Discovery Server to work with WebSphere Portal in this configuration, completely shut down and restart the Discovery Server.

 

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

If you configure SSO for WebSphere Application Server and 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 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 Domino servers.

 

Troubleshoot awareness in WebSphere Portal

When you sign into portal, the Collaborative Services will look into the CSEnvironment.properties to see if Instant Messaging is enabled. If it is, it will authenticate you with the Instant Messaging server, and writes the stlinks applet into your browser. Once you are authenticated with the Instant Messaging server, see the following on every page source in WebSphere Portal: 

<script type="text/javascript" 
        language="Javascript">

    if (typeof writeSTLinksApplet == "function") 
        writeSTLinksApplet("uid=wpsadmin,cn=users,o=ibm,c=us", "token written here", true);

</script>

The STLinks applet handles all awareness in portal. If a portlet is enabled to show awareness, it will send names to show awareness to the STLinks applet. The STLinks applet will in turn contact the WebSphere Portal server directly to determine user status (active, away, do not disturb, or not online). Pass this information back to the portlet to show the status of the user in the portlet.

If the STLinks applet does not load after configuring single sign-on between Portal and Instant Messaging, go to the support site http://www.ibm.com/software/genservers/portal/support/ and search for issues related to STLinks or awareness in WebSphere Portal.

 

Problem: Changing name formats so that names in the Notes view show up as being online

In a Lotus Instant Messaging and Web Conferencing setup with an LDAP directory, names in an abbreviated format (for example, Jane Smith/NYK/Company) in the Notes view do not show up as being online. This is because the format of the names in the Notes view do not conform to the true distinguished name (canonical name), required by the LDAP server.

 

Solution

In WebSphere Portal V5, all abbreviated names will be converted to canonical names before being sent to Lotus Instant Messaging and Web Conferencing, for example: Jane Smith/NYK/Company becomes CN=Jane Smith/OU=NYK/O=Company.

In addition, edit the CSEnvironment.properties file to specify the dnNameSeparator as a comma or slash. This allows the converted names to have commas in them when Lotus Instant Messaging and Web Conferencing is using an LDAP directory, because LDAP always uses commas, for example: CN=Jane Smith/OU=NYK/O=Company becomes CN=Jane Smith,OU=NYK,O=Company

Note: The converted canonical names must be actual names that the LDAP directory for Lotus Instant Messaging and Web Conferencing can recognize.

 

Set up QuickPlace 3.0 to use IBM Tivoli Directory Server

This procedure corrects a problem caused when QuickPlace would enter 

uid=jqpublic,ou=users,dc=lotus,dc=com

into the ACL instead of 

uid=jqpublic,cn=users,dc=lotus,dc=com

 

Solution

Follow the steps below:

    1. Shut down the QuickPlace server.

    2. Copy nquickplace.dll from the QuickPlace3_0_Hotfixes directory on the QuickPlace CD into the Domino directory (typically C:\Lotus\Domino).

    3. Copy haikucommonforms.ntf from the QuickPlace3_0_Hotfixes directory on the QuickPlace CD to ...lotus\domino\data\QuickPlace\Area Types\

    4. Make sure that the ...\lotus\domino\data\qpconfig.xml file includes the following entry: 

      <user_directory>
        ::::::::
        <ldap>
                ::::::::
                <schema>
                        <secondary_cn_component enabled="true"/>
                </schema>
                :::::::
<ldap>
</user_directory>

    5. Restart the QuickPlace server.

 

Enable diagnostic tracing on the QuickPlace server

Perform the following steps to enable diagnostic tracing on the Quickplace Server Console (when using the Team WorkPlaces Portlet or any portlet using the QPService APIs):

  1. Add the following lines in the notes.ini file of the 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 Quickplace server.
Home | Support | Terms of use | Feedback

 

WebSphere is a trademark of the IBM Corporation in the United States, other countries, or both.

 

IBM is a trademark of the IBM Corporation in the United States, other countries, or both.

 

Tivoli is a trademark of the IBM Corporation in the United States, other countries, or both.