HP P9000 Command View Advanced Edition Suite Software 7.3.1-00 Administrator Guide (web)

installation-directory-for-the-Device-Manager-server/Server/config/
logger.properties
This property file contains a set of directives that configure the Device Manager server's logging
module, including the names, locations and verbosity level of the various operation and error log
files. You can also use this file to configure trace logging for debugging and diagnostic purposes.
The properties logger.loglevel, logger.MaxBackupIndex, and logger.MaxFileSize are
applied to the following files: access.log.n, cim_access.log.n, error.log.n,
service.log.n, stdout.log.n, stderr.log.n, statuscheck.log.n, trace.log.n,
CIMOMTracen.log, and SMISClientTracen.log.
The properties logger.hbase.loglevel, logger.hbase.MaxBackupIndex, and
logger.hbase.MaxFileSize are applied to the following files: HDvMtracen.log,
HDvMGuiTracen.log, and HDvMGuiMessagen.log.
The n in the file name indicates the backup generation number of the file.
The Windows event log is viewable in the Event Viewer. The default syslog is specified in /etc/
syslog.conf
logger.loglevel
In this property, you can specify the verbosity level for the trace.log.n, error.log.n,
CIMOMTracen.log, and SMISClientTracen.log (the n in the file name indicates the backup
generation number of the file). The values accepted in this field are (in decreasing order of detail):
DEBUG, INFO, WARN, ERROR, and FATAL. If this property is set to the default, entries whose verbosity
level is either INFO, WARN, ERROR, or FATAL are written into the trace.log.n. In this case, entries
whose verbosity level is DEBUG are not written into the logs.
Default: INFO
logger.MaxBackupIndex
In this property, you can specify the maximum number of backups for the access.log.n,
cim_access.log.n, error.log.n, service.log.n, stdout.log.n, stderr.log.n,
statuscheck.log.n, trace.log.n, CIMOMTracen.log, and SMISClientTracen.log.
The n in the file name indicates the backup generation number of the file. When a log file reaches
its maximum length, its filename is modified by appending a counter, as in access.log.1, for
example. As more backup log files are created, their counters or version suffixes are incremented (for
example, access.log.1 becomes access.log.2), until the specified number of backups have
been created. After that, the oldest backup log file is deleted each time a new backup is created.
Specifiable values are from 1 to 20.
Default: 10
logger.MaxFileSize
In this property, you can specify the maximum size for the access.log.n, cim_access.log.n,
error.log.n, service.log.n, stdout.log.n, stderr.log.n, statuscheck.log.n,
trace.log.n, CIMOMTracen.log, and SMISClientTracen.log (the n in the file name indicates
the backup generation number of the file). If the maximum size is exceeded, a new log file is created.
Unless KB is specified for kilobytes or MB for megabytes, the specified size is interpreted to mean
bytes.
Administrator Guide (Web Version) 351