NonStop Server Guide for BEA WebLogic Server 9.2

Configuring Persistent WebLogic Server Processes
HP NonStop Server Guide for BEA WebLogic Server 9.2—529891-002
4-11
gname_load
The variable WLS_LOADBAL_FUNC determines the load-balancing algorithm used to
compute the loads. The next section describes how each load-balancing function
computes the current load. The sections also identify the files and environment
variables that are used.
gname_load
gname_load uses Guardian process names to calculate the current load. The process
names are specified using the environment variable WLS_GNAMES, which is a space-
separated list of Guardian process names without the leading dollar sign
(WLS_GNAMES="ms1 ms2 ms3 ms4"). gname_load then determines the CPU
where the process is being executed and calculates the aggregate load per CPU. To
allow Managed Servers to be started with a Guardian process name, the WLS_GNAME
variable is used.
You must consider two things when using gname_load. One, the process names
listed in WLS_GNAMES can be any valid Guardian process name; there is no
requirement that the process names only reference WebLogic Server processes. Two,
WLS_GNAMES is used to determine the processes that are running; WLS_GNAME
(without the "S") assigns a process name to the Managed Server being started.
jvm_load
Using CPUselector has changed this existing function. A new variable,
WLS_JVM_PATHNAMES, determines which executables should be queried when
computing the load. WLS_JVM_PATHNAMES is a colon-separated list of OSS
executables. For example,
WLS_JVM_PATHNAMES/usr/tandem/nssjava/jdk150_h50/bin/java" causes
every process using that executable to be included in the load. Likewise,
WLS_JVM_PATHNAMES="/usr/bin/java:/bin/ksh" causes both executables to
be included in the aggregate load.
The above example implies that any valid OSS executable name can be included in
WLS_JVM_PATHNAMES. However, avoid including the same executable more than
once. This can happen if a hard link or symbolic link is included because the algorithm
first converts the OSS pathname to the corresponding Guardian filename, and then
does a status for processes using that program filename. If the WLS_JVM_PATHNAMES
includes the same Guardian filename twice because the OSS file is a link, the load will
be added twice. For example, if /usr/bin/jre/java is a symbolic link to
/usr/bin/java, then setting WLS_JVM_PATHNAMES to
"/usr/bin/java:/usr/bin/jre/java" causes the same processes to be
included in the total twice.
managed_load
managed_load computes the current load by using files maintained by the Node
Manager. Each time a Managed Server starts, its pid is written to a file. This function
reads each pid and determines which CPU is being executed by the process. The list