Configure health monitoring in a cluster

Before you begin

Ensure that you have created and configured your cluster, assigned Managed Servers to the cluster, and have configured server migration. For more information about creating and configuring a cluster, see Create and configure clusters. For more information about configuring server migration, see Configure server migration in a cluster.

To configure how a WebLogic Server cluster monitors server health:

If you have not already done so, in the Change Center of the Administration Console, click Lock & Edit (see Use the Change Center).
In the left pane of the Console, select Environment > Clusters.
The Summary of Clusters table displays all the clusters defined in the domain.
In the Clusters table, select the cluster for which you want to configure health monitoring.
Select Configuration > Health Monitoring.
1. In Inter-Cluster Comm Link Health Check Interval, specify the time interval that a trigger should periodically run to check if a broken cluster link between two clusters is restored.
2. In Health Check Interval, specify the time interval at which migratable servers and cluster masters verify they are live.
3. In Health Check Periods Until Fencing, specify the maximum number of periods that a cluster member should wait before timing out a cluster master and the number of periods that a cluster master will wait before timing out a migratable server.
4. In Fencing Grace Period, specify the amount of time the cluster master waits to determine a server instance to be dead during automatic migration.
Click Save.
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).

Administration Console Online Help

Configure health monitoring in a cluster