Define health policy general properties

Use this page to create health policies, which are used to perform a variety of health-based assessments on clusters, dynamic clusters, and application server instances running on nodes. To view this administrative console page, click Operational Policies > Health Policies > New.

Extended information about the health policy fields follows:

Name The name field is a required, user-defined field. The name field cannot contain the following characters: []> \ / , : ; " * ? < > | = + & % ' # The name must be unique among health policies in a cell and cannot begin with a period (.) or a space. A space does not generate an error, but leading and trailing spaces are automatically deleted. Meaningful and consistent health policy names are recommended. For example, age-based health policies can be indicated by naming them AGE_20DAYS, AGE_15DAYS. and so on.
Description The description field complements the name field and is user-defined. This field is optional, but it is recommended in environments with multiple administrators.
Health condition Health condition is a selectable field that identifies the health policy. The possible health policies are identified in the following list. Some policies are prevention based and some are detection based. Prevention based policies are used to avoid conditions that might lead to problems, while the detection-based policies are used to identify existing conditions and to achieve resolution. These policies can be used to perform health-based assessments on clusters, dynamic clusters, and application server instances running on nodes. In the case of dynamic clusters, regardless of the health policy that you are using, the minimum number of dynamic cluster instances remains up and running.
  • Age-based condition: Restarts the members that are associated with this policy when their age reaches a certain value. This method cleans out the memory and caches.
  • Excessive request timeout condition: The members that are associated with this policy are restarted if the percentage of requests directed at that server which has timed out is reached.
  • Excessive response time condition: The members that are associated with this policy are restarted if an average number of responses takes longer than a certain amount of time.
  • Memory condition: excessive memory usage: The members that are associated with this policy restart when the memory usage exceeds a percentage of the maximum heap size for a certain amount of time.
  • Memory condition: memory leak: The memory leak condition monitors for consistent downward trends in free memory available to a server in the Java heap. The detection level determines when these trends are detected.
  • Storm drain condition: The server that is associated with this policy restarts when the specified detection level is reached. Storm drain detection relies on change point detection on a given time series data. The metrics that are used for detecting storm drain are the response times and deployment workload manager weights observed for server. The storm drain condition applies only to dynamic clusters and cells.
  • Workload condition: The members that are associated with this policy restart when a certain user-defined number of requests have been serviced. This method cleans out the memory and caches.

When you complete all of the required fields, click Next to proceed.