<
Previous |
Contents
Before starting this section, ensure you have completed the previous two
steps.
1. Configure SSO between
Lotus Quickr and Sametime.
2. Configure Sametime to
be case insensitive.
In this topic we discuss how to integrate awareness and chat capabilities
for your Services for WebSphere Portal users.
How awareness work in Lotus Quickr services for Portal
Awareness is always a two-step process:
1. Log user into Sametime
from Services for WebSphere Portal client.
2. Resolve user list to
show awareness status.
Log user into Sametime from WebSphere Portal
In services for WebSphere Portal, there are two ways users
can be logged into Sametime.
One way is to pass the Sametime distinguished name of the
user with an STToken generated by Sametime. This option in not discussed
in this paper, and typically is only used when SiteMinder is configured
in the environment to protect the Sametime servers.
A second way is to pass the Sametime distinguished name
of the user with an LTPAToken generated by WebSphere Portal.
With this option, there are two possibilities in how WebSphere
Portal determines the Sametime distinguished name of the user. When
Sametime and WebSphere Portal authenticate using the same LDAP directory,
services for WebSphere Portal take the distinguished name as known by the
Services for WebSphere Portal and pass this DN to Sametime.
However, if Sametime and WebSphere Portal authenticate
using different directories (for example, Sametime authenticates using
native Domino, while Portal authenticates using Tivoli Directory Server)
WebSphere Portal opens a server-to-server connection to Sametime passing
the distinguished name it knows (uid=cprice,cn=users,dc=greenhouse,dc=com)
to Sametime. Sametime then resolves this name in its directory to find
the Sametime distinguished name (CN=Charlie Price/O=ghquickr) and passes
this back value to WebSphere Portal. WebSphere Portal uses this name to
pass to STLinks to log the user into Sametime for awareness.
Portal attempts to log the user into Sametime by looking
for the following in a view source of any portal page: writeSTLinksApplet("uid=cprice,cn=users,dc=itso,dc=com",
,true);
It is important that the view source always shows the distinguished
name of the user as returned from the directory Sametime authenticates
with.
This process is built through the default theme in Services
for WebSphere Portal, so it does not matter if you have an awareness-enabled
portlet on the page or not, you will be logged into Sametime after you
log into Lotus Quickr, and users can start chatting with you.
The next section describes how you are able to chat with
users.
Resolve user list to show awareness status
After you have logged into Sametime, for any Lotus Quickr
component where usernames are configured to display awareness, Lotus Quickr
sends the e-mail address of each user to stlinks, which forward the names
to the Sametime server requesting the current status. Sametime then resolves
the e-mail addresses with its directory to the distinguished name. Sametime
then looks in its internal databases to determine the current status (Active,
Away, Do not disturb, In a meeting or Not online) of each user and returns
this status to stlinks. Finally, stlinks updates the icon to display
the current status of each user.
Enabling awareness and chat in Services for WebSphere
Portal
Follow these steps to set up awareness and chat in services
for WebSphere Portal, by updating the collaboration services properties
file (csenvironment.properties) with connection information about your
Sametime server.
1. Open CSEnvironment.properties
(located in C:\IBM\Quickr\PortalServer\shared\app\config directory. in
a text editor.
2. Use the following settings
for your environment:
Note: If Sametime authenticates using native Domino, leave the version
3.0, otherwise use the version of the Sametime server you are working with.
Note: The serverappPort setting is the port used by Services for WebSphere
Portal to connect to the Sametime server to get the Sametime distinguished
name of the user. If Lotus Quickr and Sametime authenticate using
the same user directory, this field should be commented out.
Note: The reconnect setting is how often the Services for WebSphere
Portal close and reopen the server connection to the Sametime server that
is used to get the Sametime distinguished name of the user. If Lotus
Quickr and Sametime authenticate using the same user directory, this field
should be commented out. Even if they authenticate using different
directories, it is usually best to keep this setting commented out.
Note: The timeout setting is how long the Services for WebSphere Portal
waits for the Sametime server to return the Sametime distinguished name
of the user. If Lotus Quickr and Sametime authenticate using the
same user directory, this field should be commented out. Even if they authenticate
against different directories, it is usually best to keep this setting
commented out.
Note: The nameFormatForResolve setting is the attribute that the Lotus
Quickr server sends to Sametime server for Sametime to resolve and return
the Sametime distinguished name of the user. If Lotus Quickr and
Sametime authenticate using the same user directory, this field should
be commented out. If they authenticate using different user directories,
the comment character must be removed, and we recommend setting it to dn.
Note: The comment character for dnNameSeparator should only be
removed if Sametime authenticates using native Domino. If Sametime
authenticates using native Domino, remove the comment character for the
dnNameSeparator setting and set it to: / (CS_SERVER_SAMETIME_1.dnNameSeparator=/).
If Sametime authenticates using any LDAP directory, including
Domino LDAP, leave this setting commented out.
Note: The comment character for dnAuthorSeparator should always
beremoved and set to / no matter what directory Sametime uses to
authenticate.
Note: watchnameformat determines how the name in the user's profile
is sent to stlinks to determine the users current awareness status. For
performance reasons, we recommend this be set to dn for most cases.
Note: When the user name in the user's profile is passed to stlinks,
resolveNames lets you tell stlinks if the name needs to be resolve or not
by the Sametime server. If Lotus Quickr and Sametime authenticate
using the same LDAP directory AND you set CS_SERVER_SAMETIME_1.watchnameformat=dn
AND Sametime has been configured to be case insensitive, then it is best
to tell Sametime that it is not necessary to resolve the name being passed.
To do this, remove the comment resolveNames and set it to false (CS_SERVER_SAMETIME_1.resolveNames=false).
3. Save and close the file.
4. Restart the Lotus Quickr
server for the change to take effect.
Note: If you make any changes to the csenvironment.properties
file, restart the server for those changes to take effect
Ensure Sametime can resolve the e-mail address
Portlets send the e-mail address of the user to Sametime
to generate awareness. Therefore, it is important to make sure that
the Sametime server is able resolve the user's e-mail address from the
directory. If Sametime authenticates using native Domino, this step
is not necessary.
1. In a Notes client, open
stconfig.nsf on the Sametime Server.
2. In the All - By Form
and Date view, open the LDAP document.
3. Ensure the mail attribute
from your directory is included in the following field: Search
filter for resolving person names.
4. Restart the Sametime
server if any changes were made to this document.
Configure awareness for Mozilla Firefox browsers
Awareness works by downloading a stlinks applet to your
browser. A security feature of Firefox requires applets to be signed
and downloaded from the server that you are currently accessing. In
this case, it is the Services for WebSphere Portal server and not another
server host name (such as the Sametime server). Therefore, for awareness
to work in Firefox browsers, copy the stlinks files to the Services for
WebSphere Portal server and use the signed applet on the server.
1. On the Servies for WebSphere
Portal server, create a folder named sametime under the wps.war directory
(C:\IBM\Quickr\profiles\installedApps\cell_name\wps.ear\wps.war\sametime).
2. Copy the entire stlinks
folder from the Sametime server (C:\Lotus\Domino\Data\domino\html\sametime)
to the Services for WebSphere Portal server (C:\IBM\Quickr\profiles\installedApps\cell_name\wps.ear\wps.war\sametime).
3. Copy the stlinks.jar
file from the signed folder (sametime\stlinks\signed) to the stlinks folder,
overwriting the existing stlinks.jar file.
4. Restart the Lotus Quickr
and Server1 application servers for the change to take effect.
Test awareness in services for WebSphere Portal
Follow these steps to test awareness in services for WebSphere
Portal
1. Open a browser to the
Services for WebSphere Portal server and sign in.
2. Click My Places.
If you have created a place, you should see awareness for your name.
<
Previous |
Contents