Phase 5
Typically, an Integration Unit is used to bring the target tree data into a particular format, such as EDIFACT or XML. There are a few exceptions, but this is noted directly in the documentation of the corresponding Integration Unit. In addition, the document type "Custom Class" allows you to hand the input file directly to the Integration Unit.
It is also possible to transfer the output data to third-party systems here, although phase 6 is actually intended for this purpose.
Instead of constant values, you can also use variables with the syntax "@variable@" in parameter fields. If you use a variable that is not defined in the profile, the expression "@variable@" is not resolved to the value of the variable, but is used as it is.
Field values cannot be used directly. You have to store them in variables first.
Settings
(1) Integration Unit: The selected Integration Unit. You can access the documentation via the question mark icon.
(2) Select variable: The execution of an Integration Unit can be made dependent on a variable of type "Boolean". The Integration Unit is executed if the variable has the value "true". Note: In principle, a variable of type String can also be used. In that case, an implicit type conversion takes place.
(3) Name, Value: The parameters of the Integration Unit. Details can be found in the documentation of the Integration Unit.
(4) Postexecution: Selection of a postexecution class. You can access the documentation via the question mark icon.
(5) Config file: The path to the configuration file of the postexecution class (if necessary). Sometimes you need to enter a direct configuration string instead, but this will be documented in the respective class.
(6) Encoding of IU data: The encoding of the output data of the postexecution class.
(7) Refresh IU parameters: If you are using an Integration Unit in an older profile, newer versions of the Integration Unit may have new parameters added. These can be updated manually with this button. Important note: Newly added parameters are set with their respective default values. That could lead to a different behaviour. Please always check the updated parameters so that no unwanted effects occur.
Where does the Integration Unit get its data from?
Most Integration Units get their data from the target structure. There are a few exceptions, but this is noted directly in the documentation of the corresponding Integration Unit. In addition, the document type "Custom Class" allows you to hand the input file directly to the Integration Unit.
Accessing output data of the Integration Unit in the Response
For a Response to be able to access the data created by an Integration Unit, the "Content" has to be set to "Content of IU".
In general, please note that for binary formats, such as PDF and Excel, you always have to use the encoding "ISO-8859-1" in Responses to ensure that the formats remain intact.
Postexecution in phase 5
After the execution of the Integration Unit, a postexecution class can be executed. If you have multiple Responses that all use the same postexecuter, you only need to run the postexecuter once if it is called in phase 5, instead of running it in each Response.