Home
Configuring
Configure your environment.
Configuring HCL UnO agent
HCL UnO agent is an on premises agent that you can install in your computer. You can configure the properties of the agent to connect it to the agent manager of HCL Universal Orchestrator.
Reconfiguring HCL UnO agent
After configuring the agent initially, you can change the properties of the agent by reconfiguring. You can change all the properties of the agent, except the agentName.

Configuring
Configure your environment.
- Configuring HCL Workload Automation dynamic agent
  In this topic you can find information about how to configure a HCL Workload Automation dynamic agent.
- Configuring HCL UnO agent
  HCL UnO agent is an on premises agent that you can install in your computer. You can configure the properties of the agent to connect it to the agent manager of HCL Universal Orchestrator.
  - Reconfiguring HCL UnO agent
    After configuring the agent initially, you can change the properties of the agent by reconfiguring. You can change all the properties of the agent, except the agentName.
  - 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.
  - 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.
- Configuring Orchestration CLI
  The extension for Orchestration CLI is bundled with the product. If required, you can download it as a stand-alone feature also.
- Managing Workload Security
  You can manage security settings in your environment both from the Orchestration CLI and the Dynamic Workload Console.
- Configuring the Dynamic Workload Console for Single Sign-On
  Configure the Dynamic Workload Console for Single Sign-On.
- Configuring High Availability
  Performance can be highly improved by configuring multiple Dynamic Workload Console instances in a High Availability configuration, so as to have multiple console instances working at the same time and with the same repository settings.
- Configuring a user registry
  In this topic you can find information about how to configure a user registry.
- Customizing your global settings
  Learn how to customize advanced settings of the Dynamic Workload Console.

Reconfiguring HCL UnO agent

After configuring the agent initially, you can change the properties of the agent by reconfiguring. You can change all the properties of the agent, except the agentName.

Overview

You can update the properties of the agent by using the configure command. It is recommended not to use any other method, such as manually editing the agent.properties file. When values are altered directly in the configuration file, there is a risk of introducing errors or inconsistencies that could compromise the functionality of the agent. To mitigate these risks and ensure reliable operation of the agent, it is advisable to use the configure command to update the values in the file. This offers a more controlled and systematic approach to update the values and ensures the changes are applied correctly.

Reconfiguring the agent downloads the certificates again from the agent manager, so make sure that you add the --apiKey parameter with the configure command. If you configured the agent in a folder other than the default, you must also provide the value for --dataDir option.

configure.ps1 [--apiKey= value] [--dataDir= value]

./configure.sh [--apiKey= value] [--dataDir= value]

All the updated values are applied on the next instance of the agent start. If the agent is running while reconfiguring, then stop the agent and start it again to run with updated parameters. For available parameters in the agent.properties file, see Mandatory and optional parameters.