Jump to: navigation, search


The following section describes the recommended architecture for an LFMT deployment. Although all LFMT components can be deployed on a single host, the recommended architecture shows three hosts: the LFMT Server Host, the LFMT Client Host, and the LFMT Database Host.

LFMT Server Host

The LFMT Server Host consists of the following components:

  • Central Log Storage (CLS) repository, the central repository in which all log files for all applications using the tool are stored.
  • LFMT Collector, which collects the log files for storage in the Central Log Storage (CLS) repository and creates packages for user downloads.
  • LFMT Indexer, which monitors the CLS repository, indexes the files as they arrive at the CLS, and compresses the CLS files for storage.
LFMT Collector and LFMT Indexer must be deployed on the same host. Multiple LFMT Indexer/Collector pairs can be deployed to service one LFMT solution. Only one LFMT Indexer/Collector pair should be deployed on a single host.


LFMT Client Host

The LFMT Client Host consists of the following components:

  • Genesys Administrator Extensions (GAX), a web-based UI to which LFMT Client is a plug-in.
  • LFMT Client, a GAX plug-in that provides the interface through which users specify the log files to retrieve, package, and upload to a given location.
LFMT Client and GAX must be deployed on the same host. Only one LFMT Client is required for each deployed LFMT solution.

LFMT Database Host

The LFMT Database Host consists of the following components:

  • LFMT Database, the central repository where all information about the copied log files is stored.
To improve performance, the LFMT Database Host should be deployed in the same locale as the LFMT Server Host. One LFMT Database is required for each LFMT Indexer/Collector pair.
This page was last edited on November 29, 2019, at 14:41.


Comment on this article:

blog comments powered by Disqus