More efficient high availability and resource utilization through manageability

23
transient_groups = 1;
}
Pulling all the pieces of the WLM configuration file together, you get the following file:
prm {
groups = pkgA:2, pkgB:3;
apps = pkgA:/opt/dbase/bin/sales
_dbase,
pkgB:/opt/dbase/bin/finance
_dbase;
}
tune pkgA
_active {
coll
_argv = wlmrcvdc sg_pkg_active pkgA;
}
tune pkgB
_active {
coll
_argv = wlmrcvdc sg_pkg_active pkgB;
}
slo pkgA
_slo {
pri = 1;
cpushares = 200 total;
entity = PRM group pkgA;
condition = metric pkgA
_active;
}
slo pkgB
_slo {
pri = 2;
mincpu = 1;
maxcpu = 800;
entity = PRM group pkgB;
condition = metric pkgB
_active;
goal = usage
_CPU;
}
tune {
absolute_cpu_units
= 1;
transient
_groups = 1;
}
Note
The OTHERS workload group is never removed, regardless of how many
active SLOs it has.
3. Validate the syntax of the configuration file and correct any errors:
# /opt/wlm/bin/wlmd -c
configfile
4. Distribute the WLM configuration file to all the nodes in the cluster.
5. Activate WLM with your configuration file on all the nodes:
# /opt/wlm/bin/wlmd -a configfile
Note
If you are using WLM’s secure communications, be sure to distribute the
security certificates as explained in the section HOW TO SECURE
COMMUNICATIONS in the wlmcert(1M) manpage.