Setup guide

IBM Lotus Sametime 7.5 Release Notes Installation, migration, upgrade, and configuration
2.
You must open the stlinks.
j
s file on the Sametime server and modif
y
the followin
g
two lines to point t
o
your WebSEAL reverse proxy server and WebSEAL junction (the WebSEAL junction is "st" in the
example below):
varII_RProxyName="https://ampc0.support.tivlab.austin.ibm.com"
varII_AffinityID="st"
var is TAM-env=true;
//racingConnTimeout-Timeout between racing connections in milliseconds. The value is sent to the
STLinks applet var racingConn Timeout=5000;
To configure the server to work with STLinks in a regular (not TAM) environment, leave the following lines
in stlinks.
j
s without an
y
chan
g
e:
var is TAM-env=false;
//racingConnTimeout-Timeout between racing connections in milliseconds. The value is sent to the
STLinks applet.
1.
Enable reverse proxy support and specify the WebSEAL junction in the Sametime Administration Tool
on the Sametime 7.5 server.
- Open the Sametime Administration Tool on the Sametime 7.5 server.
- Select Configuration-Connectivity.
- In the "Reverse Proxy Support" section, select the "Enable Reverse Proxy Discovery on the client"
setting to enable the reverse proxy support.
- In the "Reverse Proxy Support" section, enter the WebSEAL junction name in the "Server Alias"
field. In this example, "st" is the WebSEAL junction name.
2.
Create the Tivoli Access Manager WebSEAL junction as shown below:
pdadmin> server task webseald-[
servername ] create -t tcp -h [ sametime hostname ] -p 80 -i -
j
-A -F [
path to LTPA key ] -Z [ LTPA key password ]/
j
unction
You cannot use the -w parameter for this setup. Some requests generated by Sametime are not
allowed through the junction if the -w exists. You must also ensure that the LTPA key used in the
j
unction is the same LTPA ke
y
that the Sametime server uses in its Web SSO Confi
g
uration
document
After performing these configurations, you should be able to login to https://webseal/stjunction and be
prompted by WebSEAL for authentication. Once authenticated, SSO between WebSEAL and Sametime
should work and all requests for Sametime will route through WebSEAL.
16