Using WebSphere® CloudBurst Appliance, you
can configure advanced options for WebSphere Application Server
Hypervisor Edition Intelligent Management Pack to define the topology
of a system that you want to deploy.
About this task
You can define the following advanced configuration options
for
Intelligent Management Pack:
- Define dynamic clusters
- Enable overload protection
- Configure standard health policies
- Configure on demand router (ODR) - dependent health policies.
Procedure
- Create dynamic clusters across all of the custom nodes
in the pattern. When you select this option, the Dynamic
cluster configuration script is added to the ODR. Set the following
parameters:
- DYNAMIC_CLUSTER_PREFIX
- Specifies the name of the dynamic cluster.
- NUMBER_OF_DYNAMIC_CLUSTERS
- Specifies the number of dynamic clusters to be created.
- NUMBER_OF_VERTICAL_INSTANCES
- Sets the number of dynamic cluster vertical stacking instances
on the node. With vertical stacking, multiple server instances can
start on a node.
- MINIMUM_NUMBER_OF_CLUSTER_INSTANCES
- Sets the minimum number of cluster instances for the dynamic cluster.
- MAXIMUM_NUMBER_OF_CLUSTER_INSTANCES
- Sets the maximum number of cluster instances for the dynamic cluster.
- Enable overload protection. Memory overload
protection controls the rate at which requests without affinity are
permitted through the ODR to prevent Java heap utilization from exceeding
a threshold that you specify. CPU overload protection prevents processor
utilization from exceeding a threshold that you specify. When you
select the overload protection option, the Heap overload protection
configuration and CPU overload protection configuration scripts
are added to the ODR. Set the following parameters:
- PERCENTAGE_OF_MAXIMUM_HEAP_SIZE
- Specifies the maximum percentage of the heap size to be used.
The default value is 80%.
- MAXIMUM_CPU_USAGE
- Specifies the maximum CPU usage percentage to be used. The default
value is 90%.
- Create standard health policies. The standard
health polices that you can configure are defined in the following
list.
- The excessive heap usage policy restarts members when the
memory usage exceeds a percentage of your heap size over time. When
you select this option, the Excessive memory usage policy configuration script
is added to the deployment manager. Set the following parameters:
- HEAP_USAGE_PERCENTAGE
- Specifies the maximum percentage of total memory usage. Acceptable
values for this field are whole numbers between 1 and 99.
The default value is 95.
- OFFENDING_TIME_PERIOD
- Specifies the offending time period for the excessive memory condition.
Acceptable values for this field are between 1 second
and 60 minutes. The default value is 15.
- OFFENDING_TIME_UNIT
- Specifies the units for the OFFENDING_TIME_PERIOD value. Acceptable
values for this field are MINUTES or SECONDS.
The default value is MINUTES.
- EXCESSIVE_MEMORY_USAGE_POLICY_REACTION_MODE
- Specifies the reaction mode that defines the behavior of the health
policy. Acceptable values for this field are SUPERVISED or AUTOMATIC.
The default value is SUPERVISED.
- When the reaction mode is set to SUPERVISED,
the health policy is active and recommendations for the actions are
sent to the administrator with a runtime task. The administrator can
follow the recommendations. If the administrator approves a recommendation,
actions are taken to improve the health condition automatically.
- When the reaction mode is set to AUTOMATIC,
the health policy is actively logging data, and the product automatically
takes actions to improve the health conditions without approval from
the administrator.
- EXCESSIVE_MEMORY_USAGE_POLICY_ACTIONS
- Specifies the health action to take when the condition is not
met. The default value is RESTART, which restarts
the server.
- The supported health actions are provided in the following list:
- Restart server
- Take thread dumps
- Take Java virtual machine (JVM) heap dumps
- Put server into maintenance mode
- Put server into maintenance mode and break server request affinity
to the server
- EXCESSIVE_MEMORY_USAGE_POLICY_NAME
- Specifies the name of the health policy. The default value is Default_Excessive_Memory_Usage.
- The memory leak policy tracks consistent downward trends in
free memory that is available to a server in the Java heap. When you
select this option, the Memory leak policy configuration script
is added to the deployment manager. Set the following parameters:
- MEMORY_LEAK_DETECTION_LEVEL
- Specifies the detection level to be used for the memory leak policy.
The default value is NORMAL.
- MEMORY_LEAK_POLICY_REACTION_MODE
- Specifies the reaction mode that defines the behavior of the health
policy. Acceptable values for this field are SUPERVISED or AUTOMATIC.
The default value is SUPERVISED.
- When the reaction mode is set to SUPERVISED,
the health policy is active and recommendations for the actions are
sent to the administrator with a runtime task. The administrator can
follow the recommendations. If the administrator approves a recommendation,
actions are taken to improve the health condition automatically.
- When the reaction mode is set to AUTOMATIC,
the health policy is actively logging data, and the product automatically
takes actions to improve the health conditions without approval from
the administrator.
- MEMORY_LEAK_POLICY_ACTIONS
- Specifies the health action to take when the condition is not
met. The default value is RESTART, which restarts
the server.
- The supported health actions are provided in the following list:
- Restart server
- Take thread dumps
- Take Java virtual machine (JVM) heap dumps
- Put server into maintenance mode
- Put server into maintenance mode and break server request affinity
to the server
- MEMORY_LEAK_POLICY_NAME
- Specifies the name of the health policy. The default value is Default_Memory_Leak.
- The maximum server age policy detects when the server age
of a member exceeds the specified value. When you select this option,
the Maximum server age policy configuration script is added
to the deployment manager. Set the following parameters:
- SERVER_AGE
- Specifies the age of the server. Acceptable values are positive
whole numbers in days or hours between 1 hour
and 365 days. The default value is 7 days.
- SERVER_AGE_UNIT
- Specifies the unit for the SERVER_AGE value. The default value
is DAY.
- MAXIMUM_SERVER_AGE_POLICY_REACTION_MODE
- Specifies the reaction mode that defines the behavior of the health
policy. Acceptable values for this field are SUPERVISED or AUTOMATIC.
The default value is SUPERVISED.
- When the reaction mode is set to SUPERVISED,
the health policy is active and recommendations for the actions are
sent to the administrator with a runtime task. The administrator can
follow the recommendations. If the administrator approves a recommendation,
actions are taken to improve the health condition automatically.
- When the reaction mode is set to AUTOMATIC,
the health policy is actively logging data, and the product automatically
takes actions to improve the health conditions without approval from
the administrator.
- MAXIMUM_SERVER_AGE_POLICY_ACTIONS
- Specifies the health action to take when the condition is not
met. The default value is RESTART, which restarts
the server.
- The supported health actions are provided in the following list:
- Restart server
- Take thread dumps
- Take Java virtual machine (JVM) heap dumps
- Put server into maintenance mode
- Put server into maintenance mode and break server request affinity
to the server
- MAXIMUM_SERVER_AGE_POLICY_NAME
- Specifies the name of the health policy. The default value is Default_Maximum_Server_Age.
- The email notification list policy specifies a list of email
addresses to receive notification when a health condition is met.
When you select this option, the Email notification configuration script
is added to the deployment manager. Set the following parameters:
- SMTP_HOST_NAME
- Specifies the simple mail transfer protocol (SMTP) server to connect
to when sending mail.
- SMTP_PORT
- Specifies the SMTP port number to connect to when sending mail.
- SMTP_USERID
- Specifies the user ID when the mail transport host requires authentication.
- SMTP_PASSWORD
- Specifies the password when the mail transport host requires authentication.
- EMAIL_ADDRESSES_TO_NOTIFY
- Specifies the email addresses to receive notification when health
conditions are met.
- Create ODR-dependent health policies. These
health policies are available only when there is an ODR in the pattern.
- The maximum requests served policy tracks the number of requests
served by an application server. When you select this option, the Maximum
requests policy configuration script is added to the ODR. Set
the following parameters:
- TOTAL_REQUESTS
- Specifies the total number of requests served by an application
server. The value must be a whole number greater than 1000.
- MAXIMUM_REQUESTS_POLICY_REACTION_MODE
- Specifies the reaction mode that defines the behavior of the health
policy. Acceptable values for this field are SUPERVISED or AUTOMATIC.
The default value is SUPERVISED.
- When the reaction mode is set to SUPERVISED,
the health policy is active and recommendations for the actions are
sent to the administrator with a runtime task. The administrator can
follow the recommendations. If the administrator approves a recommendation,
actions are taken to improve the health condition automatically.
- When the reaction mode is set to AUTOMATIC,
the health policy is actively logging data, and the product automatically
takes actions to improve the health conditions without approval from
the administrator.
- MAXIMUM_REQUESTS_POLICY_ACTIONS
- Specifies the health action to take when the condition is not
met. The default value is RESTART, which restarts
the server.
- The supported health actions are provided in the following list:
- Restart server
- Take thread dumps
- Take Java virtual machine (JVM) heap dumps
- Put server into maintenance mode
- Put server into maintenance mode and break server request affinity
to the server
- MAXIMUM_REQUESTS_POLICY_NAME
- Specifies the name of the health policy. The default value is Default_Maximum_Requests.
- The excessive number of timed out requests tracks a specified
number of requests that time out within a one minute interval. When
you select this option, the Excessive request timeout policy configuration script
is added to the ODR. Set the following parameters:
- REQUEST_TIMEOUT_PERCENTAGE
- Specifies the percentage of requests that can time out. If the
percentage of timed out requests exceeds the configured percentage,
runtime tasks are generated to correct the situation. The default
value is 5.
- EXCESSIVE_REQUEST_TIMEOUT_POLICY_REACTION_MODE
- Specifies the reaction mode that defines the behavior of the health
policy. Acceptable values for this field are SUPERVISED or AUTOMATIC.
The default value is SUPERVISED.
- When the reaction mode is set to SUPERVISED,
the health policy is active and recommendations for the actions are
sent to the administrator with a runtime task. The administrator can
follow the recommendations. If the administrator approves a recommendation,
actions are taken to improve the health condition automatically.
- When the reaction mode is set to AUTOMATIC,
the health policy is actively logging data, and the product automatically
takes actions to improve the health conditions without approval from
the administrator.
- EXCESSIVE_REQUEST_TIMEOUT_POLICY_ACTIONS
- Specifies the health action to take when the condition is not
met. The default value is RESTART, which restarts
the server.
- The supported health actions are provided in the following list:
- Restart server
- Take thread dumps
- Take Java virtual machine (JVM) heap dumps
- Put server into maintenance mode
- Put server into maintenance mode and break server request affinity
to the server
- EXCESSIVE_REQUEST_TIMEOUT_POLICY_NAME
- Specifies the name of the health policy. The default value is Default_Excessive_Request_Timeout.
- The excessive average response time policy detects when the
average response time of all requests from a server exceeds the specified
value. When you select this option, the Excessive response time
policy configuration script is added to the ODR. Set the following
parameters:
- EXCESSIVE_RESPONSE_TIME
- Specifies the amount of time that requests take to complete. Acceptable
values for this field are between 1 millisecond
and 60 minutes. The default value is 120 seconds.
- EXCESSIVE_RESPONSE_TIME_UNIT
- Specifies the unit for the EXCESSIVE_RESPONSE_TIME value. The
default value is SECONDS.
- EXCESSIVE_RESPONSE_TIME_POLICY_REACTION_MODE
- Specifies the reaction mode that defines the behavior of the health
policy. Acceptable values for this field are SUPERVISED or AUTOMATIC.
The default value is SUPERVISED.
- When the reaction mode is set to SUPERVISED,
the health policy is active and recommendations for the actions are
sent to the administrator with a runtime task. The administrator can
follow the recommendations. If the administrator approves a recommendation,
actions are taken to improve the health condition automatically.
- When the reaction mode is set to AUTOMATIC,
the health policy is actively logging data, and the product automatically
takes actions to improve the health conditions without approval from
the administrator.
- EXCESSIVE_RESPONSE_TIME_POLICY_ACTIONS
- Specifies the health action to take when the condition is not
met. The default value is RESTART, which restarts
the server.
- The supported health actions are provided in the following list:
- Restart server
- Take thread dumps
- Take Java virtual machine (JVM) heap dumps
- Put server into maintenance mode
- Put server into maintenance mode and break server request affinity
to the server
- EXCESSIVE_RESPONSE_TIME_POLICY_NAME
- Specifies the name of the health policy. The default value is Default_Excessive_Response_Time.
- The storm drain detection policy tracks requests that have
decreased response times. When you select this option, the Storm
drain policy configuration script is added to the ODR. Set the
following parameters:
- STORM_DRAIN_DETECTION_LEVEL
- Specifies the detection level. The value can be NORMAL or CONSERVATIVE. NORMAL is
less accurate, but can detect a storm drain condition quickly. CONSERVATIVE is
the most accurate, but takes a longer time to detect a storm drain
condition. The default value is NORMAL.
- STORM_DRAIN_POLICY_REACTION_MODE
- Specifies the reaction mode that defines the behavior of the health
policy. Acceptable values for this field are SUPERVISED or AUTOMATIC.
The default value is SUPERVISED.
- When the reaction mode is set to SUPERVISED,
the health policy is active and recommendations for the actions are
sent to the administrator with a runtime task. The administrator can
follow the recommendations. If the administrator approves a recommendation,
actions are taken to improve the health condition automatically.
- When the reaction mode is set to AUTOMATIC,
the health policy is actively logging data, and the product automatically
takes actions to improve the health conditions without approval from
the administrator.
- STORM_DRAIN_POLICY_ACTIONS
- Specifies the health action to take when the condition is not
met. The default value is RESTART, which restarts
the server.
- The supported health actions are provided in the following list:
- Restart server
- Take thread dumps
- Take Java virtual machine (JVM) heap dumps
- Put server into maintenance mode
- Put server into maintenance mode and break server request affinity
to the server
- STORM_DRAIN_POLICY_NAME
- Specifies the name of the health policy. The default value is Default_Storm_Drain.
What to do next
Deploy the pattern to run in the cloud group.
- Select the pattern to deploy, and click Deploy in the
cloud.
- Enter the following information in the fields, and click OK.
- Name
- Schedule deployment
- Configure parts
For more detailed information, see
Deploying a pattern in the
WebSphere CloudBurst Appliance Information Center.