This chapter describes how to resolve problems you encounter in Oracle Communications Convergence.
This section covers how to configure log levels for the Convergence server. Log levels can be set by using the iwcadmin command.
For more information on the iwcadmin command, see "Using the Convergence Administration Utility" for more information.
The following are the log configuration parameters:
LogLocation: Path to the directory where the log file is stored.
LogPattern: Declares the information and format to specify what to log and in what format. For more information about how to specify the LogPattern, see the Log4J specification on the Apache web site:
http://logging.apache.org/log4j/1.2/apidocs/org/apache/log4j/PatternLayout.html
LogRotation: Log rotation specifies the policy for rolling over logs to a new location. This release includes the following policies:
SizeTrigger policy: SizeTrigger is defined as the number of bytes of log information to accumulate before rolling the log over to a new location.
TimeTrigger policy: TimeTrigger is defined as the time of day to roll over the log to a new log location. The value is expressed as a SimpleDatePattern.
Logger: The initial system Logger value is DEFAULT, that takes the default LogLevel. However, each module in Convergence can control the logging level of its own logs. For example, the authentication module might name its logger AUTH and set the log level to WARN. To know more about the various logging levels, see "About Log Levels" for more information.
Logging levels (LogLevel) are set using a predefined default set of log levels. For example:
DEBUG
INFO
WARN
ERROR
OFF
The DEBUG level is the most verbose level. Do not to use this for everyday logging as it negatively impacts the server's performance. However, you should use this level when you need to trap as much information about a recurring problem. After capturing the required log data, you should return the log level to a lesser level of log setting.