HP-UX Workload Manager User's Guide

Configuring WLM
Setting the WLM communications daemon to start automatically at reboot
Chapter 5 243
You can set the global arbiter to start automatically at reboot by setting
the WLMPARD_ENABLE variable in the file /etc/rc.config.d/wlm to 1:
WLMPARD_ENABLE=1
When started at reboot, the WLM global arbiter automatically uses the
most recent configuration file that was activated.
If you want the global arbiter to activate a specific configuration when it
automatically starts at reboot, edit the following line in the
/etc/rc.config.d/wlm file:
WLMPARD_STARTUP_SLOFILE=”configfile”
where configfile is the configuration file to use at reboot.
For information on starting WLM automatically, see the section “Setting
WLM to start automatically at reboot” on page 242.
Setting the WLM communications daemon to
start automatically at reboot
The WLM communications daemon (wlmcomd) services requests from the
WLM graphical user interface, wlmgui. The daemon must be running on
a system for you to control that system’s WLM instance or WLM global
arbiter using wlmgui.
You can set wlmcomd to start automatically at reboot by setting the
WLMCOMD_ENABLE variable in the file /etc/rc.config.d/wlm to 1:
WLMCOMD_ENABLE=1
With wlmcomd running on a system, WLM itself does not need to be
running on that system because you can deploy WLM there with wlmgui.
However, you can start WLM automatically if desired, as described in the
section “Setting WLM to start automatically at reboot” on page 242.