View Partitions

Use the -partitions command to view all partitions for the license server. The output lists information about every feature and every feature slice in each partition (feature slices are portions of feature counts allocated to a partition).

See JSON Response Details for a description of the most relevant lines in the JSON response.

To view all partitions

Enter a command similar to this:

flexnetlsadmin -server licenseServer_baseURL -authorize yourAdminName {yourAdminPassword|
-passwordConsoleInput} -partitions
 

The following shows example output (shortened for documentation purposes):

{

"partitions": [

{

    "id": 1,

    "name": "default",

    "lastModified": 1563445226020,

    "default": true,

    "activeFeatureSlices": [

        {

            "id": 1,

            "feature": {

                "id": 1,

                "type": "CONCURRENT",

                "featureName": "f_con_1",

                "featureVersion": "1.0",

                "expiry": "permanent",

                "featureCount": 100,

                "used": 96,

            },

            "slice": 97,

            "used": 95,

            "computedCount": 97,

            "requested": "97",

            "uncounted": false

            "status": "NORMAL",

        },

        {

            "id": 2,

            "feature": {

                "id": 2,

                "type": "CONCURRENT",

                "featureName": "f_con_2",

                "featureVersion": "1.0",

                "expiry": "permanent",

                "featureCount": 80,

                "used": 40,

            },

            "slice": 50,

            "used": 26,

            "computedCount": 50,

            "requested": "50",

            "uncounted": false

            "status": "NORMAL",

        },

    ]

},

{

    "id": 2,

    "name": "p1",

    "lastModified": 1564133869116,

    "default": false,

    "activeFeatureSlices": [

        {

            "id": 3,

            "feature": {

             "id": 1,

                "type": "CONCURRENT",

                "featureName": "f_con_1",

                "featureVersion": "1.0",

                "expiry": "permanent",

                "featureCount": 100,

                "used": 96,

            },

            "slice": 3,

            "used": 1,

            "computedCount": 3,

            "requested": "3",

            "uncounted": false

            "status": "NORMAL",

        }

    ]

}

]

}

JSON Response Details

The following section explains the most relevant lines in the JSON response that is output when you use the -partitions command to view partitions.

Elements in a JSON Response

Parent Element

Child Element

Description

partitions

"id": n

The partition ID is assigned to the partition by the license server after the model definition has been uploaded.

"name": "name"

The partition name. The names default and reservations are reserved and cannot be used.

"lastModified": yyyy-MM-dd'T'HH:mm:ss.SSS'Z'

Indicates when the partition was last changed (for example, the allocated feature count or rules for that partition have changed). The date is specified using the ISO 8601 date/time notation, expressed in UTC (for example, 2019-10-22T11:16:31.000Z).

"default": true|false

Indicates whether the partition is the default partition or not. The default partition cannot be deleted.

activeFeatureSlices

"id": n

Each feature slice is assigned an ID by the license server after the model definition has been uploaded.

"slice": n

Total license count for the feature that has been allocated to the partition.

Typically, this would be the count specified in the model definition, assuming that sufficient counts are available on the license server. If fewer counts are available on the license server than are specified in the model definition, or if existing usage prevents allocation into the partition after a new model definition has been uploaded, "slice" specifies the actual number of allocated licenses.

"used": n

The number of feature counts that have been served from this slice.

activeFeatureSlices (continued)

"computedCount": n

The number of feature counts the slice should have, based on the model definition and the number of feature counts the server has been provisioned with.

"requested": n

The license count for the feature that has been specified in the model definition, irrespective of whether sufficient counts are available on the license server.

The following sample code from a model definition requests 5 counts of feature f1 for the engineering partition:

model "example1" {

    partitions {

      partition "engineering" {

        feature "f1" 1.0 5

      }

    }

}

 

"status": "value"

The status of the feature slice indicates how the slices of a server are used.

Possible values:

OVER_ALLOCATED—The slice has more feature counts than it should have, based on the model definition and the number of counts the server has been provisioned with ("slice" > "computedCount").
NORMAL—The slice has the number of feature counts that it should have, based on the model definition and the number of counts the server has been provisioned with ("slice" = "computedCount").
UNDER_ALLOCATED—The slice has fewer feature counts than it should have, based on the model definition and the number of counts the server has been provisioned with ("slice" < "computedCount").