SCORM Engine Logging (Default Java Implementation)


Default SCORM Engine Logging (Java)

By default the Java version of SCORM Engine utilizes Java's built-in logging API. This is done via a single logger named "com.rusticisoftware.scormcontentplayer". Logging messages are routed through three different Integration methods. The DefaultIntegration class just forwards these to the logger at three different logging levels:

DefaultIntegration.LogError() - Logs at "Error" level 
DefaultIntegration.LogAudit() - Logs at "Info" level 
DefaultIntegration.LogDetail() - Logs at "Debug" level 

Note: Customers are welcome to overrride these methods to use a logging library of their choosing, but by default this is what happens.

Configuration for java.util.Logging happens via a file. There is a default version of this at JAVA_HOME/lib/ However, usually there will be a file found further up the classloader hierarchy. It can also be explicitly passed in when starting the app server with "java -Djava.util.logging.config.file=myLoggingConfigFilePath".


Tomcat logging should be configured via the file at TOMCAT_HOME/conf/ By default, the SCORM Engine logger "com.rusticisoftware.scormcontentplayer" will write to the default handler which means messages are written to TOMCAT_HOME/logs/catalina*.log files. To create a separate log file for SCORM Engine append the following to this

Add this handler to the list of "handlers": org.apache.juli.FileHandler so it will look something like this:

handlers =,,,,, java.util.logging.ConsoleHandler, org.apache.juli.FileHandler

Add the following lines:

org.apache.juli.FileHandler.level = FINE = ${catalina.base}/logs
org.apache.juli.FileHandler.prefix = scormengine.

Other Web Containers

The files still defines where logs are kept, but this file's location will vary with each app server. If no file is defined, the JAVA_HOME/lib/logging.propoerties file will be used.

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request


Powered by Zendesk