Validating Model Definitions for Named License Pools

The license server validates all model definitions. Invalid model configurations are rejected to prevent ambiguous license assignments.

Examples for Rejected Model Definitions

The following examples illustrate model definitions that will be rejected.

•

Duplicate Feature Entries (Same Name and Version)

If a model contains multiple entries for the same feature name and version, regardless of the assigned counts, it will be considered invalid.

partition "p1" {

"f1" 1.0 10

"f1" 1.0 5

}

•

Duplicate Feature Entries with Matching Vendor Strings

If the feature name, version, and vendor string all match across multiple entries, the model will be rejected.

partition "p1" {

"f1" 1.0 10 vendor string matches "abc"

"f1" 1.0 20 vendor string matches "abc"

}

•

Mixed Vendor String Assignments for the Same Feature

If a feature is assigned both with and without a vendor string match in the same partition, the model is invalid.

partition "p1" {

"f1" 1.0 10

"f1" 1.0 20 vendor string matches "abc"

}

Error Message for Rejected Model Definitions

In case of a rejected model, an error message similar to the following is displayed:

{

"key": "glsErr.invalidModel",

"message": "Invalid model posted, Duplicate feature entries found : [feature=ss_f1, version=1.0, vendorString=abc]",

"arguments": [

"Duplicate feature entries found : [feature=ss_f1, version=1.0, vendorString=abc]"

]

}