Use this page to define the settings that control application placement. You can enable the autonomic placement controller, define how often placement changes occur, and control the behavior of the placement controller when it is operating in supervised mode.
To view this administrative console page, click .
This page describes the fields for the Configuration tab and the Runtime tab. Use the Configuration tab to configure persistent settings. The Runtime tab enables you to modify parameters that are specific for the life span of the application placement controller. If you disable and then enable the application placement controller, the configuration settings are used instead of the settings that are configured in the Runtime tab.
Depending on your administrative role, you are allowed specific privileges when configuring the autonomic placement controller. The following list shows the administrative roles and privileges for configuring the autonomic placement controller:
Enabling security When security is enabled, some fields are not editable without proper security authorization.
Enables and disables the application placement controller.
If you disable the application placement controller, you are effectively disabling all autonomic operations for the dynamic clusters. After application placement is disabled, no dynamic changes occur concerning the size and placement of applications on the dynamic cluster. This action is equivalent to turning all dynamic clusters into static clusters.
Controls how long the runtime task sits in the queue waiting for approval or disapproval before the task expires automatically.
When the operating environment is set to run in supervised mode, the application placement controller creates tasks, but waits for approval before making any changes. The application placement controller treats runtime tasks that have timed out as user rejected tasks. Acceptable time values are 1 to 60 minutes.
To view all of the runtime tasks that the supervised operating mode created, click . Define the e-mail notification if you do not want to monitor the runtime tasks queue. To create an e-mail notification profile, click .
Specifies the amount of time that the application placement controller waits for a start or stop operation to complete before the operation fails.
Acceptable time values are between 1 and 60 minutes. Set this value to the predicted worst case time to start or stop a server.
Specifies the amount of time that the application placement controller waits before initiating a new batch of changes.
In some instances, the application placement controller waits for a batch of changes after completing previous changes or encountering a timeout. Acceptable values range from 1 minute to 24 hours. When setting this value, consider the overhead that is associated with starting and stopping servers. Starting or stopping servers can take several minutes and can introduce an additional load to the nodes.
Configuring the placement controllers to readjust the application placement too often causes the added overhead to negate the increased performance gains originally earned by readjusting the size of the dynamic clusters. For example, if it takes 1 minute to start a server, and the setting for the minimum time between placement changes is 20 minutes, then placement changes have a performance impact of about 5%.
Define the parameter to be at least 20 to 30 times larger than the time necessary to start a server. A value greater than several hours prevents application placement changes from happening more than once a day.
The fields in the Runtime tab are identical to those in the Configuration tab.
Click the Save to repository check box to make changes in the Runtime tab and to save the values into the configuration. The changes made for the Runtime tab are not persisted otherwise, and exist only for the life span of the application placement controller.
Click Apply or OK when all of the changes are made.