This documentation supports the 18.08 version of Asset Management.

To view the latest version, select the version from the Product version menu.

Default behavior for customized license types

For any default or custom license type, the system uses default behavior when generating the rules for various license types. This default behavior is used whether or not you set up definitions in the license type wizard.

This default behavior for connection criteria uses a certificate's company and product categorization criteria to query certificates matching that license type and determine which CIs can be connected to a certificate. The default behavior is used in addition to any questions that are specified in the license type wizard for that license type.

This default behavior for compliance criteria queries certificates that match a license type and tests the result of the query against compliance criteria.

If you need more functionality in addition to the default behavior, you have to create a custom license type. You can configure additional connection behavior, or compliance actions, or both. The custom license type can be configured in either basic or advanced modes as described in Basic and advanced mode license types. If you want to use additional license types, follow the instructions in Creating custom license types to create additional license types.

Note

In the BMC_Product class there is a ProductType attribute. This attribute informs you if the Product CI is a suite(a composite product), a standalone product, or a component of a suite. This attribute gets set as part of the normalization engine run based on the suite rollup rules. For more information about Suite Rollup, see Configuring Suite Rollup normalization rules and Configuring the Normalization Engine to populate Product Catalog entries . As part of the License Management run, the CIs that are flagged as components are not counted towards a license, because the license for the suite to which it belongs to, is consumed.

Note

The Per CPU and Per Core licenses round up the deployed number upwards as per industry norms. For example, 9.4 is rounded to 10.

The following table explains how the default license types work:

System license types

Contract type Description
Enterprise

An enterprise license type licenses all of the software from a manufacturer that is being used by a given company. There is one enterprise license per company. Anyone in the company can use the license. This license type is set to non-groupable.

Connection
Uses the default certificate criteria for connections.

Compliance
One computed compliance question is specified for number of licenses deployed. The certificate for this license type is always compliant.

Site

A site license type licenses all of the software from a manufacturer that is being used by a given site. A site license applies to a single site within a company. If a site license applies to multiple sites within a company, the contract manager or software asset manager can add a site license certificate for each site. This license type is set to non-groupable.

Connection
Uses the default certificate criteria for connections.

In addition, one connection question exists for this license type, which is Enter Certificate Site?. When the license type is created, this question maps to the site of the computer system on which the product is installed.

For each product that matches the default certificate criteria for connections, the site of the computer system on which the product is installed is used to connect the product to the license certificate to that site.

For example, a contract manager creates a license certificate with the default certificate criteria for connections:

  • Company = Calbro Services
  • Manufacturer = Microsoft
  • Product = Visio

The contract manager specifies this Site license certificate is for Frontoffice Support.

A copy of Microsoft Visio is installed on a computer in Frontoffice Support. That product is not connected to the license certificate.

A computer in Backoffice Support Services has both Microsoft Visio and Microsoft Word installed. Microsoft Visio is connected to the site license, but Microsoft Word is not (perhaps it is connected to an Enterprise license).

Compliance
One computed compliance question is specified for number of licenses deployed. The certificate for this license type is always compliant.

Per instance

Each instance of the license is counted as one license consumed. Any instance of software found requires a license. This license type is set to groupable.

Connection
Uses the default certificate criteria for connections.

Compliance
The following compliance question are asked:

  • Number of licenses purchased?
  • Breach warning level 1?
  • Breach warning level 2?
  • Number of licenses deployed (computed question)

The answers to these question are used to:

  • Determine the number of software instances related to the certificate
  • Set the certificate to not compliant, if the number of software instances related to a certificate is greater than the number purchased

Example
Two instances of BMC Atrium CMDB Enterprise Manager were found. In this situation, two licenses are required.

Per copy per device

The number of copies per device allowed or licenses purchased does not affect how many CIs might be connected to the certificate or how many licenses are consumed. One license is consumed for each device that has one or more copies of the product CI that is connected to the certificate.

