Info | ||
---|---|---|
| ||
Botschaft (sehe unten) angekommen. Hier wird beschrieben:
Alan, diese Seite ist ein Beispiel dafür, wie wir es nicht machen: Sie brauchen keine Parameter zu dokumentieren, das ist längst in der Parameter Reference Documentaton erfolgt und einfach nur redundant. Was stattdessen gebraucht wird, ist eine Erläuterung wie der Background Service funktioniert, wozu ich ihn einsetze und welche Hürden und Kanten es dabei ggf. gibt. Auf keinen Fall werden hier einzelne Parameter beschrieben. |
Table of Contents |
---|
Introduction
The JADE YADE Background Service provides a centralized transfer history collection, storage and viewing function for any number of JADE clientsYADE Clients. It is important that this service provides both prompt and reliable information and therefore two approaches approaches for handling the history information can be configured in JADEYADE.
Overview
See the YADE Component Architecture article for a schematic overview that includes the Background Service.
The
...
YADE history file
- JADE
- YADE 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 - YADE and is not an extract from the log files.
- The history file is usually located on the same server as the JADE
- YADE Client itself.
- This file is then read at regular intervals by the (central) JobScheduler providing
- that provides the Background Service and the
- . This information is then stored in the (central) transfer history database. JADE
- YADE and the Background Service can be configured to limit the size of the history file and avoid read/write conflicts between JADE
- YADE and the Background Service.
- See the JADE
- YADE Parameter Reference - History
- SystemPropertyFiles article for more detailed information about the configuration of the JADE
- YADE history file.
The automatic importing of the history file by the JobScheduler is described in more detail in the JADE - YADE Background Service Automation article.
The
...
YADE BackgroundService
There are two methods with which the YADE 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
- YADE JADE
- can be configured to send the history information after each transfer session has been completed directly
- immediately to the JobScheduler providing the Background Service.
This information is sent per - using the UDP protocol in a 'fire and forget' manner.
- The JobScheduler then uses the JADE
- YADE Background Service information to generate an order that writes
- jobs to write the history information to the transfer history database.
- The history information is lost if the JobScheduler providing the Background Service JobScheduler
- is not available at the time of transmission.
- See the JADE
- YADE Parameter Reference - BackgroundService article
- BackgroundServiceFragmentRef article for more detailed information about the configuration of the JADE Background Service
- YADE BackgroundService.
...
Delayed and persistent history information
- The
...
- YADE Background Service provides
...
- delayed transfer of the history information to the
...
- transfer history database and the
...
- YADE Background Service History Viewer or other viewing, reporting or notification system.
...
- The Background Service jobs copy the history file
...
- of each YADE instance to a central server and import the data to the transfer history database.
For more information
- see See the JADE YADE Component Architecture article for an overview of how JADEYADE, the transfer history and the Background Service integrate and links leading to further information sources.