Product Knowledge Base

Space shortcuts

Page tree

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 21 Next »

Divide article?

-> Two separate articles?

Introduction

JADE comes with a number of optional logging and event-triggered notification features.

Logging

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.

Notifications

JADE can be configured to send notifications to one or more recipients in the form of e-mails or files.

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 about logging

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

Notifications TO BE DONE

JADE can be configured to send notifications to one or more recipients in the form of e-mails or files.

E-mails are sent using the Java mail client, which is a part of the Java Runtime Environment and a requirement for the installation of JADE.

Files are sent by activating (connection) Fragments that cause a file to be sent to a receiving server.

Specifying Notifications

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 (for e-mains)
        • OnSuccess
        • OnError
        • OnEmptyFile
      • NotificationFragmentRefs (for file transfer)
    • other optional Profile elements

Notification Configuration TO BE DONE

E-Mail configuration - How/where config.?

File Transfer configuration - How/where config.?

Further information about notifications

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

See also

The JADE BackgroundService, which collects the transfer history and log files from a number of JADE Clients and adds this information to a transfer history database.

It can be configured to send notifications when detecting errors being reported from the file transfer history.

 

 

  • No labels