User guide

Appendix B - License File Format
License File Syntax
112 FLEXnet Licensing End User Guide
• HOST_BASED
• HOSTID
• PLATFORM
• USER_BASED
• VENDOR_STRING (if configured by the vendor as a pooling component)
If two lines differ by any of these fields, a new group of licenses, called a license pool, is created
in the vendor daemon, and this group is counted independently from other license pools with
the same feature name. A FEATURE line does not give an additional number of licenses,
whereas an INCREMENT line always gives an additional number of licenses.
The basic FEATURE/INCREMENT line format is:
{FEATURE|INCREMENT} feature vendor feat_version exp_date \
num_lic SIGN=sign [optional_attributes]
The six fields after the FEATURE/INCREMENT line keyword are required and have a fixed
order. They are defined by the vendor and cannot be changed. Table B-1 presents these fields
in the order they must appear.
Table B-1: FEATURE/INCREMENT Line Required Fields
Field Description
feature Name given to the feature by the vendor.
vendor Name of the vendor daemon; also found in the VENDOR line.
The specified daemon serves this feature.
feat_version Version of this feature that is supported by this license.
exp_date Expiration date of license in the format
dd-mmm-yyyy, e.g.,
07-may-2005. Note: If exp_date is the string “permanent”
or the year is 0 (or 00, 000, 0000) then the license never
expires.
num_lic Number of concurrent licenses for this feature. If the
num_lic is set to the string “uncounted” or 0, the licenses for
this feature are uncounted and no
lmgrd is required but a
hostid on the FEATURE line is required. See “Counted vs.
Uncounted Licenses.”
SIGN=sign or
AUTH=...
SIGN= signature to authenticate this FEATURE line.
If your publisher has deployed his vendor daemon using the
common vendor daemon technology, license certificate
signatures are embedded within the AUTH= keyword. Contact
your publisher for further details.