Top Level Repository Nodes
Overview
Bloomreach Content stores both content and configuration in a hierarchical node structure within its content repository. You can browse this structure using the Bloomreach Content Console. This page describes the purpose of each top-level node in the repository.
- content
- formdata
- hcm:hcm
- hippo:configuration
- hippo:log
- hippo:namespaces
- hst:*
- hst:platform
- hippo:reports
- jcr:system
- targeting:targeting
- webfiles
content
The content node contains all content managed through the CMS user interface.
/content/documents: Stores editable documents./content/gallery: Stores uploaded images./content/assets: Stores uploaded assets, such as non-editable files (e.g., PDFs)./content/attic: Stores deleted content.
formdata
The formdata node provides temporary storage for form data during a Post/Redirect/Get sequence.
hcm:hcm
The hcm:hcm node is used by Configuration Management to store baseline configuration information.
hippo:configuration
The hippo:configuration node contains all configuration for Bloomreach Content.
/hippo:configuration/hippo:derivatives: Stores Derived Data Functions./hippo:configuration/hippo:domains: Stores Security Domains./hippo:configuration/hippo:frontend: Stores CMS user interface configuration./hippo:configuration/hippo:groups: Stores user groups./hippo:configuration/hippo:initialize: Stores the repository bootstrap log./hippo:configuration/hippo:modules: Stores repository modules./hippo:configuration/hippo:queries: Stores queries, for example, to restrict document types in a folder./hippo:configuration/hippo:roles: Stores user and group roles./hippo:configuration/hippo:security: Stores security configuration, including access manager and user/group providers./hippo:configuration/hippo:update: Stores Groovy updater scripts./hippo:configuration/hippo:users: Stores users./hippo:configuration/hippo:workflows: Stores workflow configuration.
hippo:log
The hippo:log node contains the Event Log. The platform records all workflow invocations as JCR nodes, including information about the user, operation, timestamp, and affected document.
hippo:namespaces
The hippo:namespaces node stores namespaces and content type definitions. Most content types are created using the Document Type Editor. Image Set types are configured using the setup application.
hst:*
The hst:* node contains HST configuration for a site web application, including hosts, channels, URLs, and pages, components, and templates.
The asterisk (*) represents the project or site name, such as hst:myproject when creating a project from the Maven archetype with default settings. In earlier versions, this node was always named hst:hst.
hst:platform
The hst:platform node contains HST configuration for the CMS web application, including hosts and URLs.
hippo:reports
The hippo:reports node stores Reporting Dashboard configuration.
jcr:system
The jcr:system node is reserved for the underlying Jackrabbit application.
targeting:targeting
The targeting:targeting node stores Relevance Module configuration.
webfiles
The webfiles node contains static web resources stored in the repository as web files.