Home
Planning
Planning is critical to a successful deployment. Many deployment problems, growth problems, and capacity problems occur because not enough time is taken to carefully plan a deployment. Plan your IBM® Sametime® installation by determining features needed, reviewing system requirements, determining capacity requirements, and the servers and computers needed for your deployment.
Planning Sametime® features
This section describes best practices, requirements, tips, and things you should know when planning for instant messaging and presence services, meeting services, web client services, audio and video services, broadcast communities and persistent chat rooms, including IBM® Sametime® services in the extranet for remote users and customers. Included in this section are several sample topologies, everything from simple internal meetings to voice and video for intranet and extranet users.
Planning for Community services
The Sametime® Community server runs on an IBM® Domino® server. You must install the Domino server before you install the Sametime Community Server. The Domino Server that hosts the Community Server must be dedicated to supporting the real-time, interactive communication services of Sametime. If you use a Domino LDAP directory, install it on a separate server.
Deploying a stand-alone Sametime® Community Mux
You can optionally install an IBM® Sametime® Community Mux on a separate computer to remove the connection-handling load from the Sametime Community Server. Configuring a stand-alone Community Mux enables the Community Server to handle a larger number of users and improves its stability.

Deploying a stand-alone Sametime Community Mux

You can optionally install an IBM® Sametime® Community Mux on a separate computer to remove the connection-handling load from the Sametime Community Server. Configuring a stand-alone Community Mux enables the Community Server to handle a larger number of users and improves its stability.

About this task

Every Community Server contains a Community Mux that maintains connections from Sametime clients. The Community Mux is installed automatically and is configured for immediate use. You can optionally deploy a stand-alone Community Mux by installing it on a separate computer, so that clients connect to the stand-alone Community Mux instead of to the Community Server. This configuration frees the Community Server from the burden of managing the live client connections; the stand-alone Community Mux is dedicated to this task.

You can deploy a Community Mux to operate with one or more clustered or unclustered Community Servers. You can also deploy multiple stand-alone Community Muxes and use a load balancer to distribute client connections among them.

Choose to deploy a Community Mux for a single Community Server or a cluster of Community Servers.