In a typical Endeca-based application that uses the Presentation API, the MDEX Engine communicates with the web application using the Presentation API.
The online portion
of a typical Endeca implementation has the following components:
- The MDEX Engine, which receives and processes query requests.
- The Endeca Presentation API, which you use to query the MDEX Engine and manipulate the query results.
-
A Web application in the form of a set of application modules, which receive client requests and pass them to the MDEX Engine through the Presentation API.
The following diagram illustrates the data flow between these components for a typical Endeca-based application that uses the Endeca Presentation API:
In this diagram, the following actions take place:
- A client browser makes a request.
- The Web application server receives the request and passes it to the application modules.
- The application modules pass the request to the Endeca MDEX Engine, via the Presentation API.
- The MDEX Engine executes the query and returns its results.
- The application modules use Presentation API method calls to retrieve and manipulate the query results.
- The application modules format the query results and return them to the client browser, via the Web application server.
Note: For security reasons, you should never allow Web browsers to
connect directly to your MDEX Engine. Browsers should always connect to your
application through an application server.
