License server: How to deal with offline clients?

Hello!

Does anyone has expericences with License Server and offline clients?
Most of our developers stay in their office, but sometimes they are onsite and do not have a network connection to our lan.

Does the license server support that? How does that work? I tried to find some hints on the homepage to did not find anything!

Thanks for your replies!

BR
Markus

5 comments

Hi Markus,

> but sometimes they are onsite and do not have a network connection to our lan. Does the license server support that?



Yes, License Server administrator may enable "permanent" tickets on per-product basis. Users then may request a "permanent" ticket right from the IDE. The permanent ticket may be used offline. After issuing a permanent ticket, the number of tickets on the server is decremented by one. Once the user is again in the office, he/she may switch to using floating tickets by explicitly releasing the permanent ticket.


Eugene.
0

And how does the 48-hour grace period work. If I have a valid ticket from the server, can I use it for 48 hours even if the server is not available?

0

> can I use it for 48 hours even if the server is not available?

yes, exactly.

0

I am trying to better understand the 48-hour timeout period, when a user successfully receives a license from the license server and then disconnects for offline use.

In the JB License Server "Settings" tab, the Ticket Revocation Period (s): is defaulted to 600. I am assuming that is seconds? If that is the case it is a 10 minutes for the revocation period.

In order to achieve the 48-hour revocation period, would I need to set this to 172,800 seconds (which is 48 hours)?

I have looked in the user guide and searched online but cannot find a definitive answer... just that it *should* work. Is this a setting or is it baked into the licensing server (the 48-hour window).

Thanks!

0

Hi Robert,

The Ticket Revocation Period and 48h grace period are completely different things meant for different purposes.
"Ticket Revocation Period" is a period, after which the server will "revoke" dispatched ticket, unless the ticket is "prolonged" by the client. This ticket prolongation procedure is a part of floating licensing model and is the reason why the server should be constantly available while a client is up. If a client crashes or does not release for some reason the allocated ticket explicitly, the "Ticket Revocation Period" is the tool for the server to revoke such hanging tickets. So it is a good idea to keep the value of this setting relatively small, otherwise tickets not released properly will not be available for dispatching for a long time.

The 48-h grace period is another thing. As I said, the floating license model assumes that the server is always available, and this is the requirement that should be always fulfilled. The grace period is needed to allow the clients to survive accidental server downtime because of maintenance or power outage.

> when a user successfully receives a license from the license server and then disconnects for offline use.

You should not count on this grace period in normal client operation.This is not the intended usage of the license server and one should not expect the client to work further as soon as the license server is not available. Please use other licensing schemes if you need "offline" client usage.

0

Please sign in to leave a comment.