Glossary entries exist beginning with the following letters:
An Accumulator inserts extracted data into the archive Vault (for an archive operation) or the Adabas target file(s) (for a transfer operation).
Accumulators are launched automatically by a Data Archiving Service and run unattended, reporting progress as well as restart/recovery information back to the Data Archiving Service.
Actions belong to Plans. An Action defines where data is to be extracted from, where it is to go, and the computers on which the respective Extractor and Accumulator processes will run. Together, Actions and Plans are used to define and implement your archiving rules and policies.
Each run of an Action is called an Activity. Activities are monitored and recorded by Data Archiving Services.
An Archive is a flat-file contained in the Vault that holds all the extracted data from a single Adabas file for a single run of an Action. One or more Archives will be created for an Action where it defines business objects that will require data extracted from multiple Source Files.
The Extraction Syntax ARCHIVE COPY command causes the specified record(s) to be archived to the Vault. Source File records are not deleted.
The Extraction Syntax ARCHIVE MOVE command causes the specified record(s) to be archived to the Vault. Source File records are deleted.
See Data Archiving Service.
A business object in the context of Archiving is a collection of related records located in one or more files.
In the context of archiving, a Computer represents a single operating system image (this may be a virtual machine).
The Configuration File is an Adabas file used by Adabas System Coordinator and other related products for storing configuration data. Data Archiving for Adabas refers to this file as the Repository.
A Daemon manages the control of one or more services such as the Data Archiving Service. Daemons run under an Adabas System Coordinator Group Computer and a single computer can run one or more Daemons.
The Data Archiving Service manages all archive operations, it runs unattended, launching Extractors and Accumulators according to the plans defined by the administrator in the UI. It records activity progress and history to assist the administrator in monitoring and controlling archive operations.
Each Data Archiving Service runs within a Daemon (please refer to the Adabas System Coordinator documentation for more information on Groups etc.).
Extraction Syntax uses a simple scripting language to allow the user to define business objects and the archiving actions to be taken on that object.
An Extractor extracts data according to criteria defined for the Action 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 a Data Archive Service and run unattended, reporting progress as well as restart/recovery information back to the Data Archive Service.
File Mappings allow the use of Adabas long field names in the Extraction Syntax by providing a means to map Adabas short field names to long field names. The mapping records can be either manually created or imported from Predict or Natural DDMs.
An Adabas System Coordinator Group defines a logical network of computers where Daemons run.
Pacing is specified on a per Action basis and allows the user to control the number of objects per second that are processed by the Action when it is running. This allows the CPU load to be controlled for the Data Arching Service.
The Perspective is a way of specifying theRepository that the UI is to display. The Perspective may be set to select a Repository in one of three ways:
Direct to a specific Repository, either local to the UI Computer or viaEntire Net-Work.
To the defaultRepository of another Adabas System Coordinator Daemon hosted on a different computer to the UI, by specifying the hostname and port number of the Daemon.
To a specific Repository on a different computer to the UI by using the Adabas System Coordinator hosted on that machine and specifying the hostname and port number of the Daemon and the database/file number.
An Archiving Plan holds a collection of one or more Actions. Plans collect together related Actions, for example all the Actions required for a particular business application, division or department such as Accounts, Manufacturing, R and D etc. Together, Plans and Actions are used to define and implement your archiving rules and policies.
Recall, is the process of recalling the Archived data from the Vault to an Adabas file.
The Repository is the Adabas file used by Data Archiving for Adabas for storing configuration data. Adabas System Coordinator and other related products refer to this Adabas file as the Configuration File.
Your archiving rules and policies are defined and implemented using Plans and Actions.
System Management Hub, a Software AG UI for the management of multiple applications.
One or more Source Files are specified for each Action. They relate the Source File name to a specific DB/FNR from which the Archiving processes Extractor will read records.
A Target File is used as a destination file in a TRANSFER. One or more Target Files may be specified for each Action. They relate the Target File name to a specific DB/FNR and to which the Accumulator will write records.
A To-Do list is a list of records to be Archived, generated by using either the Natural or ‘C’ API’s.
The Extraction Syntax TRANSFER command causes the specified record to be copied to the Adabas Target File.
A Vault is a flat-file store which is used to hold all the archived data. Any number of Vaults may be defined and each Plan must specify the Vault to be used for all the Actions defined under the Plan.
The Vault Path is the physical location of the flat-file store used as a Vault, it can be HFS, a UNC path or a Windows directory.