This script outputs the google search URL required for search on edocs documentation.
Administration Console Online Help
Before you begin
The server instance for which
you configure self-health monitoring does not need to be running.
A server can monitor key
aspects of its subsystems and report when a subsystem is not functioning
properly. If the server is running under a Node Manager, the Node
Manager can automatically restart a server with an unhealthy
To enable health
If you have not already done so, in the Change Center of the Administration Console, click
Lock & Edit (see Use the Change Center).
See Start and stop
In the left pane
of the Administration Console, expand the
Servers folder and select a server.
Summary of Servers page, select the
server instance for which you will request health monitoring.
Configuration > Health Monitoring tab, update
Auto Restart -- Specifies whether the
Node Manager can automatically restart this server if it crashes
or otherwise or goes down unexpectedly.
Auto Kill If Failed -- Specifies
whether the Node Manager should automatically kill this server if
its health state is failed.
Max Restarts Within Interval -- The
number of times that the Node Manager can restart this server
within the interval specified in Restart Delay
Health Check Interval -- The amount of
time, in seconds, that defines the frequency that this server
instance performs self-health monitoring.
Restart Delay Seconds -- The amount of
time, in seconds, the Node Manager should wait before restarting
For information about each attribute, refer to
If the server is
running, shut it down.
Use the Node
Manager to start the server.
Node Manager can perform automatic monitoring and shutdown only
for servers that it starts.
To activate these changes, in the Change Center of the Administration Console, click Activate Changes. Not all changes take effect immediately—some require a restart (see Use the Change Center).