@WilMoe , Can I get a confirmation if by 'sleep' your use case basically included the situations when client is no more sync with license Server (i.e. not connected via web or unable to connect)?
If yes, then you could do that through the options file attribute "TIMEOUTALL/TIMEOUT". You may also want to look into the possibility of the usages of 'LM_A_TCP_TIMEOUT' from the client application end.
Let me know what sounds feasible to you and I can share further details or point you to the section of documentation that may help.
yes, as client will represent the application which is under license protection, "situations when client is no more sync with license Server (i.e. not connected via web or unable to connect)" would reflect my reported scenario.
If this could be done by using the options file (all license server admin can do) how the provider of the license protected client application can be sure that the license is not freed by the server before client rejected further application usage?
The "FlexNet Publisher - License Administration Guide" will note among TIMEOUT: "The software publisher must have enabled this feature in the FlexEnabled application for it to work".
Will this to be managed already by 'LM_A_TCP_TIMEOUT' or is there any additional setting required?
Thanks MikeSpragg for mentioning this issue. It could be the explanation to reported issue by one of our customers.
But only to be sure how we / our customers can use "TIMEOUTALL/TIMEOUT" to free consumed licenses again:
Is it that 'LM_A_TCP_TIMEOUT' from the client side will influence min./max. value of 'TIMEOUT' on server side?
As I would expect that freeing a license on server side for other clients is not wanted as long as the clients still can use checked out license, correct?
I can tell you whatever you use for TIMEOUT/TIMEOUTALL in the options file on the server will make no difference - went down that rabbit hole for a while. The LM_A_TCP_TIMEOUT goes on the server as a system env var. I set mine to 180 and it seems to have worked. Even if the license times out - it'll be immediately consumed again by the client if the client is still active (correct behaviour). However, if heartbeat is lost and this timer expires - it's released.