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-2
Overview of Generic Processes
Administration Server controlling a set of Managed Servers. This is often configured as
a cluster. There is also a Node Manager to start and stop the Managed Servers.
To provide persistence on UNIX platforms, BEA recommends configuring the
Administration Server and Node Manager as daemon processes. On the NonStop
server, there are several mechanisms that support process persistence. This section
describes how to use generic processes to provide process persistence.
Overview of Generic Processes
For complete documentation about the generic process mechanism, refer to the SCF
Reference Manual for the Kernel Subsystem.
Generic processes are configured using SCF and started and maintained by the $ZPM
persistence manager. A generic process can be configured to start in certain CPUs
and to be restarted if the process terminates. However, the process must be a
Guardian process and cannot use Guardian ASSIGNs, PARAMs, or DEFINEs. The
WebLogic Server processes are Open System Services (OSS) processes and typically
require DEFINEs to be set to run with NonStop TCP/IPv6. Therefore, the generic
process mechanism cannot be used to directly start and monitor the WebLogic Server
application server process. Instead, a program called OSH starts as the generic
process. The OSH process runs a shell script that starts and waits for the WebLogic
Server process, which is configured as the second persistent process using the
ASSOCPROC attribute. If the WebLogic Server process later fails, the shell script and
OSH process also fail. The $ZPM will restart the generic process.
Considerations
Configuration
Only a member of the SUPER group can configure and start a generic process even
though a generic process can run as any userid. Because, for security reasons, the
WebLogic Server administrator userid is not typically a member of the SUPER group,
either the script used to configure the generic process must be owned and run as a
member of the SUPER group or a member of the SUPER group has to execute the
script directly.
Automatic Restart
Generic processes can be automatically restarted after the system is restarted.
However, the WebLogic Server depends on OSS and NonStop TCP/IPv6 and part of
NonStop TCP/IPv6 does not use the generic process mechanism. Therefore, the
generic processes used to support the WebLogic Server must be started after OSS
and NonStop TCP/IPv6 have been successfully started. By default, the sample scripts
configure the generic process’ STARTMODE as APPLICATION. If OSS and NonStop
TCP/IPv6 are not started by the CIIN processing, set STARTMODE to MANUAL and run
the script after NonStop TCP/IPv6 starts.