About File Indexing with Exalead CloudView

This topic describes how 3DSpace Index handles file indexing using the Exalead CloudView search engine.

This page discusses:

Focus on Exalead CloudView Integration

The schema below describes how 3DSpace Index uses Exalead CloudView for file indexing.


Step	Description
1	All metadata documents from the MCS/MQL crawler and all converted/extracted file contents from the FCS are pushed to the consolidation server.
2	The consolidation server aggregates the metadata and file content (if available) before pushing the final document to the indexing server.
3	The indexing server is then responsible for indexing the final aggregated content.

The schema below represents the indexing pipeline for each crawled business object and connection, using Exalead CloudView consolidation server:


Step	Description
1. Transformation Job	Based on each document type, various transformation processors are applied.
2. Storage	As soon as commit conditions are met, all transformed documents are persisted to disk in the consolidation storage and the object graph is created or updated.
3. Impact Detection	As soon as aggregation conditions are met, the impact detection is launched on the new object graphs to detect the impacted nodes and aggregate them.
4. Aggregation Processors	Based on the document type of each incoming document, various aggregation processors may/may not be applied. These aggregation processors have a match expression/path associated with them. This expression is used to go through the object graph, project attributes of the matching document and generate a final aggregated document.
5. Forwarding Rules	A forwarding rule is applied to each document. This specifies where to push the aggregated document (by default, the build group `sxibg0`).
6. Indexing Server	Aggregated documents are analyzed and saved in Exalead CloudView index.