WebSphere Virtual Enterprise, Version 6.1.1
             Operating Systems: AIX, HP-UX, Linux, Solaris, Windows, z/OS


Dynamic operations environment

The dynamic operations environment, consisting of the autonomic, or on demand, features of WebSphere® Virtual Enterprise supports three modes of operation: manual, supervised, and automatic. This environment is supported by autonomic managers that perform tasks such as application placement, workload management, health management, and request flow management.

Defining the mode of the operating environment involves configuring the WebSphere Virtual Enterprise components. You might find that you want a mixed environment, with some components running automatically, or autonomically, while others are not. Flexibility is built into the product to support logical systems, rather than a switch to turn things on or off. In addition, the product supports a supervised operating mode, where the system administrator accepts or denies the recommendations of the autonomic managers.

The following are the features of the dynamic operations, as well as the operating modes they support:
Autonomic manager Description
Application placement controller Characteristics:
  • Supports two modes: enabled or disabled.

    If enabled, the application placement controller supports automatic, supervised, and manual mode for each dynamic cluster with which it is affiliated. The mode is set on the dynamic cluster.

  • Applicable to a dynamic cluster.
  • Not autonomous functionality, as this is dependent upon the dynamic cluster setting.
  • Is a distributed resource managed by the high availability manager.

    The application placement controller exists within all node agent and deployment manager processes. The controller is active in one of these processes. If the active process fails, the controller becomes active on another node agent or deployment manager process.

Autonomic request flow manager (ARFM) Characteristics:
  • Supports two modes: manual or automatic.
  • Autonomous functionality, as this can be enabled individually.
  • If you are not in ARFM manual mode, you can set the arfmManualAllocation custom property to disable the autonomic setting of the ARFM control knobs.
Dynamic WLM (DWLM) Characteristics:
  • Supports two modes: enabled or disabled.
  • Applicable to static clusters and dynamic clusters. DWLM is enabled on dynamic clusters by default, and disabled on static clusters by default. To enable DWLM on a static cluster, click Servers > Clusters > cluster_name > Dynamic workload management (DWLM). To disable DWLM on a dynamic cluster, click Servers > Dynamic clusters > dynamic_cluster_name > Dynamic workload management (DWLM).
  • Autonomous functionality, as this can be enabled individually.
Health controller Characteristics:
  • Supports two modes: enabled or disabled.
  • Applicable to a cell, or subset of a cell.
  • Autonomous functionality, as this can be enabled individually.
  • Is a distributed resource managed by the high availability manager.

    The health controller exists within all node agent and deployment manager processes. The controller is active in one of these processes. If the active process fails, the controller becomes active on another node agent or deployment manager process.




Related concepts
Overview of dynamic operations
Related tasks
Configuring the autonomic request flow manager
Configuring dynamic application placement
Configuring the health controller
Creating dynamic clusters
Related reference
Static clusters versus dynamic clusters
Related information
Autonomic request flow manager custom properties
Concept topic    

Terms of Use | Feedback

Last updated: Oct 30, 2009 1:32:02 PM EDT
http://publib.boulder.ibm.com/infocenter/wxdinfo/v6r1m1/index.jsp?topic=/com.ibm.websphere.ops.doc/info/prodovr/codoemodes.html