Technical data

4 Configuring, Starting, and Stopping Node Manager
4-2 Configuring and Managing WebLogic Server
Default Configuration
Node Manager is ready-to-run after WebLogic Server installation if you run Node
Manager and the Administration Server on the same machine, and use the
demonstration SSL configuration. By default, the following behaviors will be
configured:
! You can start a Managed Server using Node Manager, via the Administration
Console. If a Managed Server does not respond to the start command within 60
seconds, Node Manager sets the server’s state to
UNKNOWN. This does not affect
the target server instances’s ability to start up and communicate with Node
Manager. If the target server’s startup process takes longer than 60 seconds,
Node Manager will still accept messages from the server instance, and reset the
server instance’s state as appropriate. However, Node Manager will not re-issue
the start command.
! Node Manager will monitor the Managed Servers that it has started—it will
check the self-reported health status of each Managed Server every 180 seconds.
If a Managed Server does not respond to three consecutive health inquiries,
Node Manager considers the Managed Server “failed”.
! Automatic shutdown of Managed Servers is disabled. Node Manager will not
kill Managed Server processes that are failed.
! Automatic restart of Managed Servers is enabled. Node Manager will restart:
" Managed Servers that it killed, and
" Managed Servers that were running when a failure condition resulted in an
system reboot
up to two times within a 60 minute interval.
Configuration Checklist
This section summarizes the tasks required to configure Node Manager for a
production environment, and tailor its behavior.
! Configure Node Manager to accept commands from remote hosts—In a
production environment, Node Manager must accept commands from remote
hosts. To enable this, perform these tasks: