v2.1.7+Managing the HCL Universal Orchestrator on-premises instance by using scripts

When you install HCL Universal Orchestrator on-premises for the first time, the process creates multiple scripts that can be used to manage it afterward. You can run each script to accomplish specific results.

Before you begin

  • You must have installed HCL Universal Orchestrator on-premises to create the scripts. For more information, see Deploying HCL Universal Orchestrator on premises.
  • Navigate to the bin folder under the .uno data directory, where all the scripts to manage the installed instance are available.

About this task

When you install for the first time, the following scripts are created:
  • start.ps1 or start.sh: Starts the running instance of the HCL Universal Orchestrator daemon or service.
  • stop.ps1 or stop.sh: Stops the running instance of the HCL Universal Orchestrator, if any.
  • upgrade.ps1 or upgrade.sh: Updates the HCL Universal Orchestrator to the specified version.
    Note: You must know the path to the new HCL Universal Orchestrator jar file.
  • data-gather: Gathers all the data associated with the HCL Universal Orchestrator instance in a zip file.
  • rotateCerts.ps1 or rotateCerts.sh: Rotates the SSL certificates. For more information, see Managing TLS/SSL certificates.
  • daemon-install.ps1 or daemon-install.sh: Installs the HCL Universal Orchestrator as daemon.
You can run these scripts by using the command line to ensure automation of tasks and consistency in operations.

Procedure

  1. Open the command line.
  2. Type the name of any script, and then press Enter.
    Example:
    start.ps1
    Important: If you use the upgrade script to update to a new version, you must specify the path to the new HCL Universal Orchestrator .jar file.
    For example,
    upgrade.ps1 path to the new HCL Universal Orchestrator jar file