License types

After the evaluation period, you must acquire agent licenses before you can use all product features. There are two types of licenses, that is, license for typical agents and license for z/OS agents.

There are five agent license types available for HCL Launch agents:
  • Authorized license for typical (non-z/OS) agents
  • Authorized license for z/OS agents
  • Floating license for typical (non-z/OS) agents
  • Floating license for z/OS agents
  • RDT license for z/OS agents
Note: The HCL Launch server does not require any licenses in order to connect to and interact with the Web UI.

Licenses are applied to agents via the Web UI. You can configure the server to automatically apply licenses to new agents as they connect. For information about how to apply licenses, see Applying HCL licenses to agents.

Authorized license for typical agents

The authorized license type allows you to allocate license to specific agents until they are deleted or unlicensed.

The authorized type license for typical agents is shown as Authorized (HCL_Agent) in HCL Launch.

Authorized license for z/OS® agents

Agents on z/OS® use different licensing than the typical agents. However, the z/Linux™ agents use the same licensing as the typical agents. Each z/OS agent requires a license, even if multiple agents are running on a single logical partition (LPAR). One agent is required on each environment, even if the environments are on a single z/OS sysplex.

z/OS-specific agent licensing applies to the agents; it does not define the licensing model for the server on z/Linux or other supported server platforms.

The authorized type license for z/OS agents is shown as Authorized (HCL_Agent_Z) in HCL Launch.

Floating license type for agents and z/OS® agents

Floating licenses are required when you want multiple agents to share a limited number of licenses. In floating license type, the licenses are not tied to agents. When an agent which is not licensed performs a deployment, the server looks for an available license from the license pool. If a license is available, it reserves the license for that agent until the work is done. When the agent completes its work, the license is returned to the license pool for other agents to work.

If there are insufficient licenses for the number of floating agents, then the server records that but it still allows deployment to continue.

The floating type license for typical agents is shown as Floating (HCL_Floating_Agent) and for z/OS agents is shown as Floating (HCL_Floating_Agent_Z) in HCL Launch.

RDT license for z/OS® agents

RDT agents are z/OS development agents. They do not require a separate license. The RDT license type is automatically assigned when the server detects the zOS-RDT property on the agent, and an RDT agent cannot change its type to a different license type.