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-3
Considerations
Considerations
Configuration
Only a member of the SUPER group can configure and start a generic process even
though the process can run as any user ID. For security reasons, the WebLogic Server
administrator user ID is not typically a member of the SUPER group. Therefore, the
script used to configure the generic process must either be owned and run as a
member of the SUPER group, or the script must be executed directly by a member of
the SUPER group.
Automatic Restart
Generic processes automatically restart after the system is restarted. The WebLogic
Server depends on OSS and NonStop TCP/IPv6. However, 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.
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 terminated
and the WebLogic Server process is not, all processes will be restarted.
One way to reduce the number of intervening shell processes between the OSH
process and the WebLogic Server is to use exec. For example, the sample script runs
exec./startWebLogic.sh, instead of the shell script, started by OSH,
running./startWebLogic.sh, which starts a second shell process.
Using exec causes the second shell process to reuse the existing shell’s pid. To
completely eliminate the intervening shell process requires exec to be used in all
cases where a shell process is being started. In a typical installation, this requires
changing scripts in the WebLogic Server home directory or using the files from a
different location.
By using exec exclusively when starting the intervening processes, it is possible to
have the OSH process wait on the WebLogic Server. A drawback to using exec this
way is that no shell post-processing can be done. For example, if a script cannot start
the Java process, wait for it to terminate, and then perform cleanup processing.
OSH is monitored by the generic process mechanism and any script invoked by the
generic process must avoid the operations listed:
•
The shell script must wait for the WebLogic Server process. If it does not, the script
will terminate causing OSH to terminate and the generic process will restart.