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-4
Managed Servers
•
The scripts should avoid calling “sleep” for any significant period of time unless you
modify the AUTORESTART parameter of the generic process to reflect the delay.
For example, if a script delays for a failed start attempt of the generic process that
takes two minutes, the generic process will continually restart the generic process.
By using an AUTORESTART of 10, only ten failures in 10 minutes will cause the
generic process to move to the STOPPED state. By using a two-minute delay, the
process will not fail ten times in 10 minutes.
Managed Servers
Instead of using the WebLogic Server Node Manager, you can use the generic process
mechanism to monitor Managed Servers. Before using this approach, consider:
•
CPU load balancing may be difficult to achieve than when you use the supplied
nodemanager.sh. Each Managed Server must be configured to run in more than
one CPU to be fault tolerant and to allow in-doubt transactions to be recovered
after a server failure. To provide balance across CPUs, Managed Servers have to
be assigned to a subset of CPUs. Therefore, use the FIRSTOF attribute with a list
of CPU numbers.
•
The following Node Manager features are not available:
°
The WebLogic Server Administration Server is not able to use the WebLogic
Server Node Manager to start Managed Servers.
°
Automatic monitoring the health of Managed Servers and restarting server
instances that have reached the “failed” health state.
°
Shutting down or forcing the shut down of a Managed Server that failed to
respond to a shut down request.
The generic process mechanism should be faster at restarting Managed Servers that
have terminated or failed due to a processor failure. However, this speed requires
monitoring and configuring outside the WebLogic Server environment.
Generic Process Attributes
Table 4-1 contains a brief consideration for each useful attribute. These considerations
assume that you are using OSH to start and monitor a WebLogic Server. See the
sample scripts later in this section to learn how to set these attributes.