Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Info
titlepage under construction

This article makes use of deprecated configuration items and has to be re-worked

Specifying log files

  • JADE can write a separate log file for each transfer it carries out.
  • It can do this when the file transfer is started from the console and when it is started from the chrontab. There are two stages to doing this:
    • specifying the global log file name and
    • specifying the log file name for each transfer.

Specifying the global log file name

  • The log file to be used for a particular transfer is defined in the log4j.properties file.
    • A "rollingFileAppender" is used to configure the "global" log, which is not transfer-specific.
  • The log4j.properties file can be located in the same folder as the settings file. The parameter defining the location of log4j does not have to be explicitly set in the profil.

...

Code Block
languagetext
[FTP_123]
protocol = ftps
#port = 49159
host = myHost
user = ftpUser
password = ***********
log4j_Property_FileName = /opt/sosftp/sosdex_client.1.3.12.2032/profile/log4j.properties

[TEST_FTP_REC_new]
include = FTP_123
port = 49157
log_filename = /var/opt/sosftp/log/my_logfile_name.log
#verbose = 9
history = /var/opt/sosftp/log/history_TEST_FTP_REC_new.csv
file_spec = .*\.txt
force_files = false
remove_files = true
transactional = true
atomic_suffix = .tmp
local_dir = /var/data/input/ftpReceive/
remote_dir = ./

Specifying the log file name for each transfer

The log4.jproperties file is universal. The name specified with the log_filename parameter is extended using the extension ".html" and used for log4j. The trick here is that the definitions in the property file are dynamically modified. This results in two files:

...