HCL Processor Value Licensing (PVU) for Distributed Software

A Processor Value Unit (PVU) is a unit of measure used to differentiate licensing of software Programs on distributed processor technologies (defined by Processor Vendor, Brand, Type and Model Number).

HCL defines a processor, for purposes of PVU-based licensing, to be each processor core on a chip (socket). Each Program has a unique price per PVU. See tools below to establish proper PVU rating of your configuration.

Licensee can deploy the Program using either:

  1. 1) Physical hardware environment at full capacity (“Full Capacity Licensing”) - Licensee must obtain PVU entitlements sufficient to cover all activated processor cores* in the physical hardware environment made available to or managed by the Program, except for those servers from which the Program has been permanently removed.
  2. For any configuration able to take advantage of SW or HW acceleration methods (e.g. VM/Ware ESXi, LDOM, SMP, etc.) the rating per core will always be a minimum of 100 PVU for HCL Digital Experience and 70 PVU for HCL Commerce, HCL Connections and HCL Domino.
  3. The use of virtualization technology provides the capability to achieve higher levels of software workload consolidation and utilization. Consequently, increased software value can be achieved with increased scalability as measured by the maximum number of processors on the server.
  4. Note, specific rules apply when there are more than two or more servers connected to form a Symmetric Multiprocessing Server, i.e., <4 processors = 70 per core, 4 processors = 100 per core, and 4> = 120 per core:
 

PVU Table Per Core

Processor Vendor Processor Name Proc. model number Maximum sockets per server PVUs per Core
Intel® Xeon®2 All post-Nehalem (launched 11/2008) Xeon Processor Models including Xeon Scalable (Platinum, Gold, Silver, Bronze) 2
4
>4
70
100
120
Xeon® All pre-Nehalem Xeon Processor Models
3000 to 3399
5000 to 5499
7000 to 7499
All 50
Core®3 All i3, i5, i7, i9 All 70
AMD Opteron All All 50
AMD EPYC All All 70
HP Itanium All All 100
IBM Power 10 E1080
E1050
S1022, L1022, S1022s, S1014, S1024 & L1024
>4
All
All
120
100
70
Power 9 E980
E950
H922, H924, S914, S922 & S924
>4
4
2
120
100
70
Any Any single-core All All 100
 
Vendor Processor Name Server Model Number Sockets per server Processor Model Number PVUs per Core
Oracle / Sun / Fujitsu SPARC T4/T5/M7/S7/M8 T5-8, M7-8, M7-16, M8-8 >4 All 120
Oracle / Sun / Fujitsu SPARC T4/T5/M7/S7/M8 T4-4, T5-4, T7-4, T8-4 4 All 100
Oracle / Sun / Fujitsu SPARC T4/T5/M7/S7/M8 T4-1, T4-1B,T4-2, T5-1B, T5-2, T7-1, T7-2, S7-2, S7-2L, T8-1, T8-2 2 All 70
 
  • * An activated processor core is a processor core that is available for use regardless of whether the capacity of the processor core can be or is limited through virtualization technologies, operating system commands, BIOS settings, or similar restrictions.
  • Note, each minimum PVU value depends on the specific value in the PVU Table per core above.
  1. 2) Virtualization environment (“Sub-Capacity Licensing”) - In a virtualized environment for configurable capacity (“Sub-Capacity Licensing”) a virtual processor core (vCPU) is a unit of measurement that is used to determine the licensing cost of a program used in Production and Staging, and Non Production environments, as applicable to the License. When the Program is deployed in an eligible virtualized environment (see Definitions and eligible virtualization environments table below) as established by using virtualization software or a hosting cloud vendor, Licensee must obtain entitlements sufficient to cover all activated virtual processor cores* (vCPUs) made available to or managed by the Program.
  • * An activated virtual processor core is a processor core that is available for use in a virtual server, regardless of whether the capacity of the processor core can be or is limited through virtualization technologies, operating system commands, BIOS settings, or similar restrictions.
  • It is based on the maximum number of virtual processor cores (vCPUs) defined and assigned by the VM and made available to the program. Hence, one vCPU is the licensing unit equal to the PVU rating defined in the PVU Table for that hardware and processor architecture. Sub-capacity counting is only valid for eligible Virtualization Environments using VMs on physical servers. Refer to the Definitions and eligible virtualization environments table below.
  • If the HCL program is the sole proprietor in a virtualized environment, then all of the active and potential vCPUs are counted.
  • In the case of VMs without Kubernetes or OpenShift orchestration, which run on x86 public clouds such as Microsoft, AWS, Google, vCPU capacity is calculated for the maximum number of activated virtual processor cores (vCPUs) of the cloud services for shared and dedicated instances available to the Program. Refer to the Definitions and eligible virtualization environments table below.

By accepting this Disclaimer, you agree to indemnify, defend and otherwise hold harmless HCL, its officers, employees, agents, subsidiaries, affiliates and other partners from any direct, indirect, incidental, special, consequential or exemplary damages resulting from:

