Home
Orchestrating
Orchestrate anything with HCL Universal Orchestrator.
Policy-driven plan
The new HCL Universal Orchestrator policy-driven adaptive plan makes your workload more autonomous, dynamic and scalable.

Orchestrating
Orchestrate anything with HCL Universal Orchestrator.
- Orchestration CLI commands
  You can use the various command options in Orchestration CLI to achieve specific results. The command options are not case sensitive and you can use either uppercase or lowercase letters.
- Job stream definition
  This topic introduces the job stream definition, that can be managed from the Orchestration CLI and from the Dynamic Workload Console.
- Job definition
  This topic introduces the job definition, that can be managed from the Orchestration CLI and from the Dynamic Workload Console.
- Calendar definition
  This topic introduces the calendar definition, that can be managed from the Orchestration CLI and from the Dynamic Workload Console.
- Folder definition
  This topic introduces the folder definition, that can be managed from the Orchestration CLI and from the Dynamic Workload Console.
- Credentials definition
  This topic introduces credentials definition, that can be managed from the Orchestration CLI and from the Dynamic Workload Console.
- Variable table definition
  This topic introduces the variable table definition, that can be managed from the Orchestration CLI and from the Dynamic Workload Console.
- Workstation definition
  This topic introduces the workstation definition, that can be done from the Orchestration CLI and from the Dynamic Workload Console.
- Managing an event source definition from the Orchestration CLI
  In this topic you can find the syntax to manage an event source definition.
- Event plug-in structure
- Static pools
  A static pool in HCL Universal Orchestrator groups multiple workstations together and manages the workload by assigning jobs to available workstations within the pool. This helps to optimize resource utilization.
- Managing matching criteria
  In this topic you can find a description of matching criteria.
- Managing HCL UnO agent in Unix operating systems
  You can manage the agent by using scripts that are generated while configuring the agent or by Daemon process. It is recommended to use any method for ideal cohesion and efficient administration.
- Managing HCL UnO agent in Windows operating systems
  You can manage the agent by using scripts that are generated while configuring the agent or by Daemon process. It is recommended to use any method for ideal cohesion and efficient administration.
- Managing time zones
  In this topic you can find information about managing time zones.
- Policy-driven plan
  The new HCL Universal Orchestrator policy-driven adaptive plan makes your workload more autonomous, dynamic and scalable.
  - Policy-driven adaptive plan scenario
    This topic shows how the HCL Universal Orchestrator policy-driven plan operates in a practical business scenario.
  - Dependencies
    Job stream dependencies in the HCL Universal Orchestrator policy-driven plan have been updated to match the plan improved flexibility.
- Parsing OCLI files in streaming
  HCL Universal Orchestrator enables you to add or replace files containing multiple item types through OCLI in a single command.
- Data exchange and transformation
  This topic explains how you can streamline your workflows using data exchange and transformation.

HCL Universal Orchestrator policy-driven plan

The new HCL Universal Orchestrator policy-driven adaptive plan makes your workload more autonomous, dynamic and scalable.

The new plan is regulated by customizable policies that determine an automated pipeline.

Table 1. Policies
Policy	Name	Description	Default value
`active-window`	Active window	The time window in which the dependencies of active job stream instances are resolved and launched.	24 hours
`active-window.extension`	Plan extension frequency	How often the plan is updated.	5 minutes
`not-active.window.min`	Old instances retention	How much time successfully completed job stream instances are kept in the plan.	7 days
`not-active.window.max`	Non-active window	The number of days for which you want to have a continuous pipeline of job stream instances created in the database ready to be scheduled and added to the plan. The non-active window is automatically extended everyday.	14 days

These policies are fully customizable.

Policy-driven planning pipeline example

The new planning pipeline starts with the creation of a job stream using run cycles. Let's name the job stream "EXAMPLE".
New non-active "EXAMPLE" job stream instances are created and scheduled for the next 14 days by default.
The activation of the new "EXAMPLE" job stream instances happens in a time window of 24 hours by default.
When "EXAMPLE" instances are activated, their dependencies are resolved. Dependencies for not started and not modified instances are re-evaluated and their best match is determined every time a new instance is activated, or a new job is submitted. Find more information on dependencies behavior here.
Completed "EXAMPLE" instances are removed after 7 days by default.
The plan is extended every 5 minutes by default, starting again from step number 2.

The new plan is designed to run autonomously with minimal user interaction while still guaranteeing full user control over the whole workload. For more information about the new plan, see the policy-driven plan scenario.