Setup guide

IBM Lotus Sametime 7.5 Release Notes Installation, migration, upgrade, and configuration
Sametime Administrator needs to be in LDAP for policies to work
Existing Sametime customers that use LDAP have the Sametime Administrator in the local Domino
Directory. Until now, they didn't need to have a Sametime Administrator in LDAP; this is now required for
Policies.
Workaround
Put the DN name of an LDAP user in the full name of the existing local Sametime Administrator, replacing
commas with forward slashes. By logging in to Sametime administration as the LDAP user, that user is
automatically recognized as an administrator, and Policies will work. In Domino LDAP, if the full DN name
of the user is "CN=xxx/OU=yyy/O=zzz", you should add the user in the format "xxx/yyy/zzz" to the ACL of
stconfig.nsf.
Sametime Connect and HTTPS connections on port 443 or 563
This release note discusses issues pertaining to Sametime Connect client connectivity on port 443. These
issues include:
z
Connecting to the Community Services on port 443 when the Domino HTTP server is configured to
listen for SSL connections on port 443
z
Sametime 2.5 Connect client compatibility issue when connecting to a Sametime 7.5 server on port
443 or 563
z
Sametime 7.5 Connect client compatibility issue when connecting to a Sametime 2.5 server on port
443 or 563
z
Community Services multiplexer on Sametime 7.5 server does not forward HTTPS connections on
port 443 to the Domino HTTP server
Connecting to the Community Services on port 443 when the Domino HTTP server is configured to
listen for SSL connections on port 443
Sametime installs on a Domino server. Web browser users connect to the Domino HTTP server when
accessing the Sametime server. If the Domino HTTP server is configured to support SSL for Web browser
connections, the Domino HTTP server is usually configured to listen for these HTTPS connections on port
443 or port 563.
Some Sametime Connect clients may operate in networks that require the clients to connect to the
Internet or intranet through an HTTPS proxy. Many network environments that require users to connect
through an HTTPS proxy only allow outbound connections to occur on port 443. If a Sametime Connect
client operates in such an environment, the following configurations must exist on the Sametime Connect
client and the Sametime server for the connection to be successful:
In the Sametime Connect client Sametime Connectivity tab:
z
The "Community port" setting must specify port 443.
z
The "Use proxy" and "Use HTTPS proxy" settings must be selected. The IP address or DNS name of
the HTTPS proxy server and port number used to connect to the HTTPS proxy server are also
specified.
z
In the Sametime Administration Tool on the Sametime server, the Community Services Network -
Address for HTTPS-tunneled client connections - Port number setting must specify port 443.
17