NonStop Server Guide for BEA WebLogic Server 9.2

Configuring Persistent WebLogic Server Processes
HP NonStop Server Guide for BEA WebLogic Server 9.2529891-002
4-5
Generic Process Attributes
Other generic process attributes can be ignored. HOMETERM and OUTFILE should
typically be set to $ZHOME.
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 only FIRST if you want the process to run normally in
the 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,
therefore only APPLICATION or MANUAL should be used. If
NonStop TCP/IPv6 is not started during the CIIN processing, use
MANUAL and ensure that 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 the WebLogic Server process started
during system startup.
STARTUPMSG This attribute is limited to 128 characters. The sample scripts use
-c script <->>stdout 2>>stderr”. In this example, -c tells
OSH to run script, <- causes OSH to ignore stdin, >> directs
output to stdout, and >>2 directs output to stderr.
STOPMODE Using OSH, only STANDARD causes the OSH process to stop
during an SCF ABORT PROCESS command. Using SPI or
SYSMSG with OSH will cause the ABORT command to succeed,
but the process will not stop. You need to manually stop the
process.
TYPE Use OTHER.
USERID Set this attribute unless the WebLogic Server process runs as a
member of the SUPER group. This might have ramifications with
the shell scripts if your environment expects values to be set
from the profile of this user ID.
ASSOCPROC Set ASSOCPROC to the Guardian name of the OSS process.