Template (destination ETL/ELT)

Files such as XML or JSON can be generated dynamically here (Velocity).

(1) The path and name of the destination file to be created. Paths below the installation directory of the Integration Server can be specified relatively with ./ Note: Variables, see (3), and placeholders, see tooltip, can be used.

(2) Displays the destination file.

(3) Selection of ETL/ELT variables.

(4) Select XML or JSON.

(5) The replacement value for destination fields without value.

(6) The prefix text is generated once per task.

(7) This area is generated per row. ETL/ELT fields and ETL/ELT variables can be used. Velocity syntax is allowed. Note : Each time (6), (7) and (8) are executed, an empty line is placed in front of the generated text in the destination file.

(8) The suffix text is generated once per task. Note : You cannot use custom ETL/ELT fields from this task (in which the template destination data is defined). However, it is possible to use custom ETL/ELT fields from higher-level tasks or ETL/ELT variables.

(9) If you are not using any Velocity engine functions, you can deactivate this option (faster processing).