IBM Lotus Sametime 7.5.1

Release Notes

Community Services on port 80.

zA 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.x 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.x 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.x 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.x 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. The Community Services multiplexer on a Sametime 7.5.x server also cannot listen for HTTPS connections to the Sametime Meeting Services or Community Services on ports 443 or 563 and forward these connections to the Community Services and Meeting Services. HTTPS-tunneling to the Sametime Meeting Services is not supported. Sametime Meeting Room clients cannot connect to the Sametime Meeting Services through an HTTPS proxy server.

Sametime

Windows DEP process causes launch error

If Windows server administrators are running the Data Execution Prevention (DEP) process on their Windows server, the server will view the Sametime launch task StLaunch as a potentially malicious thread, and halt the process. The error message received is:

To Help protect your computer, Windows has closed this program:Name: StLaunchPublisher:

Workaround

Turn off the DEP process on Windows servers before launching the StLaunch task.

Sametime

Adjusting the logging level in sametime .properties

For the Sametime client, the properties relevant to logging into sametime.properties are described below. The sametime.properties file is found in the installation root. By default the .level value is set to INFO.

##Logging properties

.level=INFO

logger.filename=sametime.log

logger.includeClassInfo=true

logger.toConsole=true

logger.level=ALL

logger.limit=20000000

logger.count=4

redirectSystemOutput=false

44

Page 50
Image 50
IBM G325-2585-02 Windows DEP process causes launch error, Adjusting the logging level in sametime .properties, Workaround