Typical Deployment and Ports
Setting up the Lingoport Continuous Globalization System at a customer's can be done in many ways, as shown in the different deployment scenarios. The following is meant to show the necessary access to the system.
- The Customer's systems are shown in Light Blue; CentOS for the main system where Jenkins and Dashboard reside.
- Access from outside the Customer's system are shown in Light Green.
- The Globalyzer Server is hosted by Lingoport.
- The Continuous Globalization System includes the Lingoport Dashboard although they could be on different machines. It is recommended to be installed using the Stack Installer
- The Developer Machine is not shown in this diagram. The developer will push source code to the code repositories and may not have any Lingoport Software on their machine.
- Jenkins is accessed via port 8080
- Lingoport Dashboard is accessed via port 9000
- The Translation Vendor may be accessed by different means, for instance port 21 for FTP or port 22 for SFTP.
- Access for the Lingoport (or internal) installation team can be done in many ways, such as SSH for Telnet or Putty.
- The system must be able to access https://globalyzer.com.
- Jenkins installation requires access to the Jenkins update site, http://updates.jenkins-ci.org
- Dashboard may require access to the SonarQube update site, http://update.sonarsource.org
- Notifications are sent using an SMTP account: The system must allow access to an SMTP server (e.g. smtp.gmail.com for Google)
In this section, we illustrate some possible deployments.
- Globalyzer Workbench for i18n Specialists
- Globalyzer Lite for Developers
- Globalyzer Lite for Continuous Globalization
- Simple to set up.
- Lighter interface for Continuous Globalization.
- Projects can be analyzed concurrently.
- Globalyzer CLI for Continuous Globalization
- Powerful, with many options.
- Historically standard for Continuous Globalization.
- Projects must be analyzed one at a time.
- Globalyzer API for Continuous Globalization
- Most powerful and most flexible option.
- Requires writing your own Java program(s).
- LRM for Continuous Globalization
- Keeps tabs on the status of translations and resource files.
- Automates much of the translation process.
- Continuous Globalization
- Combination of the above sections.