Fileset FTP protocol
Use the Fileset FTP protocol driver for file-based interfaces. It handles groups (directories) of files, locally or remotely by FTP. It is capable of reading and writing messages contained in files, both locally and remotely, using FTP (File Transfer Protocol).
The libcurl third-party package is integrated into the system for secure implementation. This is the name of the underlying library that is used to implement cURL.
The Fileset FTP protocol has a Scheduling pane that contains the controls for scheduling:
and .The driver can process files containing multiple messages, saving state to continue at the correct point across stop/start boundaries. After all messages within the file or files are read by the engine, the source file is deleted.
- On input, supply a Tcl Procedure Stream (TPS) to parse directory listings and determine file processing order. Provide another TPS that determines which files are removed.
- On output, the driver relies on message metadata to determine the output file name.
For FTP operations, the driver assumes servers are RFC 959 (File Transfer Protocol) compliant.
Pre-configuration
Configuring this driver requires some knowledge of the remote FTP server with which it connects.
You must know:
- What user/password/account log-in information is required.
- The kind of data (ASCII or binary) to transfer.
- Whether the server supports the appropriate type.
DRIVERCTL
metadata with
the Inbound file name as a keyed list entry {FILENAME xxx}
. - For inbound, you must know how to
generate a file list and how to parse that list so your TPS can return an
ordered list. Most servers support the NLST and
LIST commands.
- The NLST command returns only the list of files.
- The LIST command produces a long listing; the formatting and data available depend heavily on the FTP server and the operating system it is running under.
Some servers permit options to be specified at the end of the NLST/LIST command line.
- For outbound, determine whether the
FTP server supports the APPE command. If it
does not, then avoid using the
OBAPPEND
flag so that the driver generates only STOR commands.
Information is available on the configurable parameters. See: