Globalyzer Lite for Continuous Globalization - Revision history

Rdaly: /* Installation Components */

2017-01-17T20:54:03Z

Installation Components

← Older revision		Revision as of 20:54, 17 January 2017
Line 26:		Line 26:
	= Installation Components =		= Installation Components =
	* The '''Globalyzer Server''' (Server system) is hosted by Lingoport. If the Globalyzer Server is on site, a Linux machine is needed to be installed with Globalyzer Server.		* The '''Globalyzer Server''' (Server system) is hosted by Lingoport. If the Globalyzer Server is on site, a Linux machine is needed to be installed with Globalyzer Server.
	* The '''Dashboard System''' and '''Continuous Globalization ~~system~~''' are shown installed on different machines, although they could be one machine installed with the [[Terms_and_Definitions#stackinstaller\|Stack Installer]]. The Globalyzer Lite client is installed on the Continuous Globalization ~~system~~ to analyze code.		* The '''Dashboard System''' and '''Continuous Globalization System''' are shown installed on different machines, although they could be one machine installed with the [[Terms_and_Definitions#stackinstaller\|Stack Installer]]. The [[Terms_and_Definitions#GlobalyzerLite\|Globalyzer Lite]] client is installed on the [[Terms_and_Definitions#continuousglobalizationsystem\|Continuous Globalization System]] to analyze code.
	* The '''Developer Machine''' is not shown in this diagram. The developer will push source code to the repositories and may not have any Lingoport Software on their machine.		* The '''Developer Machine''' is not shown in this diagram. The developer will push source code to the repositories and may not have any Lingoport Software on their machine.

Rdaly: /* Installation Components */

2016-12-30T18:26:10Z

Installation Components

← Older revision		Revision as of 18:26, 30 December 2016
Line 26:		Line 26:
	= Installation Components =		= Installation Components =
	* The '''Globalyzer Server''' (Server system) is hosted by Lingoport. If the Globalyzer Server is on site, a Linux machine is needed to be installed with Globalyzer Server.		* The '''Globalyzer Server''' (Server system) is hosted by Lingoport. If the Globalyzer Server is on site, a Linux machine is needed to be installed with Globalyzer Server.
	* The '''Dashboard ~~Server~~''' and '''~~Build Server~~''' ~~(Continuous Globalization system)~~ are shown installed on different machines, although they could be one ~~machines~~. The Globalyzer Lite client is installed on the ~~Build Server~~ to analyze code.		* The '''Dashboard System''' and '''Continuous Globalization system''' are shown installed on different machines, although they could be one machine installed with the [[Terms_and_Definitions#stackinstaller\|Stack Installer]]. The Globalyzer Lite client is installed on the Continuous Globalization system to analyze code.
	* The '''Developer Machine''' is not shown in this diagram. The developer will push source code to the repositories and may not have any Lingoport Software on their machine.		* The '''Developer Machine''' is not shown in this diagram. The developer will push source code to the repositories and may not have any Lingoport Software on their machine.

Rdaly: /* Installation Components */

2016-12-29T21:21:38Z

Installation Components

← Older revision		Revision as of 21:21, 29 December 2016
Line 25:		Line 25:

	= Installation Components =		= Installation Components =
	* The '''Globalyzer Server''' is hosted by Lingoport. If the Globalyzer Server is on site, a Linux machine is needed to be installed with Globalyzer Server.		* The '''Globalyzer Server''' (Server system) is hosted by Lingoport. If the Globalyzer Server is on site, a Linux machine is needed to be installed with Globalyzer Server.
	* The '''Dashboard Server''' and '''Build Server''' are shown installed on different machines, although they could be one machines. The Globalyzer Lite client is installed on the Build Server to analyze code.		* The '''Dashboard Server''' and '''Build Server''' (Continuous Globalization system) are shown installed on different machines, although they could be one machines. The Globalyzer Lite client is installed on the Build Server to analyze code.
	* The '''Developer Machine''' is not shown in this diagram. The developer will push source code to the repositories and may not have any Lingoport Software on their machine.		* The '''Developer Machine''' is not shown in this diagram. The developer will push source code to the repositories and may not have any Lingoport Software on their machine.

Rdaly: /* Installation Components */

2016-12-29T20:58:44Z

Installation Components

← Older revision		Revision as of 20:58, 29 December 2016
Line 26:		Line 26:
	= Installation Components =		= Installation Components =
	* The '''Globalyzer Server''' is hosted by Lingoport. If the Globalyzer Server is on site, a Linux machine is needed to be installed with Globalyzer Server.		* The '''Globalyzer Server''' is hosted by Lingoport. If the Globalyzer Server is on site, a Linux machine is needed to be installed with Globalyzer Server.
	* The '''Dashboard Server''' and '''Build Server''' are installed on different machines, although they could be one machines. The Globalyzer Lite client is installed on the Build Server to analyze code.		* The '''Dashboard Server''' and '''Build Server''' are shown installed on different machines, although they could be one machines. The Globalyzer Lite client is installed on the Build Server to analyze code.
	* The '''Developer Machine''' is not shown in this diagram. The developer will push source code to the repositories and may not have any Lingoport Software on their machine.		* The '''Developer Machine''' is not shown in this diagram. The developer will push source code to the repositories and may not have any Lingoport Software on their machine.

Rdaly: /* Installation Components */

2016-12-29T20:53:38Z

Installation Components

← Older revision		Revision as of 20:53, 29 December 2016
Line 25:		Line 25:

	= Installation Components =		= Installation Components =
	* The '''Globalyzer Server''' is hosted by Lingoport.		* The '''Globalyzer Server''' is hosted by Lingoport. If the Globalyzer Server is on site, a Linux machine is needed to be installed with Globalyzer Server.
	* The '''Dashboard Server''' and '''Build Server''' are installed on different machines, although they could be one machines. The Globalyzer Lite client is installed on the Build Server to analyze code.		* The '''Dashboard Server''' and '''Build Server''' are installed on different machines, although they could be one machines. The Globalyzer Lite client is installed on the Build Server to analyze code.
	* The '''Developer Machine''' is not shown in this diagram. The developer will push source code to the repositories and may not have any Lingoport Software on their machine.		* The '''Developer Machine''' is not shown in this diagram. The developer will push source code to the repositories and may not have any Lingoport Software on their machine.

Rdaly: /* Installation Components */

2016-12-29T20:51:50Z

Installation Components

← Older revision		Revision as of 20:51, 29 December 2016
Line 26:		Line 26:
	= Installation Components =		= Installation Components =
	* The '''Globalyzer Server''' is hosted by Lingoport.		* The '''Globalyzer Server''' is hosted by Lingoport.
	* The '''Dashboard Server''' and '''Build Server''' are installed on different machines, although they could be one machines.		* The '''Dashboard Server''' and '''Build Server''' are installed on different machines, although they could be one machines. The Globalyzer Lite client is installed on the Build Server to analyze code.
	* The '''Developer Machine''' is not shown in this diagram. The developer will push source code to the repositories and may not have any Lingoport Software on their machine.		* The '''Developer Machine''' is not shown in this diagram. The developer will push source code to the repositories and may not have any Lingoport Software on their machine.

Rdaly at 20:49, 29 December 2016

2016-12-29T20:49:22Z

← Older revision		Revision as of 20:49, 29 December 2016
Line 23:		Line 23:

	This requires the [[Terms_and_Definitions#ruleset\|rule sets]] used to [[Terms_and_Definitions#scan\|scan]] the code have been vetted and the Globalyzer Lite <code>project definition xml</code> to have been created.		This requires the [[Terms_and_Definitions#ruleset\|rule sets]] used to [[Terms_and_Definitions#scan\|scan]] the code have been vetted and the Globalyzer Lite <code>project definition xml</code> to have been created.

			= Installation Components =
			* The '''Globalyzer Server''' is hosted by Lingoport.
			* The '''Dashboard Server''' and '''Build Server''' are installed on different machines, although they could be one machines.
			* The '''Developer Machine''' is not shown in this diagram. The developer will push source code to the repositories and may not have any Lingoport Software on their machine.

	= Installation Note =		= Installation Note =
	To install Globalyzer Lite, you must have access to a the zip file for Lite. The installation only requires unzipping the zip file and executing the lite-setup script.		To install Globalyzer Lite, you must have access to a the zip file for Lite. The installation only requires unzipping the zip file and executing the lite-setup script.
	To configure Globalyzer Lite for Continuous Globalization, you then need to look at the globalyzer.com help page for Lite, [https://www.globalyzer.com/gzserver/help/referenceLite/using-globalyzer-lite.html using-globalyzer-lite.html] (login is required).		To configure Globalyzer Lite for Continuous Globalization, you then need to look at the globalyzer.com help page for Lite, [https://www.globalyzer.com/gzserver/help/referenceLite/using-globalyzer-lite.html using-globalyzer-lite.html] (login is required).

Rdaly: /* Typical Workflow */

2016-12-27T21:45:30Z

Typical Workflow

← Older revision		Revision as of 21:45, 27 December 2016
Line 22:		Line 22:


	This requires the [[Terms_and_Definitions#ruleset\|rule sets]] used to [[Terms_and_Definitions#scan\|scan]] the code have been vetted and the Globalyzer <code>project definition xml</code> to have been created.		This requires the [[Terms_and_Definitions#ruleset\|rule sets]] used to [[Terms_and_Definitions#scan\|scan]] the code have been vetted and the Globalyzer Lite <code>project definition xml</code> to have been created.

	= Installation Note =		= Installation Note =
	To install Globalyzer Lite, you must have access to a the zip file for Lite. The installation only requires unzipping the zip file and executing the lite-setup script.		To install Globalyzer Lite, you must have access to a the zip file for Lite. The installation only requires unzipping the zip file and executing the lite-setup script.
	To configure Globalyzer Lite for Continuous Globalization, you then need to look at the globalyzer.com help page for Lite, [https://www.globalyzer.com/gzserver/help/referenceLite/using-globalyzer-lite.html using-globalyzer-lite.html] (login is required).		To configure Globalyzer Lite for Continuous Globalization, you then need to look at the globalyzer.com help page for Lite, [https://www.globalyzer.com/gzserver/help/referenceLite/using-globalyzer-lite.html using-globalyzer-lite.html] (login is required).

Rdaly: /* Typical Workflow */

2016-12-27T21:44:56Z

Typical Workflow

← Older revision		Revision as of 21:44, 27 December 2016
Line 22:		Line 22:


	This requires the [[Terms_and_Definitions#ruleset\|rule sets]] used to [[~~Terms_and_Definitions3scan~~\|scan]] the code have been vetted and the Globalyzer <code>project definition xml</code> to have been created.		This requires the [[Terms_and_Definitions#ruleset\|rule sets]] used to [[Terms_and_Definitions#scan\|scan]] the code have been vetted and the Globalyzer <code>project definition xml</code> to have been created.

	= Installation Note =		= Installation Note =
	To install Globalyzer Lite, you must have access to a the zip file for Lite. The installation only requires unzipping the zip file and executing the lite-setup script.		To install Globalyzer Lite, you must have access to a the zip file for Lite. The installation only requires unzipping the zip file and executing the lite-setup script.
	To configure Globalyzer Lite for Continuous Globalization, you then need to look at the globalyzer.com help page for Lite, [https://www.globalyzer.com/gzserver/help/referenceLite/using-globalyzer-lite.html using-globalyzer-lite.html] (login is required).		To configure Globalyzer Lite for Continuous Globalization, you then need to look at the globalyzer.com help page for Lite, [https://www.globalyzer.com/gzserver/help/referenceLite/using-globalyzer-lite.html using-globalyzer-lite.html] (login is required).

Rdaly at 21:44, 27 December 2016

2016-12-27T21:44:21Z

← Older revision		Revision as of 21:44, 27 December 2016
Line 1:		Line 1:
	= Introduction =		= Introduction =
	[[Terms_and_Definitions\|Globalyzer Lite]] can be deployed on a [[Terms_and_Definitions\|Continuous Globalization]] system. It enables [[Terms_and_Definitions\|i18n]] [[Terms_and_Definitions\|scanning]] of a project based on a [[Terms_and_Definitions\|Globalyzer project definition xml file]], most likely saved at the top level directory of the source code; the results are then pushed to the [[Terms_and_Definitions\|Dashboard]].		[[Terms_and_Definitions#GlobalyzerLite\|Globalyzer Lite]] can be deployed on a [[Terms_and_Definitions#ContinuousGlobalization\|Continuous Globalization]] system. It enables [[Terms_and_Definitions#i18n\|i18n]] [[Terms_and_Definitions#scan\|scanning]] of a project based on a [[Terms_and_Definitions#Globalyzerproject\|Globalyzer project definition xml file]], most likely saved at the top level directory of the source code; the results are then pushed to the [[Terms_and_Definitions#Dashboard\|Dashboard]].

	= Target User=		= Target User=
	The results are presented via the [[Terms_and_Definitions\|Dashboard]] for any registered users, such as development team members, development management, [[Terms_and_Definitions\|i18n]] specialists, [[Terms_and_Definitions\|L10n]] management, translators, QA, etc.		The results are presented via the [[Terms_and_Definitions#Dashboard\|Dashboard]] for any registered users, such as development team members, development management, [[Terms_and_Definitions#i18n\|i18n]] specialists, [[Terms_and_Definitions#localization\|L10n]] management, translators, QA, etc.

	The typical [[Terms_and_Definitions\|Globalyzer Lite]] <code>actor</code> is a [[Terms_and_Definitions\|Jenkins]] system which automates the tasks of scanning and pushing the results to the [[Terms_and_Definitions\|Dashboard]].		The typical [[Terms_and_Definitions#GlobalyzerLite\|Globalyzer Lite]] <code>actor</code> is a [[Terms_and_Definitions#Jenkins\|Jenkins]] system which automates the tasks of scanning and pushing the results to the [[Terms_and_Definitions#Dashboard\|Dashboard]].

	= Typical Deployment =		= Typical Deployment =
	[[Terms_and_Definitions\|Globalyzer Lite]] can be unzipped from [[Terms_and_Definitions\|Jenkins]] every time, for instance on a master/slave Jenkins system, or may have been unzipped/installed beforehand, without any database requirement.		[[Terms_and_Definitions#GlobalyzerLite\|Globalyzer Lite]] can be unzipped from [[Terms_and_Definitions#Jenkins\|Jenkins]] every time, for instance on a master/slave Jenkins system, or may have been unzipped/installed beforehand, without any database requirement.
	The source code must have a <code>project definition xml file</code> which specifies how the code should be [[Terms_and_Definitions\|scanned]]. It is recommended that this be placed at the top level directory of the project.		The source code must have a <code>project definition xml file</code> which specifies how the code should be [[Terms_and_Definitions#scan\|scanned]]. It is recommended that this be placed at the top level directory of the project.

	[[File:Lite for CI.gif]]		[[File:Lite for CI.gif]]

	<b>Note</b>: If you add [[Terms_and_Definitions\|LRM]] to this picture, the [[Terms_and_Definitions\|Continuous Globalization]] system needs to be a Linux machine, preferably CentOS.		<b>Note</b>: If you add [[Terms_and_Definitions#LRM\|LRM]] to this picture, the [[Terms_and_Definitions#ContinuousGlobalization\|Continuous Globalization]] system needs to be a Linux machine, preferably CentOS.

	= Typical Workflow=		= Typical Workflow=
	[[Terms_and_Definitions\|Jenkins]] uses [[Terms_and_Definitions\|Globalyzer Lite]] via scripts to:		[[Terms_and_Definitions#Jenkins\|Jenkins]] uses [[Terms_and_Definitions#GlobalyzerLite\|Globalyzer Lite]] via scripts to:
	* Get the code to be analyzed from a [[Terms_and_Definitions\|repository]]		* Get the code to be analyzed from a [[Terms_and_Definitions#repository\|repository]]
	* Use the [[Terms_and_Definitions\|Globalyzer project definition file]] to [[Terms_and_Definitions\|scan]] the code for potential [[Terms_and_Definitions\|i18n]] issues with Globalyzer Lite		* Use the [[Terms_and_Definitions#LiteProjectDefn\|Globalyzer Lite project definition file]] to [[Terms_and_Definitions#scan\|scan]] the code for potential [[Terms_and_Definitions#i18n\|i18n]] issues with Globalyzer Lite
	** Optionally push the results of the scan to the [[Terms_and_Definitions\|Dashboard]] or use the results for other purposes		** Optionally push the results of the scan to the [[Terms_and_Definitions#Dashboard\|Dashboard]] or use the results for other purposes


	This requires the [[Terms_and_Definitions\|rule sets]] used to [[~~Terms_and_Definitions~~\|scan]] the code have been vetted and the Globalyzer <code>project definition xml</code> to have been created.		This requires the [[Terms_and_Definitions#ruleset\|rule sets]] used to [[Terms_and_Definitions3scan\|scan]] the code have been vetted and the Globalyzer <code>project definition xml</code> to have been created.

	= Installation Note =		= Installation Note =
	To install Globalyzer Lite, you must have access to a the zip file for Lite. The installation only requires unzipping the zip file and executing the lite-setup script.		To install Globalyzer Lite, you must have access to a the zip file for Lite. The installation only requires unzipping the zip file and executing the lite-setup script.
	To configure Globalyzer Lite for Continuous Globalization, you then need to look at the globalyzer.com help page for Lite, [https://www.globalyzer.com/gzserver/help/referenceLite/using-globalyzer-lite.html using-globalyzer-lite.html] (login is required).		To configure Globalyzer Lite for Continuous Globalization, you then need to look at the globalyzer.com help page for Lite, [https://www.globalyzer.com/gzserver/help/referenceLite/using-globalyzer-lite.html using-globalyzer-lite.html] (login is required).

← Older revision		Revision as of 21:44, 27 December 2016
Line 1:		Line 1:
	= Introduction =		= Introduction =
	[[Terms_and_Definitions\|Globalyzer Lite]] can be deployed on a [[Terms_and_Definitions\|Continuous Globalization]] system. It enables [[Terms_and_Definitions\|i18n]] [[Terms_and_Definitions\|scanning]] of a project based on a [[Terms_and_Definitions\|Globalyzer project definition xml file]], most likely saved at the top level directory of the source code; the results are then pushed to the [[Terms_and_Definitions\|Dashboard]].		[[Terms_and_Definitions#GlobalyzerLite\|Globalyzer Lite]] can be deployed on a [[Terms_and_Definitions#ContinuousGlobalization\|Continuous Globalization]] system. It enables [[Terms_and_Definitions#i18n\|i18n]] [[Terms_and_Definitions#scan\|scanning]] of a project based on a [[Terms_and_Definitions#Globalyzerproject\|Globalyzer project definition xml file]], most likely saved at the top level directory of the source code; the results are then pushed to the [[Terms_and_Definitions#Dashboard\|Dashboard]].

	= Target User=		= Target User=
	The results are presented via the [[Terms_and_Definitions\|Dashboard]] for any registered users, such as development team members, development management, [[Terms_and_Definitions\|i18n]] specialists, [[Terms_and_Definitions\|L10n]] management, translators, QA, etc.		The results are presented via the [[Terms_and_Definitions#Dashboard\|Dashboard]] for any registered users, such as development team members, development management, [[Terms_and_Definitions#i18n\|i18n]] specialists, [[Terms_and_Definitions#localization\|L10n]] management, translators, QA, etc.

	The typical [[Terms_and_Definitions\|Globalyzer Lite]] <code>actor</code> is a [[Terms_and_Definitions\|Jenkins]] system which automates the tasks of scanning and pushing the results to the [[Terms_and_Definitions\|Dashboard]].		The typical [[Terms_and_Definitions#GlobalyzerLite\|Globalyzer Lite]] <code>actor</code> is a [[Terms_and_Definitions#Jenkins\|Jenkins]] system which automates the tasks of scanning and pushing the results to the [[Terms_and_Definitions#Dashboard\|Dashboard]].

	= Typical Deployment =		= Typical Deployment =
	[[Terms_and_Definitions\|Globalyzer Lite]] can be unzipped from [[Terms_and_Definitions\|Jenkins]] every time, for instance on a master/slave Jenkins system, or may have been unzipped/installed beforehand, without any database requirement.		[[Terms_and_Definitions#GlobalyzerLite\|Globalyzer Lite]] can be unzipped from [[Terms_and_Definitions#Jenkins\|Jenkins]] every time, for instance on a master/slave Jenkins system, or may have been unzipped/installed beforehand, without any database requirement.
	The source code must have a <code>project definition xml file</code> which specifies how the code should be [[Terms_and_Definitions\|scanned]]. It is recommended that this be placed at the top level directory of the project.		The source code must have a <code>project definition xml file</code> which specifies how the code should be [[Terms_and_Definitions#scan\|scanned]]. It is recommended that this be placed at the top level directory of the project.

	[[File:Lite for CI.gif]]		[[File:Lite for CI.gif]]

	<b>Note</b>: If you add [[Terms_and_Definitions\|LRM]] to this picture, the [[Terms_and_Definitions\|Continuous Globalization]] system needs to be a Linux machine, preferably CentOS.		<b>Note</b>: If you add [[Terms_and_Definitions#LRM\|LRM]] to this picture, the [[Terms_and_Definitions#ContinuousGlobalization\|Continuous Globalization]] system needs to be a Linux machine, preferably CentOS.

	= Typical Workflow=		= Typical Workflow=
	[[Terms_and_Definitions\|Jenkins]] uses [[Terms_and_Definitions\|Globalyzer Lite]] via scripts to:		[[Terms_and_Definitions#Jenkins\|Jenkins]] uses [[Terms_and_Definitions#GlobalyzerLite\|Globalyzer Lite]] via scripts to:
	* Get the code to be analyzed from a [[Terms_and_Definitions\|repository]]		* Get the code to be analyzed from a [[Terms_and_Definitions#repository\|repository]]
	* Use the [[Terms_and_Definitions\|Globalyzer project definition file]] to [[Terms_and_Definitions\|scan]] the code for potential [[Terms_and_Definitions\|i18n]] issues with Globalyzer Lite		* Use the [[Terms_and_Definitions#LiteProjectDefn\|Globalyzer Lite project definition file]] to [[Terms_and_Definitions#scan\|scan]] the code for potential [[Terms_and_Definitions#i18n\|i18n]] issues with Globalyzer Lite
	** Optionally push the results of the scan to the [[Terms_and_Definitions\|Dashboard]] or use the results for other purposes		** Optionally push the results of the scan to the [[Terms_and_Definitions#Dashboard\|Dashboard]] or use the results for other purposes


	This requires the [[Terms_and_Definitions\|rule sets]] used to [[~~Terms_and_Definitions~~\|scan]] the code have been vetted and the Globalyzer <code>project definition xml</code> to have been created.		This requires the [[Terms_and_Definitions#ruleset\|rule sets]] used to [[Terms_and_Definitions3scan\|scan]] the code have been vetted and the Globalyzer <code>project definition xml</code> to have been created.

	= Installation Note =		= Installation Note =
	To install Globalyzer Lite, you must have access to a the zip file for Lite. The installation only requires unzipping the zip file and executing the lite-setup script.		To install Globalyzer Lite, you must have access to a the zip file for Lite. The installation only requires unzipping the zip file and executing the lite-setup script.
	To configure Globalyzer Lite for Continuous Globalization, you then need to look at the globalyzer.com help page for Lite, [https://www.globalyzer.com/gzserver/help/referenceLite/using-globalyzer-lite.html using-globalyzer-lite.html] (login is required).		To configure Globalyzer Lite for Continuous Globalization, you then need to look at the globalyzer.com help page for Lite, [https://www.globalyzer.com/gzserver/help/referenceLite/using-globalyzer-lite.html using-globalyzer-lite.html] (login is required).