This section describes the most important terms and concepts of the
Consolidation Server.
CDIH (Consolidated Document Identifier Holder) – is similar to the Indexing Server DIH.
It assigns unique IDs to the documents processed by the Consolidation Server.
Consolidation config – A consolidation config specifies consolidation settings, some
applying to transformation and aggregations processors. You can also specify rules to
forward consolidated documents to another build group or Consolidation Server.
Transformation processors – Use transformation processors to specify the relationships
between the objects pushed to the Consolidation Server. The documents and their
relationships are stored using an object graph, where documents are nodes and relationships
are arcs.
Aggregation processors – An Aggregation processor is a set of rules describing how to build the
documents sent to Exalead CloudView. They allow the Consolidation Server to enrich object graph documents with the metas
of their related nodes. You can write these rules in Groovy or Java.
Documents - All the objects to index, regardless of file or entity type in the data
source. For example, HTML, JPG or CSV files, database records are all considered documents
within Exalead CloudView, since they are all converted into a Exalead CloudView-specific document format (also known as a PAPI document) after being scanned by a
connector.