Skip to main content

Hi guys,

is there a easy API call where I get the license consumption for a client?

I found this API call:


{{ServerUrl}}/Client/{{clientId}}/License

 

But this gives me only the used license type / name e. g.:

{

    "licensesInfo": f

        {

            "platformType": 1,

            "license": {

                "licenseType": 1,

                "appType": 33,

                "licenseName": "Server File System - Windows File System"

            }

        },

        {

            "platformType": 1,

            "license": {

                "licenseType": 3,

                "appType": 81,

                "licenseName": "Application Class 1 - SQL Server"

            }

        }

    ]

}

 

My goal is to get a output like:

 

clientA is using 200gb of license “Server File System - Windows File System”

and 

clientA is using 100gb of license “Application Class 1 - SQL Server”

 

 

Hey @Dimitri 

Check out this other thread on a similar topic, the answer may be in there.

 

Specifically,

 

Under 11.22.3 I had a quick look through http://<hostname>/webconsole/api/help and found a couple that might do the trick for you:

  • GET /CommServ/LicenseUsage
    • This will get you all the usage. Looks like it’s not present in 11.20.x from my quick check
  • GET /CommcellRegistrationInformation
    • This will get you the expiry date and CCID

Hello Damian,

thanks for reply. As far as I can see this is not exactly what I need. With the mentioned queries you get the license usage from a given license. I need the client consumption in “gb” or “mb” or “tb” for any used license.

For example something like:

Client_A is using 100g from SQL License. 

Client_A is using 20g from Windows File System License.

...

 

I’ll have a look on this. Thought there is an easy query to show the exact client - license consumption in mb/gb/tb.

Got it - yes using REST to query the results of the report could be a good way. @bish may be able to chime in more, he posted the following in the other thread:

 

 

Reply


Terms & ConditionsCookie settings