Configuration vs Content vs System

Bloomreach Content organizes repository data into three categories:

1. Configuration
2. Content
3. System

Configuration and Content are defined in the Terminology guide. System data refers to information managed by the application code. This data typically maintains state across time or between multiple CMS instances. Examples of system data include JCR lock properties and properties such as dates or sequence numbers that track event processing progress within a cluster.

The Configuration Model defines a hierarchical structure (nodes and properties) for all configuration data in a Bloomreach Content deployment. This structure forms the backbone of the repository. When you add new properties or child nodes to this tree, the parent node in the Configuration Model determines whether the new data is classified as configuration, content, or system data.

• Configuration data is managed with fine-grained control.
• Content data is managed at a coarser level.
• System data is not managed by the Configuration Management system.

Use the Configuration Model to control how each type of data is handled within your implementation.