Components Diagram

The following diagram describes a typical deployment for LRM. The LRM system must have access to the projects' repositories and the translation endpoints.

Repositories

Two repository types are supported out of the box. Many more can be added to the framework depending on the requirements, provided the repository types support command line calls. To configure the repository for a project once the LRM system has been installed and configured, please refer to this section.

LRM System

LRM

LRM is composed of a number of jar files and configuration files. To install and configure LRM, please refer to this section.

Jenkins

Jenkins orchestrates the different tasks and automates a number of LRM tasks by calling scripts. To install and configure Jenkins, please refer to this section.

Dashboard

The Dashboard is composed of two parts, the Dashboard server and the Dashboard client. They can be set up on different systems if necessary.

Dashboard Server

The Dashboard server is a Web application and must be network accessible to the stakeholders, for instance development teams and management, localization managers, QA, and/or translators. It shows the status of the project.

Dashboard Client

The Dashboard client uses the results of LRM to push data to the Dashboard server.

Translation Systems

LRM connects seamlessly to translation systems. Out of the box, Lingotek and FTP are available. WorldServer can be added. Other systems may require some custom work to add as a translation system to the framework without changes to the core installation.

Lingotek

Lingotek provides a SaaS translation management system. To configure a project to send files back to forth to Lingotek, please refer to this section.

FTP

A file transfer protocol (FTP) endpoint for outgoing files and one for incoming files can be configured. The files sent and received must conform to a naming and a structure convention. To configure a project to send files back and forth to FTP, please refer to this section.