Jump to main content
HCL Logo Product Documentation
  • Customer Support
Sametime 10.0 Installation and Administration
  • IBM® Sametime® 10.0 Limited Use documentation
  • What's new in this release?
  • Getting started with Sametime 10
  • Accessibility features for Sametime®
  • Overview
  • Planning
  • Deploying
  • Administering
  • Performance tuning
  • Security
  • Troubleshooting
  • Uninstalling
  • Glossary
  1. Home
  2. 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.

  3. 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.

  4. Installing Sametime® Community Server

    The IBM® Sametime® Community Server supports presence, text chats, and two-way phone calls.

  5. Configuring LDAP and Domino® connections

    Configure the IBM® Sametime® Community Server to work with LDAP and Domino® directories.

  • 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.

    • Installation worksheets

      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.

    • Deploying fixes to Sametime® servers running on WebSphere® Application Server

      Install an IBM® Sametime® fix by downloading packages and installing with the Update option.

    • Deploying common components

      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.

    • 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.

      • Sametime® instant messaging worksheets

        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.

      • Reviewing the checklist for deploying instant messaging

        Review this checklist before installing instant messaging features.

      • Installing Sametime® Community Server

        The IBM® Sametime® Community Server supports presence, text chats, and two-way phone calls.

        • Disabling unused TCP global settings in Windows™ Server 2008 and later

          Avoid performance problems by disabling TCP global settings that are available in Microsoft™ Windows™ Server 2008 and later (including Windows Server 2012), but are not used by IBM® Sametime® 9.

        • Installing Domino®

          Install an IBM® Domino® server and prepare the environment before installing an IBM Sametime® Community Server.

        • Installing a Sametime® Community Server

          Use a guided activity on the IBM® Sametime® System Console to create a deployment plan, which you can use to install the Sametime Community Server.

        • Enabling the administrator to manage the Sametime® Community Server

          When you use a deployment plan to install the Sametime® Community Server, you must add the Sametime Administrator listed in the LDAP directory to the Sametime Configuration database to enable the administrator to manage the community server. Skip this task if you installed the server without using a deployment plan or if you upgraded from an earlier release.

        • Configuring partitioned Domino® servers to avoid IP conflicts

          If you install multiple IBM® Sametime® Community Servers on a single computer, you must assign a distinct IP address to each server. On AIX® or Linux™, you can install multiple Sametime Community Servers on a single computer, within the same logical partition. Each Sametime Community Server instance runs on a separate partitioned IBM Domino® server. If you are also running any other Domino servers or HTTP servers within the same logical partition, you must also be certain that those servers are assigned separate IP addresses to avoid port conflicts. After installing a community server in a Domino partitioned-server environment, configure the partitioned servers to avoid IP conflicts.

        • Verifying a Sametime® Community Server installation

          After installing the IBM Sametime® Community Server, start the server and verify that the installation was successful.

        • Registering the Sametime® Community Server with the Sametime® System Console

          Register a new IBM® Sametime® Community Server with the Sametime System Console so that you can administer the Community Server from the System Console's administration pages. Even if you will cluster Sametime Community Servers, you must register the individual servers first.

        • Enabling IPv6 support on a Sametime® Community Server

          If your Sametime® Community Server deployment requires IPv6 support, you can enable it by configuring settings for both Domino® and Sametime.

        • Installing and setting up a stand-alone Sametime® Community Mux

          Installing and setting up a stand-alone IBM® Sametime® Community Mux server involves the following procedures.

        • Configuring Sametime® Community Server connectivity

          Define the host names and ports for Community Services on the IBM® Sametime® Community Server.

        • Setting the same community ID for all servers in the environment

          To ensure that clients recognize all servers in the environment as belonging to a single community, add a ST_COMMUNITY_ID value to the sametime.ini file.

        • Configuring LDAP and Domino® connections

          Configure the IBM® Sametime® Community Server to work with LDAP and Domino® directories.

          • Excluding certain domains from user and group directory lookups

            When you use Inbox awareness, you can prevent redundant requests to the LDAP or Domino® directory by defining which domains are allowed to accept resolve requests. Previous releases allowed this filtering through the use of custom code and was available only for LDAP directories.

          • Specifying a user's login ID

            Specify an LDAP attribute that is appropriate for logging in to IBM® Sametime®. If you do not perform these steps, the default LDAP attribute, DN, is used.

          • Migrating older user IDs to a unique directory attribute

            If you are using an older release, you can migrate user IDs to a unique ID, so you do not need to run the name change utility when a person's name changes in the directory. Having a constant user ID attribute eliminates the need to change a user ID when a name changes.

          • Creating custom Java™ classes for searching the LDAP

            Create custom Java™ classes that provide greater control over how the Sametime® Community server conducts name searches of an LDAP directory and how results are formatted.

        • Configuring multi-tenancy on the Sametime® Community Server

          Multi-tenancy allows multiple organizations to be part of an IBM® Sametime® community. With multi-tenancy, Sametime users can chat, add users and groups to contact lists, and have awareness of users in their organization or in other organizations that are configured to be visible to them.

        • Preparing the Sametime® Community Server for users

          Before deploying clients, set up the login and licensing requirements that suit your environment.

      • Sametime® Community Server on IBM® i

        The IBM® Sametime® Community Server supports presence, text chats, and two-way phone calls.

      • Securing the Sametime® Community Server

        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.

      • 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.

      • Installing Sametime® Proxy Server

        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.

    • Deploying First Party Call Control

      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.

    • Deploying an instant messaging gateway for external communities

      Clients in a local IBM® Sametime® community can communicate with users in other communities through the Sametime Gateway.

    • 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.

    • Deploying for mobile users

      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.

    • Clustering servers for high availability and failover

      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.

    • Deploying Sametime® servers in the extranet

      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.

    • Integrating Sametime® with other products

      Expand the range of features in your IBM® Sametime® deployment by integrating with other products.

Configuring LDAP and Domino connections

Configure the IBM® Sametime® Community Server to work with LDAP and Domino® directories.

What to do next

Preparing the Sametime Community Server for users
  • Excluding certain domains from user and group directory lookups
    When you use Inbox awareness, you can prevent redundant requests to the LDAP or Domino directory by defining which domains are allowed to accept resolve requests. Previous releases allowed this filtering through the use of custom code and was available only for LDAP directories.
  • Specifying a user's login ID
    Specify an LDAP attribute that is appropriate for logging in to IBM Sametime. If you do not perform these steps, the default LDAP attribute, DN, is used.
  • Migrating older user IDs to a unique directory attribute
    If you are using an older release, you can migrate user IDs to a unique ID, so you do not need to run the name change utility when a person's name changes in the directory. Having a constant user ID attribute eliminates the need to change a user ID when a name changes.
  • Creating custom Java classes for searching the LDAP
    Create custom Java™ classes that provide greater control over how the Sametime Community server conducts name searches of an LDAP directory and how results are formatted.
  • Share: Email
  • Twitter
  • Disclaimer
  • Privacy
  • Terms of use
  • Cookie Preferences