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

Introduction

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.

content
formdata
hcm:hcm
hippo:configuration
hippo:log
hippo:namespaces
hst:*
hst:platform
hippo:reports
jcr:system
targeting:targeting
webfiles

content

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.

formdata

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

hcm:hcm

Used by Configuration Management to store baseline information.

hippo:configuration

Contains Bloomreach Experience Manager configuration.

/hippo:configuration/hippo:derivatives - Derived Data Functions.
/hippo:configuration/hippo:domains - Security Domains.
/hippo:configuration/hippo:frontend - CMS user interface configuration.
/hippo:configuration/hippo:groups - User groups.
/hippo:configuration/hippo:initialize - Repository bootstrap log.
/hippo:configuration/hippo:modules - Repository modules.
/hippo:configuration/hippo:queries - Queries used to e.g. restrict the document types in a folder.
/hippo:configuration/hippo:roles - User/group roles.
/hippo:configuration/hippo:security - Security configuration (access manager, user and group providers).
/hippo:configuration/hippo:update - Groovy updater scripts.
/hippo:configuration/hippo:users - Users.
/hippo:configuration/hippo:workflows - Workflow.

hippo:log

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.

hippo:namespaces

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.

hst:*

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.