Folder structure and file management for HCL UnO agent in Windows operating systems

When you run the HCL UnO agent for the first time, multiple folders and files are created within the designated directory. By effectively managing these files, you can gain control over the agent to configure, monitor, and optimize its performance as needed for your specific requirements.

Overview: folder structure

The multiple folders that are created when you configure the HCL UnO agent are as follows:
  • bin
    The folder contains all the scripts required to manage the agent. The scripts serve as a comprehensive toolkit for effectively overseeing and controlling the agent. When the agent is configured, it automatically generates a set of scripts, each serving a distinct purpose in the management of HCL UnO agent. The configuration of the agent generates the following scripts:
    • daemon-install.ps1
      You can use the script to install HCL UnO agent as a Daemon in the system for enhanced security and continuous monitoring.
    • data-gather.ps1
      You can run the script to gather all the messages and log files related to HCL UnO agent. All the messages and log files are collected in a zip file, that can be used for troubleshooting.
    • start.ps1
      You can use the script to start the agent. If the agent is already running, running the script results in an error.
    • stop.ps1
      You can use the script to stop the agent. If the agent is not running or unavailable, running the script results in an error.
    • upgrade.ps1
      You can use the script to update the agent to the latest version. If you run the script, the existing agent is stopped to run the new instance of agent.
    The folder contains the following files also:
    • agent_name.service file
      The file defines the properties of the Daemon service that runs the agent. It contains a list of key-value pairs that is created by default.
    • osh.exe (Orchestrator Service Handler)
      The command line program that reads and parse the agent_name.service file. You must use the program with agent_name.service file if you want to manage the agent through Daemon process. The supported commands are install, start, stop, and remove. For more information, see Managing HCL UnO agent using Daemon process in Windows operating systems.
    • uno-agent-jar.path: This file contains the reference to the location of the agent jar file.
      Important: Make sure the location of agent jar file remains unchanged after configuration. The change in location results in the dysfunction of the agent.
  • database
    The folder contains agent.db file, the file for the agent database.
  • iso-swid
    The folder contains hcltechsw.com_HCL_agent.swidtag file, an XML file for inventory tracking.
  • licenses
    The folder contains notices and license agreements associated with the agent.
  • security
    The folder contains the certificates and JWT tokens associated with the agent installation and registration.
  • stdlist
    The folder contains logs related to Orchestration CLI and the running instance of the agent. When ever you run a command in Orchestration CLI the existing log file is replaced by the new one. The logs related to Orchestration CLI (cli.log) and the agent (messages.log and trace.log) are stored in this folder.

Overview: file structure

After you configure the agent, the agent.properties file, a file that contains the current configuration of the agent is also created.