Configure the autonomic managers
Overview
Use these instructions to configure the behavior of the autonomic managers in WebSphere Virtual Enterprise.
Before you begin, set up your system by Preparing the hosting environment for dynamic operations.
About this task
Configure autonomic managers after your have prepared your environment to support autonomic management, and if you want to maximize utilization using your defined business goals. These autonomic managers monitor performance metrics, analyze the monitored data, offer a plan for running actions, and can start these actions in response to the flow of work. The following autonomic managers all work in or with the WebSphere Virtual Enterprise environment.
Procedure
- Configure the autonomic request flow manager
The autonomic request flow manager (ARFM) controls the order, timing, and rate of the dispatch of requests into the application server tier by using classification and the defined service policy goals. ARFM also can optionally exert admission control for CPU overload protection. The autonomic request flow manager applies to HTTP, SIP, IIOP, and JMS protocols. For the JMS protocol, the ARFM applies to traffic for message-driven beans only.
- Configure dynamic application placement
You can configure the dynamic application placement controller. Dynamic application placement occurs when the dynamic operations components of WebSphere Virtual Enterprise work together to start and stop application instances to meet the fluctuating demand of work requests of varying service policy definitions
- Optimizing the database tier for performance monitoring
Optimize the database tier. The database tier optimization component extends the monitoring of WebSphere Virtual Enterprise to detect bottlenecks at the database tier in multi-tier enterprise applications.
- Configure the health controller
You can configure the health controller, which works to enforce your defined health policies by monitoring the state of servers and comparing the data to your defined health policies. When the data meets or exceeds a condition that is defined in one of your health policies, the health management subsystem takes action.
Related concepts
Dynamic operations
Overview of request flow prioritization