Corinis is written in Java since it is the ideal language for developing professional, flexible and platform-independent solutions. The current Corinis-release is based on Sun Java 1.4. It runs on all current operating systems and platforms (for which a Java JDK exists) and with all Databases for which a JDBC-Driver is available. The only prerequisite is an application-server which supports Java, like Apache Tomcat, Macromedia JRun, JBoss, IBM Websphere, BEA Weblogic,...

Corinis is XML-based meaning that the communication between the modules, databaseconnector, userinterface,.. is XML-based. It is therefore possible to completely divide database from application and application from layout. The same application can have a HTML-output as well as a PDF-output (both have the same XML-tree as base).

Since XML is standard it is very easy to create own interfaces to external modules and functions and integrate them into the Corinis system.

Corinis has a three layer architecture:

1. The data layer responsible for storing the data
2. The application layer responsible for the application logic
3. The presentation layer responsible for user-interaction

The communication between the layers is done via XML making it possible to change the presentation layer completely without changing anything in the other 2 layers. For example you can change your database from MySql to Oracle without changing something anywhere else than in the data layer. You can implement a new design (for example additional output as PDF and WML) without changing your application logic.

The application layer itself has a module-based layout. There is a core (the Corinis Core Server) to which all modules are connected. The Core Server provides all basic functionality so that the modules itself can concentrate only on the application logic of the problem they solve. For example the CMS-module doesn't have to care about authorities, sessionmanagement, databaseconnection,.. As a result it is very easy to implement a new module into this framework. It saves a lot of time, since many basic functions are already handled by the Core Server.

 

A Corinis application consists of several components:

•  a database which hold all dynamic data - configurations are stored in a separated xml-configuration file; The Corinis Configurator creates all necessary tables, fill them with standarddata (e.g. standardgroups- and -users) and checks integrity
• a servlet container
• servlets/jsps
  
• xsl for designing the output