Folder structure and file management for HCL UnO agent in Unix 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:
  • iso-swid
    The folder contains hcltechsw.com_HCL_agent.swidtag file, an XML file for inventory tracking.
  • 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 log related to Orchestration CLI (cli.log), and the logs related to the agent (messages.log and trace.log) are stored in this folder.

  • 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:
    • start.sh
      You can use the script to start the agent. If the agent is already running, running the script results in an error.
    • data-gather.sh
      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.
    • upgrade.sh
      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.
    • stop.sh
      You can use the script to stop the agent. If the agent is not running or unavailable, running the script results in an error.
    • daemon-install.sh
      You can use the script to install HCL UnO agent as Daemon in the system for enhanced security and continuous monitoring.
    • postscript.sh
      You can specify multiple commands with conditions in the file and it triggers another task automatically when these requirements are satisfied. The file helps you to automate tasks and runs a set of instructions provided. For more information, see Postscript.
    The folder contains the following files also:
    • uno-agent-jar.path: This file that 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.
    • 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.

  • licenses
    The folder contains notices and license agreements associated with the agent.
  • database
    The folder contains agent.db file, the file for the agent database.

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.