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.
Instant messaging features are provided primarily by the IBM® Sametime® Community Server, which supports presence, text chats, and two-way phone calls.
The IBM® Sametime® Proxy Server enables browser-based clients to participate in Sametime instant messaging and online meetings. In addition, the Sametime Proxy Server works with Sametime Community Server or IBM Connections to enable the business card feature in Sametime, and with Sametime Unified Telephony or other TCSPI-enabled products to enable the Sametime click-to-call feature. The Sametime Proxy Server also provides live names awareness and can replace the Links Toolkit used in earlier releases of Sametime. Read the system requirements to ensure that you know the minimum supported software requirements.
Secure the IBM® Sametime® Proxy Server.
The installation worksheets are organized according to feature area, such as instant messaging, audio video, and common components. Use the installation worksheets to record DNS-registered host names, database names, IP addresses, ports to open, credentials, and other information. The checklist contains sample tables already filled out, and blank tables for you to fill out.
Install an IBM® Sametime® fix by downloading packages and installing with the Update option.
Many IBM® Sametime® servers use common components to support either an individual server or a server cluster. Installation Manager and WebSphere® Network Deployment are required prerequisites for most Sametime servers. DB2® and Sametime System Console must be installed once for the deployment. IBM Load Balancer is used in a clustered environment. Follow the instructions for each type of deployment to determine which common components you need to install.
The instant messaging worksheets contain Sametime® Community Server information, Sametime Community Mux information, Sametime Proxy Server information and Sametime Advanced Server information. There is also a set of blank worksheets you can use to record your own infrastructure information.
Review this checklist before installing instant messaging features.
The IBM® Sametime® Community Server supports presence, text chats, and two-way phone calls.
The IBM® Sametime® server uses the Internet and intranet security features of the Domino® server on which it is installed to authenticate web browser users who access Domino databases on the server.
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.
The IBM® Sametime® Proxy Server enables browser-based clients to participate in Sametime instant messaging and online meetings. In addition, the Sametime Proxy Server works with Sametime Community Server or Connections to enable the business card feature in Sametime, and with Sametime Unified Telephony or other TCSPI-enabled products to enable the Sametime click-to-call feature. The Sametime Proxy Server also provides live names awareness, and replaces the Links Toolkit used in earlier releases of Sametime. Read the system requirements to ensure that you know the minimum supported software requirements.
Configure connection settings to enable the IBM® Sametime® Proxy Server to communicate with other servers in the deployment.
Specifying domains that are allowed to connect to the Sametime® Proxy Server gives you the ability to connect servers from other domains, such as SmartCloud Domino® servers, to the Proxy Server domain.
When Transport Layer Security (TLS) strict mode is enabled on an IBM® Sametime® Community Server, TLS must be enabled on the IBM Sametime Proxy Server as well.
If you plan to configure telephony services in your deployment using IBM® Sametime® Unified Telephony, import the Telephony Application Server SSL certificate into the Sametime Proxy Server's truststore.
Configure Single Sign-On for IBM® Verse and Sametime® so that Verse users are automatically logged in to the on-premise Sametime deployment.
The IBM® Sametime® Advanced Server adds features including persistent chat rooms, broadcasts, multiple-file transfers, instant share, and organization tree views to a Sametime deployment.
Meeting features are provided primarily by the IBM® Sametime® Meeting Server, which creates online "meeting rooms" where users can present information and share applications. If you deploy the Sametime Media Manager, conferences can include audio and video features as well.
Audio and video features are provided primarily by the IBM® Sametime® Media Manager, which supports point-to-point and multipoint calls. The Sametime Media Manager uses standard audio and video codecs so that it works with products from other audio and video vendors.
SIP trunking allows IBM® Sametime® users to make SIP-based phone calls from their installed Sametime clients.
Deploy the First Party Call Control (FPCC) feature by configuring settings in the IBM® Sametime® Connect and Sametime Embedded client installation packages and then distributing the updated packages to users.
Clients in a local IBM® Sametime® community can communicate with users in other communities through the Sametime Gateway.
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.
The Apple iOS client is distributed through the Apple App Store. The Android client is no longer available for download from the IBM® Sametime® Proxy Server. Customers with users who are unable to access the Google Play Store should contact IBM Support to request that a build be provided to them directly.
You can provide failover and load balancing in your deployment by creating a cluster of multiple IBM® Sametime® servers of the same type. All Sametime servers can be clustered except for the Sametime System Console, and the Video MCU and TURN Server components of the Sametime Media Manager.
Ensure the security of your IBM® Sametime® deployment by deploying servers in the extranet. Deploying Sametime servers in the extranet allows external clients to access Sametime features without directly connecting to servers deployed in your intranet.
Expand the range of features in your IBM® Sametime® deployment by integrating with other products.