Ftp/Ftps receive channel
The FTP reception channel allows the connection of an FTP directory to a remote host. Messages are placed into the message basket (inbound) by the host: port/directory specified in the communication channel.
Note: FTPS1) is supported by the use or configuration of SSL.
Properties
| Properties | |
|---|---|
| Name | Description |
| Name | The name of the channel |
| Channel type name | The Type of the channel |
| Message direction | For receive channels the direction of the received message (but require also for send channels) |
| Message box | The message box |
| Public | True if the channel should be visible in the sub node |
| Host | The host to connect with |
| Port | The port to connect to the host. The default port for ftp is 21. |
| SSL handling | How to encrypt the connection using SSL. Mode (None, Offer (=Automatic), Explicit, Implicit). In implicit mode, communication is immediately started via an encrypted channel, via another port. More often, the explicit mode is used. The connection is established via the non-encrypted standard ftp port and after the connection is established, but before authentication, it is switched to the encrypted mode. |
| Password | The password to be used for the user |
| Username | The user to login on the ftp server |
| Input path | Path on the ftp server, the files should be get from |
| Input file mask | File mask to geht specific files |
| Action after receive file | Specifies whether the file should remain, be deleted or moved after retrieval. Whether the option to delete or move is supported depends on the FTP server used. |
| Move to path | Directory to which the file is to be moved in the FileHandling method Move or MoveWithTimeStamp. |
| Change logs | The changes to the element are logged. The logging is activated in the System settings, which is possible if a versioning license is available. |
| Properties (advanced) | |
| Name | Description |
| Sender validation | How the sender address should be validated |
| Default sender | The default sender |
| Recipient validation | How the recipient address should be validated |
| Default recipient | The default recipient |
| Immediate retries | Retries, used by send channels. For some receive channels, the number of pickup attempts. |
| Auto uncompress | Check if receipt data are compressed and then uncompress them |
| FTP transfer mode | Setting the transmission mode. Mode (Auto, Text, Binary) can be selected in the corresponding look main table. |
| Send 'PROT P' | If a connection is implicitly encrypted via SSL, the “Prot P”command should be sent to the server → RFC 4217 |
| Use long dir list | If this option is not selected, the FTP server will use the simple directory list to retrieve files from the FTP server. This means that directories cannot be distinguished from files, but this is irrelevant for a corresponding file mask. If this option is selected, the detailed directory display is used, but on a few ftp-servers it leads to results that cannot be evaluated. But there is no problem with the recognition of the files. |
| SSL client cert PFX file | The client's private certificate (for client side authentication) |
| SSL client cert PFX password | That to the above mentioned. Certificate associated password. |
| Sort order of read files | The sort order of the read files |
| Passive mode | The server can be placed in “passive” state to listen for data connection, rather than initiate a data connection on the data port. (RFC 959) |
| Managed Security | The SSL/TLS parameters to be used are negotiated with the server. E.g. whether TLS 1.1 or 1.2, which SHA, AES, etc. are used. |
| Only newer than | Use this to get files only once by file time. Insert the name of the default system partner variable of type text. This variable will be use to set and get the last call date (minus 5 min.). The channel will only get files changed/created newer than this date and changed/created 5 minutes before. |
| Log all | Complete output of the executed commands and results in the log (including passwords used). |
1)
FTP protocol as proposed in RFC 2228 that protects FTP data as it travels over the network using SSL encryption.