Thank you for your feedback.
Form temporarily unavailable. Please try again or contact docfeedback@servicenow.com to submit your comments.

Software license metrics

Log in to subscribe to topics and get notified when content changes.

Software license metrics

License metrics are set in software entitlements and are used for reconciliation (metric group, license metric, and software model combination).

Each metric group has a set of license metrics that are specific to the publisher.

You can view the Metric Attributes related list in software models to set the attribute value.

You can also add custom license metrics.

Adobe, Citrix, IBM, Microsoft, Oracle, SAP, and VMware publisher packs are available as add-ons that provide the capability to manage software licensed under the publisher licensing models.

Installing SaaS License Management adds the Subscription metric group.

You can view descriptions of the license metric by pointing to the reference field icon (Reference icon) in the License metric field in the software entitlement.

Table 1. License metrics
Metric group License metric
Adobe (Add-on)
Note: The license metric in not visible unless the Adobe publisher pack is installed.
  • Per Device: Licenses a device for a number of installations of software.
  • Per User: Licenses a user for a number of installations of software.
  • User Subscription: Licenses a user for the number of activated software subscriptions.
    When reconciliation is run for a software model that has one or more entitlements with the User Subscription license metric, a right is consumed for each active unique software subscription record assigned to a user.
    • A right is considered Allocated in use when a user has both allocation and a subscription record.
    • A right is considered Allocated not in use when a user does not have a user allocation but has a subscription record.
    • A right is considered Allocated not in use when a user has a user allocation but does not have a subscription record.

    If multiple rights are assigned to a user in a user allocation, then the user has the corresponding number of subscriptions for the software model. For example, if a user has a user allocation with a quantity of 2 rights, but only one subscription record related to a software model, then one right is considered Allocated in use and a second right is considered Allocated not in use.

Citrix (Add-on)
Note: The license metric is not visible unless the Citrix publisher pack is installed.

A discovery process is required for Citrix data to be collected. For ServiceNow Discovery, a Discovery schedule must be created by an admin to run on the Citrix Delivery Controller for communication with the Citrix License Server.

See License Server and Delivery Controller discovery for discovery pattern and tables.

  • Concurrent User: Licenses the number of simultaneous users accessing the program.
  • Per Device: Licenses a device for a number of installations of software.
  • Per Processor (CPU count): Licenses processors on either a physical server or virtual machine.
  • Per User: Licenses a user for a number of installations of software.
  • Per User/Device: License a unique user or a shared device. If the license is assigned to a user, they have unlimited connections to an unlimited number of devices. If the license is assigned to a device, an unlimited number of users can connect to a single device.

    If you create an entitlement with the Citrix metric group and the per user/device license metric is specified, the license calculator checks the compliance of all related software models based on the number of distinct users and devices.

Common
  • Per Core: Licenses cores on a physical server or virtual machine.

    (CPU core count * CPU count)

  • Per Device: Licenses a device for a number of installations of software.
  • Per Named Device: Licenses a specific device for a number of installations of software.
  • Per Named User: Licenses a specific user for a number of installations of software.
  • Per Processor (CPU count): Licenses processors on either a physical server or virtual machine.
  • Per User: Licenses a user for a number of installations of software.
IBM (Add-on)
Note: The license metric is not visible unless theIBM publisher pack is installed.
  • Per Device: Licenses a device for a number of installations of software.
  • Per Named User: Licenses a specific user for a number of installations of software.
  • Per Processor (CPU count): Licenses processors on either a physical server or virtual machine.
  • Per User: Licenses a user for a number of installations of software.
  • Processor Value Unit (PVU): Number of PVU entitlements required is based on the processor technology and the number of processors made available to the program.
    • Full Capacity: License all activated processor cores in the physical hardware environment.
    • Sub-capacity: License fewer than the full capacity of your server or group of servers.
  • Resource Value Unit (RVU): RVU Proofs of Entitlement are based on the number of activated processor cores used or managed by a product.
    • Full Capacity: License all activated processor cores in the physical hardware environment.
    • Sub-capacity: License fewer than the full capacity of your server or group of servers.
