Home
Welcome to the HCL Sametime® 11.5 administration documentation
Planning
This section describes the system requirements and server configurations needed for HCL Sametime 11.5.
Clustering and high availability
This topic explains the high availability capabilities of Sametime Community services and example deployment scenarios.
Sametime Meetings

Welcome to the HCL Sametime® 11.5 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.5 and Sametime® Meetings 11.5.
- Checklist to deploy Sametime
  This section provides information on reviewing the checklist to deploy the Sametime clients.
- Planning
  This section describes the system requirements and server configurations needed for HCL Sametime 11.5.
  - Sametime vs Sametime Premium
    This section provides a comparision chart between Sametime and Sametime Premium.
  - System requirements
    This section provides minimum system requirements for HCL Sametime 11.5 and Sametime 11.5 Meetings. Higher maintenance levels, such as fix packs and service packs, may be supported as they become available.
  - MongoDB
    This section describes why MongoDB is required for HCL Sametime and the deployment options.
  - LDAP
    HCL® Sametime® utilizes either a native Domino directory or an LDAP directory for user authentication. This topic provides information on LDAP directory planning. The LDAP server should be set up and running before deploying Sametime.
  - Sametime Community and Proxy servers
    This section describes the functionality of each Sametime® product and the servers or services required for each product.
  - Meetings server - FAQ
    Sametime 11.5 Meetings are an all-new meeting experience. Sametime 11.5 meetings have a new deployment model on Docker or with Kubernetes. For more detail, see the topic docker_kubernetes.html.
  - Sametime clients
    HCL Sametime 11 deployments support the following Sametime client types
  - Topology and Connectivity
    This topic explains how Sametime components are connected and the default ports that are used. There are also example topologies to illustrate how Sametime can be deployed in different scenarios. To learn more about which clients are supported by each of the servers, see the topic Sametime Serves.
  - Clustering and high availability
    This topic explains the high availability capabilities of Sametime Community services and example deployment scenarios.
    - Community Services
      This topic explains the high availability capabilities of Sametime Community services and example deployment scenarios.
    - MongoDB
    - Sametime Proxy
    - Sametime Meetings
- Installing
  This section provides information on installing and configuring the servers for HCL Sametime 11.5.
- Configuring
  This section provides information on configuring the servers for HCL Sametime 11.5.
- Securing
  This section provides information on securing HCL Sametime 11.5 environments.
- Administering
  This section provides information on administering HCL Sametime 11.5 environments.
- Troubleshooting
  Troubleshooting and Support
- Migrating and Upgrading
  This section provides information on migrating and upgrading from an earlier Sametime release.
- Notices

Sametime Meetings

High availability is supported for the front end web traffic to the Kubernetes cluster. You can deploy multiple web front-ends on different physical/virtual nodes pointing to the same back end in order to both distribute load and survive a node outage.

Is Kubernetes required for High availability?

High availability is not supported for active meetings. If a server hosting a meeting goes down, users in meetings on that server are briefly interrupted. A re-connection timer built into the client causes clients to quickly re-connect and be distributed to another available node. In some circumstances, a server going down causes a client to disconnect from a meeting. Users can quickly re-connect to the meeting from their recent meetings list and join again on an available server momentarily.

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.