Directories

(1) Files successfully sent to the MFT server or received from the MFT server are stored in the archive directory. This is the default directory for newly created clients. To overwrite it, see area Client Configuration (MFT Client). See also (8).

(2) Directory from which files are retrieved for sending to the MFT server. This is the default directory for newly created clients. To overwrite it, see area Client Configuration (MFT Client).

(3) Directory in which files coming from the MFT server are stored. This is the default directory for newly created clients. To overwrite it, see area Client Configuration (MFT Client). See also (10).

(4) If an error occurs when sending a file to the MFT server, it is stored in the error directory. This is the default directory for newly created clients. To overwrite it, see area Client Configuration (MFT Client).

(5) This directory is used to store the log information for the Logs area in file message.log. See also (11).

(6) Received files that could not be stored in the original destination directory (e.g. for FTP) are temporarily stored here. At regular intervals, a new attempt is then started, see (12). Not relevant for the standard application of the MFT server. Use the default value.

(7) Only files with the specified file extension are sent. Regular expressions are marked with (;), for example ;[A0-9].*

(8) See (1).

(9) This is the default value for the scan interval of the output directory of newly created clients. In the client, the value can be modified in area Client Configuration (MFT Client).

(10) See (3).

(11) See (5).

(12) See (6).

(13) If the deletion (after sending a file) in a directory fails more often than the number specified here, the corresponding directory will be locked and must be unlocked manually.

Communication

(14) The IP/URL of the MFT server and the port (of the Message services, default 8020).

(15) The maximum amount of time for establishing a connection to the MFT server. If this time period is exceeded, the connection attempt is considered to have failed.

(16) You can ignore this setting for the standard application.

(17) After setting the checkbox, you can define a time interval in which the client carries out its maintenance. During this time there is no connection to the MFT server.

Mail Settings

(18) Should an error occur, you can be informed by email. To do this, enter the access data for an SMTP server to which you have access.

(19) The collected error messages are sent when one of the two values is reached.

Saving Settings

(20) Local saving of the settings.

(21) In addition to saving locally, the settings can be backed up on the server.

(22) Restore backed-up settings stored on the server.