Check the page source for awareness configuration

 

+

Search Tips   |   Advanced Search

 

In a browser, determine whether awareness provided by the Lotus Sametime server and the STLinks applet is properly configured by examining the page source.

When a user logs into the portal, the Lotus Collaborative Services checks the CSEnvironment.properties file on the portal server to see whether IBM Lotus Sametime is configured. If it is, Collaborative Services authenticates the user with the Lotus Sametime server, and builds the STLinks applet into the user's browser.

The STLinks applet handles all awareness in the portal. If a portlet is enabled to show awareness, it sends names to show awareness to STLinks. Then STLinks contacts the Lotus Sametime server directly to determine the user's status (active, away, do not disturb, or not online), and passes this information back to the portlet to display the user's status in the portlet.

If the STLinks applet has loaded properly, information appears in the source of all pages in the site.

Perform the following steps:

  1. Log into the portal (with single sign-on enabled, logging into the portal also authenticates you as a user of the Lotus Sametime server).

  2. Select...

    View | Source

    If you see the following information in the source, the STLinks applet is loaded:

    <script type="text/javascript" language="Javascript">
        if (typeof writeSTLinksApplet == "function")
        writeSTLinksApplet("uid=wpsadmin,cn=users,o=ibm,c=us", "<token written here>", true);
    </script>

If the STLinks applet has not loaded, see the following technote for several tests we can perform to troubleshoot the issue:

Technote 1163790: Troubleshooting Sametime Awareness in WebSphere Portal
We can also use Search at IBM Support to find technotes by number.

 

Parent Topic

Configure single sign-on between WebSphere Portal and Lotus Domino

 

Previous topic

Testmeeting services for Inline QuickPlace

 

Next topic:

Reconciling single sign-on across Lotus Domino and another LDAP directory