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

Top Level Repository Nodes

Introduction

Hippo's content repository is used to store content as well as configuration in a node tree. The CMS 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.

jcr:system
hippo:configuration
hippo:log
hippo:namespaces
hst:hst
content
formdata
hippo:reports
targeting:targeting

jcr:system

Used by the underlying Jackrabbit application.

hippo:configuration

Contains Hippo CMS 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 Hippo Event Log. Hippo Repository logs all workflow invocations as JCR nodes. These nodes contain information about which user performed what workflow operation when and on what document.