Use this page to modify the global health controller settings, which are global parameters that are created by default. The health controller acts upon health policies to ensure that certain conditions in the environment are met. A health policy is a specific health criteria that you set. You can also apply limits to the frequency of restarts or prohibit restarts during certain times.
To view this administrative console page, click .
The Intelligent Management provides a continuous health monitoring and management subsystem to detect functional degradation related to software malfunctions.
This page is divided into two tabs: Configuration and Runtime. With the Configuration tab, you can view previously configured fields, and in some cases, edit the fields. With the Runtime tab, you can view the fields that are currently used by the health controller, and in some cases, make changes to the values. Unlike the Configuration tab, when you change values on the Runtime tab, the changes go directly to the health controller to change the parameters that the controller uses at that time. The changes are not stored into the repository by default, so you can make a temporary change to the parameters that does not persist.
Depending on your administrative role, you are allowed specific privileges when configuring the health controller. This list shows the administrative roles and privileges for configuring the health controller:
Specifies if health monitoring is enabled.
When enabled, the health controller continuously monitors the health policies in the system. When disabled, health conditions that are defined in the health policies are not monitored. You can disable the health controller without removing the health policies from the system.
Specifies the time between consecutive health checks to determine if a health policy condition is breached. The value is specified in minutes and ranges from 1 to 60 minutes. Longer control cycles reduce the health monitoring load.
The disadvantage is that health conditions that occur during the period are not detected until the next control cycle. For example, if you have a health policy with a workload condition of 10,000 requests associated with an application server, and the control cycle length value is specified as 60 minutes, the controller checks only every 60 minutes to determine if the application server has serviced 10,000 requests. If the application server served 9,999 requests at the time of check up, the controller does not check again for another 60 minutes. Therefore, the server might serve more than 10,000 requests before restarting the server.
Specifies the number of attempts to revive an application server after a restart decision is made.
If this number is exceeded, a failed operation is assumed and restarts are disabled for the server. The value must be a whole number between 1 and 5, inclusive.
Specifies how long to wait for a server to stop before explicitly checking its state and attempting another start.
A restart consists of the sequence of stop and start server actions. If in your environment, the action of starting or stopping an application server is unusually high, you might want to set this value so that the restart action does not time out. The value is always specified in minutes and can range from 1 minute to 60 minutes, specified as a whole number.
Controls the minimum amount of time that must pass between consecutive restarts of an application server instance.
If a health condition for an application server is breached during this time, the restart is set to a pending state. The restart occurs when the minimum restart interval passes. The value can range from 15 minutes to 365 days, inclusive. A value of 0 disables the minimum restart value.
Specifies the times and days of the week during which a restart of an application server instance is prohibited.
The start and end times are specified by selecting the hour and minute using a 24-hour clock, and the days of the week. You can specify multiple time blocks if needed. If you specify a start time and end time, you must also specify at least one day of the week that these times are prohibited. The block between the start time and end time cannot cross the boundary of midnight. For example, if you need to specify a block of 10:00 PM to 1:00 AM, specify two blocks, one from 22:00 to 23:59 and one from 00:00 to 01:00. Click Add to add additional time constraints. To remove an existing constraint, highlight the constraint and click Remove. Any actions on violated health conditions do not occur until after the prohibited time interval passes.
Saves the runtime values to the configuration.
You can make changes and view how the system reacts with the updated values. To permanently save the values, select this option instead of returning to the Configuration tab to enter all of the same values.