Mapping test
You can test your mapping while you are creating your profile. You simply select a test file and check the mapping results. Note: The test can be opened in a new window via the icon on the right in the submenu.
SQL functions in phase 3 will be executed, but the SQL statements of phase 4 (SQL nodes) will not be executed (but can be logged). The Integration Unit can be executed. Responses will not be executed.
The mapping settings can be checked here as well. If you check without warnings, nothing is displayed if there are no errors. If you check with warnings, warnings are displayed if there are no errors. If there are errors, errors and warnings will be displayed for both options.
You can also restart the profile.
Select test file
(1) List below: Here you will find a list of available test files. You can simply drag and drop new test files. If you are using Input Agent DB, you can use option "Execute SQL and save result" with a right-click, which allows you to specify the number of lines that are read from the database and then saved as a test file. If you do not have a test file available, you can use option (2). Note: If the profile has the document type EDIFACT and you have an EDIFACT test file, you can use the context menu to create an analysis report of that file.
(2) Backups: Backup files from a previous job of this profile can also be selected for testing. Important note: System variables of the affected job as well as variables with prefix MSG_CALL_ will be available. This is helpful if the job was triggered from the outside or if it received data via Message. Please note that the variables, e.g. the system variable VAR_TIMESTAMP, always get the value of the original job.
(3) Select file: If you mark one of the files (1), you can start the test.
Test mapping
(4) Target tree: The target structure filled with data (the target tree). For the data history, also see tab "Log" and tab "Lists/Maps/Variables" (per record).
(5) Settings: See section "Settings (Mapping Test)".
(6) IU: The output of the Integration Unit is displayed here if this was set in (5). For larger amounts of data, the output is appended at the end of the test log.
(7) Lists/Maps/Variables: Here you can see the contents of lists, maps and variables.
(8) Subprofile calls: Here data of called subprofiles is displayed (per record). See section Profile in source structure (sub profile).
(9) Snapshot: See function create snapshot().
(10) Replacement values for functions: See section "Replacement values for functions".
Settings (mapping test)
|
Do not create log |
Here you can set whether you want to log for the test and for which phases. |
|
Perform min/max checks |
If this option is set, the entries of the source structure properties "Minimum", "Maximum" and "Mandatory field" for fields of the target tree are checked during the execution of the mapping test. |
|
Ignore function 'log user error' |
Any existing functions log user error(a,b,[c]) are ignored. |
|
Hide fields without values |
Fields that have no value are not displayed. |
|
Show calculation fields |
Fields marked as calculation fields appear in the output. |
|
Remove SQL nodes |
Nodes in the target tree whose attribute "Only for SQL" has the value Yes are excluded from the target tree. |
|
Do not sort |
There is no sorting of the target tree nodes using the attributes Sort field and Sorting. |
|
Use replacement values for functions |
See section "Replacement Values for Functions". |
|
Show source structure |
If the source structure has been filled with data, it can be removed by removing the tick. |
|
Log phase 2/3/4 |
Self-explanatory. |
|
Max. file size |
The maximum allowed size of the test file. |
|
Max. elements in structure |
The maximum number of elements displayed in the structure in the test. |
|
Max. processing time |
The maximum processing time of the mapping test can be set here. If you use the value "Profile setting", the value "Max. processing time" under "Main settings → Backup/Limits" is used. If the maximum processing time is exceeded, the test is aborted. Note: If the function wait() is used in the profile with a waiting time greater than the maximum processing time, the test will still run for the entire wait time. |
|
Execute IU |
The Integration Unit (if it generates text) is also executed in the test. The output of the Integration Unit is displayed in a separate tab or added to the end of the test log, for larger data sets. The options Enter output channels for each record and Incorporate IU are ignored. |
Replacement values for function
If functions use external data sources like databases or configuration files on shares, it is possible to supply those functions with a "replacement value" (11) for a mapping test. If, for example, a database were not reachable, a test would otherwise run into an error if a select statement was run on that database.
As a prerequisite, however, you must have set the option "Use replacement values for functions" in "Settings" (5).