HP StorageWorks XP Command View Advanced Edition software Device Manager server installation and configuration guide (web version) (T1780-96078, March 2008)

Device Manager server properties
200
8-3-3 dbm.startingCheck.retryPeriod
This property specifies the interval (in seconds) the Device Manager server will retry whether DBMS
has started when the server is launched. The specifiable values range from 0 to 60 (seconds) As a
general rule, you do not need to change this setting.
Default: 10 seconds
8-4 Logger properties
Logger properties are contained in the logger.properties file.
This properties file contains a set of directives that configure 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, error.log, service.log, stdout.log,
stderr.log, and trace.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 (where n
is an integer that represents 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
8-4-1 logger.loglevel
In this property, you can specify the verbosity level for the trace log (trace.log) and error log
(error.log). The values accepted in this field are (in decreasing order of detail): DEBUG, INFO,
WARN, ERROR, and FATAL. The default logging level for production systems is INFO, which
means that warnings and error messages are written into the trace and error logs, but debugging or
informational entries are not.
Default: INFO
8-4-2 logger.MaxBackupIndex
In this property, you can specify the maximum number of backups for each log file (for
access.log, error.log, service.log, stdout.log, stderr.log, statuscheck.log, and
trace.log). If this property is set to zero, no rolling backups are created, and log files are simply
truncated when their maximum file size is reached. When a log file reaches its maximum length its
filename is modified by appending a counter, for example, access.log.1. As more backup log files
are created, their counter or version suffix is incremented (for example, access.log.1 becomes
access.log.2), until the specified number of rolling backups have been created. After that, the oldest
backup log file is deleted each time a new backup is created. You can specify a range of 1 to 20.
Default: 10
8-4-3 logger.MaxFileSize
In this property, you can specify the maximum size for each log file (for access.log, error.log,
service.log, stdout.log, stderr.log, statuscheck.log, and trace.log). Unless KB is
specified for kilobytes or MB for megabytes, bytes is assumed. In this property, the term KB is
interpreted as 1024 bytes, and MB as 1024 kilobytes.
Specifiable range: from 512 KB to 32 MB
Default: 1 MB