System event logging

The system event logging facility of WebSphere Portal enables the recording of information about the operation of WebSphere Portal.

Event logs provide administrators with information on important or abnormal events, especially errors that occur during the operation of the product. In addition, event logs gather debugging information that helps IBM support to resolve problems.

WebSphere Portal provides two types of logging: logging of messages and logging of debugging messages called traces.

For information about how to use log files and a list of trace logger strings refer to the topic about WebSphere Portal logs.

This topic has the following sections:


Message logging

WebSphere Portal provides the logging of messages that report errors and status information.

The following types of messages are provided:
Informational


Warning


Error

Messages for WebSphere Portal are logged in the following files:

SystemOut.log

System.err


Locating the log files: Log files for WebSphere Portal, including SystemOut.log and System.err are located in... WP_PROFILE/logs/WebSphere_Portal


Trace logging

WebSphere Portal provides the logging of debugging messages called traces. These traces are useful for fixing problems. However, to save system resources, they are switched off by default.

Traces can be set for different durations:
Temporary


Extended


Change the log file name and location

You can change the locations of the log files by configuring them in the WAS administrative console. Select Troubleshooting -> Logs and Trace -> server_name and select the logger type that you want to change. In the configuration dialog change the path for the log file as required. For a description of the available types of log files refer to the WAS information center.


Change the language used in the log file

By default, information in the log file is written in the language that was used for the WebSphere Portal installation. However, because WebSphere Portal supports a number of languages, you can choose to have the log file information written in a language other than that used during installation.

To change the language used for the log file, edit the file log.properties. This file is located in the following WebSphere Portal directory:

Add the following line:

locale=xx 

where xxis the two-letter abbreviation for the locale. For a list of the locale abbreviations used with WebSphere Portal, refer to Directories for languages. For example, to have log information generated in English, you would add the following line:

 locale=en 


Reference: Log file format

If the logs are written to the log file of WebSphere Portal and not redirected to the logging facility WAS, the log file consists of a sequence log records that are separated by blank lines.

The log records have the following format:

     timestamp classification classname method threadID
     messagecode: logmessage

Where:

  1. Traces are written only if the specific tracing facility is enabled; all other messages are written unconditionally.

  2. The system locale is part of the general internationalization features of WebSphere Portal and can be configured via LocalizerService. For more information refer to the topics about Setting service configuration properties and about the Portal configuration services.

The following is an example of a log record:

2011.05.16 13:36:14.449 W com.ibm.wps.services.datastore.DataStoreServiceImpl init 0000003a
DSTO0063W: The transaction isolation level is not set to READ_COMMITTED.
 
The current value is TRANSACTION_REPEATABLE_READ.


Parent

Logging and tracing


Related tasks


Set service configuration properties
Portal configuration services

WAS V 7.0 Log and trace settings

 


+

Search Tips   |   Advanced Search