Page History

Logging parameters 

log_filename - Name (and path name) of the logging-file

This parameter specifies the location of a file to which the log output will be written.

log4jpropertyfilename

The name of the log4j property file.

verbose - the debug message granularity

The verbose parameter specifies the intensity of log entries.

A value between 1 and 9 can be specified. Higher values cause more detailed information to be logged.

Log output is written to stdout or to a file that has been specified with the log_filename parameter.

Introduction

Logging is specified in the JADE XML hierarchy in the General branch of the configuration, which is used to specify parameters that are neither related with specific file transfer operations.

• General
  • History
  • BackgroundService
  • Logging
    • LogFile
    • Log4JPropertyFile
    • DebugLevel
    • ProtocolCommandListener

All logging parameters are optional and covered by default settings, which are described in the next section.

Logging Settings

JADE uses the log4j framework and logs to two locations:

• stdout using the relatively compact rootLogger and
• a file using the more detailed reportLogger.
  
  • The location of this file is specified in the LogFile configuration element.
  • The default location for this file is the JADE logs directory.

These default logging settings themselves are specified in a log4j.properties file, whose location is specified using the Log4JPropertyFile configuration element. The default location of this log4j.properties file is the bin file of the JADE installation.

The detail of logging is specified using the DebugLevel element - the default level is "info" - more detailed levels can be specified if required.

In addition, JADE can use the Apache Commons FTP Client to receive detailed information about transfers carried out using FTP. This information is activated using the ProtocolCommandListener element.

Further Information

More detailed information about the JADE logging settings can be found in the JADE Parameter Reference - Logging article.

Notifications

JADE can be optionally configured to send e-mails and/or activate (connection) Fragments that ....

E-mails are sent

Specifying Notrifications

Notifications are protocol-specific and are specified in the JADE XML hierarchy as descendants of Profile elements as shown below:

• Profile
  • Operation (required)
  • Notifications (optional)
    • NotificationTriggers
      • OnSuccess
      • OnError
      • OnEmptyFile
    • NotificationFragmentRefs
  • other optional elements

Further Information

More detailed information about the JADE notifications settings can be found in the JADE Parameter Reference - Notifications article.

 This parameter is optional.