Home
Welcome to the HCL Sametime® 11.6 administration documentation
Configuring
This section provides information on configuring the servers for HCL Sametime 11.6.
Clustering
This section will discuss clustering steps specific to the HCL Sametime Community server.
Clustering Community Servers
Community server clusters allow you to have high capacity and fail over/redundancy for Community services. For more information on clustering and capacity planning, see planning section in Community Services. Sametime leverages the Domino clustering feature to keep the VPUserInfo.nsf database replicated and up to date on participating servers. The user’s privacy configuration and contacts are stored in this database.
Setting up the load-balancing network device

Welcome to the HCL Sametime® 11.6 administration documentation
- Accessibility features for Sametime
  Accessibility features help users who have a disability, such as restricted mobility or limited vision, to use information technology products successfully. HCL® strives to provide products with usable access for everyone.
- What's new in HCL Sametime
  This section describes what's new in HCL Sametime® 11.6 and Sametime® Meetings 11.6.
- Checklist to deploy Sametime
  This section provides information on reviewing the checklist to deploy the Sametime clients.
- Encryption usage in Sametime
  HCL® Sametime® uses several types of encryption to protect data.
- Planning
  This section describes the system requirements and server configurations needed for HCL Sametime 11.6.
- Installing
  This section provides information on installing and configuring the servers for HCL Sametime 11.6.
- Configuring
  This section provides information on configuring the servers for HCL Sametime 11.6.
  - Setting up business cards
    You can configure the Sametime Community Server so that business card information about an individual displays when a user hovers over a name in a chat window or a contact list.
  - Community Services
    This section will discuss configuration steps specific to the HCL Sametime Community server.
  - Clustering
    This section will discuss clustering steps specific to the HCL Sametime Community server.
    - Clustering Community Servers
      Community server clusters allow you to have high capacity and fail over/redundancy for Community services. For more information on clustering and capacity planning, see planning section in Community Services. Sametime leverages the Domino clustering feature to keep the VPUserInfo.nsf database replicated and up to date on participating servers. The user’s privacy configuration and contacts are stored in this database.
      - Assigning users to a Home Sametime Server 
        This topic discusses the concept of the Home Sametime Server setting, its purpose, use and configuration. 
      - Create the Domino cluster
      - Creating a cluster document in the Configuration Database
        The Sametime cluster document enables the servers in a cluster to operate as part of the cluster, and enables the servers outside of the cluster (but within the community) to communicate with the cluster.
      - Copying a cluster document to all Sametime Community Servers
        Each Sametime Community Server cluster has a Cluster Information document, which was created on one Sametime server in the cluster. Every server in the Sametime community must have a copy of this Cluster Information document, even if the server is not part of a cluster. The document allows users to share presence and instant messaging capabilities with all other users in the community, regardless of their home server assignment.
      - Setting up the load-balancing network device
        Rotating DNS Limitations with cached DNS resolve requests
        This section describes some of the limitations related to setting up a rotating DNS system to load balance connections to the Sametime Community Services cluster.
      - Enabling scheduled replication
        When clustering Domino servers, the cluster replicator task will keep the databases synchronized, but it is a best practice to also schedule a periodic replication.
      - Ensuring all Community Servers have the same settings
  - Meetings
    This section will discuss Meetings configuration steps specific to the HCL Sametime Meetings server.
- Securing
  This section provides information on securing HCL Sametime 11.6 environments.
- Administering
  This section provides information on administering HCL Sametime 11.6 environments.
- Uninstalling Sametime
  In the event that Sametime must be uninstalled, follow these steps to uninstall the Community, Proxy, and Meetings servers.
- Troubleshooting
  Troubleshooting and Support
- Migrating and Upgrading
  This section provides information on migrating and upgrading from an earlier Sametime release.
- Notices

Setting up the load-balancing network device

About this task

Environments without Standalone Multiplexers

If you have not deployed standalone multiplexers, you have two choices for setting up the load balancing mechanism.

Recommended: Use a network appliance such as an IP sprayer or load balancer to direct the connections to each Community Server.
Set up a rotating DNS system to accomplish load balancing. Use rotating DNS to associate the IP addresses of the Sametime Community Server computers to a single DNS name.
For example, associate the IP address of Sametime Community server 1 (10.22.33.66) and Sametime Community server 2 (10.22.33.77) to the DNS name cscluster.example.com.

Note: There are some limitations with using a rotating DNS. For more information, see Rotating DNS Limitations with cached DNS resolve requests.

Environments with Standalone Multiplexers

If you have deployed standalone multiplexers you have two choices for setting up the load balancing mechanism.

Recommended: Use a network appliance such as an IP sprayer or load balancer to direct the connections to each Mux.
Set up a rotating DNS system to accomplish load balancing. Use rotating DNS to associate the IP addresses of the Mux computers to a single DNS name.
For example, associate the IP address of Mux1 (10.22.33.44) and Mux2 (10.22.33.55) to the DNS name cscluster.example.com.
Note: There are some limitations with using a rotating DNS. For more information, see Rotating DNS Limitations with cached DNS resolve requests.

Rate this topic

5 stars 4 stars 3 stars 2 stars 1 star

Comment on this topic.

By clicking this box, you acknowledge that you are NOT a U.S. Federal Government employee or agency, nor are you submitting information with respect to or on behalf of one. HCL provides software and services to U.S. Federal Government customers through its partners immixGroup, Inc. Contact this team at https://hcltechsw.com/resources/us-government-contact. Do not include any personal data in this Comment box. Note: To report a problem or question about the product software, do not use this form. Instead, go to the HCL Software Support site.