(1) and (2) You first have to select a client for both systems. After that, the all released profiles are displayed on the left side. Note: Whether a profile is listed for the source system at all can be individually configured for each profile in the General Data area of a profile using the checkbox Marked as ready for Transport Manager. This can also be done via the context menu in the profile overview. On the right side, all groups and profiles are displayed.

(3) You select the profile to be transported. On the target system, the group (4) into which the profile is to be moved, must be selected. You can create new groups via the context menu (5). If (7) is set, a profile instead of a group has to be selected on the target system.

(6) The name that the profile to be transported should get on the target system. You can also set whether the profile should be active or inactive on the target system.

(7) If a profile with the same name already exists on the target system, it can be overwritten.

(8) You can decide whether package files (the possibly existing test files and macros) of the profile should be overwritten on the target system or not.

Note: Configuration files in any subfolder of the ./conf folder named _exclude_ are not considered by the Transport Manager, so they are not transferred. Examples:

./conf/_exclude_/sub1/sub2/test.txt

./conf/sub1/_exclude_/test.txt

(9) If an existing profile is overwritten, you can decide whether the Input Agent and the Response Routes should be overwritten. See also (7).

(10) If there are already identically named variables in an existing target profile (that is to be overwritten), their initial values can be preserved. See also (7).

(11) If you have made all the settings for a profile to be transported, you can add the transport job to the list (12). (13) executes all existing transport jobs. Subsequently, the status of a transport job is displayed in (14). You can remove transport jobs via the context menu.