Dynamic Workload Manager (DWLM)

Dynamic workload manager (DWLM) applies the same principles as the workload manager (WLM). Both DWLM and WLM perform routing based on a weight system, which establishes a prioritized routing system. Instead of manually setting a static weight like WLM, DWLM grants the system the ability to modify the weights to stay current with business goals.

To view this administrative console page, click Servers > Clusters > cluster_name > Dynamic workload management (DWLM) or Servers > Dynamic clusters > cluster_name > Dynamic workload management (DWLM).

Selecting the check box grants the system the ability to modify the WLM weights, if necessary. Not selecting the check box disables the DWLM functionality.

Consider the following items when deciding whether to enable DWLM:

Does your cluster need a static weight or do you want cluster weight to change with the traffic capacity?
If you are using dynamic operations for the cluster, then you set business goals and use policies to define your threshold. In this case, setting a static weight is not useful. If you are working in a static environment, then set a static weight.
Are you planning on using dynamic operations?
If you intend to use the automatic mode for dynamic operations, then setting a static WLM weight on any of your dynamic clusters could get in the way of allowing dynamic operations to function properly.
Do you want to restrict certain work from being done on the cluster?
If you have a cluster that you do not want to be dedicated to the current workload, then you can create it as a static cluster and define a static WLM weight to it. By setting a static weight, you are setting aside a percentage of the cluster for other work.
Are you interested in using HTTP session rebalancing?
With HTTP session rebalancing, the product can dynamically and actively balance the distribution of HTTP sessions among application servers.

File name: dwlm_collection.html