Image map created by yEd

SnapArchiver: Records the attributes values picture in the SNAP database.
SnapManager: Manages the snapshots configuration and send the request to the archiver
SnapExtractor: Provides database extraction methods based on various criteria

Python API for the Tango Archiving system
This package allows to:
Integrate Hdb and Snap archiving with other python/PyTango tools.
Start/Stop Archiving devices in the appropiated order.
Increase the capabilities of configuration and diagnostic.
Import/Export .csv and .xml files between the archiving and the database.
NOTE: It access directly the MySql database.

E-Giga displays the data stored by the Tango archiving system within your
favorite WEB browser.
(PHP, Javascript)

The GUI named SGAD generates scripts to create MySql databases.

TdbArchiver: Records the attributes values in the TDB database
ArchivingManager: Allows to start / stop the attributes archiving without GUI
(use load-balancing). The same device is used to manage the HDB and TDB archivers.
TdbExtractor: Provides database extraction methods based on various criteria
TdbArchivingWatcher: Controls the global archiving status and issue periodically
refreshed reports

HdbArchiver: Records the attributes values in the HDB database.
ArchivingManager: Allows to start / stop the attributes archiving without GUI
(use load-balancing). The same device is used to manage the HDB and TDB archivers.
HdbExtractor: Provides database extraction methods based on various criteria
HdbArchivingWatcher: Controls the global archiving status and issue periodically
refreshed reports

The HDB++ is a novel TANGO device server for Historical Data Base (HDB) archiving.
It’s written in C++ and is fully event-driven

Historical DataBase - HDB : Persistent storage of attributes values which are
scanned at a minimal period of 10 seconds.

Temporary DataBase - TDB : Volatile storage of attributes values which are
scanned at a minimal period of 100 milliseconds.
The data are kept 3 days in the database.

Snapshots – SNAP: Persistent storage allowed taking a picture of a set of
attributes values.

The HDB and TDB archiving is managed thanks to the GUI named Mambo.

The SNAP archiving is managed thanks to the GUI named Bensikin.

Communication Layer (CORBA / ZMQ)

In order to simplify device server process administration, a device of the
DServer class is automatically added to each device server process. Thus, every
device server process supports the same set of administration commands. The
implementation of this DServer class follows the device pattern and therefore,
its device behaves like any other devices. The device name is:
dserver/device server executable name/device server instance name

TANGO devices and database are implemented using the TANGO device server model.
To access them the user has the CORBA interface e.g. command_inout(),
write_attributes() etc. defined by the idl file. These methods are very
low-level and assume a good working knowledge of CORBA. In order to simplify
this access, high-level api in C++, Python and Java have been implemented which
hides all CORBA aspects of TANGO.