Microsoft (Add-on)
Note: The license metric in not visible unless theMicrosoft publisher pack is installed.
  • Device CAL: Licenses a number of device client access licenses to server software.
  • Per Core: Licenses cores on both the physical server and the virtual cores that support virtual machines and presents a cost-efficient model based on the number of rights used. For information on Per Core for Microsoft SQL Server Enterprise edition with Software Assurance, see Record software rights for a Microsoft Software Assurance.
    Note: Per Core (Physical Core) and Per Core (Virtual OSE) metrics is deprecated from the New York release. Any existing entitlements using Per Core (Physical Core) and Per Core (Virtual OSE) metrics are replaced with Per Core. You may see a change in your reconciliation results.
  • Per Core (with CAL): Licenses physical servers. The number of licenses depends on the number of installs and Operating System Environments (OSE)s.

    Per Core (with CAL) licenses at the cluster level only when the physical server is an ESX Server and is a part of a cluster. This license metric uses all processors on every ESX Server within a cluster to determine the total number of cores/processors that need to be licensed on the cluster.

    Note: If vMotion/DRS is enabled on a cluster, any virtual machine can move to any ESX Server within that cluster. The peak capacity of the cores on all the ESX Servers is taken into consideration for rights needed to license the cluster.
  • Per Device: Licenses a device for a number of installations of software.
  • Per Processor: Licenses a set number of processors on a physical server.
  • Per User: Licenses a user for a number of installations of software.
  • Server (Per Instance): Licenses a set number of software installations on either a physical server or virtual machine.
  • Server (Per Server): Licenses all software installations on a physical server and any virtual machines hosted by the physical server.
  • User CAL: Licenses a number of user client access licenses to server software.
  • User Subscription: Licenses a user for the number of activated software subscriptions.

    When reconciliation is run for a software model that has one or more entitlements with the User Subscription license metric, one right is consumed for each active unique software subscription record assigned to a user.

Oracle (Add-on)
Note: The license metric is not visible unless the Oracle publisher pack is installed.
  • Named User Plus: Licenses the number of users accessing a product.
  • Per Processor: Licenses the number of cores on a processor.
    Note: For the Oracle Per Processor license metric, enable Hyper-Threading if you are using a virtual machine (VM) running Amazon Web Services (AWS).
Note: You can select the level of aggregation for the reconciliation calculation of VMware-based Oracle instances using the com.snc.samp.oracle.reconlevel property. See Software Asset Management properties.
SAP (Add-on)
Note: The license metric is not visible unless theSAP publisher pack is installed.
Named User: SAP system users across all clients that a user has access to.
Subscription
Note: The license metric is not visible unless theSaaS License Management is installed.
  • User Subscription: License is for a number of users.
  • Envelopes: License is for a number of envelopes. Used for the DocuSign service only.
VMware (Add-on)
Note: The license metric is not visible unless theVMware publisher pack is installed.
  • Per Application Instance: Licenses per application instance.

    Applies to VMware products: vCenter Server software.

  • Per Device: Licenses per specific device. A license can only be reused if it is completely removed from the device. The number of software users on the device is not relevant as long as the license is used on the licensed device.

    Applies to VMware suite of products: Horizon FLEX, ThinApp, ThinApp Virtualization Packager, Mirage Windows Migration.

  • Per Named User: Licenses per named user.

    Applies to VMware named users: Horizon Advanced, Horizon Enterprise, Horizon Suite, Mirage, Horizon Socialcast on Premise, Workspace (Portal), Workspace Suite, Horizon Air, Horizon Air Desktop DR, ThinApp, ThinApp Virtualization Packager, vRealize Operations for Horizon, User Environment Manager, vRealize Business.

  • Per OSI: Licenses any server, virtual or physical, with an IP address that generates logs, including network devices and storage arrays.

    Applies to VMware suite of products: vRealize Operations, vRealize Log Insight, vRealize Automation, vRealize Business for Cloud, vRealize Code Stream.

  • Per Processor: Licenses a physical processor (CPU) in a server. One VMware suite processor license key is required for each physical processor in a server.

    Applies to VMware suite products: vSphere, vSphere with Operations Management.

Oracle metric group database options

Oracle Database options and management packs that enhance the capabilities of Oracle Database in specific application environments are licensed separately. Therefore, separate entitlements are required for each product.
Note: The Oracle Database option field is shown only when configuring entitlements that meet the following conditions:
  • The Product field on the software model form is DB Server.
  • The Metric group field on the entitlements form is set to Oracle, which requires special licensing.
Table 2. Oracle Database options
Category Product
Oracle Database options Active Data Guard
Advanced Analytics
Advanced Compression
Advanced Security
Airlines Data Model
Communications Data Model
Database In-Memory
Database Vault
Label Security
Multitenant
On-Line Analytical Processing (OLAP)
Partitioning
Real Application Clusters One Node
Real Application Clusters (Oracle RAC)
Real Application Testing
Retail Data Model
Spatial and Graph
TimesTen Application-Tier Database Cache
Utilities Data Model
Oracle management packs Database Lifecycle Management Pack
Diagnostics Pack
Tuning Pack
Cloud Management pack for Oracle Database
Data Masking and Subsetting Pack
Feedback