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 the Sametime® client to users
The IBM® Sametime® Connect client or Sametime Embedded Client has to be installed on users' computers to use instant messaging and meetings. This section explains how to install these clients.
Installed clients
The IBM® Sametime® Connect and Sametime Embedded clients install directly on the user's computer. You can configure preferences for installed clients before distributing them to users, and then push updates to them automatically.
Configuring the Sametime® client
This section describes how to configure IBM® Sametime® clients.
Connecting the Sametime® Connect client to the Sametime® Community Server
The Sametime® Connect Client uses Server Communities preferences to connect to the Sametime Community Server for presence and chat features.
Defining the host server and port for connecting to a Sametime® Community Server
The Sametime® Connect Client uses the Host and Server community port preferences to determine the host name and port it should use when attempting a connection to the Sametime Community Server.
Configuring client connectivity to the Sametime® Community Mux
After you have configured the stand-alone IBM® Sametime® Community Mux, give users the fully qualified host name of the server and instruct them to set up their Sametime Connect Client preferences to connect to the multiplexer instead of directly to the Sametime Community Server.

Configuring client connectivity to the Sametime Community Mux

After you have configured the stand-alone IBM® Sametime® Community Mux, give users the fully qualified host name of the server and instruct them to set up their Sametime Connect Client preferences to connect to the multiplexer instead of directly to the Sametime Community Server.

About this task

Each user must update the Sametime Connect Client with the DNS name of the Sametime Community Mux server. If you have deployed multiple Sametime Community Mux servers, distribute users evenly among the servers. For example, with two multiplexers, direct half of your users to use multiplexer 1 and the other half to use multiplexer 2.

Procedure

Open Sametime Connect Client.
Choose File > Preferences > Server Communities.
In the Server Community field, type the fully qualified host name of the Sametime Community Mux server, such as messaging.example.com, as instructed by the administrator.