The Tealeaf Management System (TMS) centralizes configuration management for Tealeaf systems on Windows™-based hosts.

In many customer environments, the Tealeaf solution is deployed across multiple servers, which may be spread across multiple data centers with varying access permissions and security requirements. As a result, applying configuration changes across the Tealeaf solution can be problematic, if you do not use TMS. Through a central configuration interface, TMS enables the following Tealeaf configuration features:

• Security: TMS eliminates the need to have operating system-level access to Tealeaf machines for supported configuration changes.
• Visibility: Through TMS, you can review the services, settings, and pipelines available on each server where Tealeaf software is installed.
• Complexity and Scaling: Through the central interface, you can easily apply configurations across multiple servers, including ones that have been added after base installation of the solution.
• Updates: As needed, you can use the Advanced features of TMS to get and put files within the Tealeaf install directory on individual servers.
• Data Segmentation: Through TMS, you can configure access to session data through user groups. Data Segmentation is managed through Search Server configuration within TMS.

TMS consists of a master server (normally the Portal server) and multiple slave servers, which are all other servers running Tealeaf software, with the exception of Passive Capture and cookie injectors. The TMS master server communicates configuration information to the appropriate slave servers. Each slave then updates the appropriate configuration file or registry.

Changes can be made from the Portal and scheduled for later updating on the relevant computers. Additionally, configuration settings can be defined as common to multiple servers, reducing the overall workload with multiple server systems.

Each of these TMS updates is called a job, which can be created, scheduled, rescheduled, and canceled through the Portal interface. Each job contains one or more tasks. A task implements the configuration changes, which allows for a set of related changes to be made at one time.