FlexNet Publisher versus FlexNet Embedded license server
FlexNet Publisher versus FlexNet Embedded license server
Summary
How does a FlexNet Publisher work compared to a FlexNet Embedded license server?
Question
What's the difference between how a FlexNet Publisher (FNP) and FlexNet Embedded (FNE) license server work?
Answer
An FNE license server and an FNP license server are entirely different animals.
FNE uses regenerative (replacement) licensing, whereas FNP uses iterative licensing (via dynamic license pools). So while FNP would have an active job handle with heartbeats taking up RAM (memory) via the vendor-specific license pool, FNE license checkouts work more like FNP activations. With an FNE license server, memory activity is limited to when the capability requests are actually exchanged. After that, the server is back to idle again (as all the client licenses are completely refreshed with each capability exchange, per the regenerative model).
Additional Information
Chapter 10 "FlexNet Publisher and FlexNet Embedded Comparison" from the FNE Client C SDK User Guide provides some high-level similarities and differences between the products.
what is the difference between regenerative licensing and iterative licensing? can you give an example? Also when should we use FNE and when should we use FNP, any criteria to help make decision?
Hi @vishalakshi We recommend you raise a support case or contact Revenara with your use case so that our team can help you to give all the answers for your use case and also help to select the license server based on the requirement.
