Skip to content

Configuring

This section provides information on configuring the HCL Sametime server. Configuration tasks are dependent on the deployment environment.

  • Adding corporate branding to meeting pages
    You can customize meetings to reflect your company's branding and visual presence.
  • Downloading content to the server
    When downloading content to the Sametime sever, it must be downloaded to the web/download directory.
  • Adding virtual backgrounds to the global library
    By default, you can customize your meetings with virtual backgrounds. As an administrator, you can choose which backgrounds are available to all users.
  • Configuring alternate STUN servers
    Sametime Meetings uses public Google STUN servers by default. To use different STUN servers, you must complete this procedure before installing Sametime Meetings.
  • Setting up business cards
    You can configure the Sametime 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. Business card information also displays at the top of an active chat window.
  • Configuring LDAP
    Sametime supports LDAP directory servers as the user repository.
  • Updating the time-to-live index for persistent chat
    The time-to-live (TTL) setting defines how long the chat history is stored in the database. The default value is 90 days. However, administrators can update the value based on the organization's preferred setting.
  • Managing secrets in Kubernetes
    Sensitive information such as passwords, service account names, certificates, and other confidential data needed by Sametime pods are stored in secrets. In addition to helm charts and configuration map, the Sametime configuration is also derived from secrets.
  • Applying configuration changes in Docker or Podman
    Configuration files contain environment variables that can be changed and applied to the Sametime server.
  • Applying configuration changes in Kubernetes or Openshift
    Configuration files contain environment variables that can be changed and applied to the Sametime server.
  • Chat
    This section contains Chat configuration considerations.
  • Meetings
    This contains configuration steps specific to the HCL Sametime Meetings server.
  • Integrating with other applications
    Integration with an application such as Verse prior to Sametime 12.0 requires the legacy web-client interface. Beginning in Sametime 12.0 the legacy web-client is not enabled by default, but can enabled when needed for integration with other products.
  • Push messaging through a proxy
    Depending on your network settings, your firewalls could prevent Sametime proxy from connecting to push networks like Apple Push Notification Service (APNS) and Firebase Cloud Messaging (FCM) through the Internet. Sametime supports the sending of APNS and FCM messages through a proxy server. If you need to send APNS or FCM message through a proxy server in your environment, you need to configure the settings for the messages you want routed through the proxy.
  • Deployment customization best practices in Kubernetes This topic describes some best practices with respect to how to customize the configuration of the deployment.