User guide

Appendix B - License File Format
License File Syntax
116 FLEXnet Licensing End User Guide
Examples:
PACKAGE suite sampled 1.0 SIGN=3B24B2F508CB \
COMPONENTS="comp1 comp2" OPTIONS=SUITE
FEATURE suite sampled 1.0 1-jan-0 5 SIGN=4193E6ABCCCB
This is a typical OPTIONS=SUITE example. There are two features, “comp1” and “comp2,”
which are each version 1.0, each with five non-expiring licenses available. When “comp1” or
“comp2” is checked out, “suite” is also checked out.
PACKAGE suite sampled 1.0 SIGN=2CBF44FCB9C1 \
COMPONENTS="apple:1.5:2 orange:3.0:4"
FEATURE suite sampled 1.0 1-jan-2005 3 SIGN=321E78A17EC1 SN=123
In this example, the component version overrides the feature version, and the number of
licenses available for any component is the product of the three licenses for “suite” and the
number of licenses for that component. The result is equivalent to:
FEATURE apple sampled 1.5 1-jan-2005 6 SIGN=0D3AD5F26BEC SN=123
FEATURE orange sampled 3.0 1-jan-2005 12 SIGN=EB16C5AE61F0 SN=123
FLEXNET LICENSING VERSION NOTES
• Ability to store PACKAGE lines in separate files introduced in v6 client library.
•
pkg_version field required in pre-v7.1 client library.
SUPERSEDE
[="
p1 p2 ..."]
Optional field. Used in conjunction with ISSUED date.
Replaces all PACKAGE lines for the same package name
with ISSUED dates previous to
dd-mmm-yyyy.
ISSUED=
dd-mmm-yyyy
Optional field. Used in conjunction with SUPERSEDE.
Replaces all PACKAGE lines for the same package name
with ISSUED dates previous to
dd-mmm-yyyy.
SIGN=\
pkg_sign
License key or SIGN= signature.
Table B-4: PACKAGE Line Fields (cont.)
Field Description