The Software Asset Management application can then use the metric attribute values to determine the number of rights that are required for each Oracle product. To determine this number, the Software Asset Management application multiplies the appropriate metric attribute value by the number of processors (Oracle WebLogic Server Standard Edition and all Oracle Database Standard editions) or processor cores (Oracle WebLogic Server Enterprise Edition and Oracle Database Enterprise Edition) on the underlying physical server that the Oracle product is installed or running on. The resulting value is compared against the total number of users and devices that are accessing the Oracle product. The number of required rights is set to the larger of the two values.

For example, 20 users are accessing an Enterprise Edition (EE) database that is running on a physical server with eight processor cores. The Named User Plus license metric consumes 200 rights because the number of rights that is based on the metric attribute value (25 minimum licenses x 8 CPU cores = 200 rights) is greater than the number of users that are accessing the database (20 users).

Although you can install and run Oracle products on physical servers, virtual servers, partitioned servers, and the cloud, the Per Processor license metric licenses processors on only the underlying physical server or cloud server.

The Per Processor license metric calculates the number of rights that are required for your Oracle products by multiplying the total number of processor cores by a core processor licensing factor, as specified on the Oracle Processor Core Factor Table. Use this license metric in environments where large numbers of users and devices are accessing the same environment or where users are not easily identifiable and countable, such as the Internet.

For example, a physical server that is running an Enterprise Edition (EE) database has two processors with four cores each. If your core processor licensing factor is 0.5, the Per Processor license metric consumes four rights for the physical server.

2 CPUs x 4 CPU cores x 0.5 licensing factor = 4 rights.

When you allocate rights for a database using the Named User Plus or Per Processor license metric, Software Asset Management automatically allocates rights for the associated database options and management packs using the same license metric.

If you create a Client Access License (CAL) record to specify the number of users or devices that can access an Oracle Database or WebLogic server, the Software Asset Management application licenses users and devices using only the Named User Plus license metric. Software Asset Management does not use the Per Processor license metric even if Per Processor licenses are available.

The Employee license metric licenses the total number of full-time, part-time, and temporary employees, including those employed directly and indirectly through agents, contractors, and consultants, according to Oracle's definition of internal business operations.

The Employee license metric calculates the number of licenses that are required by the total number of employees and not the number of employees that use the Oracle Java SE Universal. The licensing cost is calculated using a tier-based pricing model defined by Oracle. The pricing model is stored in the Price tier [samp_price_tier] table. For more details, see Pricing model for Oracle Java SE Universal.

Additionally, for the Employee license metric, the true-up cost is shown for a subscription period of one year.

When you run reconciliation for a software model that has one or more entitlements with the Employee license metric, a right is consumed for each employee recorded in the resource value records. You can create a resource value record for the Java SE software model keeping the value of units consumed same as the number of employees consuming the licenses. For details, see Create a resource value record.

When you're using a custom tier table, you can update the override license cost records associated with the Java SE software model. For details, see Create or update an override license cost record.