WebSphere Extended Deployment, Version 6.0.x
             Operating Systems: AIX, HP-UX, Linux, Solaris, Windows, z/OS


Managing runtime tasks

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

Before you begin

Before reviewing the following steps, click the ShowMe icon on this page to familiarize yourself with task management.

Configure your hosting environment. For more information, see Preparing the hosting environment for dynamic operations .

About this task

Use runtime tasks to view and manage the recommendations that the autonomic controllers are providing to improve the health and performance of your environment. If you 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.

Procedure

  1. From the administrative console, click Runtime operations > 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 might be a server, cluster, service policy, node, health policy, application, and so on. 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 for the TestNodeGroup node group might recommend that an instance of the TestCluster dynamic cluster start on the test4 node. The recommendation states that this is action is required for the dynamic cluster to meet its configured minimum number of running instances. You 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, you can click a link to a chart with data that is specified in the monitor and specific to the target object. For a log monitor, you 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. You 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 that you selected to perform on each task.



Related concepts
Task management
Related tasks
Preparing the hosting environment for dynamic operations
Related information
Show Me
Defining e-mail notification
Task topic    

Terms of Use | Feedback

Last updated: Oct 16, 2009 11:10:11 AM EDT
http://publib.boulder.ibm.com/infocenter/wxdinfo/v6r0/index.jsp?topic=/com.ibm.websphere.xd.doc/info/xadmin/txadmtask.html