Explanation of Detachable/Borrowable/Transferable in terms of FNO and FNP
The below definitions might look alike, but they have a clear difference as explained below:
|
Yes (detachable) |
Only applicable to trusted license models. Licenses are floating and served from a license server, but they can also be removed from the floating group of licenses and be activated on an individual client machine. |
|
No (not detachable) |
Only applicable to trusted license models. Licenses are floating and only served from a license server. The licenses can be configured to allow them to be transferred between vendor daemons. |
|
Floating Borrowable |
The first step in the life of these license rights is activation on a license server. From there, the vendor daemon can:
Also known as Hybrid. |
|||||||||
|
Floating Transferrable |
The first step in the life of these license rights is activation on a license server. From there, the vendor daemon can:
The vendor daemon cannot activate these licenses on end-user machines. Also known as Concurrent. |
- Detachable is used only for clients whereas transferable is used for servers. The license can be borrowed in case of clients and license can be moved from one server to another in transferable.
- From the Flex Net Publisher end, the count of hybrid would be same as detachable and the count of concurrent can be compared to non-detachable.
- Hybrid allows both concurrent and borrowable, so if the license model is just concurrent then it will not allow borrow.
If concurrent is 0 then the non-borrowable licenses is 0,we can have both concurrent and hybrid licenses activated on the server
concurrent would not necessarily be 0 if hybrid > 0
