Getting Started : What is Exalead CloudView : What Are the Main Parts of Exalead CloudView
 
What Are the Main Parts of Exalead CloudView
To start with a high-level view of the product, let us say that it is made of the following parts:
• Connectors to fetch data from data sources.
• Indexing to process fetched documents and store them into the index.
• Searching to define how data will be searchable and what will be displayed in the Search-Based Application.
• Mashup UI or custom front-end applications based on search.
The following diagram summarizes the process to index and search with Exalead CloudView.
Figure 1. A simplified view of Exalead CloudView
#
Description
1
Connectors:
• access the data sources,
• fetch their files,
• convert the files into documents,
• send them to the Indexing Server through the Push API protocol.
2
During the analysis phase, the Indexing Server:
• Receives documents.
• Triggers their analysis sequentially, entirely in memory.
• The analyzers process each document in the analysis job, perform text extraction, semantic processing, custom operations, and mapping.
3
During the build phase, the Indexing Server analyzes pushed documents, and creates a new generation of the index. It creates a set of files (tables, inverted list, and other structures) to make the index efficient at search time.
4
Once the build phase is complete, it is stored into the index.
• It merges the data computed for analysis with the current version of the index.
• Once done, the index is committed and updated. The new documents are available for search.
5
The Search Server interprets and processes user queries.
Each user query is processed by the Search Server based on a specific search logic.
6
Search queries and search results can be entered and displayed either in the Mashup UI (the default search application), or a custom search application relying on the Exalead CloudView Search API.