CloverETL Server uses log4j library for logging. WAR file contains default log4j configuration.
By default, log files are produced in directory specified by system property "java.io.tmpdir" in "cloverlogs" subdirectory.
"java.io.tmpdir" usually contains common system temp dir i.e. "/tmp". On tomcat, it is usually "[TOMCAT_HOME]/temp"
Default logging configuration may be overridden by system property "log4j.configuration", which should contain URL to log4j config file.
log4j.configuration=file:/home/clover/config/log4j.xml
Since such configuration overrides 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 logging of HTTP requests/responses to stdout:
client side:
com.sun.xml.ws.transport.http.client.HttpTransportPipe.dump=true
(for more information consult CloverETL Designer Users's Guide - chapter
Integrating CloverETL Designer with CloverETL Server)
server side:
com.sun.xml.ws.transport.http.HttpAdapter.dump=tru
Each graph run has it is own log file, which is accessible i.e. in web GUI, section "executions history".
By default these log files are produced in subdirectory cloverLogs/graph in the directory specified by "java.io.tmpdir" system property.
It is possible to specify different location for these logs by CloverETL property "graph.logs_path". This property does not have any influence over main server logs.