Endeca provides agile information in two ways.
1. Latitude agile BI – for decisions made by customers
2. BI Commerce – for decisions made by buyer(s)
You will get the data based on MDEX engine. MDEX engine will be useful to search the data records that was loaded using Graphs (Clover ETL)
A graph is essentially a pipeline of components that processes the data. The simplest graph has one
Reader component to read in the source data and one of the Endeca components to write (send) the
data to the MDEX Engine
The Latitude Data Integrator (LDI) is a high-performance platform that lets you extract source records
from a variety of source types, and load them into the MDEX Engine
In Endeca we have Information Transformation Layer (ITL) is used to join all data from different sources into Endeca records (MDEX engine) Endeca creates indexes for all data records and those indexed records are loaded to MDEX engine. All the indexes will sits into memory whenever a query fires on Latitude (reports) the records will be fetched from indexed records using MDEX engine.
Index is collection of Endeca Records
Endeca Information Discovery (Integrator) used to built graphs (clover ETL)
· Centralized ETL job management
· Integration into enterprise workflows
· Multi-user environment
· Parallel execution of graphs
· Tracking of executions of graphs
· Scheduling tasks
· Clustering and distributed execution of graphs
· Launch services
· Load balancing and failover
At glance
Endeca creates an index of all your data
The index is loaded into the MDEX engine
Studio is configured to query the MDEX engine and for searching the content used for reporting
We will see how to build reports & Graphs using Endeca Studio/Integrator in another post