Glossary

The process by which FlexNet Manager for Engineering Applications takes imported report log data and uses it to populate the data warehouse, so the data can be used to generate Flexera Analytics (Cognos) reports.

A document that defines the terms under which an enterprise purchases product licenses from a software vendor. These terms typically include the contract’s start and end dates, the fixed and variable costs, remix rules for the contract, and any license usage restrictions (for example, geographic restrictions).

Product licenses purchased under a contract are grouped into one or more license pools.

A process that “serves” clients. Sometimes referred to as a server or service process.

One or more ASCII text files written by the license server. A debug log file contains status and error messages useful for debugging the license server.

Your customer to whom the FlexEnabled product is supplied.

The characteristics that define the legal right to use the feature or product.

A license to use a discrete unit of functionality in a software product. A software vendor delivers feature licenses to the enterprise in one or more license files.

Feature licenses are distributed over a network by a vendor daemon running on a license server. Feature licenses are used when an end user accesses licensed parts of a software product.

A line in a license file that licenses a particular feature. A feature line begins with one of the keywords FEATURE, INCREMENT, or UPGRADE.

Contains all the necessary components and libraries used by the software publisher to create a FlexEnabled product.

A license that can authorize usage of a product by one of a group of users on a network.

A license server is required to manage a floating license. Floating licenses can either be counted or uncounted. An uncounted floating license is effectively a site license.

A means used to uniquely identify a specific system.

A user-based organizational structure that is enabled for hybrid (or multi-dimensional) aggregation—aggregation on both the organization level (for example, geographic) and the license-server level.

The legal right to use a feature. FlexNet Publisher can restrict licenses for features by counting the number of licenses already in use for a feature when new requests are made by the FlexNet Publisher product. FlexNet Publisher can also restrict product usage to particular node or user name.

A license file is a collection of feature licenses. It is a text file specific to an enterprise site containing the license certificates from one or more software publishers and/or vendors. The enterprise installs the license file on a license server.

This file can contain descriptions of the following, for one or more FlexEnabled products:

A 12- to 20-character hexadecimal license signature used to authenticate a license. See also signature.

License pools are used to define common license terms for a group of product licenses purchased under a contract. These terms include remix rules and license usage restrictions.

A computer system that runs the license server processes. The license server machine hosts all site-specific information regarding licensed feature usage. Multiple license server machines used for three-server redundancy can logically be considered the license server machine. Also known as license server node.

The constraints applied to the legal right to use a feature.

The daemon that sends client processes to the correct vendor daemon on the correct machine. The same license manager daemon process can be used by any application from any vendor because this daemon neither authenticates nor dispenses licenses. lmgrd processes no user requests on its own, but forwards these requests to a vendor daemon.

A license that can authorize use of a product to be run on a specific machine based on a unique identifier known as a hostid. Node-locked licenses can be counted or uncounted. Node-locked, uncounted licenses do not require a license server.

Hierarchical structures that help you report on how software is being used by user ID, host, or project. Organizational structures provide a set of rules for how to distribute software usage across nodes in your enterprise.

A set of products combined into a package with the restriction that the package components of a single license may not be simultaneously shared.

A product choice captures the results of the product resolution process for each unique set of possible products to choose from.

A product license event records the usage of a product license by a user. Product license events are not created directly by the license server; they are created by the product usage aggregation process by combining feature license events.

The process of creating product license events by analyzing feature license events. This is how FlexNet Manager for Engineering Applications identifies which products were used.

The feature usage data written by a single vendor daemon. Report logs are not human readable; the data is compressed and authenticated for use with FlexNet Manager for Engineering Applications.

FlexNet Manager for Engineering Applications uses the data contained in the report log files to produce various usage reports.

A license that requires the management of a license server.

A company that makes software products that use a licensing system to control access to various functions (features) of the product. The software producer may also be the software vendor.

See package suite.

An encryption method employing an industry-recognized asymmetric, public/private key digital signature.

A license that does not restrict the number of uses of a feature. Usually node-locked to a machine hostid.

The concept of upgrading the version entitlement for a given license certificate.

The alias given to one or more vendor daemon names that symbolically represents the vendor’s name from whom the daemons are deployed.

A unique vendor name that is supplied to the software publisher by Flexera Software. This is used as the name of the vendor daemon.