Bloomreach

Bloomreach Documentation version

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

Upgrade / Configuration Verifier

The Configuration Verifier

Introduction

The Bloomreach Experience Manager Configuration Verifier, BECV or just CV in short, is a tool to support projects and developers during the upgrade between major Bloomreach Experience Manager releases, and is available to Bloomreach Experience Manager customers and partners.

The CV supersedes and replaces the earlier Bootstrap Configuration Upgrade Verifier and is available as of Bloomreach Experience Manager release version 12. Compared to the earlier Upgrade Verifier, the CV is more versatile and useful beyond just major (product) upgrades; it can also be used to verify and report on project specific configuration changes, at any time!

CV is setup and configured as an extension of an existing Bloomreach Experience Manager project, and is available as a standard (enterprise) Maven dependency.

In its initial release, CV runs as a custom local build step and generates a detailed report in YAML format about the differences (deltas) between the current project configuration and an existing (e.g. previous version) repository (database), without (yet) modifying or updating the repository.

The current version of CV only checks for differences between the config definitions of the project configuration (see: Manage Configuration) and the existing repository, but not for changes in the namespaces of in content. Also, CV does not yet have a UI, and the reported differences are not yet correlated with the documented configuration changes of the product.

How it works

CV runs only the CMS web application through a custom Maven cargo.run execution, and then uses a different Hippo Repository initialization which only loads the provided CMS project configuration. Instead of applying the project configuration, it will then only compare it against the existing repository database, and report all the detected differences in a specific YAML delta format.

The existing repository is not modified (persistently) during this process and also not kept available afterwards for regular usage. After this process has finished, the web container (Tomcat) is stopped again. CV can only be run locally, by a developer.

Using the Configuration Verifier

Usage of CV is further described in these documents (login required):

Did you find this page helpful?
How could this documentation serve you better?
On this page
    Did you find this page helpful?
    How could this documentation serve you better?