The CloverETL Server uses the log4j library for logging. The WAR file contains the default log4j configuration.
By default, log files are produced in the directory specified by system property "java.io.tmpdir" in the "cloverlogs" subdirectory.
"java.io.tmpdir" usually contains common system temp dir i.e. "/tmp". On Tomcat, it is usually "[TOMCAT_HOME]/temp"
The default logging configuration may be overridden by system property "log4j.configuration", which should contain the URL to log4j config file.
Since such a configuration overrides the default configuration, it may have influence over Graph run logs. So your own log config has to contain following fragment to preserve Graph run logs
<logger name="Tracking" additivity="false"> <level value="debug"/> </logger>
These system properties allow for logging of HTTP requests/responses to stdout:
(for more information consult CloverETL Designer Users's Guide - chapter
Integrating CloverETL Designer with CloverETL Server)
Each graph or jobflow run has its own log file – for example, in the Server Console, section "Executions History".
By default, these log files are saved in the subdirectory cloverLogs/graph in the directory specified by "java.io.tmpdir" system property.
It’s possible to specify a different location for these logs by the CloverETL property "graph.logs_path". This property does not influence main Server logs.