Setup guide

IBM Lotus Sametime 7.5 Release Notes Installation, migration, upgrade, and configuration
Step 5 - Configure the Sametime Connect clients to connect to the new DNS name of the Community
Services
To connect to a Sametime server configured to listen for HTTPS connections on the host name and port
specified above, the Sametime Connect client must have the following settings in the Sametime
Connectivity tab:
z
The "Host" setting must specify community-www.sametime1.com.
Note If a Sametime 2.5 Connect client connects to a Sametime 7.5 server using HTTPS on port 443
or 563, it is only necessary to enter the server name (www.sametime1.com) in the "Host" setting of
the Sametime 2.5 Connect client. For example, enter "www.sametime1.com" instead of
"community-www.sametime1.com" in the "Host" field. For more information, see "Sametime 2.5
Connect client compatibility issue when connecting to a Sametime 7.5 server on port 443 or 563"
below.
z
The "Community port" setting must specify 443.
z
"Use proxy" and "Use HTTPS proxy" must be selected. Enter the host name and port on which the
Sametime Connect client connects to the HTTPS proxy.
Sametime 2.5 Connect client compatibility issue when connecting to a Sametime 7.5 server on port 443
or 563
The Sametime 2.5 Connect client is designed to use HTTPS tunneling on ports 443 or 563 to connect to a
server that uses multiple IP addresses.
When a Sametime 2.5 server is configured to listen for HTTPS-tunneled client connections on port 443 or
563, the server listens for Community Services connections on the server name
"Community-servername." For example, if your Sametime 2.5 server is named
sametimeserver.acme.com, the server listens for HTTPS-tunneled Community Services connections on
ports 443 or 563 on the server name "Community-sametimeserver.acme.com." The Sametime 2.5 server
is hard-coded to prepend the string "Community-" to its server name when listening for Community
Services connections on ports 443 or 563. This design in the Sametime 2.5 server accomodates the
multiple IP address issues discussed in "Connecting to the Community Services on port 443 when the
Domino HTTP server is configured to listen for SSL connections on port 443" above.
The Sametime 2.5 Connect client is also hard-coded to prepend the string "Community-" to its Host
setting when its "Community port" setting specifies port 443 or 563. For example, assume the following
settings exist in the Sametime Connectivity tab of a Sametime 2.5 Connect client:
z
Host - "sametimeserver1.acme.com"
z
Community port - Either port 443 or port 563 is specified.
With this configuration, the Sametime 2.5 Connect client attempts the connection to the server
name "Community-sametimeserver1.acme.com" even though the string
"sametimeserver1.acme.com" is entered in its Host setting.
Because the Sametime 2.5 Connect client automatically prepends the string "Community-" to its host
name, it is not necessary to enter the string "Community-servername" in the Sametime 2.5 Connect client
when this client connects to a Sametime 7.5 server that is configured to listen for HTTPS connections on
multiple IP addresses.
Note also that when a Sametime 7.5 server listens for HTTPS-tunneled connections from Sametime 2.5
Connect clients, the additional DNS name assigned to the Community Services on the Sametime 7.5
server must begin with the "Community-" string, as described in "Connecting to the Community Services
on port 443 when the Domino HTTP server is configured to listen for SSL connections on port 443"
above. If the Sametime 7.5 Community Services DNS name does not begin with the "Community-" string,
the Sametime 2.5 Connect client cannot connect to the Sametime 7.5 server.
20