This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Revenera Community
- :
- FlexNet Publisher
- :
- FlexNet Publisher Forum
- :
- FlexNet Publisher API Help!
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Jan 29, 2014
11:25 AM
FlexNet Publisher API Help!
We are having a struggle between managing two separate license managers. On our product side we utilize FlexNet in a "True/False" architecture, however with a new 3rd party product we are integrating which has it's own license manager we need to somehow manage concurrent usage.
With the 3rd Party product there is an API call we can make to request "available licenses". I need to find out if there is a similar API function within FlexNet Publisher. That way we can sum the available licenses and determine if we can allow the product to check out a license.
Does anyone have any experience with this?
With the 3rd Party product there is an API call we can make to request "available licenses". I need to find out if there is a similar API function within FlexNet Publisher. That way we can sum the available licenses and determine if we can allow the product to check out a license.
Does anyone have any experience with this?
(1) Reply
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Feb 03, 2014
09:19 AM
If by 'available licenses' you mean the number of keys that have not been checked out yet, they you should look at the doc for the LM_A_VD_FEATURE_INFO attribute. This will tell you how many keys are on the server and how many are in use. Then you do the math to figure out how many are available.
This isn't as straight forward as it seems. This is the type of data that is out of date as soon as you get it since a key may get checked out immediately after you make the call. You also have to take into account the possibility of multiple feature lines for the same feature, multiple license servers, and uncounted licenses.
-Eric
This isn't as straight forward as it seems. This is the type of data that is out of date as soon as you get it since a key may get checked out immediately after you make the call. You also have to take into account the possibility of multiple feature lines for the same feature, multiple license servers, and uncounted licenses.
-Eric
![](/skins/images/CC38E504FC9E1309DC48ACFEB4925670/responsive_peak/images/icon_anonymous_message.png)