v2.1.7+Files and folders: HCL Universal Orchestrator on-premises installation in Unix operating systems

When you install HCL Universal Orchestrator 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 instance to configure, monitor, and optimize its performance as needed for your specific requirements.

Overview: Folder structure

When you install the HCL Universal Orchestrator, the following folders are created:
  • iso-swid
    The folder contains hcltechsw.com_HCL_Uno.swidtag file, an XML file for inventory tracking.
  • security
    The folder contains the certificates and JWT tokens associated with the installation.
  • bin
    The folder contains all the scripts required to manage the HCL Universal Orchestrator instance. The scripts serve as a comprehensive toolkit for effectively overseeing and controlling the HCL Universal Orchestrator instance. When the universal orchestrator instance is installed, it automatically generates a set of scripts, each serving a distinct purpose in the management of HCL Universal Orchestrator. The configuration of the HCL Universal Orchestrator instance generates the following scripts:
    • start.sh
      You can use the script to start the HCL Universal Orchestrator instance. If it 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 Universal Orchestrator. 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 HCL Universal Orchestrator to the latest version. If you run the script, the existing instance is stopped to run the new instance of HCL Universal Orchestrator.
      Note: The upgrade script is compatible with HCL Universal Orchestrator version 2.1.4 and later.
    • stop.sh
      You can use the script to stop the HCL Universal Orchestrator instance. If it is not running or unavailable, running the script results in an error.
    • rotateCerts.sh
      You can use the script to manually rotate the SSL certificates for the HCL Universal Orchestrator instance. For more information, see Managing TLS/SSL certificates.
    • daemon-install.sh
      You can use the daemon-install script to install the HCL Universal Orchestrator as a daemon in the system for enhanced security and continuous monitoring. The script manages the existing instance of the HCL Universal Orchestrator and configures it to run as a daemon.
    • uno-uninstall.sh: The script to uninstall the universal orchestrator instance on Unix operating systems. For more information, see Removing an HCL Universal Orchestrator instance using scripts.
  • licenses
    The folder contains notices and license agreements associated with the HCL Universal Orchestrator.
  • storage
    The folder contains event-manager and job-plugins.
  • logs
    The folder contains logs related to installation, the Orchestration CLI, and the running instance of the engine.
  • configuration
    The folder contains the following files:
    • uno-install.sh: The script to install the universal orchestrator instance on Unix operating systems.
    • hcl-uno-VERSION.jar: The HCL Universal Orchestrator jar file.
  • logs
    The folder contains logs related to installation, the Orchestration CLI, and the running instance of the engine.

After you install the HCL Universal Orchestrator, the uno.properties file, a file that contains the current configuration of the HCL Universal Orchestrator is also created.