A number of deployments are possible. This page describes one possible deployment where both Globalyzer and LRM run on the same repositories on a Continuous Globalization system and push the results to a central Dashboard, the i18n specialist works with the Workbench, developers have integrated Globalyzer Lite into their IDE, and resource files go back and forth to a translation system.
Development team members, development management, i18n specialists, L10n management, translators and QA are all target users.
The developer desktop has some Globalyzer Lite external tools configured in the IDE.
The i18n specialist works with Workbench.
Note: the Continuous Globalization system needs to be a Linux machine, preferably CentOS.
- The Globalyzer Server is hosted by Lingoport. If the Globalyzer Server is on-site, a Linux system needs to be provided and installed with the Globalyzer Server software.
- The Dashboard System and Continuous Globalization system are installed on separate machines, although they could be on one Linux system installed by the Stack Installer. The Continuous Globalization system has Globalyzer Clients; Workbench, Lite or CLI.
- There are two Developer Machines shown in this diagram.
- The software developer will have the Globalyzer Lite client on their machine to analyze the code.
- The I18n specialist may use the Globalyzer Workbench to analyze software projects.
A number of possible variations exist, depending on your IT constraints.
- Jenkins can be in a master/slave configuration
- The Jenkins jobs must have access to the the LRM, Globalyzer, and Dashboard client, the source code, and the Globalyzer server (via HTTP/s)
- The Dashboard server can be setup on the same system as the Dashboard client or on a different system
- The MySQL databases can be setup on a separate system or many separate systems