By setting the APC.predictor custom
property to a value of CPU, the application placement
controller extends the dynamic cluster management to additional topologies.
By default, the application placement controller automatically
controls dynamic clusters for the following topologies:
- Dynamic clusters of web containers to which requests are routed
through an on demand router
- Dynamic clusters of Enterprise JavaBeans (EJB)
- Dynamic clusters of message-driven beans (MDB) with the WebSphere
Service Integration Bus
When the
APC.predictor custom property is
set to
CPU, the following additional topologies
are supported:
- Dynamic clusters of web containers to which requests are routed
using the web server plug-in, when Intelligent Management is enabled.
- Dynamic clusters of MDBs with WebSphere MQ
- Dynamic cluster of on demand routers
Table 1. APC.predictor custom property valuesValue |
Description |
Scope |
Cell |
Valid value |
CPU |
When the APC.predictor custom property is
set to CPU, the application placement controller
starts and stops application servers, and adds and removes nodes,
based on the average CPU usage of all currently running cluster members.
When the average CPU usage exceeds the Maximum CPU usage setting
of CPU overload protection, and if the maximum
number of application servers is not already started, an application
server is started where CPU is available. When the elasticity mode
is enabled, an add operation is required, if no CPU is available.
When the elasticity mode is enabled, and the average CPU usage is
low so that a WebSphere node is no longer needed, all application
servers on the node are stopped, and a remove operation is performed.