Bloomreach

Bloomreach Documentation version

Developer Docs / Backend Development / Upgrade / Upgrade 16.3 to 16.4

Upgrade 16.3 to 16.4

Introduction

Goal

Upgrade a Bloomreach Experience Manager implementation project from version 16.3.x to 16.4.y.

Significant Changes

  • In version 16.4, the BrXM AI Content Assistant (BETA), powered by Loomi, is introduced as a new content co-pilot. It helps streamline tasks like generating metadata tags, creating multilingual content and translations, and performing grammar checks, aiming to increase efficiency and quality3. It requires an organization to configure its own AI provider, with only OpenAI currently supported for version 16.4.

  • Content editors now have enhanced visibility into document lifecycle, as the depublicationDate and depublishedBy properties are now displayed in the document information dialog.

  • An important LDAP synchronization retry mechanism has been implemented6. This addresses a critical issue where users might be removed from JCR if communication with the LDAP server is interrupted during the sync process, thereby improving system stability and data integrity.

  • The Advanced Search functionality has been enhanced to allow documents to be properly selectable for custom workflows even for users who do not possess hippo:editor privileges1. A new configuration option has been added to SearchViewPlugin to align these permission checks, which streamlines workflow management for a wider range of users.

  • The slf4j logging library has been upgraded from 1 to 2 (see below)

See the 16.4.0 release notes for a full list.

Upgrade Steps

Perform Generic Minor Upgrade Steps

Follow the generic instructions for minor upgrades.

Replace the Log4j-Slf4j Bridging Library to Slf4j 2

The latest SLF4J 1 version 1.7.36 is no longer actively developed, so it has been upgraded to 2.0.17, along with a log4j upgrade from 2.23.1 to 2.24.3. This requires changing the bridging jar log4j-slf4j-impl to version 2 as well. As this jar is
located in Tomcat's shared lib this has impact on Maven profiles and the distribution configuration, therefore in your code base:

  • Rename all occurences of "log4j-slf4j-impl" to "log4j-slf4j2-impl", typically in the Maven profiles "dist" and "dist-with-development-data" and in assembly file "shared-lib-component.xml"
  • Search for occurrences of Maven property "slf4j.version" and replace with "slf4j2.version" (in a standard project, no occurences expected).

Note: at deployment time, be sure that the old "shared/lib/log4j-slf4j-impl.jar" file is removed. Best practice is to delete the whole "shared/lib" and have it repopulated.

Detailed Release Notes

See also the detailed release notes for more information.

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?