# Glossary

FlexNet Publisher uses the following terms:

Term | Meaning
activation specification record (ASR) | A signed XML file used with local activation and short code activation that contains information about license rights, configuration settings for the publisher’s trusted storage segment, and additional information required by the activation transaction.
activatable license | A license right in trusted storage that can be activated to a FlexEnabled client. See also license group.
activate | The action of loading license rights into trusted storage.
activation | In FlexNet Publisher Licensing Toolkit, this is a process used to load license rights into trusted storage. Different activation types include:
| • | programmatic activation
| • | manual activation
| • | short code activation
| • | local activation
In FlexNet Operations, this is a process used to generate license rights in either trusted storage and in license files.
activated feature line | See feature definition line.
Activation API | Functions available in the FlexNet Publisher Licensing Toolkit libraries that allow you to initiate transactions and manage license rights in trusted storage. The Activation API is used to develop the functionality in an activation utility.
activation client | The system that works with an activation server to receive license rights. This system can be either a license server or a FlexEnabled client. The activation client initiates an activation, repair, or return transaction with an activation server, using an activation utility. The following transaction types can be initiated by an activation client:
| • | activation transaction
| • | return transaction
| • | repair transaction
activation ID | A unique value used in FlexNet Operations to identify the transaction that generated the license rights, either for license files or trusted storage. When license rights are requested for trusted storage, this value must be included in the activation request as the entitlement ID. It is stored in the fulfillment record (in trusted storage) as the entitlement ID.
activation request | A message sent by an activation utility to an activation server that initiates an activation transaction.
activation response | A message sent from an activation server to an activation client, in response to an activation request. This message defines the license rights.
activation server | A system that responds to requests for license rights from an activation client. The activation server can be one of the following:
| • | a license server
| • | FlexNet Operations
| • | an LGT-based activation server
An activation server can also perform repair and return transactions.
activation transaction | A sequence of activation request and activation response messages, and related actions that result in license rights being loaded into trusted storage.
activation utility | A utility that initiates an activation transaction, repair transaction, or return transaction by sending a request to an activation server. This utility also processes the response received from the activation server. It uses the Activation API to perform these capabilities. It is written by the software publisher to meet specific business process requirements. This application can be either separate from or embedded in the FlexEnabled application.
anchor | A link between the system and the trusted storage that is used to detect whether trusted storage has been tampered with, deleted, or restored. Anchors are also used to ensure that information in trusted storage about trial licenses persists beyond the expiration date.
ASR file | See activation specification record (ASR) .
binding | A capability used with trusted storage where one or more properties of a system, combined together into a unique identifier, are used to ensure that license rights held in trusted storage are not copied to another system.
borrowing | A capability available in FlexEnabled applications that enables a user to temporarily obtain a license in such a way that the license can be used locally for a limited period of time while the user is disconnected from the local network.
bulk entitlement | An entitlement created for an order of multiple copies of a single product or suite. Bulk entitlements are used for sales through reseller channels.
checkin | The transaction that a FlexEnabled application performs to return a license after it has been checked out. This operation is not the same as an activation transaction. FlexEnabled applications must perform a checkout and checkin transaction to use a license.
checkout | The transaction that a FlexEnabled application performs to request a license. This transaction is different than activating a license. FlexEnabled applications must perform a checkout and checkin transaction to use a license.
client system | A general term used to define any system that interacts with a server in a client-server relationship. When using FlexNet Publisher Licensing Toolkit there are two types of clients:
| • | activation client
| • | FlexEnabled client
concurrent license | A license that can be shared among users by allowing each user to check out and then return the license. These licenses are served to FlexEnabled applications from a license server. If all licenses are being used, an additional user cannot run the FlexEnabled application until one of the other users check in their license. When one user finishes using the license, another user can begin using it. Also called floating license or served license rights .
config response | A response to any request from an activation client that contains information about how the publisher’s trusted storage segment must be configured (called the trusted storage segment configuration). This response is processed by the activation utility and results in a segment of trusted storage being created or re-configured for that publisher.
consumer | An individual or small business who purchases a license for their individual use. Compare with enterprise.
counted | A type of license right or license model that defines a multiple quantity of licenses and allows concurrent use of the licenses. This term is taken from the fact that the license server counts the number of licenses that are being used.
debug log file | A file used by the license server to record status and error messages that are useful for debugging the license server. Each license server can have one or more of these files.
demo license | See trial license.
duplicate grouping | A capability in the FlexNet Publisher Licensing Toolkit used to uniquely identify a single client (or client checkout request) for the purpose of counting the number of licenses that are used. Duplicate grouping defines a set of rules under which multiple checkout requests can share the same license(s).
embedded activation | See local activation.
encryption seed | A set of values defined by a software publisher that are used when creating a publisher-specific vendor daemon.
end-user | A person who uses a FlexEnabled application. This role is not the same as a license administrator.
end-user system | See client system.
end-user license administrator | See license administrator.
enterprise | An organization that purchases licenses on behalf of a number of individual users. Compare with consumer.
entitlement | A representation of the license model and product that a customer has bought. It is a definition only. The customer will need to fulfill the entitlement so that the license rights can be populated to license files or trusted storage. In FlexNet Operations, there are two types of entitlements:
| • | bulk entitlement
| • | simple entitlement
Each entitlement is uniquely identified by an entitlement ID.
entitlement ID | In FlexNet Publisher Licensing Toolkit, an attribute in trusted storage that stores a value used to identify the customer’s entitlement. FlexNet Operations uses an intermediary step to generate license rights, called Activate Licenses. The activation ID generated by Activate Licenses step in FlexNet Operations is stored as the entitlement in trusted storage. In FlexNet Operations, a value that uniquely identifies the entitlement.
expiring license | License rights granted to a customer for a limited duration. When the license rights have expired, the licenses can no longer be checked out.
feature | In the context of a software application, this is a single unit of capability. In FlexNet Publisher Licensing Toolkit, this is an identifier used to associate a license model to a unit of capability in a software application. The software publisher defines which features in their software application map to a single feature in FlexNet Publisher Licensing Toolkit. For example, a feature in FlexNet Publisher Licensing Toolkit could represent any of the following:
| • | The entire software application.
| • | A subset of menu items.
| • | A specific set of data available from the software application.
| • | A process in the software application.
The software publisher also defines the license model for each FlexNet Publisher Licensing Toolkit feature. This gives software publishers the ability to define a different license model for each feature in the software application. The combination of FlexNet Publisher Licensing toolkit features with the respective license model define the license rights for the entire software application.
feature bundle | A collection of features in FlexNet Operations. It exists primarily to enable modularity and re-use.
feature definition line | An entry in a license file or fulfillment record that describes a feature. Each line begins with the keyword FEATURE, INCREMENT, or UPGRADE. In license files, feature definition lines are used with SERVER and VENDOR lines to define the license model. In trusted storage, feature definition lines are used with the fulfillment record properties to define the license model.
feature line | See feature definition line.
file-based activation | See manual activation.
FlexEnabled application | A software application that uses FlexNet Publisher Licensing Toolkit to implement its license models.
FlexEnabled client | A client system where a FlexEnabled application is installed.
Flexible API | Functions available in the FlexNet Publisher Licensing Toolkit libraries that allow FlexEnabled clients to access license rights.
FlexNet Agent | A utility that runs on a license server and allows communication between the license server and other FlexNet products.
FlexNet Manager | This is a license server management and license management decision support solution in the FlexNet product family that allows companies to centrally manage license servers and license usage across the enterprise.
FlexNet Operations | A product in the FlexNet family of products that manages entitlements and generates license rights.
floating license | A license that can be shared among users and is served to FlexEnabled applications from a license server. When a user finishes using the license, another user can begin using it. Also called concurrent license or served license rights .
fulfill | The action of getting license rights.
fulfillment record | In FlexNet Publisher Licensing Toolkit, a data structure specific to trusted storage that defines license rights.
heartbeat | A type of message sent periodically between two systems (for example, a FlexEnabled application and a license server) to identify whether each is running and able to communicate with the other.
hop count | In FlexNet Publisher Licensing Toolkit, the number of times that license rights in a single fulfillment record have been transferred from one license server to another.
hostid | In FlexNet Publisher Licensing Toolkit, the value of a specific system attribute that uniquely identifies the host. For example, if IP address is a hostid type, then the hostid might be 129.87.33.101. Hostids are used in node-locked license.
hostid type | A type of attribute that is available to uniquely identify a system. For example, disk serial number, IP address, or MAC address.
hybrid license | In FlexNet Publisher Licensing Toolkit, a type of license right in the license group on trusted storage that can function as either a concurrent license or as an activatable license.
internet activation | See programmatic activation .
keyboard activation | See short code activation.
license administrator | A person in an enterprise who is responsible for installing the FlexEnabled application and administering the licenses and license servers.
license certificate | A set of feature lines in a license file that define the complete license model for a single FlexEnabled application. A single license file can contain multiple license certificates. Compare with license file.
license file | A text file, usually with the .lic extension, that contains license certificates from one or more publishers.
license-file list | See license search path.
license generator | A general term used to describe any mechanism a software publisher uses to generate license rights for their customers. The following FlexNet capabilities and products can function as a license generator:
| • | LGT-based activation server: generates license rights for trusted storage.
| • | FlexNet Operations: generates license rights for trusted storage and license files.
| • | lmcrypt: generates license rights for license files.
License Generator API (LGAPI) | A set of functions in the FlexNet Publisher License Generator Toolkit (LGT) used to create an activation server.
License Generation Toolkit (LGT) | A product in the FlexNet product line used to create an activation server.
license group | A mechanism used to describe licenses rights held in server-side trusted storage. These groups are not used with license rights held in license files.
| • | activatable—A license right in trusted storage that can be activated to a FlexEnabled client.
| • | concurrent—license rights in this group can be shared among users by having a FlexEnabled client to check out, and then return the license.
| • | hybrid—these license rights have the same characteristics as both the activatable license group and concurrent license group. They can be activated to client-side trusted storage on a FlexEnabled client or checked out by a FlexEnabled client.
Although you see these group names used to describe license rights in client-side trusted storage, the capabilities of the license rights do not change. Once license rights are in client-side trusted storage, you cannot transfer, serve, or activate them to another system. The FlexEnabled application can only check out and check in these licenses. The group names are used when a license right is returned to the license server, so that it is assigned to the correct license group on the license server.
license model | The set of characteristics that determine the conditions under which (for example, how, when, where, and by whom) a FlexEnabled application can be used.
license rights | Information in trusted storage or license files that defines the license model and controls user access to a specific FlexEnabled application.
license search path | A property that the FlexEnabled application uses to locate where license rights are stored. Sometimes known as a license-file list.
license server | A set of files from the FlexNet Publisher Licensing Toolkit, that work together to manage and serve licenses to FlexEnabled applications. A license server is required to support a concurrent license model. The license server consists of a license server manager, one or more vendor daemons, zero or more options files, zero or more debug logs, and, optionally, a report log. These components are available in the FlexNet Publisher Licensing Toolkit. If the license server supports license rights held in trusted storage, it also includes an activation utility. It may, optionally, act as an activation server.
license server system | See license server.
license server manager (lmadmin or lmgrd) | A license server manager lmadmin or lmgrd executable that forwards connections from a FlexEnabled application to the correct vendor daemon. Because the vendor daemons are responsible for authenticating requests and serving licenses, a single license server manager can be used with multiple vendor daemons on the license server.
license sharing | A capability available in FlexNet Publisher Licensing toolkit where multiple license requests from the same user, host, or display results in only one license being used. Also known as duplicate grouping.
licensing client | See FlexEnabled client.
lmadmin | The license server manager introduced in version 11.6, which includes a Web-based interface.
lmgrd | A command-line-based license server manager.
local license rights | License rights that are stored on the same system where the FlexEnabled application is running, rather than on a license server.
local activation | A type of activation where license rights are loaded using an ASR file. The ASR file must reside with the FlexEnabled application. This does not require user intervention.
machine ID | A value, generated using attributes of the system, that is used to bind trusted storage to that system.
maintenance | A maintenance represents a customer’s right to obtain updates and upgrades to a particular licensed product or suite for a specified duration. Used in FlexNet Operations.
manual activation | An type of activation where license rights are transmitted from an activation server to another system using a set of request and response messages that are formatted as XML. These messages are saved to and read from physical XML files. An activation utility loads the license rights from an XML file into trusted storage.
node-locked license | A license that can be used only when the FlexEnabled application is run on a specific system or by a specific user (as defined by the hostid).
options file | A configuration file available on the license server that license administrators can use to either change license server behavior or implement certain licensing policies. Each software publisher has its own separate options file that works with a specific vendor daemon.
orderable | Anything that can be purchased by a customer. Orderables can include suites, products, documentation, and maintenances.
package | In FlexNet Publisher Licensing Toolkit, a set of features that can be grouped and licensed together.
part number | A unique identifier, typically correlated with an order system, assigned by a publisher to a product.
permanent license | License rights granted to a customer that do not expire.
product | Anything that can be sold by a publisher and can be licensed.
product ID | In FlexNet Publisher Licensing Toolkit, one of the values that uniquely identifies the license rights in trusted storage. See also entitlement ID.
programmatic activation | A type of activation where license rights are transmitted from one system to another across a network using a set of request and response messages that are formatted as XML. This process is the identical to manual activation, except that it does not generate a physical XML file. An activation utility loads the license rights from the XML message into trusted storage. This is an automated process and does not require user intervention.
publisher ID | A value used by trusted storage to uniquely identify the software publisher’s logical and physical licensing components. Flexera Software distributes this identifier to software publishers. It is used to prepare certain FlexNet Publisher Licensing toolkit files that access trusted storage. This value is not the same as the vendor daemon.
quorum | A condition specific to three-server redundancy that is met when at least two of the three license servers are running and can communicate with each other using heartbeats.
rehost | The process of reissuing a node-lockedlicense for a different system. This process requires software publishers to perform certain activities to redefine the license rights so that they will work properly on the new system.
repair | An action that uses a repair transaction to correct damage to the license rights in trusted storage.
repair request | A message sent by an activation utility to an activation server that initiates a repair transaction. The activation server provides the information that repairs the license rights in trusted storage. An activation utility is an application that initiates the repair transaction.
repair response | A message sent from an activation server to an activation client, in response to a repair request. This message contains information that is used to the repair the license rights.
repair transaction | A sequence of repair request and repair response messages, and the related actions that result in license rights being repaired in trusted storage.
report log file | A file that runs on a license server that contains data about the features used by a single vendor daemon. Report logs are encrypted and cannot be read by a person, but are used by FlexNet Manager to produce reports.
return | The process used with trusted storage where license rights are transferred back to the activation server that originally held them. These license rights are then available so that they can be activated on another system.
return request | A message sent by an activation utility to an activation server that initiates a return transaction. The activation server receives the license rights returned by an activation client. An activation utility is an application that initiates the return transaction.
return response | A message sent from an activation server to an activation client, in response to a return request.
return transaction | A sequence of return request and return response messages, and the related actions, that result in license rights being returned from trusted storage to the activation server.
served license rights | License rights that are stored on a license server and are checked out when needed by FlexEnabled applications that run on client systems. These license rights are used for concurrent licensing.
short code | A multi-character code used with a short code activation transaction, a repair transaction, or a return transaction.
short code activation | A type of activation where license rights are loaded from an ASR file using an activation transaction that requires a specific code (called a short code). Often the user enters this code into a prompt from the application. This is also is used for licensing via automated telephony.
signature | A secure multi-character string added to the license certificate that ensures it has not been modified.
simple entitlement | An entitlement for a single, specific customer.
software component | A product component that is instrumented with a licensing technology by software developers. Possible deployment formats include, but are not limited to: a compiled and fully linked executable, a software library, or a shared object. A component may have one or more features implemented. Compare with feature.
suite | A set products grouped together that are functionally complementary and associated with one or more license models.
supersede | A capability in FlexNet Publisher Licensing Toolkit, used to replace the characteristics of old license rights with new characteristics.
three-server redundancy | A capability in the FlexNet Publisher Licensing Toolkit that enables license administrators to configure three license servers in a failover cluster.
triad | A set of three license servers which operate together to support three-server redundancy.
trial license | License rights granted to a user for a limited duration so that the user can evaluate the software application.
transfer | A process used by trusted storage to move license rights from one license server to another.
trusted storage | A tamper-proof area on the system that stores license rights. This storage location is different than license files and requires a different mechanism for loading and managing license rights. Compare with license file.
trusted configuration | A set of attributes that define the security configuration of a segment of trusted storage. Each software publisher can configure their segments of trusted storage differently. This configuration defines the settings for binding, anchoring, and windback detection.
trusted configuration file | A file that stores the attributes that define a software publisher’s trusted storage segment configuration.
trusted storage configuration | See trusted configuration.
uncounted | A license right attribute that allows an unlimited number of concurrent uses of a FlexEnabled application. Compare with counted.
unserved license rights | These are license rights that are not served from a license server. These license rights are located with the FlexEnabled application. Also known as local license rights.
upgrade | A process where a user installs a newer version of a FlexEnabled application and also updates the license rights so that they can use this newer version.
upsell | The process of transitioning from a product of lesser functionality to one of greater functionality in the same product line.
vendor daemon | One of the files that is a part of the license server. This executable is customized and built by the software publisher using files in the FlexNet Publisher Licensing toolkit. The vendor daemon is responsible for communicating with the FlexEnabled application and issuing licenses.
Vendor Certificate Generator | A publisher-built component, that is a part of FlexNet Operations, that creates license certificates or signed feature lines in fulfillment records. This functions similarly to lmcrypt.
vendor name | A value used to uniquely identify a software publisher’s logical and physical licensing components. It is used to prepare certain files in the FlexNet Publisher Licensing toolkit that manage license rights in both trusted storage and license files. Flexera Software distributes this identifier to software publishers. This value is not the same as the publisher ID.
windback | A condition where the system clock has been set to an earlier date or time. One reason users change the system clock is to extend the license duration.
windback detection | A capability in FlexNet Publisher Licensing Toolkit that detects whether a user has reset the system clock. This prevents a user from extending the duration of the license.
windback tolerance | An acceptable amount of windback to a system clock that won't trigger windback detection. A certain tolerance is normally allowed to account for time zone differences or Daylight Saving Time.
web register key | A unique value used in a bulk entitlement to create the activation ID for an entitlement line item. After web register keys are either generated or imported, this value becomes the activation ID in the bulk entitlement. When a user requests license rights for trusted storage, this value must be included in the activation request as the entitlement ID. It is stored in the fulfillment record (in trusted storage) as the entitlement ID.

Open topic with navigation