Response Route SCP

Introduction: Phase 6.

This Response Route works in principle like the Response Route File, but the login on the destination computer and the transmission of the data is encrypted.

(1) Here you can select a channel of type SSH. Note: If possible, always use channels to centrally manage connection parameters. In addition to the increased clarity that also facilitates maintenance. If the connection parameters change, you only have to adjust the data in one place and you do not forget a profile.

(2) DNS name or IP address of the FTP server and the port of the FTP server. A value greater than 0 overrides the port of a selected channel. If value 0 is set, the port set in the channel is used.

(3) The destination directory can also contain placeholders for dates (<y>,<M>,<d>, usw.) and variable values.

(4) Name of the temporary file during the transfer of the data. If a value is entered in this field, Lobster_data first transfers the data to a temporary file on the destination system. After the file has been transferred successfully, the temporary file is renamed to the final destination file. The name of the temporary file can be set as follows.

• The content of the field is appended as a suffix to the file name. Example: If the value .tmp is entered in the field, the temporary file order4711.csv.tmp is created when transferring the file order4711.csv.

• The content of the field is prefixed to the file name. Example: If the value tmp is entered in the field, the temporary file tmporder4711.csv is created when the file order4711.csv is transferred.

• The content of the field is used as the name of the temporary file, regardless of the file name. Example: If the value tmp.csv is entered in the field, the temporary file tmp.csv is created when the file order4711.csv is transferred.

(5) The file name pattern of the file to be transferred.

(6) After the transfer, a control file with the set suffix or prefix is created. The settings correspond to the analogue settings in the Response Route FTP.

(7) Indicates whether all keys of the server are accepted, or only the key specified in (9). The key can be fetched from the destination server with button (10).

(8) Indicates what type of key it is. At the moment, only the type RSA is supported.

(9) The key that is expected of the server. If the server does not deliver the entered key, the connection will not be established.

(10) The key type (8) and the fingerprint (9) can be fetched from the destination computer. Note: Key type and fingerprint are taken from a selected partner channel of type SSH.

(11) If this checkbox is set, empty files are transferred as well.