The Oracle Endeca Application Controller (EAC) controls, manages, and monitors components in your Guided Search implementation. It is installed with the Platform Services package. The Endeca HTTP service, which controls the EAC, is created, registered, and configured when you install Platform Services and starts when you reboot the machine after installation.
The EAC must run on each server that hosts Guided Search components. One instance acts as the EAC Central Server (selected during Platform Services installation), while the other instances act as EAC Agents and receive configuration information and commands from the central server.
Note
For information about how to enable SSL communication between the EAC Central Server and EAC agents, refer to the Oracle Commerce Guided Search Security Guide.
The EAC is platform and language independent and uses Web Services Descriptive Language (WSDL) to communicate both internally (between the central server and agents) and with external resources. It manages operations such as partial updates, delta updates, and phased MDEX Engine updates. The EAC Central Server stores and propagates configuration for the following components across all EAC Agents:
Forge — Data ingest software that transforms source data into tagged Guided Search records.
Dgidx — An MDEX Engine component that generates indexes from Guided Search records and sends them to all Dgraphs.
Dgraphs — The MDEX Engine software that processes queries against indexed records.
Report Generator — The MDEX Engine report generator that generates reports from log files.
