Sage CRM 2020 R2: Changes in logging associated with Java based features

1 minute read time.

Sage CRM provides logging that covers all of its internal actions. There are two parts to this logging which reflect Sage CRM's hybrid architecture. The configuration of the logging associated with the main user interface - the Company, Person and Opportunity screens etc is configured within the product administration screens here:

Administration → System → Logging

These are all features that are driven through the 'eWare.dll'. But the other side to the Sage CRM's hybrid architecture is enabled through java webapps running under Apache Tomcat. The logging for these features is controlled within a configuration file formatted using XML.

In Sage CRM 2020 R2 the location and name of the file has changed.

In Sage CRM 2020 R1 and earlier

To control logging on the Sage CRM server you would need to locate and open the following file:

<Sage CRM installation folder>\tomcat\webapps\<InstallName>j\WEB-INF\log4j.xml


<Sage CRM installation folder> is the folder you specified when installing Sage CRM. By default, this is %ProgramFiles(x86)%\Sage\CRM\CRM.
<InstallName> is the Sage CRM installation name. By default, this is CRM.



In Sage CRM 2020 R2 onwards

On the same Sage CRM server file has changed location and name

<Sage CRM installation folder>\tomcat\webapps\<InstallName>j\WEB-INF\classes\log4j2.xml



Automatic archiving of log files.

Sage CRM 2020 R2 has added automatic archiving of log files. If logging is kept running on a machine then logs can rapidly grow but now when the size of a log file exceeds 500 MB, the file is automatically moved to a gzip archive located in the folder where the log file originally resided.

Each archive created will have the the following name and extension:


where %i is the increment number assigned to the archive.