Configuration Management Terminology

Configuration

Byconfiguration, we refer to the part of the data in the repository, which is contributed byBloomreach Experience Manager, developers and administrators in order to control how a particular instance of Bloomreach Experience Manager (a Bloomreach Experience Managerimplementation) behaves. See also content.

Content

Bycontent, we refer to the part of the repository which is contributed and maintained by Bloomreach Experience Manager users in order to manage their website(s). See alsoconfiguration.

Bloomreach Experience Manager

In the context of configuration management, byBloomreach Experience Manager, we refer to the code andconfiguration provided out of the box by Bloomreach Experience Manager, which is then extended for a particularimplementation.

Implementation

Byimplementation, we refer to a particular customization of Bloomreach Experience Manager. Animplementation is based onBloomreach Experience Manager, and extended by Bloomreach Experience Manager developers to meet the requirements of a specific customer / use case.

Configuration Model

CMS 12 manages an in-memory model of a desired/controlled set ofconfiguration. This model is the result of mergingconfiguration contributions into a single model, theConfiguration Model. For most cases, theConfiguration Model can be considered equivalent to theconfiguration part of the repository, with additional metadata to track for example the source and correct processing order for individual nodes and properties.

Repository

Therepository is where Bloomreach Experience Manager stores any data that needs to be persisted, includingconfiguration andcontent.