EPSIAE » eneraptor

h1. Human Computer Interaction

{{toc}}

h2. 1 Basic concept

h3. 1.1 Hardware

p. The HCI will will be realised as a website. It will run on an Apache Tomcat http server, which will not run on the same device as Eneraptor's logic. Instead it will run on an independent proxy server.

p=. !HMI_website_overall.png!

p. The intended server-side html generating aplication is Tomcat's Jasper, making JSP the intended website programming language.

h3. 1.2 HCI features

The picture below shows basic HCI features:

!HCI_basic.png!

h2. 2 Communication with other parts

h3. Logged data (instructions for syslog dev)

All logged data has to be written in a *PostgreSQL* database. Database's name must be *eneraptor-db*. Data must be writen in *standard public schema* (default).

The database table will exist prior to logging unit's (Janez) first run, so logging unit does not need to create the table. The logging unit *must* know, how to add a log entry to the database correctly, so that HCI will be able to use this data:

Every new log entry should be added with the following SQL query:

<pre>

INSERT INTO logged_data(

            id, "version", date_recieved, device_id, reported_data)

    VALUES (nextval('hibernate_sequence'), 0, now(), 'enterDeviceIdHere', 'enterReportedDataHere');

</pre>

enterDeviceIdHere and enterReportedDataHere should be replaced with actual data. Logging unit *must not* change other parts of the SQL query above.

While developing the logging unit (Janez) it may be useful to have a test database like the one HCI will create in the final product. You can create such a database with the following SQL query:

[[createEneraptorDatabase.backup]]

h2. References

# Chopra, Vivek, et al., _Professional Apache Tomcat 6_, Wrox - Wiley, 2007

# Basham, Bryan, et al., _Head First Servlets and JSP™_, O’Reilly, 2008

h2. Attachments