Manage runtime tasks

A runtime task is generated by a runtime component within the product. Runtime tasks provide information from which we can accept, deny or close the recommended action plan.

Configure the hosting environment. For more information, read about preparing the hosting environment for dynamic operations

Use runtime tasks to view and manage the recommendations that the autonomic controllers are providing to improve the health and performance of the environment. If we are running in supervised mode, you must accept, deny, or close each runtime task. In automatic mode, the autonomic controllers automatically take these actions.

A task is lost when it is sent from a node when the deployment manager is not running. The same holds true in a high availability deployment manager environment. Even though the down time is minimal between the time when an active highly available deployment manager shuts down and when the standby deployment manager becomes active, tasks are still lost. After a failover of a highly available deployment manager occurs, the executing tasks at the original active deployment manager are changed to the unknown state.

1. From the administrative console, click System administration > Task management > Runtime tasks.

2. Click the task ID link to view the task target objects and corresponding monitors of a specific task. A task target object is a server, cluster, service policy, node, health policy, or application. One of these objects might be linked to configuration, performance or log monitor views in the administrative console.

   With a configuration monitor, the placement controller might recommend that an instance of the TestCluster dynamic cluster start on the test4 node. The recommendation states that this action is required for the dynamic cluster to meet its configured minimum number of running instances. We can click the link to the configuration panel for the TestCluster dynamic cluster to view its settings and verify or change the minimum number of running cluster instances.

   For a performance monitor, we can click a link to a chart with data specified in the monitor and specific to the target object. For a log monitor, we can click the Runtime tab of the target object Java virtual machine logs to investigate the displayed logs.

3. To view the action plan for the task, click the task ID.

4. To act on a specific task, select the corresponding task, and from the action list select Accept, Deny or Close. Accepting the task commits the previewed action plan. Closing the task means that the task is successfully handled by the task management service or is manually closed. Denying the task places the task in inactive status if the task is not submitted again in the next batch of task submissions by the originating component. We can also select multiple tasks with the same actions. After you act on a task, the action list is unavailable for that task.

5. Click Submit.

Results

The Runtime tasks panel refreshes, and performs the actions selecteded to perform on each task.

Subtopics

• Task management
  We can be notified about decisions that are made by autonomic managers. Notifications can represent either planned or unplanned events.

• Task management service event logger
  We can enable an event logger that logs all JMX notifications from the TaskManagement MBean into its own log file.

• Intelligent Management: runtime task custom properties
  We can use runtime task custom properties to customize the e-mails containing runtime task information.

• Define email notification
  In addition to actively monitoring tasks on the Runtime tasks panel, we can have email notifications sent to specified users when runtime tasks occur.

Related concepts

Task management

Related tasks

Define email notification

Set up Intelligent Management for dynamic operations