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-16
Shutting Down a WebLogic Server Application
To summarize, changing the value for NODEMGR_HOME in the start script allows
multiple Node Managers to be run without conflict. If NODEMGR_HOME is changed, the
variable must be exported for the nodemanager.sh script to use the updated
location. If each Node Manager then wishes to use a unique nodemanager.sh and/or
CPUselector, the StartTemplate property needs to be used to redirect the Node
Manager to the non-default location. The nodemanager.sh can then point at a
different CPUselector, if desired.
Shutting Down a WebLogic Server Application
If the generic process mechanism is used to monitor the Administration Server and
Node Manager, the generic process must be stopped before the WebLogic Server
process is stopped. A sample shell script, stopgp.sh, and TACL macro,
stopgp.tacl, are provided. They can be used to abort, and optionally delete, the
generic process. Running stopgp.tacl stops the OSH process and prevents $ZPM
from restarting the generic process. Once the generic process is stopped, the usual
WebLogic Server method of stopping the process can be employed.