Local UI

The default method to manage Arc is through the parent system software. However, it is also possible to manage Arc through a local UI.

Figure 1. Local UI

Arc local UI dashboard showing system version, sensor ID, status checks, upstream connection details, asset inventory with discovery and smart polling, latest run status, and last 100 runs summary with an option to open archives

The local user interface (UI) has these sections:

Version: This shows the version of Arc that has been deployed.

Sensor ID: This shows the identifier (ID) of the sensor.

Start button: This lets you choose and control a mode. You can choose between:

  • Start (in Service mode)
  • Start in One-shot mode
  • Start in Offline mode

For more details, see Execution modes.

To access the Offline archives page, you can select the Archives icon.

To access the Configuration page, you can select the icon.

To log out, you can select the icon.

The main method to manage Arc is through the system that it connects to. This can be:
  • Guardian
  • CMC, or
  • Vantage
Default settings are set for Arc the moment that it is deployed. However, you can access the local UI, which is in the form of a web server, if you need to:
  • Check the status of Arc locally
  • Change the settings after Arc has been downloaded
  • Run it locally during a manual deployment
To get access to the local UI, you can:
  • Double-click the executable file, or
  • From a shell, invoke it from a terminal without a parameter, with a command like .\arc-windows-amd64.exe
Note:
On macOS, before you can open the local UI, you might need to enable Arc in System Preferences > Security & Privacy.
Note:
To use the commands install and uninstall, you must run the local UI with admin rights. When you double-click the executable file, a request for admin rights will be made. In Windows, and additional prompt will show when you do this. To have full control, use the shell.

When you do this, Arc will open a page in your default browser at the address http://127.0.0.1:4510

Note:
If the port 4510 is in use, the first open port above 4510 will be used.
Note:
To open the browser page automatically, you need to consider:
  • That the browser will only open when a default browser is installed and configured
  • That the double-click action will only work if the application is recognized as an executable. For Linux and macOS, this means that it needs to be associated to the Terminal (shell) application
  • For Ubuntu distribution, you can only open the browser when the package xdg-utils is installed
  • For Linux, the root user cannot open a browser, so you must not open the local UI as root
  • If the browser does not open for one of the reasons listed above, you can open the browser and page manually
Note:
Closing the browser won’t unlock the process. Make sure that you escape from your command line so that you can execute more operations on your executable.