Deployment Scenarios: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 12: | Line 12: | ||
* [[Deployment and Security]] | * [[Deployment and Security]] | ||
** Shows which ports need to be open for a typical installation. | ** Shows which ports need to be open for a typical installation. | ||
* [[Globalyzer Lite for Continuous Globalization]] | * [[Globalyzer Lite for Continuous Globalization]] | ||
** Simple to set up. | ** Simple to set up. | ||
Revision as of 23:56, 17 November 2016
The Lingoport Suite is composed of a number of components. You may need some of the components for a set of users and other components for continuous globalization.
In this section, we illustrate some possible deployments.
- Globalyzer Workbench for i18n Specialists
- i18n Specialists use the powerful Globalyzer Workbench to refine rule sets and interactively internationalize applications.
- Globalyzer Lite for Developers
- Developers run Globalyzer Lite from within their IDEs, getting quick feedback on potential i18n issues within their code.
- Deployment and Security
- Shows which ports need to be open for a typical installation.
- 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).
- Globalyzer and Check in Verification
- Analyze source code during commit check in.
- Reject commits that fail i18n requirements.
- 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.