Chapter 1. Overview of Sametime 13
This following sections discuss the new features that were added in Sametime
3.1 that affect the various Sametime APIs. For the full list of new features (both
end-user feautres, as well as features impacting the APIs, please see the
“What’s new” section of the Sametime 3.1 Release Notes, found at:
1.6.1 Reverse proxy support
A Sametime 3.1 server can be deployed behind a reverse proxy server. End
users can connect to the Sametime server through the reverse proxy server. The
STLinks and Java Toolkit support reverse proxy environment in Sametime 3.1.
Reverse proxy support in STLInks Toolkit
There are two new variables declared in the stlinks.js run-time file:
ll_proxyName: The reverse proxy name
ll_AffinityId: The Sametime server affinity ID
These variables are commented out with a default value and should be modified
by the administrator when using a reverse proxy environment. The administrator
should change the default values to the real ones.
After setting those variables, STLinks Toolkit is ready to support a reverse proxy
environment. There are no changes in the API resulting from this new reverse
proxy support and no additional required code by the developer.
Reverse proxy support in Java Toolkit
There is no default support for a reverse proxy environment in the Java Toolkit.
However, a new API has been added to the Java Toolkit in order to allow
applications to take advantage of this support. The new API concerns the
connection classes like HTTPConnection, PollingConnection, and so on. In the
com.lotus.sametime.core.util.connection package, the Sametime development
team has added constructors that accept a URL parameter versus host/port in
the older constructors.
For example, we added a new HttpConnection constructor:
public HttpConnection(URL hostUrl, long timeout
Note: This new API (constructors) can be used for any other purpose than
Reverse Proxy support. It is important to understand that they are not
implemented directly for the purpose of Reverse Proxy behavior.