WebLogic Server (WLS) 7.0

Configuring Persistent WebLogic Server Processes
HP NonStop Server Platform Guide for WebLogic Server—525779-001
3-8
Shutting Down a WebLogic Server Application
Server domains share the node manager, all managed servers will influence the CPU
selection. To avoid this situation, use a different node manager for each domain.
Both algorithms are dependent on being able to accurately calculate the current load of
the system. However, managed_load depends heavily on the information contained
in the files maintained by the node manager. If the contents of the files do not reflect
the current state, the script may fail to balance new start requests. One example of this
problem is when you try to start multiple managed servers at the same time. This can
be done on the console by selecting the "Start this cluster..." option. Using this option
will cause multiple start attempts to be generated at the same time and the servers will
not be properly balanced among the available CPUs. This can happen even if
jvm_load is used.
It is important to realize that to fully exploit the node manager other attributes might
need to be changed. For example, the node manager only restarts servers if
AutoRestart is true (the default value). However, if the same event that causes the
node manager to fail causes a managed server to fail, the server will not be restarted
unless HostsMigratableServices is false (the default value is true). For single
node domains, HP recommends HostsMigratableServices be set to false. This
attribute is not externalized on the console; instead the Server element of each
managed servers needs to be updated in the config.xml file directly. If
HostsMigratableServices is not set to false, the node manager may report the
status of a managed server as FAILED_MIGRATABLE. In that case, restart the server
using the console or weblogic.Admin utility.
Shutting Down a WebLogic Server Application
If the generic process mechanism is used to monitor the administration server and
node manager, the generic process must be stopped before the WebLogic Server
process is stopped. A sample shell script, stopgp.sh, and TACL macro,
stopgp.tacl, are provided. They can be used to abort, and optionally delete, the
generic process. Running stopgp.tacl stops the OSH process and prevents $ZPM
from restarting the generic process. Once the generic process is stopped, the usual
WebLogic Server method of stopping the process can be employed.