TIBCO Spotfire Server 3.2.2 - TIBCO Product Documentation

Technical Reference
11.1.4 Console Debugging:
All levels of logging are also available in "Console Debugging" versions:
• log4j-minimal-with-console.properties
• log4j-with-console.properties
• log4j-debug-with-console.properties
• log4j-debug-soap-with-console.properties
• log4j-trace-with-console.properties
• log4j-trace-soap-with-console.properties
These should only be used temporarily when running the server in console mode. This
will provide real-time logging in a console window.
Do NOT use these while running the Spotfire Server as a Windows service, since this
may rapidly create huge log files.
11.1.5 Log Files
TIBCO Spotfire Server uses rolling logs, which means that when a log file gets too big
it splits into several files. These are indexed by a number, (the higher the number, the
older the log) and can be selected in the drop-down list in the Server Log Files
interface. When a rolled log file reaches a certain number it is deleted.
The log files are located in the /tomcat/logs/spotfire,
/tomcat/logs/admin, and /tomcat/logs/
controller directories.
There are several log files that you can configure and view:
Server Log
SQL Log
SOAP Log
Actual file located in /tomcat/logs/spotfire/
dss.log.
This file logs all activity on the server except the events recorded in the
Server Access Log. It includes the SQL log and a simplified version of
the Server Access log. You can set the detail level of what this file logs by
selecting different Log Configuration Files.
Actual file located in /tomcat/logs/spotfire/
sql.log.
This file logs the SQL that is generated each time a user executes an
information link. You can set the detail level of what this file logs by
selecting different Log Configuration File.
This log stores information about the SOAP communication on the
server.
TIBCO Spotfire® Server 3.2.2 133 (144)