...
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 sectionJADE uses standardized log files with a structured and configurable format. This allows detailed logging of all characteristics of a file transfer, e.g. renaming of files, transfer duration, resolution of host names for source systems and target systems.
Notifications
JADE can be configured to send e-mail notifications to one or more recipients in the form of e-mails or fileswhen specific file handling events such as file transfer ends in error occur.
Logging Settings
JADE uses the log4j framework and logs to two locations:
...
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.
Logging configuration
Logging is specified in the JADE XML hierarchy in the General branch of the configuration, which is used to specify parameters that are not related with specific file transfer operations.
- Fragments
- etc.
- Profiles
- etc.
- General
- History
- BackgroundService
- Logging (optional)
- LogFile
- Log4JPropertyFile
- DebugLevel
- ProtocolCommandListener
All logging parameters are optional and covered by default settings, which are described in the next section.
Further information about logging
...