JSON (source ETL/ELT)

images/download/attachments/131696358/1443-version-5-modificationdate-1709113368231-api-v2.png


(1) 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) Displays the source file.

(3) Selection of ETL/ELT variables.

(4) The source file is deleted after processing.

(5) 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) Extracts the names of the ETL/ELT source fields (the subelements of the elements found by the JSONPath expression).

(7) Selection of ETL/ELT variables.

(8) See section Test JSONPath.

(9) This is an expert setting (Scriptella) and can be ignored.

(10) See (1).