This article covers a Bloomreach Experience Manager version 13. There's an updated version available that covers our most recent release.

Top Level Repository Nodes


Bloomreach Experience Manager's content repository is used to store content as well as configuration in a node tree. The Bloomreach Experience Manager Console can be used to browse the node tree. This pages provides an overview of the top level nodes and what they are used for.


Contains all content managed through the CMS UI.

  • /content/documents - Editable documents.
  • /content/gallery - Uploaded images.
  • /content/assets - Uploaded assets (e.g. non-editable files such as PDFs).
  • /content/attic - Deleted content.


Temporary storage for form data persisted during a Post/Redirect/Get sequence.


Used by Configuration Management to store baseline information.


Contains Bloomreach Experience Manager configuration.


Contains the Event Log. The platform logs all workflow invocations as JCR nodes. These nodes contain information about which user performed what workflow operation when and on what document. 


Contains namespaces in which content type definitions are stored. Most content type definitions are created using the Document Type Editor. Image Set types are configured using Bloomreach Experience Manager's setup application.


Contains HST configuration such as hosts, channels, URLs, pages, components, and templates for a site webapp.

Where * is the name of the project or site, e.g. hst:myproject when creating a project from the Maven archetype with default settings. Previously fixed at hst:hst.


Contains HST configuration such as hosts and URLs for the CMS webapp.


Reporting Dashboard configuration.


Used by the underlying Jackrabbit application.


Relevance Module configuration.


Static web resources stored in the repository as web files.

Did you find this page helpful?
How could this documentation serve you better?
On this page
    Did you find this page helpful?
    How could this documentation serve you better?