The number of copies per device is used to calculate compliance. To be compliant, the number of copies per device must not be exceeded and the number of licenses purchased must not be exceeded.

For example, if three copies of Product X are installed on Device Y, and two copies per device are allowed for the certificate, one license is consumed, and one license is out of compliance.

The per device number specified for a license type determines how many copies can be installed on each device. This license type is set to groupable.

Connection
Uses the default certificate criteria for connections.

Compliance
The following compliance questions are asked:

  • Number of licenses purchased?
  • Breach warning level 1?
  • Breach warning level 2?
  • Number of copies allowed per device?
  • Number of licenses deployed (computed question)

The answers to these questions are used to compute compliance:

  • If any devices have more than the allowable number per device, the certificate is marked as not compliant.
  • Also, if the number of software licenses related to a certificate is greater than the number purchased, the certificate is marked as not compliant.

Example
Two copies of Microsoft Word were found on a computer, but only one license exists. If the number of copies allowed on a device is one, this is not compliant.

Per copy

This license type is per copy per user. Each unique user (since, for example, there could be two software items linked to one user) is counted as one license consumed. If a user is not linked to a license, it is assumed that one license is consumed. This license type is set to groupable.
Connection
Uses the default certificate criteria for connections.

Compliance
Compliance is computed based on the number of unique individuals using a software product. The following compliance question will be asked:

  • Number of licenses purchased?
  • Breach warning level 1?
  • Breach warning level 2?
  • Number of licenses deployed (computed question)

The answer to these questions are used to determine the number of unique individuals connected to a product. If the number counted is greater than the number of licenses purchased, the license certificate is set to not compliant.

Example
Two copies of an application were found on separate computers owned by one user and only one license exists. This situation is compliant, because only one license is required.

BMC Remedy AR System fixed and floating The number of fixed and the number of floating licenses are compared against the number that is entitled. This is a demonstration of the advanced model. To walk through the creation of this license type as an example of the advanced model, see BMC Remedy AR System fixed and floating license type example (advanced mode).
Per Server

The per server license supports performing a count of the unique number of servers with the specified manufacturer and model, on which a particular software title is installed, and comparing that with the total number of servers with the specified manufacturer and model, that a certificate allows from a compliance standpoint.

Connection
Uses the default certificate criteria for connections. The only additional information that needs to be stated for the connection are details about the physical server on which the software is installed so that you can potentially limit a certificate for a particular hardware type or manufacturer.

Compliance
The compliance rules for this license type are based on the calculation of the number of unique physical servers that are associated with the products related to a certificate. This requires that you start with a product and then query the computer system to which the product is related.

Per CPU Sum Based

The per CPU license models are used when a product's license is not based on the number of instances deployed of the software, but on the number of CPUs on which the software is installed. These server instances can be either physical or virtual systems.

Connection
The connection rules for all Per CPU licenses are the same. The connection between the CIs and Certificate is made based on the matching Company and Product Categorization.

Compliance
The Per CPU Sum Based license model is based on the sum of all unique CPUs associated with products that are associated with the certificate. This rule searches for the products that are associated with the certificate. For each product, the rules query to find the associated physical hardware and the number of CPUs associated with that physical hardware. The total per physical hardware is stored and the next product is evaluated. If two or more products are on virtual systems associated with the same physical hardware, those CPUs are counted only once.

Per CPU Multiplier Based

The per CPU license models are used when a product's license is not based on the number of instances deployed of the software, but on the number of CPUs on which the software is installed. These server instances can be either physical or virtual systems.

Connection
The connection rules for all Per CPU licenses are the same. The connection between the CIs and Certificate is made based on the matching Company and Product Categorization.

