You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

LM-X License Manager handles the most simple to the most complex licensing needs. If you require a simple licensing solution, you can use LM-X default settings with few or no modifications.
If your licensing needs are more sophisticated, LM-X includes many advanced features to handle your needs, as described in Feature descriptions. LM-X offers outstanding flexibility to adjust the license model to your business strategy in two main ways: a universal and wide selection of license file settings (tags), and a license file structure with independent sets of tags that define features. (See Protecting your application for details on license files.)
You should consider the following as part of your licensing strategy, depending on the type of license you want to use:

  • For node-locked licenses, you should consider whether the license will work on terminal servers or virtual machines (not enabled by default) and whether to enable a trial license if a normal license is not in place.
  • For floating licenses, you should consider policies for dealing with heartbeats and network disconnects (for example, how you will handle saving files and quitting the application in case the network is down).
  • For trial licenses, you do not need to change your procedures. To enable trial licenses, you simply set a predefined trial length as described in See "Trial licenses" on page . A trial license begins when the application is run for the first time. Trial licenses have anti-reuse and anti-clock tampering mechanisms that prevent usage after the trial length has expired. You may also consider whether to allow the trial to work on terminal servers or virtual machines.

Example source code for each of these basic license types are included in the examples directory and are described in Getting Started with LM-X License Manager.
The following tables show the most common feature settings for node locked and floating licenses, whether they are required or optional, and whether they are set by default.

  • No labels