Configuring the FTP-ZIP-SRC Translation Package Destination

A system administrator must specify settings in the Astoria application document to support using an FTP-ZIP-SRC server for the Translation Package destination.

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 FTP-ZIP-SRC.
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
   SDL FTP Username	The username to login to the SDL/Nexus FTP server.	Mandatory This value also becomes the Job Creator value in the Job Information File.
   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 Sample value: /Astoria/For_Translation.
   SDL FTP Base Directory for Upload	The base directory where Astoria expects to retrieve post-translated files.	Mandatory Sample value: /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/GUID Pair	The name of each configuration and its unique GUID. Select an SDL Configuration name from the SDL Configurations list, and enter the Configuration GUID.	Optional The GUID is a 36-character string and must be in the format AAAAAAAA-BBBB-CCCC-DDDD-EEEEEEEEEEEE, including the dash characters. There is a one-to-one relationship between the SDL Configuration Name and its Configuration GUID. It is an error to omit the Configuration GUID in the application document. When the user selects a Translation Configuration value on the Start Translation dialog, the Configuration GUID value is placed into the read-only data field and into the jobdata.xml file that is included in the packages created by the SDL/Nexus-SJP connector.
   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.
   Vendors	A repeat group listing the names of the vendors your organization uses.	Optional Each entry is an alphanumeric value limited to 50 characters. When the user selects a Vendor value on the Start Translation dialog, the vendor name is placed in the Job Information File. Note: Astoria supplies the value <none> as the first item in the vendor list, and the list is sorted alphabetically thereafter. The value <none> implies an empty value for the Vendor parameter in the Job Information File.
   Default Organization Name	The name of the organization initiating the translation operation.	Mandatory This is typically the name of your company or organization unit. The name is limited to 50 alphanumeric characters. When the user starts a translation job, the Default Organization Name value is placed in the Start Translation dialogs Organization field. The user may override the default name, but the field cannot be left blank.

5. Note: The FTP-ZIP-SRC connector does not use a Configuration GUID, so you can leave that field empty for each configuration you define. If specified, it goes into the jobdata.xml file that is included in the packages created by the FTP-ZIP-SRC connector.
   
   
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.