The Lingoport Suite is composed of Globalyzer, LRM (Resource Manager) and the Lingoport Dashboard. A number of other products are used with the Suite. You may need some of the components for a set of users and other components for Continuous Globalization.
- 1 Typical Deployment and Ports
- 2 Installation Components
- 3 Data Flow
- 4 Additional Deployments Scenarios
Typical Deployment and Ports
Setting up the Lingoport Continuous Globalization System at a customer site can be done in many ways, as shown in the different deployment scenarios. The following is meant to show some of the flow and the necessary access to the system.
The green box is the Continuous Globalization System. It is a Linux (CentOS or RedHat) operating system that has the following installed:
- Globalyzer clients
- Lingoport Dashboard Server and Database
- Lingoport Dashboard Client
- Localyzer Server and Database
- InContext Server
- SMTP mail server account
The Globalyzer Server is either a hosted Lingoport server or another onsite server.
A typical workflow
- Code is committed to a central source code repository (Git, Subversion, etc) by developers.
- Jenkins tools pull the source code from the code repository and scan using Rule Sets stored on the Globalyzer Server or analyze the resource files.
- Jenkins tools determine if the resource files need to be sent to, or imported from, the translation vendor. This may be done via an FTP connection.
- Emails are sent to designated recipients about the status of the translation upload or import.
- Lingoport Dashboard updates the status using the results of the Globalyzer scans and Localyzer resource reports.
External Access and Ports
- Must have the ability to install/update programs via 'yum'
- Access to epel yum package repository: https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm
- Access to https://globalyzer.com.
- May purchase an Enterprise License to deploy an on-site Globalyzer server.
- If using local rulesets for Globalyzer, access is still needed to https://globalyzer.com to manage and store rulesets.
- Access to the Jenkins update center
- Access to the SonarQube update center
Internal to company network
|SSH (for system config/maintenance)
|System configuration and maintenance
|Jenkins & Lingoport Dashboard: HTTP(S) Access
|80 (HTTP) and/or 443 (HTTPS)
|HTTPS requires configuration of certificate.
|Automation (Bot) support
|Optional. May also place directly on 443 if a second DNS + HTTPS provided
|Translation Vendor interactions: FTP/FTPS/SFTP (MemoQ, etc.)
|21 (FTP) or 443 (FTPS) or 22 (SFTP - recommended)
|FTP/FTPS also require data ports (> 1024). Recommend SFTP if possible.
|Translation Vendor interactions: XTM and Memsource
|80 (HTTP) optional. 443 (HTTPS) required.
|May need to be external if XTM/Memsource not installed on premise.
|25 or 465 or 587
|Depends on corporate mail setup.
|Lingoport SSH access
|Optional. Recommended for ease of upgrades and maintenance.
|HTTP & HTTPS access to required sites (above)
|80 and 443
|See Deployment_Scenarios#External Access
- Lingoport Installers and Updaters available on Lingoport SFTP site (lingoport.net). Or may be sent in a custom fashion by special request. Download does not have to be directly to the target machine. It can be downloaded by another machine and then transferred.
- Lingoport requests SSH access to the Lingoport Server. This allows Lingoport to best debug and troubleshoot problems. If this is not possible, Lingoport can guide a customer through the setup using a videoconferencing program such as WebEx or GoToMeeting.
You may want to update either Jenkins or the underlying Dashboard platform to the latest version. If so, you may want to update the continuous globalization system directly or to download the files on one system and copy them over to the continuous globalization system. The URL for updates are:
Furthermore, email notification emails require an SMTP account. The SMTP server access may be internal to your Company or external depending on your email services (e.g. smtp.gmail.com for Google).
Globalyzer scans code and detect internationalization (i18n) issues.
The Globalyzer Server stores regular expression (regex) scanning rules called Rule Sets that are used to identify issues in source code.
- Stores regex pattern based 'rule sets' used to detect i18n issues and filter out false positives and Globalyzer accounts.
- The Globalyzer Server does not store any code or customer information.
The Globalyzer clients display i18n issues found by the Globalyzer scan.
- The Globalyzer clients connect to the Globalyzer Server. The clients log in and download rule sets from the Globalylzer server to scan code. No code is sent to the Globalyzer server, although the Globalyzer clients may push rule set modifications.
- The Globalyzer clients run on developer machines.
- The Globalyzer clients also run on the Lingoport Server (light-blue box at bottom of graphic) and the results are displayed on the Lingoport Dashboard (see data flow)
Localyzer (formerly LRM)
Localyzer manages translation resource files.
- Localyzer detects problems in resource files (duplicate or missing keys, parameter mismatch in text for different languages, etc.)
- Localyzer also detects changes to resource files and sends relevant changes out to the translation vendor for translation into other languages.
- Localyzer automatically retrieves translations from translations vendors and checks those changes into the code source control repository.
- Localyzer runs on the Lingoport Server (light-blue box at bottom of graphic).
- Displays overview and detail views of Globalyzer scan results and Resource Manager translation status.
- Users can view Globalyzer and Resource Manager issues in context within the source code.
- Lingoport Dashboard runs on the Lingoport Server (light-blue box at bottom of graphic).
Lingoport Dashboard Client
The Lingoport Dashboard client runs the scripts which analyzes the projects and creates the XML files that get pushed to the server.
Lingoport Dashboard Server
The Lingoport Dashboard server displays the results of the Globalyzer Scans and Localyzer reports in a web application.
Jenkins (not a Lingoport program)
Jenkins is used to automate running of Globalyzer Client, Resource Manager and updating of the Lingoport Dashboard.
- Several tools created by Lingoport are used to run automation and analysis scripts from the Jenkins interface for the Lingoport Dashboard.
- Jenkins runs on the Lingoport Server (light-blue box at bottom of graphic)
- The internationalization team creates and configures rule sets on the Globalyzer Server. Rule sets are based on the coding languages used.
- Developers can use the Globalyzer Lite client with the rule sets to validate their code locally before committing to a repository.
- A Jenkins tool scans the code using the rule sets, creates XML reports, and pushes the results to the Lingoport Dashboard Server using the Lingoport Dashboard Client.
Resource Manager Process
- Resource Files and Bundles are pulled from the Source Control Repository to the LRM Server.
- Localyzer determines if there are problems with the resource files or if there are new keys to be translated.
- If there are keys to be translated, a Prep Kit is created using MySQL to track the translation.
- The prep kit files (one per translation locale) are sent to the translation vendor via SFTP and success or failure emails are sent to designated recipients.
- When the prep kits have been translated, Localyzer downloads and imports the files and sends status emails.
- Localyzer pushes the new resource files into the source code repository.
- The Lingoport Dashboard updates its status using the Localyzer reports.
Additional Deployments Scenarios
In the Additional Deployments section, we illustrate some possible deployments:
- Team Members
- i18n specialists
- Other Continuous Globalization Deployments