HP StorageWorks XP Command View Advanced Edition Software 6.4 Server Administrator Guide for Device Manager and Provisioning Manager (web) (T1780-96341, July 2010)

Appendix A Specifying properties
195
A-4-4 logger.hbase.loglevel
In this property, you can specify the verbosity level for each operation (trace) log file and error log
file written by Common Component. The log files are HDvMtracen.log, HDvMGuiTracen.log,
and HDvMGuiMessagen.log, where n is an integer that represents the backup number for the file.
Each logging event has its own importance level independent from its type (error, warning, and
information). The levels, in increasing order of importance, are: 30, 20, 10, and 0. The default
logging level for production systems is 20, which means that messages for logging event levels 20,
10, and 0 are written into the HDvMtrace1.log, but messages for logging event level 30 are not.
Default: 20
A-4-5 logger.hbase.sysloglevel
In this property, you can specify the verbosity level for the operation (trace) log data and error log
data written to the event log (in Windows) or to syslog (in Linux) by Common Component. Each
logging event has its own importance level independent from its type (error, warning, and
information). The levels, in increasing order of importance, are: 30, 20, 10 and 0. The default
logging level for production systems is 0, which means that messages for only the logging event
leveled 0 are written into the EventLog (Windows) or the syslog (Linux) but messages for the
logging event leveled 30, 20, and 10 are not. The default value is recommended.
Default: 0
A-4-6 logger.hbase.MaxBackupIndex
In this property, you can specify the maximum number of backups for each trace and error log file
that is written by Common Component. The log files are HDvMtracen.log,
HDvMGuiTracen.log, and HDvMGuiMessagen.log (the n in the file name indicates the backup
generation number of the file). Valid values are from 1 and 16. When a log file reaches its maximum
length, its filename is modified by increasing a counter (for example, for example, HDvMtrace2). As
more backup log files are created, their counter or version suffix is incremented (for example,
HDvMtrace2.log becomes HDvMtrace3.log), 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.
Default: 10
A-4-7 logger.hbase.MaxFileSize
In this property, you can specify the maximum size of each operation (trace) log file and error log file
that is written by Common Component. The log files are HDvMtracen.log,
HDvMGuiTracen.log, and HDvMGuiMessagen.log (the n in the file name indicates the backup
generation number of the file). The specified size is assumed to be in bytes unless you specify KB
for kilobytes, MB for megabytes or GB for gigabytes. Valid values are from 4096 to 2147483647
(less than 2 GB).
Default: 5 MB
A-5 Device Manager dispatcher properties
The dispatcher.properties file contains the dispatcher properties.
• In Windows:
installation-folder-for-the-Device-Manager-
server\Server\config\dispatcher.properties
• In Linux: