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

Use log4 v1.x at runtime with Bloomreach Experience Manager 12

While Bloomreach Experience Manager 12 now requires log4j2 for development and by default also at runtime, it still is possible, if really needed, to use log4j v1.x at runtime.

In order to create a CMS 12 distribution with log4j v1.x, the following actions should be executed:

Open distribution archive:

1. Under conf folder replace log4j2.xml with a valid log4j.xml.

2. Under shared/lib folder replace the following files (specific versions may change/differ):

jcl-over-slf4j-1.7.25.jar
log4j-api-2.8.2.jar
log4j-core-2.8.2.jar
log4j-slf4j-impl-2.8.2.jar
slf4j-api-1.7.25.jar

with this list:

jcl-over-slf4j-1.7.6.jar
log4j-1.2.17.jar
slf4j-api-1.7.6.jar
slf4j-log4j12-1.7.6.jar
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?