Deployment Scenarios - Revision history

Olibouban: /* Internal to company network */

2021-11-02T18:28:49Z

Internal to company network

← Older revision		Revision as of 18:28, 2 November 2021
Line 51:		Line 51:
	\|Automation (Bot) support \|\| 5001 \|\| Y \|\| Y \|\| Optional. May also place directly on 443 if a second DNS + HTTPS provided		\|Automation (Bot) support \|\| 5001 \|\| Y \|\| Y \|\| Optional. May also place directly on 443 if a second DNS + HTTPS provided
	\|-		\|-
	\|[[Terms_and_Definitions#translationvendor\|Translation Vendor]] interactions: FTP/FTPS/SFTP \|\| 21 (FTP) or 443 (FTPS) or 22 (SFTP - recommended) \|\| (FTP/S only) \|\| Y \|\| FTP/FTPS also require data ports (> 1024). Recommend SFTP if possible.		\|[[Terms_and_Definitions#translationvendor\|Translation Vendor]] interactions: FTP/FTPS/SFTP (MemoQ, etc.) \|\| 21 (FTP) or 443 (FTPS) or 22 (SFTP - recommended) \|\| (FTP/S only) \|\| Y \|\| FTP/FTPS also require data ports (> 1024). Recommend SFTP if possible.
	\|-		\|-
	\|[[Terms_and_Definitions#translationvendor\|Translation Vendor]] interactions: XTM and Memsource \|\| 80 (HTTP) optional. 443 (HTTPS) required. \|\| (Some cases) \|\| Y \|\| May need to be external if XTM/Memsource not installed on premise.		\|[[Terms_and_Definitions#translationvendor\|Translation Vendor]] interactions: XTM and Memsource \|\| 80 (HTTP) optional. 443 (HTTPS) required. \|\| (Some cases) \|\| Y \|\| May need to be external if XTM/Memsource not installed on premise.

Masnes: /* Internal to company network */

2021-02-25T20:19:04Z

Internal to company network

← Older revision		Revision as of 20:19, 25 February 2021
Line 49:		Line 49:
	\|[[Terms_and_Definitions#Jenkins\|Jenkins]] & [[Terms_and_Definitions#LingoportDashboard\|Lingoport Dashboard]]: HTTP(S) Access \|\| 80 (HTTP) and/or 443 (HTTPS) \|\| Y \|\| N \|\| HTTPS requires configuration of certificate.		\|[[Terms_and_Definitions#Jenkins\|Jenkins]] & [[Terms_and_Definitions#LingoportDashboard\|Lingoport Dashboard]]: HTTP(S) Access \|\| 80 (HTTP) and/or 443 (HTTPS) \|\| Y \|\| N \|\| HTTPS requires configuration of certificate.
	\|-		\|-
	\|Automation (Bot) support \|\| 5001 \|\| Y \|\| Y \|\| Optional		\|Automation (Bot) support \|\| 5001 \|\| Y \|\| Y \|\| Optional. May also place directly on 443 if a second DNS + HTTPS provided
	\|-		\|-
	\|[[Terms_and_Definitions#translationvendor\|Translation Vendor]] interactions: FTP/FTPS/SFTP \|\| 21 (FTP) or 443 (FTPS) or 22 (SFTP - recommended) \|\| Y \|\| Y \|\| FTP/FTPS also require data ports (> 1024). Recommend SFTP if possible.		\|[[Terms_and_Definitions#translationvendor\|Translation Vendor]] interactions: FTP/FTPS/SFTP \|\| 21 (FTP) or 443 (FTPS) or 22 (SFTP - recommended) \|\| (FTP/S only) \|\| Y \|\| FTP/FTPS also require data ports (> 1024). Recommend SFTP if possible.
	\|-		\|-
	\|[[Terms_and_Definitions#translationvendor\|Translation Vendor]] interactions: XTM and Memsource \|\| 80 (HTTP) optional. 443 (HTTPS) required. \|\| Y \|\| Y \|\| May need to be external if XTM/Memsource not installed on premise.		\|[[Terms_and_Definitions#translationvendor\|Translation Vendor]] interactions: XTM and Memsource \|\| 80 (HTTP) optional. 443 (HTTPS) required. \|\| (Some cases) \|\| Y \|\| May need to be external if XTM/Memsource not installed on premise.
	\|-		\|-
	\|SMTP/SMTPS \|\| 25 or 465 or 587 \|\| N \|\| Y \|\| Depends on corporate mail setup.		\|SMTP/SMTPS \|\| 25 or 465 or 587 \|\| N \|\| Y \|\| Depends on corporate mail setup.

Olibouban at 20:19, 23 February 2021

2021-02-23T20:19:55Z

Masnes: /* Internal to company network */

2020-09-08T19:33:29Z

Internal to company network

← Older revision		Revision as of 19:33, 8 September 2020
Line 43:		Line 43:

	{\| border="1" class="wikitable" style="text-align:left; width=50%;"		{\| border="1" class="wikitable" style="text-align:left; width=50%;"
	!Services!!Ports!!Inbound!!Outbound!!Notes		!Services!!Ports!!Inbound (session)!!Outbound (session)!!Notes
	\|-		\|-
	\|SSH (for system config/maintenance)\|\| 22 \|\| Y \|\| N \|\| System configuration and maintenance		\|SSH (for system config/maintenance)\|\| 22 \|\| Y \|\| N \|\| System configuration and maintenance

Masnes: /* Internal to company network */

2020-05-22T19:36:33Z

Internal to company network

← Older revision		Revision as of 19:36, 22 May 2020
Line 45:		Line 45:
	!Services!!Ports!!Inbound!!Outbound!!Notes		!Services!!Ports!!Inbound!!Outbound!!Notes
	\|-		\|-
	\|SSH (for system config/maintenance)\|\| 22 \|\| Y \|\| N \|\|		\|SSH (for system config/maintenance)\|\| 22 \|\| Y \|\| N \|\| System configuration and maintenance
	\|-		\|-
	\|[[Terms_and_Definitions#Jenkins\|Jenkins]] & [[Terms_and_Definitions#LingoportDashboard\|Lingoport Dashboard]]: HTTP(S) Access \|\| 80 (HTTP) and/or 443 (HTTPS) \|\| Y \|\| N \|\| HTTPS requires configuration of certificate.		\|[[Terms_and_Definitions#Jenkins\|Jenkins]] & [[Terms_and_Definitions#LingoportDashboard\|Lingoport Dashboard]]: HTTP(S) Access \|\| 80 (HTTP) and/or 443 (HTTPS) \|\| Y \|\| N \|\| HTTPS requires configuration of certificate.

Rdaly: /* External Access */

2020-01-22T00:09:43Z

External Access

← Older revision		Revision as of 00:09, 22 January 2020
Line 33:		Line 33:
	* Access to epel yum package repository: https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm		* Access to epel yum package repository: https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm
	* Access to https://globalyzer.com.		* Access to https://globalyzer.com.
	** May purchase an Enterprise License to deploy Globalyzer server.		** 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.		** 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 Jenkins update center

Rdaly: /* External Access */

2020-01-22T00:09:25Z

External Access

← Older revision		Revision as of 00:09, 22 January 2020
Line 32:		Line 32:
	* Must have the ability to install/update programs via 'yum'		* 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 epel yum package repository: https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm
	* Access to https://globalyzer.com. ~~Or may~~ purchase an Enterprise License to deploy Globalyzer server.		* Access to https://globalyzer.com.
	* ~~Access~~ to https://~~updates~~.~~jenkins-ci~~.~~org (~~Jenkins update center)		** May purchase an Enterprise License to deploy Globalyzer server.
	* Access to ~~https://update.sonarsource.org (~~SonarQube update center)		** 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

	=== Ports ===		=== Ports ===

Masnes: /* Internal to company network */

2019-11-27T00:20:04Z

Internal to company network

← Older revision		Revision as of 00:20, 27 November 2019
Line 51:		Line 51:
	\|[[Terms_and_Definitions#translationvendor\|Translation Vendor]] interactions: FTP/FTPS/SFTP \|\| 21 (FTP) or 443 (FTPS) or 22 (SFTP - recommended) \|\| Y \|\| Y \|\| FTP/FTPS also require data ports (> 1024). Recommend SFTP if possible.		\|[[Terms_and_Definitions#translationvendor\|Translation Vendor]] interactions: FTP/FTPS/SFTP \|\| 21 (FTP) or 443 (FTPS) or 22 (SFTP - recommended) \|\| Y \|\| Y \|\| FTP/FTPS also require data ports (> 1024). Recommend SFTP if possible.
	\|-		\|-
	\|[[Terms_and_Definitions#translationvendor\|Translation Vendor]] interactions: XTM and Memsource \|\| 80 (HTTP) optional. 443 (HTTPS) required. \|\| Y \|\| Y \|\| May need to be external if ~~using non-enterprise versions of APIs~~		\|[[Terms_and_Definitions#translationvendor\|Translation Vendor]] interactions: XTM and Memsource \|\| 80 (HTTP) optional. 443 (HTTPS) required. \|\| Y \|\| Y \|\| May need to be external if XTM/Memsource not installed on premise.
	\|-		\|-
	\|SMTP/SMTPS \|\| 25 or 465 or 587 \|\| N \|\| Y \|\| Depends on corporate mail setup.		\|SMTP/SMTPS \|\| 25 or 465 or 587 \|\| N \|\| Y \|\| Depends on corporate mail setup.

Masnes: /* Internal to company network */

2019-11-27T00:19:45Z

Internal to company network

← Older revision		Revision as of 00:19, 27 November 2019
Line 51:		Line 51:
	\|[[Terms_and_Definitions#translationvendor\|Translation Vendor]] interactions: FTP/FTPS/SFTP \|\| 21 (FTP) or 443 (FTPS) or 22 (SFTP - recommended) \|\| Y \|\| Y \|\| FTP/FTPS also require data ports (> 1024). Recommend SFTP if possible.		\|[[Terms_and_Definitions#translationvendor\|Translation Vendor]] interactions: FTP/FTPS/SFTP \|\| 21 (FTP) or 443 (FTPS) or 22 (SFTP - recommended) \|\| Y \|\| Y \|\| FTP/FTPS also require data ports (> 1024). Recommend SFTP if possible.
	\|-		\|-
	\|[[Terms_and_Definitions#translationvendor\|Translation Vendor]] interactions: XTM and Memsource \|\| 80 (HTTP) optional. 443 (HTTPS) required. \|\| Y \|\| Y \|\| ~~Direct integrations into XTM or Memsource~~ APIs		\|[[Terms_and_Definitions#translationvendor\|Translation Vendor]] interactions: XTM and Memsource \|\| 80 (HTTP) optional. 443 (HTTPS) required. \|\| Y \|\| Y \|\| May need to be external if using non-enterprise versions of APIs
	\|-		\|-
	\|SMTP/SMTPS \|\| 25 or 465 or 587 \|\| N \|\| Y \|\| Depends on corporate mail setup.		\|SMTP/SMTPS \|\| 25 or 465 or 587 \|\| N \|\| Y \|\| Depends on corporate mail setup.

Masnes: /* Internal to company network */

2019-11-27T00:18:54Z

Internal to company network

← Older revision		Revision as of 00:18, 27 November 2019
Line 50:		Line 50:
	\|-		\|-
	\|[[Terms_and_Definitions#translationvendor\|Translation Vendor]] interactions: FTP/FTPS/SFTP \|\| 21 (FTP) or 443 (FTPS) or 22 (SFTP - recommended) \|\| Y \|\| Y \|\| FTP/FTPS also require data ports (> 1024). Recommend SFTP if possible.		\|[[Terms_and_Definitions#translationvendor\|Translation Vendor]] interactions: FTP/FTPS/SFTP \|\| 21 (FTP) or 443 (FTPS) or 22 (SFTP - recommended) \|\| Y \|\| Y \|\| FTP/FTPS also require data ports (> 1024). Recommend SFTP if possible.
			\|-
			\|[[Terms_and_Definitions#translationvendor\|Translation Vendor]] interactions: XTM and Memsource \|\| 80 (HTTP) optional. 443 (HTTPS) required. \|\| Y \|\| Y \|\| Direct integrations into XTM or Memsource APIs
	\|-		\|-
	\|SMTP/SMTPS \|\| 25 or 465 or 587 \|\| N \|\| Y \|\| Depends on corporate mail setup.		\|SMTP/SMTPS \|\| 25 or 465 or 587 \|\| N \|\| Y \|\| Depends on corporate mail setup.

← Older revision		Revision as of 20:19, 23 February 2021
Line 13:		Line 13:
	* Lingoport Dashboard Server and Database		* Lingoport Dashboard Server and Database
	* Lingoport Dashboard Client		* Lingoport Dashboard Client
	* ~~LRM~~ Server and Database		* Localyzer Server and Database
	* InContext Server		* InContext Server
	* SMTP mail server account		* SMTP mail server account
Line 24:		Line 24:
	# 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.		# 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.		# 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 ~~LRM~~ resource reports.		# Lingoport Dashboard updates the status using the results of the Globalyzer scans and Localyzer resource reports.

	== External Access and Ports ==		== External Access and Ports ==
Line 100:		Line 100:
	* The Globalyzer clients also run on the Lingoport Server (light-blue box at bottom of graphic) and the results are displayed on the [[Terms_and_Definitions#LingoportDashboard\|Lingoport Dashboard]] (see data flow)		* The Globalyzer clients also run on the Lingoport Server (light-blue box at bottom of graphic) and the results are displayed on the [[Terms_and_Definitions#LingoportDashboard\|Lingoport Dashboard]] (see data flow)

	==~~Resource Manager~~ (LRM) ==		==Localyzer (formerly LRM) ==
	~~The Lingoport Resource Manager (LRM)~~ manages translation [[Terms_and_Definitions#resourcefiles\|resource files]].		Localyzer manages translation [[Terms_and_Definitions#resourcefiles\|resource files]].
	* ~~LRM~~ detects problems in resource files (duplicate or missing keys, parameter mismatch in text for different languages, etc.)		* Localyzer detects problems in resource files (duplicate or missing keys, parameter mismatch in text for different languages, etc.)
	* ~~LRM~~ also detects changes to resource files and sends relevant changes out to the [[Terms_and_Definitions#translationvendor\|translation vendor]] for translation into other languages.		* Localyzer also detects changes to resource files and sends relevant changes out to the [[Terms_and_Definitions#translationvendor\|translation vendor]] for translation into other languages.
	* ~~LRM~~ automatically retrieves translations from translations vendors and checks those changes into the code source control repository.		* Localyzer automatically retrieves translations from translations vendors and checks those changes into the code source control repository.
	* ~~LRM~~ runs on the Lingoport Server (light-blue box at bottom of graphic).		* Localyzer runs on the Lingoport Server (light-blue box at bottom of graphic).

	==Lingoport Dashboard==		==Lingoport Dashboard==
	The Lingoport Dashboard, a web application, displays [[Terms_and_Definitions#internationalization\|internationalization]] and [[Terms_and_Definitions#localization\|localization]] status using Globalyzer and ~~LRM~~ reports.		The Lingoport Dashboard, a web application, displays [[Terms_and_Definitions#internationalization\|internationalization]] and [[Terms_and_Definitions#localization\|localization]] status using Globalyzer and Localyzer reports.

	* Displays overview and detail views of Globalyzer scan results and Resource Manager translation status.		* Displays overview and detail views of Globalyzer scan results and Resource Manager translation status.
Line 118:		Line 118:

	===Lingoport Dashboard Server===		===Lingoport Dashboard Server===
	The Lingoport Dashboard server displays the results of the Globalyzer Scans and ~~LRM~~ reports in a web application.		The Lingoport Dashboard server displays the results of the Globalyzer Scans and Localyzer reports in a web application.

	==Jenkins (not a Lingoport program)==		==Jenkins (not a Lingoport program)==
Line 139:		Line 139:

	*[[Terms_and_Definitions#ResourceFiles\|Resource Files]] and Bundles are pulled from the Source Control Repository to the [[Terms_and_Definitions#LRMServer\|LRM Server]].		*[[Terms_and_Definitions#ResourceFiles\|Resource Files]] and Bundles are pulled from the Source Control Repository to the [[Terms_and_Definitions#LRMServer\|LRM Server]].
	* ~~LRM~~ determines if there are problems with the resource files or if there are new keys to be translated.		* 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 [[Terms_and_Definitions#prepkit\|Prep Kit]] is created using MySQL to track the translation.		* If there are keys to be translated, a [[Terms_and_Definitions#prepkit\|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.		* 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, ~~LRM~~ downloads and imports the files and sends status emails.		* When the prep kits have been translated, Localyzer downloads and imports the files and sends status emails.
	* ~~LRM~~ pushes the new resource files into the source code repository.		* Localyzer pushes the new resource files into the source code repository.
	* The Lingoport Dashboard updates its status using the ~~LRM~~ reports.		* The Lingoport Dashboard updates its status using the Localyzer reports.

	= Additional Deployments Scenarios =		= Additional Deployments Scenarios =