Difference between revisions of "TradosEnterprise"

From Lingoport Wiki
Jump to: navigation, search
 
(6 intermediate revisions by the same user not shown)
Line 1: Line 1:
 
Trados Enterprise uses FTP in order to pass files back and forth with Localyzer. However, because the structure on the FTP site for Trados Enterprise is organized by locale-named directories, the configuration to move files back and forth requires first a local vendor, which is then used by two Jenkins jobs, TradosEnterpriseUpload and TradosEnterpriseDownload to move files back and forth using FTP.
  
Trados Enterprise uses FTP in order to pass files back and forth with Localyzer. However, because the structure on the FTP site for Trados Enterprise is organized by locale-named directories, the configuration to move files back and forth requires first a local vendor, which is then used by two Jenkins jobs, TradosEnterpriseUpload and TradosEnterpriseDownload to move files back and forth using FTP.
  +
  +
  +
===Install lftp===
  +
lftp is a Linux utility to transfer data and is used by two Jenkins jobs,
  +
* TradosEnterpriseUpload
  +
* TradosEnterpriseDownload
  +
  +
On Centos type system, as a user with 'sudo' priviledges, execute the following command:
  +
  +
sudo yum install lftp
  +
  +
To verify lftp is correctly installed, as the 'jenkins' user, type in this command and check it runs without errors:
  +
  +
lftp --version
  +
   
 
===Link Localyzer and Trados Enterprise===
  
===Link Localyzer and Trados Enterprise===
−
Firstly, configure a Local Vendor.
+
Configure a Local Vendor.
   
 
To begin working with Trados Enterprise, create or use the following directories on the Linux file system:
  
To begin working with Trados Enterprise, create or use the following directories on the Linux file system:
Line 31: Line 46:
 
<li>Choose <b>Group</b> or <b>Project</b>; if project, click <b>Local Vendor</b> and then select the <b>Local Vendor Name</b> from the list</li>
  
<li>Choose <b>Group</b> or <b>Project</b>; if project, click <b>Local Vendor</b> and then select the <b>Local Vendor Name</b> from the list</li>
 
<li>Save</li>
  
<li>Save</li>
  +
<li>Build (run) the Jenkins job</li>
 
</ul>
  
</ul>
 
</ol>
  
</ol>
Line 38: Line 54:
 
<li>Enable the <b>TradosEnterpriseUpload</b> Jenkins job.</li>
  
<li>Enable the <b>TradosEnterpriseUpload</b> Jenkins job.</li>
 
<li>Enable the <b>TradosEnterpriseDownload</b> Jenkins job.</li>
  
<li>Enable the <b>TradosEnterpriseDownload</b> Jenkins job.</li>
−
<li>Make sure the Jenkins job <b>TradosEnterpriseUpload</b> trigger <b>Build after other projects are built</b> after <b>DashboardPrepkit</b>.</li>
 +
<li>Make sure the Jenkins job <b>TradosEnterpriseUpload</b> trigger <code>Build after other projects are built</code> after <b>DashboardPrepkit</b>.</li>
−
<li>Modify the Jenkins job <b>LocalVendorDownload</b> and check <b>Build after other projects are built</b> and then in <b>Projects to watch</b>, type in <b>TradosEnterpriseDownload</b>.</li>
 +
<li>Modify the Jenkins job <b>LocalVendorDownload</b> and check <code>Build after other projects are built</code> and then in <b>Projects to watch</b>, type in <b>TradosEnterpriseDownload</b>.</li>
 
</ol>
  
</ol>
−  
−  
   
 
===Trados Enterprise Locale Mapping===
  
===Trados Enterprise Locale Mapping===
−
Configure '''config_trados_enterprise_locale_mapping.properties''' (which can be specified at the group or project config level).<br>
 +
Configure '''config_trados_enterprise_locale_mapping.properties''' which must be specified at the project config level.<br>
−
This file maps locales from LRM to Trados Enterprise. For example, LRM supports the language only locale '''fr''', which must be mapped to '''fr-FR''' for Trados Enterprise.
 +
This file maps locales from LRM to Trados Enterprise. For example, for a repository locale '''fr''', it must be mapped to '''fr-FR''' for Trados Enterprise. The '''fr-FR''' must be the name of the directory in the FTP endpoint TO_RWS and FROM_RWS
   
 
<pre>
  
<pre>
Line 70: Line 84:
 
</ul>
  
</ul>
 
<li>
  
<li>
  +
Set the FTP credentials in ~jenkins/.netrc, which must correspond to the <code>TRADOS_ENTERPRISE_FTP</code> value
−
Create an Trados Enterprise local vendor in Jenkins:
  
 
</li>
  
</li>
 
<ul>
  
<ul>
−
<li>Select '''Manage Jenkins->Configure System'''</li>
 +
<li>machine <FTP DNS></li>
  +
