The From FTP Reader component connects with a FTP, FTPS, or SFTP server and retrieves files from a target directory for processing. These files are downloaded to a local folder and then either deleted from the server or moved to a designated folder on the server. The downloaded files are then read and pushed downstream for further processing in the same way the https://interfaceware.atlassian.net/wiki/x/AQDqsw processes files.
By default, this component polls every 60 seconds.
...
| Expand |
|---|
| title | STEP 1: Import the File Retriever From FTP component |
|---|
|
Using +COMPONENT, import the From FTP component. |
| Expand |
|---|
| title | STEP 2: Set up the component configurations |
|---|
|
 Fields marked with an asterisk * are required. Connection Configurations: Field | Description | Default Value |
|---|
Protocol * | Specifies the protocol you’ll be using. Supports: FTP, FTPS, or SFTP | FTP
| Server * | The server you will be connecting with | - | Port * | The port to use | - | Username * | The remote user to login as. This account will need permissions to read, delete, and/or move files to the specified FTPDirectory | - | Password | The password to authenticate with. | - | Certificate | The name of your certificate file, if in use. By default, this should be a PEM certificate. The default configurations can be changed by modifying the net.[protocol].init function directly in the script. See Adapting the Component. This configuration is only applicable for FTP and FTPS. | - | PrivateKey | The name of your private key file, if in use. By default, this should be a PEM certificate and not be password-locked. The default configurations can be changed by modifying the net.[protocol].init function directly in the script. See Adapting the Component. | - | RetryCount | The number of times to retry the connection if it drops. Default is set to 3 attempts. | 3
|
FTP Workflow Configurations: Field | Description | Default Value |
|---|
FTPDirectory * | The source directory on the FTP server you’ll be retrieving files from | FTP
| FileType | The types of files you wish to retrieve (e.g. txt). You can also specify multiple files (e.g. txt,hl7) or all file types (e.g. *). | - | MoveFTPProcessedFiles | Set to true if you wish to move processed files (i.e. files that have already been downloaded to the local server) to a folder on the FTP server designated by FTPProcessedDirectory. If false, processed files will be deleted. | true
| FTPProcessedDirectory | The directory on the FTP server that processed files will be moved into. You will need to create this folder if you choose to use this workflow. | - |
Local File Workflow Configurations: Field | Description | Default Value |
|---|
LocalDirectory * | The local directory that the files will be downloaded to from the FTP server. Files in this directory will then be picked up for processing. | - | MoveProcessedFiles | Set to true if you wish to move processed files to a local folder designated by ProcessedDirectory. If false, processed files will be deleted. | true
| ProcessedDirectory | The local directory that processed files will be moved into. You will need to create this folder if you choose to use this workflow. | - | MinimumFileAge * | The time to wait in seconds after last modified date before processing. | 0
| IgnoreSegments * | Specifies whether to remove identified segments when processing file. Default segments to ignore include: FHS, BHS, FTS, BTS. This can be modified in config.lua. See Adapting the Component. | false
| InputFileEncoding * | The encoding used in the output file. If left blank, encoding will be updated to the default according to OS. See supported encodings below. Supported File Encodings | Western (Windows-1252) for Windows
Western (ISO-8859-1) for Linux/Mac OS
|
|
| Expand |
|---|
| title | STEP 3: Start the component and view the processed files' contents in the logs |
|---|
|
Once the component has been started, it will download files that match the provided parameters to the specified local directory. It will then process the downloaded files and push their contents to the component’s queue for further processing. Open the component’s logs to see the queued files and verify that the contents are being read as expected. |
| Expand |
|---|
|
|
Encoding Name | Code |
|---|
Chinese (Big 5 HKSCS) | BIG5-HKSCS |
Chinese (GB 18030) | GB18030 |
Chinese (GB 2312) | GB2312 |
Chinese (GBK) | GBK |
Japanese (ISO-2022-JP) | ISO-2022-JP |
Korean (ISO-2022-KR) | ISO-2022-KR |
Western (ISO-8859-1) | ISO-8859-1 |
Central European (ISO-8859-2) | ISO-8859-2 |
South European (ISO-8859-3) | ISO-8859-3 |
Central European (ISO-8859-4) | ISO-8859-4 |
Cyrillic (ISO-8859-5) | ISO-8859-5 |
Arabic (ISO-8859-6) | ISO-8859-6 |
Greek (ISO-8859-7) | ISO-8859-7 |
Hebrew (ISO-8859-8) | ISO-8859-8 |
Turkish (ISO-8859-9) | ISO-8859-9 |
Western (Windows-1252) | Windows-1252 |
Chinese (Big 5) | big5 |
Japanese (EUC-JP) | eucJP |
Japanese (Shift JIS) | sjis |
8-Bit Unicode (UTF-8) | UTF-8
Adapting the Component
There are a few ways you can adapt and expand this component for more complex workflows:
...
| Expand |
|---|
| title | Add more file retrieval conditions |
|---|
|
Currently, the component retrieves files from the FTP server based on two conditions: The file is retrievable The file extension matches the provided extension (e.g. txt)
This is typically sufficient for most cases, but if additional conditions are needed, they can be added to the FTPmatchRules function in FTP/FTPmatchRules.lua:  |
| Expand |
|---|
| title | Customize the ignored segments or message delimiter via config.lua |
|---|
|
Ignored segments: the ignored segments list can be modified to remove additional segments from a message when IgnoredSegments = true Replace message delimiter: replaces the delimited at the end of the message with ‘\n’
|