JADE Documentation (PDF) - SOS-Berlin

SOSFTP Documentation 28
4.6 Logging
There are two options for logging, the transfer log and the transfer history. Both can be used independently from
each other:
4.6.1 Transfer Log
The transfer log contains all relevant transfer information. By default this is logged to stdout. Instead of logging to
stdout you can redirect the log output into a file by using the parameter “log_filename”. Should this file not yet
exist then it will be created otherwise the log output is appended to the existing file.
4.6.2 Transfer History
(send and receive only, not for jump)
The transfer history is created in order to store the file transfer information of the SOSFTP Client into a CSV file
and subsequently into a database. The information about file transfers is required for further processing steps
like automated alerting. By default this log type is not active as it requires the SOSFTP server to be in place.
Example Command 1:
sosftp.cmd -settings=ftp_settings.ini -profile=ftp_send -operation=send
The profile of the configuration file ftp_settings.ini:
…
[ftp_send]
protocol = ftp
host = 8of9
user = sos
password = sos
file_spec = .*
local_dir = outbound/
remote_dir = /inbound/
history = history.csv
…
By setting a filename for the parameter “history” this log output is written to that file in CSV format. Should the
file not yet exist then it will be created otherwise the log output will be appended to the existing file. The transfer
history is one text line per transferred file. If one call of the SOSFTP Client causes the transfer of N files then N
records are created. The transfer history is only created for the operations send and receive. Each record contains
the following values:
guid;mandator;transfer_timestamp;pid;ppid;operation;
localhost;localhost_ip;local_user;remote_host;remote_host_ip;remote_user;
protocol;port;local_dir;remote_dir;local_filename;remote_filename;file_size;
md5;status;last_error_message;log_filename
Software- und Organisations-Service GmbH