...
The JADE Background Service provides a centralized transfer history collection, storage and viewing function for any number of JADE clients. It is important that this service provides both prompt and reliable information and therefore two approaches for handling the history information can be configured in JADE.
The JADE history file
- JADE can be configured to write the history information directly to this file after each transfer session has been completed.
Note that the history information is directly written by JADE and is not an extract from the log files. - The history file is usually located on the same server as the JADE Client itself.
- This file is then read at regular intervals by the JobScheduler providing the Background Service and the information stored in the (central) transfer history database.
- JADE and the Background Service can be configured to limit the size of the history file and avoid read/write conflicts between JADE and the Background Service.
- See the JADE Parameter Reference - History article for more detailed information about the configuration of the JADE history file.
The automatic importing of the history file by the JobScheduler is described in the JADE Background Service Automation article.
The JADE BackgroundService
- JADE can be configured to send the history information after each transfer session has been completed directly to the JobScheduler providing the Background Service.
- This information is sent per UDP in a 'fire and forget' manner.
- The JobScheduler uses the JADE BackgroundService information to generate an order that writes the history information to the transfer history database.
- The history information is lost if the Background Service JobScheduler is not available at the time of transmission.
- See the JADE Parameter Reference - BackgroundService article for more detailed information about the configuration of the JADE BackgroundService.
Prompt and persistent history information
...