Compliance
The Per CPU Multiplier Based license model is computed based on a multiplier factor for each processor. The value for each processor is then summed to determine the number of licenses consumed. For each unique CPU, the system looks up a value in an AR System form called AST:ComplianceMultiplierLookupTbl. The multipliers can be defined per Software Manufacturer, Processor Type, Processor Model, Processor Family, and Max Clock Speed of the processor. Processor Family and Max Clock Speed are optional in the multiplier lookup table, and the multipliers need not be defined based on these fields if the multipliers are the same. For example, an Intel processor might have a value of 2 while an AMD processor might have a value of 1.

Per CPU Constant Based

The per CPU license models are used when a product's license is not based on the number of instances deployed of the software, but on the number of CPUs on which the software is installed. These server instances can be either physical or virtual systems.

Connection
The connection rules for all Per CPU licenses are the same. The connection between the CIs and Certificate is made based on the matching Company and Product Categorization.

Compliance
The Per CPU Constant Based license model is computed based on a constant value for each processor. You must define a constant multiplier for every software manufacturer. The value for each processor is then summed to determine the number of licenses consumed. The compliance calculation is based on each unique core having a constant value based on the processor type with which it is associated.

Per Core Sum Based

The Per Core license model is similar to the Per Processor model. The main difference is that one additional level of information is retrieved, which is the number of cores. This information is then used to determine compliance based on the sum of cores on unique hardware, or through the use of a multiplier which could be used against the cores.

Connection
The connection rules for Per Core licensing are similar to the way other licenses work as well as how the Per Processor model works. The connection between the CIs and Certificate is made based on the matching Company and Product Categorization.

Compliance
The Per Core Sum Based license model is based on the sum of cores on the unique hardware on which the software is installed. These server instances can be either physical or virtual systems. This rule searches for the products that are associated with the certificate. For each product, the rules query to find the physical hardware associated and the number of cores associated with that physical hardware. The total per physical hardware is stored and the next product is evaluated. If two or more products are on virtual systems associated with the same physical hardware, those cores are only counted once.

Per Core Multiplier Based

The Per Core license model is similar to the Per Processor model. The main difference is that one additional level of information is retrieved, which is the number of cores. This information is then used to determine compliance based on the sum of cores on unique hardware, or through the use of a multiplier which could be used against the cores.

Connection
The connection rules for Per Core licensing are similar to the way other licenses work as well as how the Per Processor model works. The connection between the CIs and Certificate is made based on the matching Company and Product Categorization.

Compliance
The Per Core Multiplier Based license model is computed based on a multiplier factor for each processor type, which is then multiplied by the number of cores found. This value is then summed to determine the total number of cores in use. For each unique core, the system looks up a value in an AR System form called AST:ComplianceMultiplierLookupTbl. The multipliers can be defined per Software Manufacturer, Processor Type, Processor Model, Processor Family, and Max Clock Speed of the processor. Processor Family and Max Clock Speed are optional in the multiplier lookup table, and the multipliers need not be defined based on these fields if the multipliers are the same. For example, an Intel processor might have a value of 2 while an AMD processor might have a value of 1. The total number of cores that are required for compliance is based on these numbers and not on a raw count.

Per Core Constant Based

The Per Core license model is very similar to the Per Processor model. The main difference is that one additional level of information is retrieved, which is the number of cores. This information is then used to determine compliance based on the sum of cores on unique hardware, or through the use of a multiplier which could be used against the cores.

Connection
The connection rules for Per Core licensing are similar to the way other licenses work as well as how the Per Processor model works. The connection between the CIs and Certificate is made based on the matching Company and Product Categorization.

Compliance
The Per Core Constant Based license model is computed based on a constant value for each processor, which is then multiplied by the number of cores found. You must define a constant multiplier for every software manufacturer. This value is then summed to determine the total number of cores in use. For each unique core, the system looks up a value in a table that is stored for that processor type. For example, an Intel processor might have a value of 2 while an AMD processor might have a value of 1. The total number of cores that are required for compliance is based on these numbers and not on a raw count.

Was this page helpful? Yes No Submitting... Thank you

Comments