![]() ![]() ![]() ![]() ![]() ![]() |
This section describes how to start and stop WLOC Controllers and Agents.
The WLOC Administration Console starts when you start the Controller. You can access the console using a web browser.
The default user name and password for the WLOC Administration Console are WLOCBootUser and changeit.
To stop an Agent using the Administration Console, do one of the following:
As an alternative to shutting down an Agent, you can disconnect it. The Controller cannot deploy services to a disconnected Agent.
To stop the Controller using the Administration Console:
Stopping the Controller also shuts down the Administration Console application.
WLOC provides scripts that allow you to set up the Controller and Agent(s) to run as Windows services.
Note: | To run a WLOC Agent as a Windows service, it must be run on a local disk drive. Running the Agent as a Windows service from a mapped drive is not supported. |
To set up a Controller or Agent to run as a Windows service, open a Command Prompt window and enter one of the following commands:
When the script completes, the service will be configured to start automatically upon system boot and run using the Local System account.
You can revert to running the Controller or Agent from a command line by removing the Windows service. Use one of the following commands:
The unexpected shutdown of a WLOC Agent does not impact the operation of the Controller. When the Agent is rebooted, it will attempt to reconnect to its managed resources. The Controller will poll for disconnected Agents periodically (once for every heartbeat-interval
configured in loc-controller-config.xml
) and re-establish the connection with the Agent when it becomes available.
If the Controller shuts down unexpectedly, the Agents to which it connects will continue to collect and locally store information from its managed resources. Once the Controller restarts and re-establishes connections with the Agents, they will then send that information to the Controller.
![]() ![]() ![]() |