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 Compliance |
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 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:
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 |
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 Compliance
The answers to these question are used to:
Example |
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 Compliance
The answers to these questions are used to compute compliance:
Example |
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. Compliance
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 |
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 Compliance |
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 Compliance |
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 Compliance |
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 Compliance |
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 Compliance |
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 Compliance |
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 Compliance |
Comments
Log in or register to comment.