FTP output connector

This connector transfers files to an FTP server. TCP/IP profile and Authentication profile resources are used to specify the connection settings and logon credentials. In the TCP/IP profile resource you can also select to use a secure channel between the connector and FTP server.

Comments

If a Project has several connectors (FTP input or FTP output) per user account, the number of concurrent connections specified on the FTP server must be equal to, or more than, the number of FTP connectors. For example, if a Project has one FTP input connector and one FTP output connector that use the same user account, the number of concurrent connections specified on the FTP server must be at least 2.

 

Setting	Description
TCP/IP Profile	The TCP/IP profile resource that contains the connection and recovery settings for the channel between the FTP connector and FTP server. See TCP/IP profiles in the Profile configurations documentation.
Authentication Profile	The Authentication profile resource that contains the logon credentials to the FTP server. See Authentication profiles in the Profile configurations documentation.
Remote directory	The directory to be accessed on the FTP server. If you leave this blank, the root directory will be set as remote directory. The FTP server software determines whether to use slash or back-slash. Example: /invoices/pdfout/area2
Create Directories	Select whether to create the Remote directory if it does not exist. • Yes – If any of the directories in the remote path does not exist, they are created. • No – If any of the directories in the remote path does not exist, the file is put in the undeliverables folder.
File	The file to write the output to, and to upload to the FTP server. You can use variables, but only in the runtime connector settings. Example: Script before process: $file = getdate() + "_" + $invo + ".pdf"; Runtime FTP connector settings: $file
Tmp File	A temporary filename for the file to upload. You must use a file name pattern different from the filename pattern used by the receiving application. This prevents the receiving application from downloading the file before the upload is completed. When the upload is completed, the file is renamed to the name specified in File above, and the receiving application can download the file. If external files are uploaded (see External files below) all files will be uploaded, one by one, with the same temporary file name. After a successful upload, each file will be renamed to its final file name.
External files	Enables upload of external files, together with the generated output file, to the Remote directory specified. You can use an absolute path to the external file, or a path relative to the working directory of the StreamServer application. You can add several external files if you separate the file paths with semicolon. For example: <path1>;<path2>;<path3>
Data transfer mode	Specifies the transfer mode for the data. • Passive – use passive mode. This mode is used when communicating through firewalls. It opens a control connection to the FTP server, tells the FTP server to expect a control connection and a second connection. Then it opens the data connection to the FTP server on a randomly chosen high-numbered port. This works with most firewalls unless the firewall restricts outgoing connections on high-numbered ports. • Active – use active mode.
File transfer type	Specifies the transfer mode for the files. • ASCII – use ASCII, Type A, transfer method. Control and formatting data is converted to local equivalents. • Binary – use FTP Image, Type I, transfer method. The file is transferred without any changes.

Runtime specific connector settings

The <Default> options for Passive Mode and Transfer Mode means the Platform settings will be used.