General control elements
Filter fields in tables
In all tables, at various places in the GUI (here, for example, in the log overview), filter fields (8) are available for columns.
You can enter search terms in these filter fields. As a result, only rows that contain the search term as a substring in this column are displayed.
The search term can be negated with a preceding exclamation mark "!", e.g. " !searchterm" . As a result, only rows that do not contain the search term as a substring in this column are displayed.
Exceptions
Column "Duration" (at various places in the GUI, e.g. in the log overview). |
There, only given values can be selected. In addition, a specific seconds value can be specified, e.g. " 3" , or optionally an interval, e.g. " 2-4" . |
Column "Name" in the profile overview. |
See section Profile Overview. |
Inserting variables and constants
Next to input fields, you will often find button "%". It allows you to insert variables and constants defined in the profile.
Allowed values in function parameters
When configuring functions (in the target structure in phase 3), you will often have the possibility to choose from a list of allowed values for function parameters (e.g. usable encodings or MIME types, available database aliases, certificates, channels, etc.). A useful feature that you should keep in mind. First click on the three dots on the right of the parameter fields (1), then choose "Paste" (2), and then select the desired value under "Allowed values" (3).
Icons in mappings
The following icons are used in the source and target structure in phase 3.
|
Source structure node/Target structure node active, without path . |
|
Source structure node/Target structure node inactive, without path . |
|
Source structure node/Target structure node active, with path . |
|
Source structure node/Target structure node inactive, with path . |
|
A function on a node and field of the target structure. |
|
|
|
An iteration node. |
|
|
|
Node attribute "Minimum>0". |
|
Node attribute "Maximum=1". |
|
Field mapped. |
|
Field not mapped. |
|
Match code on a node of the source structure. |
|
Represents a source structure field with set attribute "New record if value changes". |
Saving and caching profiles
(1) Create intermediate version: This creates an intermediate state of the profile (2). The current profile state is stored internally but not 'published', i.e. the profile is not yet saved. Note: An intermediate version of a profile can be recognised in the profile overview in column "Intermediate version". You will also see a corresponding icon in the context menu of the profile entry.
(2) This can be used to restore the intermediate state. If an intermediate state (2) is available and the server or browser crashes or the session is invalid and the profile is edited again, a dialogue appears asking whether the intermediate status should be used.
(3) Save: The profile is actually saved with this button. The intermediate state (2) is then automatically deleted.
(8) Variables: You can define variables and constants in another dialogue.
Backup of profiles
Via "Save & backup & close" (4), first a backup of the profile is created (unsaved changes are not adopted) and then the profile is saved (with the changes). If the profile is a template that was changed in phases 1, 3-6, another dialogue appears in which you can select which profiles derived from the template are to be synchronised accordingly. Note: In the file system you will find the profile backups under ./datawizard/settings/-1.
Via (5) you can enter a change note for the saved changes. You will find these notes on page "Info (Main Settings)", further details there. Please note that the note does not refer to the backup, but to the subsequently saved profile with the changes.
Version of a profile
By creating a backup, a new version of the profile is created (the backup has the current version number). The initial version number 1 is created after the creation and first (normal) saving of the profile. If a backup is imported, the profile takes over the version number of the backup. It is also possible to increase the version number by a "normal" saving (i.e. without a backup). To do this, set the following entry in configuration file ./etc/startup.xml to true (default is "false").
<
Set
name
=
"incrementVersionOnSave"
>true</
Set
>
Deleting a profile and backups
A backup is also created when a profile is deleted. Backups are not deleted when the profile from which they originate is deleted. So if you have accidentally deleted a profile and created backups before, you can create a new profile and load a backup of the old profile (if you name the new profile exactly like the old one).
Importing profile backups
Profile backups can be imported in the Main Settings of a profile in tab "Backup/Limits". Another dialogue will then appear.
(6) If you select a profile backup, the change notes of this profile appear in (7) (see above). Please note that the last change you see here does not come from the creation of the backup (see above), as the backup is created first and only then is the profile saved with the new change note.
Default values in GUI
You can define a few default values for different areas of the GUI in configuration file ./etc/admin/datawizard/defaults.properties .
System name
dataSystem.TEST |
Name of test system. |
dataSystem.PROD |
Name of productive system. |
Profiles
Is specified depending on the client. The value -1 represents the default client. The format is "profile.<client ID>.parameter".
profile.-1.transportManager |
Marked as ready for Transport Manager in Main Settings/General. Allowed values: true or false. |
profile.-1.errorMailPhase25 |
Mail recipient on error at Additional actions for errors in phase 2 to 5 in Main Settings/Error Handling. |
profile.-1.hint |
Note text in Main Settings/Info. |
profile.-1.encoding |
Encoding in Main Settings/General. Example: "8859_1". |
profile.-1.errorMailSubject |
Subject at In the event of an error, send email in Main Settings/Error Handling. |
profile.-1.errorMailReceiver |
Receiver at In the event of an error, send email in Main Settings/Error Handling. |
profile.-1.errorMailBody |
Message at In the event of an error, send email in Main Settings/Error Handling. |
profile.-1.attachData |
Attach input data at In the event of an error, send email in Main Settings/Error Handling. Allowed values: true or false. |
profile.-1.isTestRun |
"Is test run" in restart dialogue. Allowed values: true or false. |
profile.-1.noCheckPoint |
"Do not create checkpoint" in restart dialogue. Allowed values: true or false. |
sap.response.waitTime |
For Responses SAP and SAP ALE in Connection Settings/Permitted execution time. |
Transport Manager
tm.withoutAgent |
Transport Manager/Profiles → Without input agent. Allowed values: true or false. |
tm.withoutResponses |
Transport Manager/Profiles → Without response units. Allowed values: true or false. |
tm.preserveVariables |
Transport Manager/Profiles → Keep initial value of variables. Allowed values: true or false. |
tm.replaceFiles |
Transport Manager/Profiles → Package files replace existing files. Allowed values: true or false. |
tm.replaceProfile |
Transport Manager/Profiles → Replace profile on target system. Allowed values: true or false. |
tm.replaceCI |
Transport Manager/Content Inspection→ Replace inspector in target system. Allowed values: true or false. |
tm.profileMode |
Transport Manager/Profiles → Profile status after transport is. Allowed values: source, active, inactive. |
Server URL/IP for channel datasheet PDF
The value for the server URL/IP in created channel datasheet PDFs. See section Channels.
serverUrl.as2 |
For channel type "AS2". |
serverUrl.common |
Default value if no value is specified for a specific channel type. |
serverUrl.ssh |
For channel type "SSH". |
serverUrl.ftp |
For channel type "FTP". |
serverUrl.oftp |
For channel type "OFTP". |
serverUrl.http |
For channel type "HTTP". |