• Technical Overview
  • Overview
    • What is Jahia?
    • The closer View
    • Technical Requirements
    • Everything is Content, whatever the type or source
      • Integrator and Developer Customization
    • Integrated technologies
    • Architecture Overview
    • Modules
    • Jahia's Different Actors
  • Web Layers
    • Content Flows
    • Templates and Views
    • The Jahia Template Studio
      • Page templates
      • Content Templates
    • REST API
      • Actions
      • Example : native iPhone/iPad application
    • Mobile Rendering
    • Macros
    • Filters
  • Back-end Layer
    • Workflow
    • JBoss Drools and event listeners
    • File Repository
    • Searching and Indexing
      • Full text queries using search tag librairies
      • Query Languages
    • Enterprise Jahia Tool - Authentication and Authorization
    • Import / Export
    • Enterprise Jahia Tool - Distant Server Publications
    • Portlets
      • Portlets vs. Modules
  • Enterprise Jahia Tool - Optimizing deployment and performance
  • Additional Resources

The closer View

If the previous description of Jahia was a bit too abstract, the following description should be more helpful. Jahia is basically composed of the following layers:

• A servlet container (Apache Tomcat, Oracle WebLogic, IBM WebSphere or others)

• A set of filters and servlets that form the “outer layer” of Jahia

• A set of Spring beans that make up the main architecture of Jahia

• A set of modules that extend the basic functionality

• A JCR implementation for storage of content (Apache Jackrabbit 2.x)

• A portal container (Apache Pluto 2.x)

• A scheduler (Quartz)

• A workflow engine (jBPM)

• A rules engine (Drools)

Of course this is a much-simplified view of the elements that Jahia is made of, but it should help identify the type of technologies involved.