Agiloft employs a multi-tier, J2EE/Application Server/RDBMS architecture on the server for enterprise connectivity and compatibility across operating systems.
A fourth generation, Document Object Model (DOM) architecture on the browser provides immediate response (AJAX) and local caching for operations that do not require server access.
The installer will detect and automatically configure the system to communicate through an Apache or IIS webserver. As indicated by the dotted lines, it can also be configured for direct communication with the JSP Servlet container if no webserver is installed on the machine.
As indicated by the above diagram, the webserver, database and J2EE server can all be installed on different machines.
In general, moving the database to a separate machine will not affect performance because J2EE caching is used to minimize database access and the database only uses one quarter of the CPU resources of the J2EE server.
For security reasons, the default Agiloft installation configures the database not to listen on any ports and the J2EE server communicates with it via a "pipe" file. This prevents the possibility of a remote hacker accessing the database and also optimizes performance.