WebSphere brand IBM WebSphere Premises Server, Version 6.1.x

Logging

If you are unable to resolve technical problems, this topic describes log files, and the process for gathering log files and sending them to your IBM® services representative.

Logging levels

The following table lists the available log levels and their meanings.

Table 1. Available log levels and descriptions
Log level Description
OFF No events are logged.
FATAL Task cannot continue and component cannot function.
ERROR Task cannot continue, but component can still function.
WARN Potential error or impending error.
INFO General information outlining overall task progress.
CONFIG Configuration change or status.
DETAIL General information detailing subtask progress.
FINE Trace information - general trace + method entry / exit / return values.
FINER Trace information - detailed trace.
FINEST Trace information - a more detailed trace that includes all the detail that is needed to debug problems.
ALL All events are logged. Can provide a more detailed trace than FINEST.

A message is logged if the logging request's priority is greater than or equal to the currently assigned priority of the utilized logger. For example, if you have a logger with an assigned log level of INFO, then an ERROR request will pass the approval, but a DETAIL request will be blocked. Level ALL causes a logger to accept all logging request; OFF blocks all requests.

Configuring logging

Follow these steps for configuring logging:

  1. Modify the WAS_HOME\lib\ext\log4j.properties file to modify logging for the Location Awareness Services for WebSphere® Premises Server components.
  2. Restart WebSphere Application Server.

Log files are stored in the WAS_HOME\profiles\profile_name\logs directory.

Turning off logging

For Location Awareness Services for WebSphere Premises Server, logging is performed within the Apache log4j framework that has been designed for simplicity and performance. Turning off all logging is not recommended. It is strongly recommended that you at least keep the ExceptionLogger turned on. However, if you want to turn logging off, perform the following steps:
  • Set the rootLogger to OFF.
  • To turn off the com.ibm.atlas logger, set its level to OFF and its additivity parameter to false .
  • To turn off the com.ibm.atlas.exception.ExceptionLogger, set its level to OFF and its additivity parameter to false.

For more information on how to configure logging, consult the log4j-documentation available at: http://logging.apache.org/log4j/docs/documentation.html

Gathering logs

  1. Collect the following log files (for example, as .zip files):
    • For WebSphere Application Server:
      • WAS_PROFILE_HOME\logs\General.log
      • WAS_PROFILE_HOME\logs\Atlas.log
      • WAS_PROFILE_HOME\logs\AtlasException.log

      Additional logs are found in the WAS_PROFILE_HOME\logs\server1directory.

    • For the Spatial Management Client: IHS_HOME\htdocs\en_US\Tracking GUI\logs
  2. Send the files to your IBM services representative.

Library | Support | Terms of use

(c) Copyright IBM Corporation 2004, 2008. All rights reserved.
U.S. Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.