An interface consists of a set of rules that define the loading of a datastore or a temporary target structure from one or more source datastores.
The target datastore is the element that will be loaded by the interface. This datastore may be permanent (defined in a model) or temporary (created by the interface in the staging area).
The source datastores contain data used to load the target datastore. Two types of datastores can be used as a source of an interface: The datastores from the models, and temporary datastores target of an interface.
The source datastores of an interface can be filtered during the loading process, and must be put in relation through joins. Joins and filters can be recovered from the models definitions, and can also be defined for the interface.
The mapping defines the transformation rules on the sources enabling to generate data to load the target.
The flow is the set of loading and integration strategies for mapped data, based on knowledge modules.
The flow control strategy lets you define the method used to check the flow before the insertion in the target. The control strategy is defined by a Check Knowledge Module (CKM).
The interfaces use the following components:
Datastores defined in the models as sources and target or the loading process.
Knowledge Modules to generate the appropriate processes.
Variables and Sequence to store values or counters in the expressions.
Users functions to ease the transformation rule coding.