Setup guide

IBM Lotus Sametime 7.5 Release Notes Installation, migration, upgrade, and configuration

Sametime 7.5 Connect client compatibility issue when connecting to a Sametime 2.5 server on port 443

or 563

If a Sametime 7.5 Connect client connects via HTTPS-tunneling to a Sametime 2.5 server on port 443 or

563, the Sametime 7.5 Connect client does not prepend the "Community-" string to its host name when

making the connection to the Sametime 2.5 server.

The Sametime 2.5 server is hard-coded to prepend the string "Community-" to its server name when

listening for HTTPS connections on port 443 or 563. To ensure the Sametime 7.5 Connect client can

connect to the Sametime 2.5 Community Services on port 443 or 563, the string "Community-" must be

manually added to the Host name in the Sametime Connectivity tab in the Sametime 7.5 Connect client.

Manually adding the "Community-" string to the Host name in the Sametime 7.5 Connect client ensures

that the client attempts the connections on the name on which the Sametime 2.5 server listens for the

connections.

For example, to ensure a Sametime 7.5 Connect client can connect on port 443 or 563 to the Sametime

2.5 server named "sametimeserver1.acme.com," the following settings must exist in the Sametime

Connectivity tab of the Sametime 7.5 Connect client:

Host - "Community-sametimeserver1.acme.com."

Community port - Either port 443 or port 563 is specified. (Specify the port on which the

Sametime 2.5 server listens for HTTPS-tunneled connections.)

Community Services multiplexer on Sametime 7.5 server does not forward HTTPS connections on port

443 to the Domino HTTP server

A Sametime 7.5 server can simulaneously listen for HTTP connections to multiple services on port 80

when the Sametime server machine includes a single IP address. For example:

A Web browser can connect to the Domino HTTP server on a Sametime server on port 80.

A Sametime Connect client can make an HTTP-tunneled connection to the Sametime

Community Services on port 80.

A Sametime Meeting Room client can make HTTP-tunneled connections to both the

Sametime Community Services and Meeting Services on port 80.

All of these connections can occur to the same DNS name using port 80. On a Sametime 7.5 server, it is

not necessary to assign separate IP addresses to the HTTP Services, Community Services, and Meeting

Services to enable connections to all services to occur using a single DNS name on port 80. The design

of the Community Services multiplexer on a Sametime 7.5 server makes this capability possible. The

Community Services multiplexer can listen for HTTP connections from Web browsers, Sametime Connect

clients, and Sametime Meeting Room clients on port 80. The Community Services multiplexer examines

these connections and then forwards the connections to the appropriate service. For example, the

Community Services multiplexer forwards the Web browser connections to the Domino HTTP Server, the

Community Services connections to the Community Services, and the Meeting Services connections to

the Meeting Services.

Note that the Community Services multiplexer on a Sametime 7.5 server cannot listen for connections on

port 443 or 563 and then forward these connections to the Domino HTTP server. The Community

Services multiplexer can forward HTTP connections on port 80 to the Domino HTTP server, but not

connections on port 443 or 563. For this reason, a Sametime 7.5 server must be assigned multiple IP

addresses when both the Domino HTTP server and the Sametime Community Services on the Sametime

server must listen for connections on port 443 or 563.