WebLogic Server (WLS) 7.0

HP NonStop Server Platform Guide for WebLogic Server—525779-001

3-1

Configuring Persistent WebLogic

Server Processes

Overview of Generic Processes

Considerations

Configuration

Automatic Restart

Sample Scripts

Managed Servers

Generic Process Attributes

Sample Shell Scripts and TACL Macros

startgp.sh

startgp.tacl

Scripts to Start the WebLogic Server Process

stopgp.sh and stopgp.tacl

nodemanager.sh

Shutting Down a WebLogic Server Application

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. 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 Parallel Library TCP/IP (PTCPIP). Therefore, the