More efficient high availability and resource utilization through manageability

6
available, you could leave low-priority packages as they are and let WLM activate the additional
TiCAP or PPU resources only if needed to achieve SLOs.
• Simplifying routine/scheduled maintenance—With WLM running on a secondary server, you can
fail over packages from their primary servers to perform maintenance on the primary servers,
knowing WLM will ensure that the applications are allocated CPU resources based on their relative
priorities. Thus, your most critical applications will be getting the most CPU resources. After all the
work is finished, you can move the applications back to their primary servers.
Figure 2 illustrates some of these benefits. Upon a failure on one of the nodes, the package is started
on one of the other systems in the cluster. WLM controls the level of resources available to the
packages, based on their business priorities and the load on each application.
Figure 2. Failover with adjustment to resource allocation