The Content Engine uses the Apache log4j utility to handle logging. log4j is very flexible: among other things, it allows the logging level to be changed without restarting the Content Engine.

By default, the Content Engine outputs log messages to System.out, which means the application server's log file. You can, however, change this (and many other log settings) by creating a trace.properties file and adding it to your application server's classpath. An easy way of doing this is:

  1. Copy the supplied template trace.properties file from /opt/escenic/engine/classes to the root folder of your common configuration layer (/etc/escenic/engine/common).

  2. Edit the copied file (see Editing trace.properties).

  3. Most application servers have a folder whose contents are automatically added to the classpath. Create a symbolic link to your trace.properties file in this folder. If you use Tomcat, for example, you can make sure your trace.properties is added to the classpath by entering:

    $ cd /opt/tomcat/lib/
    $ ln -s /etc/escenic/engine/common/trace.properties

If you do this, then any changes you make to trace.properties will take effect the next time you start the application server.