Generally, for licensing within a virtualized environment, you may license to the lower of:

  • PVUs for the maximum number of physical cores in the server available to the Program at any given time.
  • PVUs for the maximum number of vCPUs in the virtual machines (VMs) available to the Program at any given time.
 

Definitions and eligible virtualization environments:

VM – Virtual Machine (VMs) A VM represents a complete system with processors, memory, disk and network resources. Multiple VMs can share physical resources and run side by side on the same server
Virtual Core (vCPU) Each VM is assigned a virtual CPUs, i.e., vCPU. Each vCPU is (equal to one PVU) for the purpose of licensing.
Cluster A group of dedicated servers, that are linked together using vCenter Server (VM/Ware ESXi) or Microsoft Windows Server 2022 Hyper-V feature. Failover Clustering Feature to provide resources (i.e. processor core capacity) to the VMs.
AWS EC2 instances & Dedicated Instances
VMWare on Cloud
Microsoft Azure Virtual Machines
Azure VMware Solution
Google Google Compute Engine
Oracle Oracle VM Server for SPARC.
Logical Domain (LDOM): Virtual machine that runs an independent OS instance and contains virtualized CPU, memory and storage.

 

Examples:

  • A) Single server example - Full Capacity
  • 2 Processor server with 6 cores per socket requires 840 PVUs (70 per core x 12 cores)
  • 4 Processor server with 6 cores per socket requires 2400 PVUs (100 per core x 24 cores)
  • 8 Processor server with 6 cores per socket requires 5760 PVUs (120 per core x 48 cores)

 

  • B) Two or more servers as an SMP server - Full Capacity
  • If sockets on two or more servers are connected to form a Symmetric Multiprocessing (SMP) Server, the maximum number of sockets and associated processor cores made available for use on the server increases. Therefore, when sockets on a 2 socket server with 6 cores per socket are connected to sockets on another 2 socket server with 6 cores per socket, this becomes an SMP server with a maximum of 4 sockets per server and 24 cores, and requires 2400 PVUs (100 per core x 24 cores).

 

  • C) Using Virtualization with Physical Servers – Sub Capacity
  • In an eligible Virtualized environment, if two VMs are deployed on a server that has two processors. Each processor has 8 physical cores which give 16 cores in total. Each VM is assigned 10 vCPUs. If an HCL program is installed only on the first VM and has access to 10 vCPUs. The number of vCPUs to license is 10. The second HCL program is installed on both VMs and thus has access to 20 vCPUs. Because the number of physical cores is lower than the number of vCPUs that are assigned to the VMs, the number of vCPUs to license is capped to 16.
  • Two VMs capped to 16 vCPUs requires 1120 PVUs (70 per core x 16 cores). This assumes that the vCPU is rated at 70 PVUs from the PVU Table above.
  • Licensee must maintain a record of total PVUs allocated to the product to be presented to HCL on request in accordance with HCL’s Master License Agreement.
  • HCL accepts the following reports as relevant input for calculating and validating the Full and Sub-Capacity Licensing.

 

Product Family HCL PVU Calculator(1) Big Fix(2) ILMT(3) Notes
HCL Commerce Yes Yes Yes -
HCL Connections Yes Yes Yes -
HCL Digital Experience v8.5 and v9 Yes Yes Yes -
HCL Domino  (from V11) Yes n/a n/a -
HCL Domino  (through V10) Yes Yes Yes *EOS announced (More Info).
HCL Portal v8.5 and v9 Yes Yes Yes Yes
HCL Sametime (through v9) Yes Yes Yes *EOS announced (More Info).
HCL Web Content Manager v8.5 and v9 Yes Yes Yes Yes

 

  1. 1) The HCL supplied Sizing Calculator is available to HCL registered customers. The calculator is for guidance based on HCLs licensing rules. All results should be validated with HCL to ensure all deployment scenarios have been considered and are accurate. Click here. (1)
  2. 2) HCL BigFix Inventory which includes PVU reporting for Virtual Deployments (2).
  3. 3) IBM License Metric Tool (ILMT) which is a tool available to IBM Passport Advantage customers. IBM License Metric Tool (ILMT) 'Audit Snapshot' report must be presented for full or Sub-Capacity reporting data for a minimum of 90-days. (3)
  4. 4) Using the correct PVU/vCPU value assumes the hyperthreading of cores is not being used or the customer can ensure that the BigFix Inventory or ILMT report is properly reflecting when hyperthreading of cores when is being used.

 

Guidelines for customers deploying HCL Digital Experience or HCL Domino to supported Kubernetes or OpenShift orchestration platforms

HCL customers who deploy HCL Digital Experience software to supported Kubernetes or OpenShift orchestration platforms are required to be licensed through the HCL Digital Experience Cloud Native 9.5 license model , located at the HCLSoftware License Agreements site.

HCL customers who deploy HCL Domino software to supported Kubernetes or OpenShift orchestration platforms are required to be licensed through the HCL Domino Complete Collaboration license model, located at the HCLSoftware License Agreements site.