“A floating key has got an expiration date? Why and why didn’t the system give me an reminder so I can purchase a new one!”
We often get this or similar reactions, here now how it really works.
The floating key was enabled by SparxSystems to provide a small amount of licenses to a big group of users. E.g. a team with 10 people where only 5 users will use Enterprise Architect at the same time need only 5 floating keys in the keystore file.
Now you got two ways of configuration:
1. Key lease time (expiration date)
You can set the expiration of the key. i.e. when someone “checks out” a key this key will be locked for the user for X days/weeks.
Pro: You can run Enterprise Architect without access to the company LAN (Keystore File) when you previously “checked out” the key.
Con: Only after expiration of the „lease time“, respective after returning the key “by hand” no other user can use this key.
2. Auto check in
When a user closes the EA the will be automatically returned to the keystore file (checked in).
Pro: Since the key is automatically returned it’s free for another user.
Con: Without access to the company LAN (Keystore file) no Enterprise Architect.
Important:
Even if you have no access tothe company LAN (Keystore file) Enterprise Architect itself will enforce the expiration date. I.e. The Enterprise Architect client will prompt you a dialog to check out a new key and the Keystore will make the key available for other users. Expiration date for the checked out key / Contextmenu –> Options to change the “lease time”
Abb: Options Dialog to change the „lease time“ / auto check in
