How does Escenic Analysis Engine work?

The figure below shows an architectural overview of Escenic Analysis Engine. The visitors of the Escenic web sites download pages from the ECE server. These pages contain some scripts (JavaScript) which will initiate a request to the EAE, i.e., uploading information about the page being viewed.

The Escenic Analysis Engine consists of three main components; EAE Logger, EAE Query Service, and EAE Query Service Client. The figure below provides a more detailed view of the Escenic Analysis Engine and illustrates the architectural composition of the main components.

Both Eae Logger and EAE Query Service are standalone J2EE web applications, and must be run on a J2EE application server. The Logger receives all the requests from the visitors of the web sites, handles the log information received with these requests and finally stores the handled log data in the database.

The Query Service is a Servlet used for retrieving reports from the EAE database, i.e., the most popular page views. Both queries and responses sent to and from the servlet are XML, and the protocol is defined by XML Schemas.

The EAE Query Service Client is a remote Java API for querying the EAE Query Service. It makes the communication with EAE Query Service transparent and hides all the XML processing logic. Hence, it simplifies the implementation of report modules.