HP UX 11i Workload Management (gWLM/WLM) Software manual

gwlmagent.properties on Windows. (The given Windows path is the default; however, a different path might have been selected at installation.)

NOTE: You must restart the gwlmagent daemon on each managed node where you have modified the properties file for the changes to the file to take effect.

The gwlmagent.properties file is shown below.

#

#(C) Copyright 2004-2007 Hewlett-Packard Development Company, L.P.

#$Date: 2008/12/02 20:17:18 $

#$Revision: 1.1 $

#

#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

#

#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 movement of

#cores across nPartitions. To use iCAP, you must enable this property on

Setting gWLM properties 39