Skip to main content
Jump to: navigation, search

COSMOS Logging

Revision as of 15:43, 13 May 2008 by (Talk | contribs) (Logging Configurations)

Logging for Web Applications and Web Services

Log4j will be used to do logging in web applications (such as the COSMOS UI) and web services (data managers). Information about log4j can be found at the log4j website.

Logging Configurations

To configure a web applciation to use log4j, we need a configuration file called in the classpath, usually put under WebContent/WEB-INF/classes. Axis2.jar comes with a that contains some default settings.

The installation/configuration program of the COSMOS demo should update the file to include settings appropriate for the COSMOS demo. Deployers can also customize the logging settings.

In order to log all log entries to the same log file, we need to add the following lines to the

# Configure all classes in the org.eclipse.cosmos namespace to use the COSMOSLOG logger
# Change "ALL" to the desired log level, COSMOSLOG

# COSMOSLOG is set to be a File appender using a PatternLayout.
log4j.appender.COSMOSLOG.layout.ConversionPattern=%d [%t] %-5p %c %x - %m%n

The above configuration will write the logs to cosmos.log file in the logs directory under the Tomcat install directory. 

We can also configure log4j to open a log file for each web application or web service, assume each web application or web service has a unique package namespace.  For example, if we want the broker to have a separate log file, we can add the following lines to the
# Logger for COSMOS Broker, BROKERLOG

# COSMOSLOG is set to be a File appender using a PatternLayout.
log4j.appender.BROKERLOG.layout.ConversionPattern=%d [%t] %-5p %c %x - %m%n

Logging API

Log Levels

Naming Convention for Message Keys

Externalize log messages

Logging for Eclipse Plugins

Back to the top