Skip to end of metadata
Go to start of metadata

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

Compare with Current View Page History

« Previous Version 15 Next »

Introduction

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.
See the
JADE Component Architecture article for a schematic overview that includes the Background Service.

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 (central) JobScheduler providing the Background Service and this information is then 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 more detail in the JADE Background Service Automation article.

The JADE BackgroundService

There are two methods with which the JADE Background Service can import the file transfer history to a database. Both methods can be applied at the same time to receive file transfer information immediately and reliably. 

Immediate and transient history information

  • JADE can be configured to send the history information after each transfer session has been completed immediately to the JobScheduler providing the Background Service.
    This information is sent using the UDP protocol in a 'fire and forget' manner.
  • The JobScheduler then uses the JADE Background Service jobs to write the history information to the transfer history database.
  • The history information is lost if the JobScheduler providing the Background Service 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.

Delayed and persistent history information

  • The JADE Background Service provides a delayed transfer of the history information to the transfer history database and the JADE Background Service History Viewer or other viewing, reporting or notification system.
  • The Background Service jobs copy the history file of each JADE instance to a central server and import the data to the transfer history database.

For more information

  • See the JADE Component Architecture article for an overview of how JADE, the transfer history and the Background Service integrate and links leading to further information sources.

 

  • No labels
Write a comment…