Glossary entries exist beginning with the following letters:
Archive Services manage all archive operations. Archive Services run unattended, launching extractors and accumulators according to the plans defined by the administrator in the configuration file.
Archive Services record activity progress and history to assist the administrator in monitoring and controlling archive operations.
Each Archive Service runs within a member of an Adabas System Coordinator Group (please refer to the Adabas System Coordinator documentation for more information on groups etc.).
An Accumulator inserts extracted data into the archive vault or the alternate (Adabas) destination.
Accumulators are launched automatically by Archive Services and run unattended. Filtering rules can cause only a subset of the extracted data to be archived, if defined.
Accumulators communicate progress as well as restart/recovery information to Archive Services.
In archiving terms, a computer represents a single operating system image, even if that image is acting as a virtual machine.
The configuration file is an Adabas file containing the archive definitions for your site. The same configuration file is also shared by Adabas System Coordinator (and other products).
Each Data Archiving for Adabas service runs within an Adabas System Coordinator Group daemon. One or more daemons for a group run within each computer, usually one for Data Archiving for Adabas.
An extractor extracts data according to criteria defined for the actions in the archive plan, and then transfers the extracted data to the accumulator peer responsible for archiving the extracted data.
Extractors are launched automatically by Archive Services and run unattended.
Extractors communicate progress as well as restart/recovery information to Archive Services.
An Adabas System Coordinator Group defines a logical network of computers where System Coordinator daemons run. Each daemon can in turn run one or more product services. One of these product services can be for Data Archiving for Adabas. There are also many other services that can be run for other products within the same logical computer network (group).
An archiving plan allows you to bring together the archiving rules that you require for one or more related actions. For example, you may use a plan to define all the archiving that is required for a particular business application, or perhaps a whole business division or department, etc. You decide what you want to put together in one plan. For each action within the plan, you define what the data source is, where it is located, how data is to be extracted from it, when, where it is to be archived, how long the data is to be kept, etc.
A vault is a flat-file store which contains all the archived data taken since the inception of the archive according to the rules defined in the plans contained within the configuration file. Any number of vaults may be defined. Each archive plan must specify the vault to be used for all archiving processes defined in the plan.
