The Tealeaf Management System (TMS) centralizes configuration management for Experience Analytics systems on Windows™-based hosts.
In many customer environments, the Experience Analytics 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 Experience Analytics solution can be problematic, if you do not use TMS. Through a central configuration interface, TMS enables the following Experience Analytics configuration features:
- Security: TMS eliminates the need to have operating system-level access to Experience Analytics machines for supported configuration changes.
- Visibility: Through TMS, you can review the services, settings, and pipelines available on each server where Experience Analytics 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 Experience Analytics 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 Experience Analytics 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.
FQDN (Fully-Qualified Domain Name)
Consider the following points about TMS servers:
- TMS peers (all Windows-based Experience Analytics servers other than the Portal server)
automatically detect if an updated version of TMS is installed on the TMS Master (normally the
- The peer servers then request for the new TMS executable from the TMS master.
- The current TMS version is renamed.
- The new TMS version is installed.
- The TMS server restarts so that the new TMS version can take effect.
- TMS peers also automatically detect if the TMS Master has re-initialized the TMS datastore. The local TMS service is restarted and then re-registers itself with the TMS Master.
The components of TMS enable the following basic functionality:
|WorldView tab||Select the server and the type of TMS-controlled objects on the server to view. Make changes to servers, configurations, and configuration items as needed.|
|Pipeline Editor||Accessed from within TMS WorldView tab, the TMS Pipeline Editor enables the creation and configuration of the Windows pipelines and their session agents, which process data captured by Experience Analytics.|
|Jobs tab||Configure and execute jobs to assign configurations to servers in the Experience Analytics environment, and start and stop services as needed.|
|Pipeline Status tab||Monitor the performance of individual pipelines and session agents within each pipeline.|
|Advanced tab||Backup, restore, import and export of TMS configuration data.|