This topic presents a global overview the Jahia enterprise offering.
Jahia is content and data. At its core is jContent, our Content Management System (CMS). What makes Jahia more than just a CMS is jExperience, our embedded personalization engine powered by a Customer Data Platform (CDP). With jContent and jExperience together, you can personalize every aspect of your digital experience, tailored to a 360 degree data-driven view of your audience. The final layer is StackConnect, our integration hub that unifies content, data, and applications into a cohesive marketing stack. These components together make Jahia what it is—a Digital Experience Platform (DXP).
The following diagram illustrates the component parts of the Jahia DXP and how they work together to make digital experiences simpler.
The Jahia offering consists of following key pieces:
Jahia core features include a traditional and headless CMS and a traditional and headless CDP. These features enable you to manage your content lifecycle from creation to publication and deliver and reuse content across multiple channels.
Jahia also enables you to manage:
jExperience provides personalization and optimization features that enable you to:
StackConnect enables you to:
The section shows examples of a single server architecture and clustered architectures. The single server scenario is suitable for a development environment and clustering is required for a production environment.
This example shows how you can run Jahia on a single server. This setup would be suitable for a development environment. In this case, the application server is responsible for browsing, contribution, and processing. The database stores metadata and data and the additional optional database stores binary data on the file system.
This example shows how you can run Jahia in a clustered environment. A clustered environment provides high availability and load-balancing for both browsing and contribution environments. In the example, the web server load-balances the traffic between the browsing servers and contribution servers. You can scale out horizontally and add as many servers as you want to the cluster.
Only one server can be designated as a processing server. In the example, the processing server is on a node that is also serving as a contribution node.
This example shows a clustered environment that includes jCustomer, which is Jahia’s CDP. jCustomer is installed in a separate cluster as is Elasticsearch. The Elasticsearch cluster stores the jCustomer indexes and stores data that jCustomer collects.
Jahia uses a Java-based technology and many of the components in the stacks are also Java based. Jahia uses the following technologies:
For information on additional frameworks used by Jahia, see Jahia embedded frameworks.
For information on minimum and recommended requirements for Jahia, see the supported stack for Jahia 8.
For a technical overview of:
For information on our Cloud offering, see About Jahia Cloud or Jahia Cloud FAQs.