WebLogic Server (WLS) 7.0

Configuring Persistent WebLogic Server Processes
HP NonStop Server Platform Guide for WebLogic Server—525779-001
3-2
Considerations
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. 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 PTCPIP and part of PTCPIP
does not use the generic process mechanism. Therefore, the generic processes used
to support the WebLogic Server must be started after OSS and PTCPIP have been
successfully started. By default, the sample scripts configure the generic process’
STARTMODE as APPLICATION. If OSS and PTCPIP are not started by the CIIN
processing, set STARTMODE to MANUAL and run the script after PTCPIP starts.
Sample Scripts
The sample scripts provided use OSH and shell scripts to start and wait for the
WebLogic Server process. If the intervening OSH or shell processes are killed but the
WebLogic Server process is not, the generic process will be restarted. Since the
original WebLogic Server process is still running, the newly started process cannot use
the TCP/IP port and fails. This failure causes the generic process to restart.
Use caution when externally stopping processes to avoid this situation. Once the
generic process is stopped through SCF, make sure the WebLogic Server process is
also stopped. Otherwise, restarting the generic process will appear to succeed but will
enter the same restart loop because the original WebLogic Server process is still
running.
One way to reduce the number of intervening shell processes between the OSH
process and the WebLogic Server is to use exec. For example, instead of the shell
script, started by OSH, running exec ./startWebLogic.sh, which starts a second
shell process, the sample script runs an exec./startWebLogic.sh. Using exec
causes the second shell process to reuse the existing shell’s pid. To completely
eliminate the intervening shell processes requires that exec be used in all cases