Settings

(1) File name with absolute path: The path and name of the source file. Paths below the installation directory of the Integration Server can be specified relatively with "./". Note: You can use variables, see (3), and placeholders, see tooltip.

You can also specify a URL. Example: https://example.com/myfile.json

You can also specify file archives (ZIP, TAR, RAR) with multiple files if (10) is set. The task is then executed for each file in the archive (implicit loop).

(2) Icon right of (1): Displays the source file.

(3) Icon right of (2): Selection of ETL/ELT variables.

(4) Delete file after successful finish: The source file is deleted after processing. Note: Does not work if the file name in (1) is dynamically generated (e.g. with variables or placeholders).

(5) JSONPath term: The JSONPath expression. See section Test JSONPath. The elements found are the 'rows'. Important note: The subtree read in via (5) is available internally in memory, i.e. further JSONPath expressions can be applied to it in the destination data. Simple expressions are automatically available there as ETL/ELT fields (leaf nodes can be addressed with $jnode) . If you want to use more complicated expressions, please create custom ETL/ELT fields.

(6) Icon right of (5): Extracts the names of the ETL/ELT source fields (the subelements of the elements found by the JSONPath expression).

(7) Icon right of (6): Selection of ETL/ELT variables.

(8) Test query/settings: See section Test JSONPath.

(9) Miscellaneous ETL driver settings: This is an expert setting (Scriptella) and can be ignored.

(10) Data comes in compressed: See (1).