Logging

Logging for the Business Analysis and Reporting Component is following the general concepts of logging in Stardust products.

Configuration

Please create the subdirectories <user.home>/log and <current directory>/log, where the logging will take place. In this case user.home is the user's home directory when you startup a JVM. You can find it with the command:

System.out.println(System.getProperty("user.home"))

The current directory is the directory where you startup your application server. This maybe the bin directory of your JBoss or your Tomcat installation.

Logging for the Business Analysis and Reporting Component is configured using the following properties in the carnot.properties file, residing in the Stardust plugin.

Logging.Directory = c:/temp/
Logging.LogLevel = DEBUG

The log level DEBUG is only relevant if you need to analyze problems with the Business Analysis and Reporting Component together with the Stardust Support Organization. Normally, you would use the log level ERROR, where only internal and public exceptions are logged.

You can set debug logging parameters with the Java parameter carnot.log.debug.filter. It expects a comma separated list of classes and packages that you want to log in debug mode. You can set this parameter as part of your application server startup script.

Example:

-Dcarnot.log.debug.filter=org.eclipse.stardust.reporting.AbstractProcessInstanceView, org.eclipse.stardust.reporting, org.eclipse.stardust.reporting.oda

Log Files

Three different log files are created under Logging.Directory:

• carnot-processdatabase-log.txt containing all log events for the Stardust Process Database data source,
• carnot-processmodel-log.txt containing all log events for the Stardust Process Database data source,
• carnot-reporting-log.txt containing log events of the facilities used by both data sources.