Setting gWLM Properties

# (C) Copyright 2004-2006 Hewlett-Packard Development Company, L.P.
#
# $Date: 2006/05/19 17:52:24 $
# $Revision: 1.18 $
#
# Contents:
#       This file contains the default configuration values for the
#       Global Workload Manager CMS.
#
#       You must restart gwlmcmsd for changes made to this file
#       to take effect--unless otherwise noted.
#
 
#
# Set FileHandler /var/opt/gwlm/gwlmcmsd.log.0 log level.
# Valid levels, from most severe to least, are:
#       SEVERE
#       WARNING
#       INFO
#       CONFIG
#       FINE
#       FINER
#       FINEST
# When you set the level, you will see messages only from that level and
# the levels that are more severe. So, the SEVERE level produces the fewest
# messages, while the FINEST level includes messages from all seven levels.
#
com.hp.gwlm.util.Log.logLevel = INFO
 
#
# Turn on/off ConsoleHandler. ConsoleHandler uses the same log
# level as defined for FileHandler /var/opt/gwlm/gwlmcmsd.log.0.
#
com.hp.gwlm.util.Log.ConsoleHandler = off
 
#
# Support for the database cache on the CMS.
#
#   cachesize:
#       The number of database objects that should be cached in memory
#       in order to reduce the number of round-trip operations.
#
com.hp.gwlm.cms.cachesize = 70000
 
 
 
# Support for local data caching on a remote node for report generation.
# These properties are defined on the CMS but are pushed out to the remote
# node managers during deployment of an SRD.  The cached objects on the
# agent consume an amount of memory approximated by:
#
#    Memory = 5000 * workloads * cachesize * (60 / resource_domain_interval)
#
# bytes of memory.  For example, if there are 4 workloads deployed with a
# 15 second interval and a cachesize of 20 minutes, the agent will need:
#
#    Memory = 5000 * 4 * 20 * (60 / 15) ~ 2.5 MB.
 
#
#   cachesize:
#       The number of minutes of real-time data to maintain on the remote
#       node for future CMS access.  This value must be at least three
#       times the ‘samples’ value specified below.  The default value is
#       20 minutes.
#
#   samples:
#       The number of minutes of real-time data used to aggregate into a
#       historical data point. The default is to aggregate the data into
#       5-minute averages.
#
com.hp.gwlm.node.cachesize = 20
com.hp.gwlm.node.samples   = 5
 
#
# Support for real-time graphing properties.
#
#   viewport:
#       The size of the displayed real-time graph (in minutes).
#
#   refresh:
#       The refresh rate of the real-time graphs and tables (in seconds).
#
com.hp.gwlm.ui.monitor.viewport = 15
com.hp.gwlm.ui.monitor.refresh  = 15

#
# (C) Copyright 2004-2006 Hewlett-Packard Development Company, L.P.
#
# $Date: 2006/05/19 17:52:23 $
# $Revision: 1.13 $
#
# Contents:
#       This file contains the default configuration values for the
#       Global Workload Manager Agent on a given managed node. The
#       agent on each managed node uses the default values unless you
#       edit that node’s gwlmagent.properties file.
#
#       You must restart gwlmagent for changes made to this file to
#       take effect.
#
 
#
# Set FileHandler /var/opt/gwlm/gwlmagent.log.0 log level.
# Valid levels, from most severe to least, are:
#       SEVERE
#       WARNING
#       INFO
#       CONFIG
#       FINE
#       FINER
#       FINEST
# When you set the level, you will see messages only from that level and
# the levels that are more severe. So, the SEVERE level produces the fewest
# messages, while the FINEST level includes messages from all seven levels.
#
com.hp.gwlm.util.Log.logLevel = INFO
 
 
 
 
# Specify the size (in MB) and number of files to use  
# for logging. For a single file of unlimited size, set
# logFileSize to negative one (logFileSize=-1).
# Otherwise, total log file size is
#    logFileSize * logNFiles
#
com.hp.gwlm.util.Log.logFileSize = 20
com.hp.gwlm.util.Log.logNFiles = 3
 
#
# Turn on/off ConsoleHandler. ConsoleHandler uses the same log
# level as defined for FileHandler /var/opt/gwlm/gwlmagent.log.0.
#
com.hp.gwlm.util.Log.ConsoleHandler = off
 
#
# Set the number of seconds for the high availability (HA) minimum
# timeout. Communication is considered lost on a managed node
# once the timeout period has elapsed.
#
# By default, communication is not considered lost until 10 allocation
# intervals have elapsed without communication. The default value of the
# property (60) is used only when the allocation interval is less than 6
# seconds.  
#
com.hp.gwlm.node.HA.minimumTimeout = 60
 
#
# Enable/disable use of Instant Capacity (iCAP) to simulate CPU movement
# across nPartitions. To use iCAP, you must enable this property on each
# managed nPartition where you want to take advantage of iCAP. Also, each
# nPartition must meet the requirements outlined in the online help topic
# “Getting the most out of gWLM” as well as in the section “USING NPARS AS
# COMPARTMENTS IN AN SRD” in the gwlmxml(4) man page on HP-UX or the
# gwlmxml(5) man page on Linux.
#
com.hp.gwlm.platform.icap.manageWithIcap = on