Glossary

A

Application Program Interface (API): Standard interface for Data Manager: it is a way to feed the knowledge base with external information (for example, change management, database design, and data base catalog). Data Builder needs a standard interface, and the API’s task is to fill this interface. APIs can be developed by Micro Focus or customers, but they are not part of Data Manager.

client: Tool or suite of tools that provide a front-end interface to the knowledge base.
cataloging: Group of batch jobs populating the knowledge base with the technical structure information of the data stores (for example, name, size, data elements, and data element properties).
class: Abstract property of a field that describes its meaning, for example, Name, Amount, Account, or code.
classification: Group of data entry functions and batch jobs populating the knowledge base with the application information of the data stores (class-data elements association).
confidence: An abstract measurement that indicates how well the data types in the analyzed data stores match the data types in a copybook.

engine: Group of batch jobs creating the target environment data by applying the rules defined in the Knowledge Base to the files cataloged in the Knowledge Base. The output of the engine constitutes a flat file.
environment: Set of the files to be processed and moved into another place.
environment population: Group of data entry functions and batch job loading the engine result in the target environment.

fingerprint: A data element content analysis function that provides statistical information about the content of a data element.

Knowledge Base: Collection of tables within a database that contain all information about cataloged data stores, including properties and processing rules.

Life Cycle: Group of data entry functions and batch job keeping the knowledge base up to date when a change in the technical structure occurs, keeping intact the classification and rule definition information as much as possible.

Programmable Rules Definitions (PRD): Code that can be used in order to add flexibility to Data Manager. In addition to the standard in reduction and in masking rules, it is possible to call external code with a standard program interface (provided by Micro Focus) from the engine. PRDs can be developed by Micro Focus by or customers, but in any case they are not part of Data Manager.

rules definition: Group of data entry functions and batch job populating the knowledge base with the masking and reduction rules to be applied to an environment.

step: Phase, marked by a successive number, which comprises a method. Operations belonging to the same step can be performed in an arbitrary order, whereas the performance of the steps must be performed in order according to the associated number.
Super class: A set of several different classes. During the class automatic assignment phase, this type of classification enables you to restrict the search