Example WLM configurations and properties files

manual_cpucount.wlm

WLM configuration file to help with benchmarking and capacity-planning tasks. You can resize the workload (WebLogic instance) PSET by manually running wlmsend. For example:

% /opt/wlm/bin/wlmsend wls1_grp.desired.cpucount 2.0

would assign two cores to the wls1_grp.

wls_1inst_3level.wlm

WLM configuration file to demonstrate how to control a single WebLogic instance and monitor its execution queue to determine if it is idle (normal allocation), busy (boost of one additional core), or very busy (boost of two additional cores).

wls_2inst_3level.wlm

WLM configuration file to demonstrate how to control two WebLogic instances and monitor the execution queue of each to determine if it is idle (normal allocation), busy (boost of one additional core), or very busy (boost of two additional cores).

wls_1inst_CPUusage.wlm

WLM configuration file to demonstrate how to control a single WebLogic instance versus other workloads. The WebLogic instance’s workload group starts with one core. As its CPU consumption grows, it is allocated more cores, to a maximum of four.

wls_2inst_CPUusage.wlm

WLM configuration file to demonstrate how to control a pair of WebLogic instances. Each WebLogic instance’s workload group starts with one core. As each instance’s CPU consumption grows, it is allocated more cores, to a maximum of four.

wls_1inst_q_goal.wlm

WLM configuration file to demonstrate how to control a WebLogic instance. The WebLogic instance’s workload group is allocated from one to four cores, which wlmd allocates in an attempt to keep the instance’s queue_busy metric below 0.

wls_2inst_q_goal.wlm

WLM configuration file to demonstrate how to control a pair of WebLogic instances. Each WebLogic instance’s workload group is allocated from one to four cores, which wlmd allocates in an attempt to keep the instance’s queue_busy metric below 0.

wls_2queue_2inst.wlm

WLM configuration file to demonstrate how to control a pair of WebLogic instances, instA and instB. InstA is higher priority and the administrator has created a special ‘hipri’ queue for high-priority work. Each WebLogic instance’s workload group starts with one core. If the hipri queue depth has work, instA’s group is allocated an additional core. If the instA default queue depth shows activity, its group is allocated an additional core. Lastly, if the instB queue depth has work, its workload group is allocated an additional core, if any are left.

wls_1inst_hybrid_qc.wlm

WLM configuration file to demonstrate how to control a WebLogic instance. The WebLogic instance’s workload group is allocated from one to four cores, which wlmd allocates using a pair of SLOs: a CPU usage SLO similar to the wls_2inst_CPUusage.wlm example, and a queue metric based goal similar to the wls_2inst_q_goal.wlm example. This two SLO per group or hybrid approach will control both queue and non-queue based instance workloads.

wls_2inst_hybrid_qc.wlm

WLM configuration file to demonstrate how to control a pair of WebLogic instances. Each WebLogic instance’s workload group is allocated from one to four cores, which wlmd allocates using a pair of SLOs: a CPU usage SLO similar to the wls_2inst_CPUusage.wlm example, and a queue metric based goal similar to the wls_2inst_q_goal.wlm example. This two SLO per group or hybrid approach will control both queue and non-queue based instance workloads.

instA_qbusy.props

wlmwlsdc properties file with example properties showing how to fetch the queue_busy metric from WebLogic instance ‘instA’. It is used in the single or multiple instance use cases whose resource allocations are based on the JMX ExecuteQueue MBean metrics.

instB_qbusy.props

wlmwlsdc properties file with example properties showing how to fetch the queue_busy metric from WebLogic instance ‘instB’. It is used in the multiple instance use cases whose resource allocations are based on the JMX ExecuteQueue MBean metrics.

instA_qdepth.props

wlmwlsdc properties file with example properties showing how to fetch the queue_depth metric from WebLogic instance ‘instA’. It is used in the single or multiple instance use cases whose resource allocations are based on the JMX ExecuteQueue MBean metrics.

instB_qdepth.props

wlmwlsdc properties file with example properties showing how to fetch the queue_depth metric from WebLogic instance ‘instB’.

instA_qdepth_hipri.props

wlmwlsdc properties file with example properties showing how to fetch the queue_depth metric from WebLogic instance ‘instA’ high priority queue (named ‘hipri’). It is used in the multiple instance, multiple queue use case whose resource allocations are based on the JMX ExecuteQueue MBean metrics.