Define a Model Definition
Named license pools are defined using a model definition. The model definition is configured and uploaded per license server instance or Cloud Licensing Service (CLS) instance. You can use the FlexNet License Server Administrator command-line tool to view or delete named license pools and license count allocations on the license server.
A model definition usually specifies the following:
| • | One or more named license pools |
| • | Rules of access that allow access to licenses |
| • | Rules of access that deny access to licenses |
The model definition must be written according to the grammar described in Model Definition Grammar and Syntax—EBNF. The following shows a sample model definition:
|
model "example" { partitions { partition "engineering" { f1 1.0 2 } }
on hostid("F01898AD8DD3/ETHERNET", "5E00A4F17201/ETHERNET") { use "engineering" accept }
on any() { use "default" accept } } |
This model definition creates the named license pool called engineering. It places 2 counts of feature f1, version 1.0 in the engineering license pool. The remainder of the counts will be placed in the default license pool. Client requests that include the ETHERNET hostid F01898AD8DD3 or 5E00A4F17201 are allowed access to the engineering license pool, ensuring that they have access to these licenses. Client requests from other hostids are only allowed access to counts in the default license pool.
For more information about the setup and use of named license pools and model definitions on the license server, see Allocating Licenses Using Named License Pools in the More About License Server Functionality
The appendix Model Definition Grammar for Named License Pools , section Use Case Examples and Their Model Definitions for Named License Pools, lists use cases that help you write your own model definition.