Release Notes

10.0 HotFix 1

Back Next

Logging improvements

Logging in Product 360 has been updated to run with

log4j2

. This means that a number of configuration files have been changed to support the newer version of

log4j

. Besides changes made in

log4j

configuration files, the wrapper.conf files needed to be adjusted too in order to configure the path to the new

log4j2.xml

configuration. The following code snippet is an example for the Audit Trail component:

wrapper.conf
# Old configuration to specify the path to log4j.xml

wrapper.java.additional.11=-Dlog4j.configuration=file\:configuration/audittrailserver/log4j.xml

vs.
# New configuration to specify the path to log4j2.xml

wrapper.java.additional.11=-Dlog4j2.configurationFile=configuration/audittrailserver/log4j2.xml

wrapper.java.additional.12=-Dorg.apache.commons.logging.LogFactory=org.apache.commons.logging.impl.LogFactoryImpl

Please note that the variable to the

log4j

path has also changed inside the

log4j2.xml

file. Instead of using

${pim.log4j.path}

, you now need to use

${sys:pim.log4j.path}

to access the

log4j2

path.

Platform Enhancements