Home
Deploying
IBM® Sametime® consists of a variety of servers and clients, and can be deployed to suit many different environments. The deployment instructions are organized by feature set, beginning with the minimum components that are necessary to support instant messaging, and then expanding the deployment to include features such as audio and video support, and conferencing.
Deploying instant messaging
Instant messaging features are provided primarily by the IBM® Sametime® Community Server, which supports presence, text chats, and two-way phone calls.
Deploying Sametime® Community Server to support external users
If your IBM® Sametime® deployment will support users hosted outside of your organization's intranet, you have several options for deploying and configuring the Sametime Community Server to support those users.
Using reverse proxy or portal servers with the Sametime® Community Server
To support clients hosted outside of your intranet, you can deploy the IBM® Sametime® Community Server behind a reverse proxy server or a portal server.
Requirements and limitations of Sametime® reverse proxy support
Using a reverse proxy server with IBM® Sametime® is subject to some limitations as described in this topic.
Viewing the Signer certificates
The Java™ Plug-in has access to several different Signer certificates that can be used for reverse proxy support.

Viewing the Signer certificates

The Java™ Plug-in has access to several different Signer certificates that can be used for reverse proxy support.

About this task

To view the Signer certificates that are available to the Java Plug-in 1.4.2, use the Java Plug-in Control Panel:

Procedure

From the Windows® desktop, open the Control Panel by clicking Start > Settings > Control Panel.
Double-click on the Java Plug-in 1.4.2 icon to open the Java Plug-in Control Panel.
Click Certificates.
Click Signer CA.

Results

The server certificate sent by the reverse proxy server to the client web browser must be signed by one of the CAs that appears in the signer CA list for the SSL connection handshake to succeed.