NonStop Server Guide for BEA WebLogic Server 9.2

Configuring Persistent WebLogic Server Processes
HP NonStop Server Guide for BEA WebLogic Server 9.2—529891-002
4-2
Overview of Generic Processes
°
Step 5. Start Managed Servers Using the Node Manager on page 4-15
°
Step 6. Monitor Startup of the Managed Server on page 4-15
°
Troubleshooting and Notes on page 4-15
•
Starting the Node Manager from a Non-Default Location on page 4-16
•
Shutting Down a WebLogic Server Application on page 4-17
The WebLogic Server supports three process types:
•
Administration Server
•
Managed Server
•
Node Manager
In a typical production application on the HP NonStop server, it is assumed that all
three process types are present on a single system. Specifically, there is an
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. The next
section describes how to use generic processes to provide process persistence.
Overview of Generic Processes
For complete documentation about the generic process mechanism, see SCF
Reference Manual for the Kernel Subsystem.
Generic processes are configured using SCF, and are started and maintained by the
$ZPM persistence manager. A generic process can be configured to: start in certain
CPUs and restart 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. $ZPM then restarts the generic process.