Message-ID: <> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_1998_824542005.1563812129499" ------=_Part_1998_824542005.1563812129499 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html Example showing logging capabilities to log messages exchanged b= etween source and target server

Example showing logging capabilities to log messages exchanged betw= een source and target server

=20 =20

YADE profiles with settings for transfer history, log file = and Background Service


YADE logs each and every file transfer in a local CSV history file and i= n a log4j format file. The transfer file history can be sent to the YADE Ba= ckground Service.
The Background Service will insert the transfer histor= y into a table of its database.

Example for transfer profile with global= settings for transfer history, log file and Background Service

jade_settings.ini file with settings for history CSV, log file = and Background Service:

 file_notification_to      =3D
 file_notification_subject =3D YADE Client mail
 file_notification_body    =3D This is a test.
 mail_smtp                 =3D
 BackgroundServiceHost     =3D 8of9.sos
 BackgroundServicePort     =3D 4210
 SendTransferHistory       =3D true
 TransferMethod            =3D TCP

 log_filename      =3D ${basedir}/jade_history.log
 HistoryFileName   =3D ${basedir}/jade_history.csv

 include           =3D MailSettings , JADEHistory, BackgroundService
 title             =3D Global Profile
 basedir           =3D C:\\jade

In this example all files with the file name extension .txt sho= uld be transferred from the server wilma via SFTP to the server 8of9 by FTP. the folders are not explicitly specified and therefore = the home folders of the user is selected. YADE will write the tran= sfer history into a CSV file and will send the log entry to the Background = Service

Define profiles = using the include directive

The include parameter will include the named profiles in the or= der they are defined. The globals profile is included automaticall= y, no need to specific it in an include parameter.
The profile= s have to be defined in the same settings file:

 include                =3D globals=20
 source_user            =3D kb
 source_password        =3D *****=20
 source_ssh_auth_method =3D password
 source_host            =3D wilma.sos
 source_protocol        =3D sftp
 source_port            =3D 22
 target_user            =3D test
 target_password        =3D *****
 target_host            =3D 8of9.sos
 target_protocol        =3D ftp
 target_port            =3D 21
 operation              =3D copy
 file_spec              =3D ^.*\.txt$

See also