NonStop Server Guide for BEA WebLogic Server 8.1

Configuring Persistent WebLogic Server Processes
HP NonStop Server Guide for BEA WebLogic Server 8.1529891-001
4-7
stopgp.sh and stopgp.tacl
stopgp.sh and stopgp.tacl
The script and macro have one required argument, the generic process name, and an
optional delete argument if the generic process entry should be deleted. The script and
macro attempt to run an ABORT PROCESS command to cause the generic process to
stop. Because the process being stopped is the OSH process, running the ABORT
PROCESS command does not cause the WebLogic Server process to stop. Instead, the
scripts put out a message reminding you that the WebLogic Server process also needs
to be stopped.
Realize that if the entry is not deleted, if the system is reloaded the process will be
automatically restarted if STARTMODE is APPLICATION. That is, aborting the process
only stops the current process while the system is still running. The entry will persist in
the system configuration unless the delete option is used.
Using the Node Manager on the NonStop
Server
The Node Manager can be used to start and stop Managed Servers. Its use on the
NonStop server is the same as on other platforms. However, due to the NonStop
server's multi-CPU architecture, the Node Manager is appropriate even when the
cluster consists of only one NonStop server. To learn how to configure and use the
Node Manager, refer to Configuring the Node Manager and the Overview of Node
Manager and Configuring, Starting, and Stopping Node Manager sections in the BEA
document titled Configuring and Managing WebLogic Server.
The primary consideration when using the Node Manager on the NonStop server is
that native process control is not supported. This means the Node Manager property
NativeVersionEnabled must be set to false in either the
nodemanager.properties file, or in the shell script (named
startNodeManager.sh by default) used to start the Node Manager. Also, the default
value for ListenAddress (that is, localhost) will normally need to be changed to be
that of the NonStop server's TCP/IP process.
It is important to realize that to fully exploit the Node Manager, other WebLogic Server
properties may need to be changed. For example, the Node Manager only restarts
servers if AutoRestart is true (the default value). However, if the same event that
causes the Node Manager to fail causes a Managed Server to fail, the server will not
be restarted unless HostsMigratableServices is false (the default value is true).
For single node domains, HP recommends HostsMigratableServices be set to
false. This property is not externalized on the console; instead the Server element of
each Managed Server needs to be updated in the config.xml file directly. If
HostsMigratableServices is not set to false, the Node Manager may report the
status of a Managed Server as FAILED_MIGRATABLE. In that case, restart the server
using the console or weblogic.Admin utility.