<li>login <user></li>
−
<li>Scroll down to the <b>LRM L10n Vendor Setup</b> section and select <b>Add Local Vendor</b></li>
  
−
<li>Provide a unique vendor name</li>
 +
<li>password <pwd></li>
−
<li>Select <b>Group</b> or <b>Project</b>; if group, select group name from drop down list</li>
  
−
<li>Configure Prep Kit Files Directory: <code>/var/lib/jenkins/translation/TradosEnterprise/to_translation</code></li>
  
−
<li>Configure Imported Files Directory:<code>/var/lib/jenkins/translation/TradosEnterprise/from_translation</code></li>
  
−
<li>Save</li>
  
−
</ul>
  
−
<li>
  
−
Configure your Jenkins job to use Trados Enterprise local vendor:
  
−
</li>
  
−
<ul>
  
−
<li>Select the Jenkins job you want to use Trados Enterprise</li>
  
−
<li>Click Configure</li>
  
−
<li>Scroll down to the <b>L10n Vendor</b> section of your LRM configuration</li>
  
−
<li>Choose <b>Group</b> or <b>Project</b>; if project, click <b>Local Vendor</b> and then select the <b>Local Vendor Name</b> from the list</li>
  
−
<li>Save</li>
  
 
</ul>
  
</ul>
 
</ol>
  
</ol>
−  
−  
−  
−
machine centralftp.sdl.com
  
−
login Lingoport_US
  
−
password WnM7Bz
  

Latest revision as of 22:30, 31 May 2022

Trados Enterprise uses FTP in order to pass files back and forth with Localyzer. However, because the structure on the FTP site for Trados Enterprise is organized by locale-named directories, the configuration to move files back and forth requires first a local vendor, which is then used by two Jenkins jobs, TradosEnterpriseUpload and TradosEnterpriseDownload to move files back and forth using FTP.


Install lftp

lftp is a Linux utility to transfer data and is used by two Jenkins jobs,

  • TradosEnterpriseUpload
  • TradosEnterpriseDownload

On Centos type system, as a user with 'sudo' priviledges, execute the following command: 

   sudo yum install lftp

To verify lftp is correctly installed, as the 'jenkins' user, type in this command and check it runs without errors: 

   lftp --version


Link Localyzer and Trados Enterprise

Configure a Local Vendor.

To begin working with Trados Enterprise, create or use the following directories on the Linux file system:

    • /var/lib/jenkins/translation/TradosEnterprise/to_translation
    • /var/lib/jenkins/translation/TradosEnterprise/from_translation
  1. Create an Trados Enterprise local vendor in Jenkins:
    • Select Manage Jenkins->Configure System
    • Scroll down to the LRM L10n Vendor Setup section and select Add Local Vendor
    • Provide a unique vendor name
    • Select Group or Project; if group, select group name from drop down list
    • Configure Prep Kit Files Directory: /var/lib/jenkins/translation/TradosEnterprise/to_translation
    • Configure Imported Files Directory:/var/lib/jenkins/translation/TradosEnterprise/from_translation
    • Save
  2. Configure your Jenkins job to use Trados Enterprise local vendor:
    • Select the Jenkins job you want to use Trados Enterprise
    • Click Configure
    • Scroll down to the L10n Vendor section of your LRM configuration
    • Choose Group or Project; if project, click Local Vendor and then select the Local Vendor Name from the list
    • Save
    • Build (run) the Jenkins job

Configure and Enable Trados Enterprise Jenkins Jobs

  1. Enable the TradosEnterpriseUpload Jenkins job.
  2. Enable the TradosEnterpriseDownload Jenkins job.
  3. Make sure the Jenkins job TradosEnterpriseUpload trigger Build after other projects are built after DashboardPrepkit.
  4. Modify the Jenkins job LocalVendorDownload and check Build after other projects are built and then in Projects to watch, type in TradosEnterpriseDownload.

Trados Enterprise Locale Mapping

Configure config_trados_enterprise_locale_mapping.properties which must be specified at the project config level.
This file maps locales from LRM to Trados Enterprise. For example, for a repository locale fr, it must be mapped to fr-FR for Trados Enterprise. The fr-FR must be the name of the directory in the FTP endpoint TO_RWS and FROM_RWS 

#
#Locale mapping language only repo locales <--> Trados Enterprise Locales 
aa=aa-DJ
ab=ab-GE
af=af-ZA
ak=ak-GH
am=am-ET
...

Configure FTP

  1. Set a Jenkins global variable:
    • The name of the Jenkins variable must be: TRADOS_ENTERPRISE_FTP
    • The value of the variable must be in the form: ftp://<user>@<FTP DNS>
  2. Set the FTP credentials in ~jenkins/.netrc, which must correspond to the TRADOS_ENTERPRISE_FTP value
    • machine <FTP DNS>
    • login <user>
    • password <pwd>
Retrieved from "http://wiki.lingoport.com/index.php?title=TradosEnterprise&oldid=96334"