Technical components

ABACUS/Regulator is designed in a 3-tier-architecture.
It is is based on a flexible client-server architecture as well as a relational database for data storage. The use of the following proven standard technologies enables the reliability of the system and its productive use:

As a web based application, client access to ABACUS/Regulator takes place via a standard web browser. Operating ABACUS/Regulator within a virtual environment (e.g. using Citrix) is also possible. Additional installation of other components on the client, apart from the web browser, is not necessary. The underlying architecture furthermore permits distributed installation of the database, the web server and the application on different servers.


Since ABACUS/Regulator, with the exception of the database components, is Java-based, the application (i.e. the ABACUS server) can be installed independently from the operating system. From an architectural point of view ABACUS/Regulator consists of the following main parts:

Client


The client is the interface between the user and the ABACUS/Regulator system. It processes the input from the user, displays results and provides results as data files.

Web server 


The web server contains the functional logic of the system. It receives input from the client, processes it and sends back the results. Furthermore it manages the system processes necessary for data processing.

ABACUS server 


The ABACUS server executes the data processing necessary for the realization of the functional system logic. It is triggered by the web server or batch processes.

Database server


The database server is required for the provision of the data necessary for the system. Furthermore the processing results and the data necessary for processing are stored on it.

 

Back
Share:

Choose your language

×