Wiki source code of Architecture and Concepts
Version 5.1 by Pierre Dubois on 2011/10/20 10:01
- Manage
Copy- Actions
Export
Print preview
View Source- Viewers
Siblings
Comments- Annotations
Attachments (2)
History
Information
Show last authors
| 1 | = REQUEA Applications = |
| 2 | |
| 3 | Requea is a framework designed to build and adapt enterprise applications such as: |
| 4 | |
| 5 | * ITIL - Incident, Problem and Change Management, ... |
| 6 | * Human Resources - Requests Management, Payroll, ... |
| 7 | * Facility Management - Room Reservation, ... |
| 8 | * Finance - Contract Management |
| 9 | |
| 10 | Those applications typically require: |
| 11 | |
| 12 | * A strong data management with complex relationships and ability to manage large data in a secured and transactional manner |
| 13 | * Flexibility to adapt to the specific and evolving business requirements of the customers |
| 14 | * Complete User access and security management |
| 15 | * Role base portal access |
| 16 | * A fast and intuitive user interface and user navigation |
| 17 | * Workflow capabilities for notifications, and approvals |
| 18 | * Reporting capabilities |
| 19 | |
| 20 | = The REQUEA Platform = |
| 21 | |
| 22 | The REQUEA Platform is a component that is typically installed in a standard web application server (J2EE such as Tomcat, JBoss, OracleAS, JonAs) and provides: |
| 23 | |
| 24 | * An OSGi architecture within the web application for modularity and extensibility of the platform |
| 25 | * An document based model architecture (MDA) for creating document based application where the data manipulated is easily and effitiently stored in a database (such as Oracle, MySQL, Microsoft SQL Server). |
| 26 | * A web user interface that is optimized for speed, ergonomics and complex interactivity with the user. |
| 27 | |
| 28 | = Platform services = |
| 29 | |
| 30 | The platform runs on top of standard J2EE application server and uses J2EE services provided by the environment (such as Servlets, JDBC, ...). |
| 31 | |
| 32 | The platform provides the following services: |
| 33 | |
| 34 | * database storage persistence service |
| 35 | * application business rules |
| 36 | * user interface service |
| 37 | * import / export services |
| 38 | * WebServices interfaces (SOAP) |
| 39 | * Java Content Repository interface |
| 40 | * Workflow services |
| 41 | * Reporting services (JasperReports integration) |
| 42 | * Graphs and Statistics services |
| 43 | |
| 44 | All those base services are provided as OSGi services (packaged in bundles) |
| 45 | |
| 46 | On top of those base services, we find the applications that are also OSGi bundles: |
| 47 | |
| 48 | * Core applications, such as security and user definitions |
| 49 | * Standard applications, such as calendar, events, resources and catalog management |
| 50 | * Applications such as ITIL incident management |
| 51 | * Customer Specific applications where customer specific code may be created |
| 52 | * Customer customization where changes in labels, workflows, ... for a specific implementation can be added. |
| 53 | |
| 54 | [[image:architecture.png]] |
| 55 | |
| 56 | See a general architecture presentation: |
| 57 | [[General Architecture Presentation>>attach:architecture-general.pdf]] |
| 58 | |
| 59 | = Applications and Bundles = |
| 60 | |
| 61 | Applications are packaged in OSGi bundles (see bundles: [[Bundles>>Bundles]]) that can be deployed on a modular fashion. This provides flexibility and modularity to the platform. |