Named License Pools

You can define one or more named license pools under the optional partitions element. If you do not specify a named license pool, all feature counts are placed in the default license pool. (The naming of the element stems from previous releases of the FlexNet Embedded license server, where named license pools were referred to as “partitions”.)

Each named license pool is introduced by a partition element, followed by the name of the license pool. You then specify one or more features that the named license pool should contain. For each feature, you need to specify the feature name, feature version, and feature count. The feature count can be expressed as a number or as a percentage of the overall feature count that is available on the license server.

Example

partitions {

partition "p1" {

"f1" 1.0 50

"f1" 2.0 25

"f2" 1.0 100

}

}

Limitations

In a model definition, the features defined in each partition element must be unique. In other words, a named license pool with the following features is not allowed:

partition "p1" {

"f1" 1.0 50

"f1" 1.0 25

}

However, when the license server creates a named license pool, it may create two slices of a feature that has the same name and version. This can occur only if the features have different feature IDs, for example, because they differ in their expiry dates, as shown in this example:

•

Feature slice 1: fid1 f1 1.0 10 permanent

•

Feature slice 2: fid2 f1 1.0 10 2028-12-31

Further Information

The following section, Rules of Access and Conditions, describes the syntax and condition types used in rules of access.

For information about how the license server allocates feature counts to license pools, see Server Behavior When Distributing Feature Counts to Named License Pools.