Architecture
The system is characterized by a Web Based levels architecture. The framework may be thought as a set of components distributed across multiple layers.
jAPS has the following separation in layers:
- Presentation Layer: includes the components involved to manage the interface to the user (jsp, Servlet, Tag Libraries);
- Business logic layer: it includes components that interact to manage application services (search engine, newsletters, etc.) and support (internationalization service, error management service, contents cache service etc.);
- Date layer: is used by the business logic layer to carry out state rescues continuously. The data layer is essentially made of the portal configuration database, of application services and content archive.
A portal built with jAPS needs an Application Server to provide the necessary support to technology platforms used and to external resources, such as DBMS (database manager).
The portal manages the classic web channel with a browser access, otherwise it can provide a more general accessibility through an adapter layer. The database is hosted by a DBMS (Data Base Management System), and is typically an external resource accessed through the Application Server services or through the portal itself (eg. Pooling system JDBC).
Currently jAPS was tested on PostgreSQL database, MySQL and application server Tomcat.
From an architectural point of view the jAPS system implements the MVC pattern (Model View Controller).
The MVC strategy (Model View Controller) allows you to:
- Make business logic data (model) independent from the presentation (view) and control logic
- Have different views on the same model
- Support new clients types.
The model includes data to be presented to the user, then the contents structured and unstructured (documents, images, audio, video).
jAPS acts as a controller, which handles input and the flow of information to present them in a timely View (browser, mobile phones, PDAs and other devices).
The major benefits arising out of the MVC model are: reliability, reusability, adaptability, low costs in the development cycle of customizations, quick putting into operation, maintainability.
The separation between content and presentation
- Facilitates the software maintenance because each code function is limited;
- Maintenance related time are significantly reduced
- The ease to read code reduces the cases of introduction of bugs during the maintenance
- Allows great flexibility in the treatment of information that can then be used in different contexts (example: the same content can be displayed in the back office area, or in the portal or other applications) and other devices (PDAs, mobile phones etc. .)
The content is stored in the database in XML format.
