Difference between revisions of "XTM"
(→XTM Configuration) |
|||
Line 18: | Line 18: | ||
===XTM Configuration=== |
===XTM Configuration=== |
||
+ | Configure the XTM settings in the file '''<code>config_xtm_vendor.properties</code>''', located in either the group or project config directory. |
||
− | The file information that is needed to upload the files to be translated as well as retrieve translated files is in the : |
||
<pre> |
<pre> |
||
+ | # |
||
− | #Lingotek Attributes |
||
− | #Contains |
+ | # Contains configuration for xtm |
+ | # |
||
− | lingotek.api.hosturl=https://cms.lingotek.com |
||
+ | # Note: this file should be placed in ~/Lingoport_Data/L10nStreamlining/<group>/config |
||
+ | # or ~/Lingoport_Data/L10nStreamlining/<group>/projects/<project>/config |
||
+ | # |
||
+ | # Run the following command to get the token: |
||
+ | # java -jar lingoport-xtm-cli.jar --get-token -s <server> -c <client> -u <userId> -p <password> |
||
+ | # |
||
+ | # Run the following command to get the customerId: |
||
+ | # java -jar lingoport-xtm-cli.jar --get-customer-id -s <server> -t <token> -cn <customerName> |
||
+ | # |
||
+ | # Run the following command to get the templateId (if using a template): |
||
+ | # java -jar lingoport-xtm-cli.jar --get-template-id -s <server> -t <token> -ci <customerid> -tn <templatename> |
||
+ | # |
||
+ | # Run the following command to get the workflowId (if using a workflow id): |
||
+ | # java -jar lingoport-xtm-cli.jar --get-workflow-id -s <server> -t <token> -wn <workflowname> |
||
+ | # |
||
+ | # Required to configure either a workflow name, workflow id, or template id |
||
+ | # |
||
+ | # the following are required |
||
− | #Contains the ids for community, workflow and access token |
||
+ | xtm.api.hostURL=https://wstest2.xtm-intl.com |
||
− | lingotek.api.id.access.token= |
||
− | + | xtm.api.token= |
|
− | + | xtm.api.id.customer= |
|
+ | xtm.api.source.locale=en_US |
||
+ | # one of the following must be configured |
||
− | #Example callbackURL - replace job name (lingotek) with actual Jenkins job name |
||
+ | xtm.api.name.workflow= |
||
− | lingotek.api.callbackurl=http://jenkins.company.com:8080/buildByToken/buildWithParameters?job=LingotekCallback&token=LINGOSQUARE& |
||
+ | xtm.api.id.workflow= |
||
+ | xtm.api.id.template= |
||
+ | # configure proper URL for your company |
||
− | #{0} is the access.token |
||
+ | xtm.api.callbackURL=http://jenkins.company.com:8080/jenkins/buildByToken/buildWithParameters/build?job=XTMCallback&token=ZISXTMTOKEN |
||
− | lingotek.api.bearer=Bearer {0} |
||
</pre> |
</pre> |
||
Revision as of 18:34, 27 August 2019
Link LRM and XTM
Configure <HOME>/Lingoport_Data/L10nStreamlining/<group name>/config/config_l10n_vendor.properties:
- uncomment
l10n.vendor=local
- configure
local.out.absolute.path
- configure
local.in.absolute.path
Configure <HOME>/Lingoport_Data/L10nStreamlining/config/config_xtm_tofrom.properties:
- configure
xtm.to.translation.dir
- configure
xtm.from.translation.dir
XTM Configuration
Configure the XTM settings in the file config_xtm_vendor.properties
, located in either the group or project config directory.
# # Contains configuration for xtm # # Note: this file should be placed in ~/Lingoport_Data/L10nStreamlining/<group>/config # or ~/Lingoport_Data/L10nStreamlining/<group>/projects/<project>/config # # Run the following command to get the token: # java -jar lingoport-xtm-cli.jar --get-token -s <server> -c <client> -u <userId> -p <password> # # Run the following command to get the customerId: # java -jar lingoport-xtm-cli.jar --get-customer-id -s <server> -t <token> -cn <customerName> # # Run the following command to get the templateId (if using a template): # java -jar lingoport-xtm-cli.jar --get-template-id -s <server> -t <token> -ci <customerid> -tn <templatename> # # Run the following command to get the workflowId (if using a workflow id): # java -jar lingoport-xtm-cli.jar --get-workflow-id -s <server> -t <token> -wn <workflowname> # # Required to configure either a workflow name, workflow id, or template id # # the following are required xtm.api.hostURL=https://wstest2.xtm-intl.com xtm.api.token= xtm.api.id.customer= xtm.api.source.locale=en_US # one of the following must be configured xtm.api.name.workflow= xtm.api.id.workflow= xtm.api.id.template= # configure proper URL for your company xtm.api.callbackURL=http://jenkins.company.com:8080/jenkins/buildByToken/buildWithParameters/build?job=XTMCallback&token=ZISXTMTOKEN
XTM Locale Mapping
XTM 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 XTM locale should be entered into config_xtm_locale_mapping.properties
file if it doesn't already exist.
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 <HOME>/lingoport/lrm-server-x.y/deploy/templates/dir_structure/group/config
folder.
# #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 ...