NonStop Server Guide for BEA WebLogic Server 8.1

Configuring Persistent WebLogic Server Processes
HP NonStop Server Guide for BEA WebLogic Server 8.1—529891-001
4-4
Generic Process Attributes
•
The following Node Manager features are not available:
°
The WebLogic Server Administration Server is not able to use the WebLogic
Server Node Manager to start Managed Servers
°
Automatically monitoring the health of Managed Servers and restarting server
instances that have reached the “failed” health state
°
Shutting down or forcing the shut down of a Managed Server that failed to
respond to a shut down request
The generic process mechanism should be faster at restarting Managed Servers that
have terminated or failed due to a processor failure. However, this speed requires
monitoring and configuring outside of the WebLogic Server environment.
Generic Process Attributes
Table 3-1 contains a brief consideration for each useful attribute. These considerations
assume that you are using OSH to start and monitor a WebLogic Server. See the
sample scripts later in this section to learn how to set these attributes.
Table 4-1. Generic Process Attributes Table
Attribute Consideration
AUTORESTART A setting of 0 means the process will not be persistent. The
sample scripts set the value to 10 to allow up to ten failures in 10
minutes. Reducing this value might help avoid hitting an infinite
restart loop.
CPU Use FIRSTOF to allow the process to run in a list of available
CPUs. Use FIRST only if you want the process to normally run in
CPU 0.
NAME Choose an available process name.
PRIORITY Unless the script that starts the WebLogic Server process
specifies a Guardian priority, set this attribute to ensure that the
WebLogic Server process runs at an appropriate priority for your
system. An inappropriate setting can significantly affect system
performance and user response times.
PROGRAM The scripts use $SYSTEM.SYSTEM.OSH so that OSH will be
found in the current SYSnn.
STARTMODE The WebLogic Server process depends on NonStop TCP/IPv6,
so only APPLICATION or MANUAL should be used. If NonStop
TCP/IPv6 is not fully started during the CIIN processing, use
MANUAL and make sure the script used to configure and start the
WebLogic Server process is run after the system is reloaded.
Conversely, if the WebLogic Server process should not be
automatically started after a system restart, change the script to
use MANUAL to avoid having the WebLogic Server process
started during system startup.