WebLogic Server (WLS) 7.0

Configuring Persistent WebLogic Server Processes

HP NonStop Server Platform Guide for WebLogic Server—525779-001

3-7

nodemanager.sh

The node manager can be used to start managed servers. On NonStop servers, native

process control is not used. The node manager must be started by using:

weblogic.nodemanager.nativeVersionEnabled = false

The node manager invokes, by default, a shell script named nodemanager.sh to start

the managed server.

The node manager passes four arguments to the script:

•

Java command-line

•

stdout to use

•

stderr to use

•

filename to which the PID of the Java process should be written

Therefore, the nodemanager.sh could be as simple as:

#!/bin/sh

java $1 >$2 2>$3 &

echo $! > $4

To take advantage of the NonStop server multi-CPU architecture, a sample script is

provided that will balance the managed servers throughout the system. By default, the

script can be found in $WL_HOME/server/lib/unix under the filename

nodemanager.sh. The script should be modified for your installation as described in

the script itself.

The nodemanager.sh contains the basic infrastructure to:

•

Determine what CPUs are running and not excluded from consideration

•

Start the WebLogic Server process

•

Place the PID in the appropriate file

nodemanager.sh allows different load balancing functions to be used in deciding

what CPUs should be selected. There are currently two such functions: jvm_load and

managed_load. Once the load balancing function has calculated the current load, the

process is started in the CPU with the lightest load.

jvm_load, the default function, attempts to find all currently running Java processes

and determines what CPUs they are running in. The function assumes the Java

executable is located in /usr/tandem. If a non-standard location is being used, the

script can be modified as appropriate. This algorithm is simple and effective.

managed_load balances the server load by using information maintained by the

WebLogic Server. The MonitoredProcessList is read to obtain a list of servers the

node manager is managing and calculates the number of servers per CPU. One

consequence of this algorithm is that all managed servers monitored by the node

manager are considered when choosing a CPU. Therefore, if multiple WebLogic