Special L10n Vendor Integrations - Revision history

Llawson: /* FTP / Recommended */

2019-05-20T16:20:24Z

FTP / Recommended

← Older revision		Revision as of 16:20, 20 May 2019
Line 11:		Line 11:
	== FTP / Recommended ==		== FTP / Recommended ==
	Return to the [[ L10n Vendors \| L10n Vendors ]] page for a detailed description and example using FTP as the vendor.		Return to the [[ L10n Vendors \| L10n Vendors ]] page for a detailed description and example using FTP as the vendor.

			==== Test Connection ====
			One minimal way to test the connection is to invoke the --test-connection command for the LRM project:
			<pre>
			java -jar lingoport-ftp-cli.jar --test-connection --group-name <GROUP> -project-name <PROJECT>
			INFO 2019-05-20 10:19:46,554 com.lingoport.ftp.connection.pipeline.TestConnectionPipelineContext.logIsDoneMessage: Test Connection process completed successfully.
			Process completed successfully.
			</pre>

	==GlobalLink==		==GlobalLink==

Llawson: /* WorldServer URL Endpoint */

2019-05-20T16:13:52Z

WorldServer URL Endpoint

← Older revision		Revision as of 16:13, 20 May 2019
Line 151:		Line 151:
	* LRM uses the [https://docs.sdl.com/LiveContent/content/en-US/SDL%20WorldServer%20Developer%20Documentation-v1/GUID-0DEE2BEB-B752-478E-ABD9-C9DF7C0D37AB\| wssdk-client .jar file to communicate with WorldServer ] when sending files to be translated		* LRM uses the [https://docs.sdl.com/LiveContent/content/en-US/SDL%20WorldServer%20Developer%20Documentation-v1/GUID-0DEE2BEB-B752-478E-ABD9-C9DF7C0D37AB\| wssdk-client .jar file to communicate with WorldServer ] when sending files to be translated
	* For instance, the URL could look like <code>https://lingoport.worldserver.com/ws-legacy</code>		* For instance, the URL could look like <code>https://lingoport.worldserver.com/ws-legacy</code>
	* One minimal way to test the connection is to invoke a command for an LRM project:		==== Test Connection ====
			One minimal way to test the connection is to invoke the --test-connection command for the LRM project:
	<pre>		<pre>
	java -jar lingoport-ws-cli.jar --test-connection --group-name <GROUP> -project-name <PROJECT>		java -jar lingoport-ws-cli.jar --test-connection --group-name <GROUP> -project-name <PROJECT>

Rdaly: /* WorldServer URL Endpoint */

2019-05-02T18:13:44Z

WorldServer URL Endpoint

← Older revision		Revision as of 18:13, 2 May 2019
Line 153:		Line 153:
	* One minimal way to test the connection is to invoke a command for an LRM project:		* One minimal way to test the connection is to invoke a command for an LRM project:
	<pre>		<pre>
	java -jar lingoport-ws-cli.jar -tc -gn <GROUP> -pn <PROJECT>		java -jar lingoport-ws-cli.jar --test-connection --group-name <GROUP> -project-name <PROJECT>
	INFO 2019-04-25 10:33:58,638 com.lingoport.lrm.persistence.LrmConnectionFactory.buildSqlSessionFactory: Connect to database successful.		INFO 2019-04-25 10:33:58,638 com.lingoport.lrm.persistence.LrmConnectionFactory.buildSqlSessionFactory: Connect to database successful.
	INFO 2019-04-25 10:34:00,489 com.lingoport.ws.pipeline.stage.TestWorldserverConnectionStage.execute: Testing the Worldserver Connection		INFO 2019-04-25 10:34:00,489 com.lingoport.ws.pipeline.stage.TestWorldserverConnectionStage.execute: Testing the Worldserver Connection
Line 160:		Line 160:
	Process completed successfully.		Process completed successfully.
	</pre>		</pre>


	=== WorldServer Project Type Mapping===		=== WorldServer Project Type Mapping===

Rdaly: /* WorldServer */

2019-05-02T18:11:33Z

WorldServer

← Older revision		Revision as of 18:11, 2 May 2019
Line 110:		Line 110:

	==WorldServer==		==WorldServer==
	To choose WorldServer as the vendor, uncomment the <code>l10n.vendor=worldserver</code> in the config_l10n_vendor.properties file.		To choose WorldServer as the vendor, uncomment the '''<code>l10n.vendor=worldserver</code>''' in the '''<code>config_l10n_vendor.properties</code>''' file.

	With the WorldServer integration, files to be translated are sent via the WorldServer API to a Workflow/Client; The translated files are returned via FTP.		With the WorldServer integration, files to be translated are sent via the WorldServer API to a Workflow/Client; The translated files are returned via FTP.

Rdaly: /* Local Vendor Configuration */

2019-05-02T18:10:52Z

Local Vendor Configuration

← Older revision		Revision as of 18:10, 2 May 2019
Line 98:		Line 98:

	===Local Vendor Configuration===		===Local Vendor Configuration===
	To choose a Local vendor for the prep/translated files, uncomment (or add) the <code>l10n.vendor=local</code> in the appropriate config_l10n_vendor.properties file.		To choose a Local vendor for the prep/translated files, uncomment (or add) the '''<code>l10n.vendor=local</code>''' in the appropriate '''<code>config_l10n_vendor.properties</code>''' file.

	The information that is required when configuring a local vendor is:		The information that is required when configuring a local vendor is:

Rdaly: /* Lingotek */

2019-05-02T18:09:48Z

Lingotek

← Older revision		Revision as of 18:09, 2 May 2019
Line 55:		Line 55:

	==Lingotek==		==Lingotek==
	To choose Lingotek as the vendor, uncomment the <code>l10n.vendor=lingotek</code> in the config_l10n_vendor.properties file.		To choose Lingotek as the vendor, uncomment the '''<code>l10n.vendor=lingotek</code>''' in the '''<code>config_l10n_vendor.properties</code>''' file.

	The information that is needed to upload the files to be translated as well as retrieve translated files is:		The information that is needed to upload the files to be translated as well as retrieve translated files is:
Line 79:		Line 79:

	The default location for the configuration file is at the group level (<HOME>/Lingoport_Data/L10nStreamlining/<group name>/config). The configuration file also exists in the LRM install directory's <code><HOME>/lingoport/lrm-server-x.y/deploy/templates/dir_structure/group/config</code> folder.		The default location for the configuration file is at the group level (<HOME>/Lingoport_Data/L10nStreamlining/<group name>/config). The configuration file also exists in the LRM install directory's <code><HOME>/lingoport/lrm-server-x.y/deploy/templates/dir_structure/group/config</code> folder.

			<pre>
			#
			#Locale mapping language only locales - Locales should be in the java format (_)
			# This is the default mapping. For your community, you'll need to edit this file
			# and place it either at the group level or the project level.
			#
			aa=aa_DJ
			ab=ab_GE
			af=af_ZA
			ak=ak_GH
			am=am_ET
			...
			</pre>

	== Local Vendor==		== Local Vendor==

Rdaly: /* GlobalLink Locale Mapping */

2019-05-02T18:04:45Z

GlobalLink Locale Mapping

← Older revision		Revision as of 18:04, 2 May 2019
Line 39:		Line 39:

	===GlobalLink Locale Mapping===		===GlobalLink Locale Mapping===
	GlobalLink does not allow language only locales. If there are LRM target locales that are language-only, then a mapping between the LRM locale and the GlobalLink locale should be entered into <code>config_gl_locale_mapping.properties</code> file if it doesn't already exist.		GlobalLink does not allow language only locales. For example, 'fr' instead of 'fr_FR'. If there are LRM target locales that are language-only, then a mapping between the LRM locale and the GlobalLink locale should be entered into <code>config_gl_locale_mapping.properties</code> file if it doesn't already exist.

	Though the default location for the configuration file is at the global level (<HOME>/Lingoport_Data/L10nStreamlining/config), the file may also reside at the group or project level. The configuration file also exists in the LRM install directory's <code><HOME>/lingoport/lrm-server-x.y/deploy/templates/dir_structure/global/config</code> folder.		Though the default location for the configuration file is at the global level (<HOME>/Lingoport_Data/L10nStreamlining/config), the file may also reside at the group or project level. The configuration file also exists in the LRM install directory's <code><HOME>/lingoport/lrm-server-x.y/deploy/templates/dir_structure/global/config</code> folder.

			<pre>
			#Mapping between the lrm target locale and their corresponding GlobalLink target locale
			#lrm locale = globallink locale
			es = es_es
			</pre>

	===GlobalLink File Format Mapping===		===GlobalLink File Format Mapping===

Rdaly: /* FTP / Recommended */

2019-05-02T18:01:34Z

FTP / Recommended

← Older revision		Revision as of 18:01, 2 May 2019
Line 10:		Line 10:

	== FTP / Recommended ==		== FTP / Recommended ==
	Return to the [[ L10n Vendors \| L10n Vendors ]] page for detailed description of using FTP as the vendor.		Return to the [[ L10n Vendors \| L10n Vendors ]] page for a detailed description and example using FTP as the vendor.

	==GlobalLink==		==GlobalLink==

Rdaly: /* Overview */

2019-05-02T18:00:51Z

Overview

← Older revision		Revision as of 18:00, 2 May 2019
Line 2:		Line 2:
	LRM supports 5 localization paths for sending files to be translated. They are:		LRM supports 5 localization paths for sending files to be translated. They are:

	*Local - Files are kept on the system LRM resides on. ~~Good~~ for debugging.		*Local - Files are kept on the system LRM resides on. This is good for debugging.
	*FTP - FTP/SFTP. ~~Typical~~ method of sending resource files to/from translation.		*FTP - FTP/SFTP. The typical method of sending resource files to/from translation.
	*API Based:		*API Based:
	**GlobalLink		**GlobalLink

Rdaly at 17:59, 2 May 2019

2019-05-02T17:59:58Z

← Older revision		Revision as of 17:59, 2 May 2019
Line 1:		Line 1:
			==Overview==
	LRM supports 5 localization paths for sending files to be translated. They are:		LRM supports 5 localization paths for sending files to be translated. They are: