4.2.4.5. FTP Server Gateway In
With a Ftp Server In Gateway, incoming messages are received on a Babelway specific ftp server and processed as soon as they arrive.
The specific settings are:
Babelway ftp server is the hostname for the ftp server where the files will be fetched. |
|
Login or username to access your account on Babelway ftp server. This username must be unique as it is linked to a specific directory on the ftp server. |
|
Password associated with the username. |
|
The directory on the ftp server on which you wil have to put your files so that they are processed by this gateway. |
After channel deployment, your ftp server will be available to send messages. You can access this ftp server using any ftp client software set up with the previous account settings.
The files sent by FTP commands STOR, STOU, APPE are processed as soon as the command is completed. There is no need to use a temporary file name suffix or other precautions. The FTP server does not support FTP commands RMD, MKD, RNTO.
Babelway FTP gateways are supporting FTP and FTPS (Explicit mode) on port 21. It also support FTPS (Implicit mode) on port 990.
Note:
- The ports used for the FTP connections in Babelway are: (FTP, FTPs explicit : 20020-21020, FTPs implicit : 22021-23020).
- There is no need to use temporary file name suffix when sending files to "Gateway In" of type FTP server, There is no risk of collision because our FTP server does not use a filesystem. Instead, the data are directly sent to the Babelway messaging engine when the upload command is completed.
- If there is a file name provided in the "Message In" or "Message Out" which contain ~ tilde character, All browser based on Chromium will replace the ~ tilde character by the _ underscore character when you try to download the file from the Babelway interface, For more details you can check this link https://bugs.chromium.org/p/chromium/issues/detail?id=479419
- The maximum file size accepted by this gateway is 100/250 MB.