Configuring SDL/Nexus-FTP Translation Options

A system administrator must specify settings in the Astoria application document to support using SDL/Nexus-FTP translation management services for either an FTP or SFTP host.

An SFTP host must be validated before it can be used for Translations. See Configuring Remote SFTP Hosts.

Note: Consult with your vendor's account representative for details about these settings.
  1. In the Workbench, navigate to and select the application document, located in the Administration cabinet.
  2. Right-click the document and select File > Edit.
    The application document webform opens for editing.
  3. Scroll down in the webform to the Translation Package destination field and select SDL/Nexus-FTP.
  4. Scroll down to the SDL options and enter these fields:
    All fields are mandatory, unless indicated optional.
    Option Description Comments/Sample Value
    SDL FTP URL The URL to the SDL/Nexus FTP server. Mandatory
    The leading protocol indicates whether the host is an FTP or SFTP host. If no protocol is present, the URL indicates an FTP host. For example:
    • astoriaondemand.com indicates an FTP host.
    • ftp://astoriaondemand.com indicates an FTP host.
    • sftp://astoriaondemand.com indicates an SFTP host.
    SDL FTP Username The username to login to the SDL/Nexus FTP server. Mandatory
    SDL FTP Password The password to login to the SDL/Nexus FTP server. Mandatory
    SDL FTP Base Directory for Export The base directory where Astoria deposits pre-translated files. Mandatory

    For example, /Astoria/For_Translation.

    SDL FTP Base Directory for Upload The base directory for where Astoria expects to retrieve post-translated files. Mandatory

    For example, /Astoria/From_Translation.

    SDL Configurations A repeat group listing the SDL Configurations. Values in this field specify sub-directories within SDL FTP Base Directory for Export and SDL FTP Base Directory for Upload for depositing and retrieving translation packages. Click New, and enter an SDL Configuration Name. Add additional configuration names as needed. Optional

    Each entry is an alphanumeric value limited to 50 characters.

    Creates the Translation Configuration selection list in the Start Translations dialog.

    Sample value: Group_1. Specifies /Astoria/For_Translation/Group_1 when combined with a value for SDL FTP Base Directory for Export.

    SDL Configuration Name The name of each configuration. The values you enter here populate the Translation Configurations list in the Start Translation dialog. The SDL/Nexus-FTP service does not use a Configuration GUID, so you can leave that field empty for each configuration you define. If specified, it goes into the
    Vendors Not used.  
    SDL Locales A repeat group listing the SDL Locales. Values in this field specify sub-directories within SDL Configurations for depositing and retrieving translation packages. Click New, and enter an SDL Locale Name. Add additional locale names as needed.

    Each entry is an alphanumeric value limited to 50 characters.

    Sample value: es_ES. Specifies /Astoria/For_Translation/Group_1/es_ES when combined with a value for SDL FTP Base Directory for Export and the value for SDL Configurations.

    Locale

    A repeat group listing the SDL Locales. Click New, and select a Locale from the list. Add additional locales as needed.

    The list contains the language/locale information for the target language translation cabinets you have created in the repository.
    Folder Name The name of the each Locale subdirectory. Data values correspond to the SDLX language/locale specification.
  5. In the SDL Configurations area, click New, and enter an SDL Configuration Name.
    A configuration identifies a subdirectory under the FTP Base Directory on the SDL/Nexus server. You can define multiple configurations. For each configuration there is one subdirectory under the FTP Base Directory. The values you enter here populate the Translation Configurations list in the Start Translation dialog.
    Note: The SDL/Nexus-FTP service does not use a Configuration GUID, so you can leave that field empty for each configuration you define.
  6. Scroll to the top (or bottom) of the webform and click Checkin Document.
  7. When prompted, provide a checkin note indicating what was changed in the webform, then click OK.
The configuration is stored in the repository and the connector is activated to manage SDL/Nexus-FTP translations.