I am exploring how metered licensing can benefit us for one of our business use case. I went through the documentation and below are my queries/ understanding I want to clear. If I’m not wrong, metered licensing is supported by both C & Java FNE. What minimum version of C & Java FNE supports Metered Licensing? Is it possible to just capture the ‘capped’ usage at the FNE side, and enforce (stop the use of any feature, say, after x number of hours) the metered licensing w/o reporting usage back to the back-office? Or in other words, is it optional to send the usage information to the back office? If yes: is it supported on both FNEs (C and Java)? Is ‘Flexnet usage management’ a separate paid service, than FNO? Any steps/processes to use ‘Flexnet usage management’? If we enforce metered licensing only at the FNE side, then do we still need ‘Flexnet usage management’? What are the features/ benefits of using ‘Flexnet usage management’? Do we need the acquisition API for metered licensing to work? Is FlexNet Embedded local license server supported for both C & Java FNEs? ... View more

Hi, We are using generateCapabilityResponse API, in that we pass 'generateCapabilityResponseRequestType' object, inside that we pass data in 'request'. We are sending some data (string) inside request, which is stored in 'notes' in FNO (visible on device page). I want to know what is the maximum size allowed in bytes (or length of string),that can be stored in 'notes' of a device? I went through the FNO documentation there was no explicit mention about the limit. Thanks and Regards, Anshul Jain ... View more

Background: I am using flexnetsdk.version 2017.11.0.218710 (Java) Code change I have done: called method   enableWindbackDetection(windbackTolerance, windbackFrequency) with windbackTolerance=1800, windbackFrequency=0 Scenario: license expiry date: 20 Jan 2020 system date and today's date: 17 Dec 2019 license processed today on license client (LC) Today acquisition working fine, as expected, timestamp must be set to 17 Dec 2019 I set clock to 31 Dec 2019 (future), acquisition working fine, as expected, timestamp must be set to 31 Dec 2019 I set clock to 25 Dec 2019 (windback), acquisition working fine, not expected as windback MUST be detected (as per my understanding) Query Is my expectation/ understanding above (in third point of scenario section) is correct ? How can I explicitly verify if I have successfully turned on windback detection ? Is there any way to see/ check/ verify the timestamp (which is used to detect windback) ? @ejohnson1  ... View more

Can someone point me to a good resource where I can get more/complete information about  " Clock Windback Detection " and will be good to have some demo, if available.   Thanks in advance 🙂 ... View more