General Data (GUI)

In this area, basic settings of the profile can be made and processing beyond the six main phases can be configured.

(1) The name of the profile.

(2) The group of the profile. See section Profiles.

(3) The document type (the input format) of the profile.

(4) Here you can activate the profile. Only an active and valid profile accepts data (unless you upload data manually). See also section Profile Suspensions.

(5) If this checkbox is set, the profile is listed in the Transport Manager. Note: This option can also be set in the profile overview via the context menu.

The checkbox can automatically be deselected after the transfer. This behaviour can be set with the following entry in configuration file ./etc/startup.xml.

(6) If option No mapping is used, phases 2-5 are deactivated (profile variables, for example, cannot be use in this case). In that case, the profile will only pass through the data.

Option Data routing, on the other hand, will still allow you to use phases 2-5 when input data cannot be parsed, like in the case of binary data. The binary data will be replaced by dummy data provided by the DummyPreParser. It provides the parser with a short line of text, which allows you to implement a logic with variables and function calls in phase 3, run database operations in phase 4 and call an Integration Unit in phase 5. In the Response Routes in phase 6, you can either use the mapping result or the binary input file as received. Such a profile usually uses the document type CSV. The automatically created source structure is a node with a contained field. If a source structure already exists, this node is additionally inserted at the top of the existing structure. Note: See also section Working with Purely Binary Input Data.