HP P9000 Command View Advanced Edition Suite Software 7.4.0-00 Administrator Guide (web) (TB581-96325, December 2012)

Device Manager log output properties (logger.properties file)
The logger.properties file contains the log output properties.
• In Windows:
installation-folder-for-the-Device-Manager-server\Server\config\log-
ger.properties
• In Linux:
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
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
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 size (as specified in logger.MaxFileSize), the file is renamed
by adding a counter (which represents the version) to the file name. For example, access.log
becomes access.log.1. 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
Device Manager server properties356