|
DBPrism layer architecture is divided into several level:
- Lower level is the system level and it includes the operating system and and database.
- Container level is the Servlet container capable of running Apache Cocoon 2,
the list of tested container includes Tomcat 4.1.18+, Oracle 9iAS Containers for
J2EE (OC4J), Orion 1.4+, JBoss/Jetty 3.0.2+, Caucho Resin, but the list could be
expanded to the list supported by Apache Cocoon Project.
- CMS level is DBPrism CMS code. It includes basic services such as the CMS header
and content, and additional services such as the Search Engine, the News Feed and
FAQs, it could be expanded with a little work with services such as Discussions
forums and RSS connectors.
- Application level is a level that provides the facility to make application on
top of the CMS, that is, using the CMS concepts a Shopping Cart application could
be implemented with less effort than an standalone application because many
functionality are already implemented, for example, security, meta-data information,
searching and so on. DBPrism CMS's Administration Utility (CMS FrontEnd) is an
example of an application running on top of DBPrism CMS.
- The upper level is the presentation level managed by Cocoon, it is responsible
of portal content aggregation, formatting and so on.
 |
Cocoon supports the four upper level because its functionality affects these
components, for example DBPrism CMS runs as an application which uses DBPrism
generator for Cocoon 2, CMS applications will require inclusion as Cocoon's matcher,
pdf output require an stylesheet used by Cocoon and so on. |
|
