Home
HCL Sametime® Administration Guide 12
Configuring
This section provides information on configuring the HCL Sametime server.
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.
Customizing business cards in Docker or Podman
You can override the default business cards configuration by editing a UserInfoConfig.xml file and adding it as a volume in the docker-compose.yml.

HCL Sametime® Administration Guide 12
- 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.
- New features in Sametime 12
  The current version of HCL Sametime and HCL Sametime Premium includes new features and enhancements.
- Planning
  This section describes the system requirements and server configurations needed for HCL Sametime and HCL Sametime Premium.
- Installing
  This section provides information on installing and configuring the servers for HCL Sametime and HCL Sametime Premium.
- Configuring
  This section provides information on configuring the HCL Sametime server.
  - Adding corporate branding to meeting pages
    You can customize meetings to reflect your company's branding and visual presence.
  - Adding virtual backgrounds to the global library
    By default, you can customize your meetings with virtual backgrounds and themes. As an administrator, you can choose which backgrounds and themes are available to all users.
  - Configuring the recorder on Docker and Kubernetes instances
    Each recorder instance requires access to a unique ALSA loop-back device on the host. To accomplish this, you must run a series of commands on any node that hosts a recorder pod.
  - 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 business cards using an LDAP directory
      Configuring business cards is done in the UserInfoConfig.xml file in the community pod.
    - Customizing business cards in Kubernetes
      You can override the default business cards configuration by creating an extra-community-configs secret to hold the configuration files.
    - Customizing business cards in Docker or Podman
      You can override the default business cards configuration by editing a UserInfoConfig.xml file and adding it as a volume in the docker-compose.yml.
    - Storing photos in the Domino directory
      If the Sametime server is connected to a Domino LDAP server, you can store business cards photos in the Domino Directory.
    - Using HCL Connections photos for the Sametime business card
      You can use the HCL Connections profiles photos for the Sametime business cards. A benefits for using this method is that updated photos in Connections are automatically updated in Sametime.
  - 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
    Configuration files contain environment variables that can be changed and applied to the Sametime server.
  - Applying configuration changes in Kubernetes
    Configuration files contain environment variables that can be changed and applied to the Sametime server.
  - Chat
    This section contains Chat configuration considerations.
  - Meetings
    This section will discuss Meetings 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.
- Securing
  This section provides information on securing your HCL Sametime environments.
- Administering
  This section provides information on administering on Sametime environments.
- Troubleshooting
  This section provides information on troubleshooting and supporting Sametime environments.
- Uninstalling Sametime
  In the event that Sametime must be uninstalled, follow these steps to uninstall the Community, Proxy, and Meetings servers.
- Migrating and Upgrading
  This section provides information on migrating data from an earlier release to Sametime 12.
- Notices

Customizing business cards in Docker or Podman

You can override the default business cards configuration by editing a UserInfoConfig.xml file and adding it as a volume in the docker-compose.yml.

Procedure

Copy the existing files out of the container.


docker cp <container_name>:/local/notesdata/UserInfoConfig.xml . 
docker cp <container_name>:/local/notesdata/StCommunityConfig.xml

Places files into the current directory.

Make needed changes, then update volumes in the Community service section of docker-compose.yml by adding the following.
```
./UserInfoConfig.xml:/local/notesdata/UserInfoConfig.xml
```
Restart the Sametime server to apply the changes.
```
docker-compose down
docker-compose up -d
```