Create license models

You can create license models in 10Duke SysAdmin:

  • You can create floating license models out of the box. In a floating license model, a limited number of licenses are shared by a larger number of users or device clients.

    The out-of-the-box floating license model creates seat-based licenses. You define the maximum duration of license tokens in online and offline consumption, and the limit for concurrent use on multiple devices. The default token refresh time is set to 75% of the license token’s validity duration.

    The license model doesn’t limit how many seats a single user or device client can consume. It doesn’t allow restricting license consumption based on software versions, and doesn’t include the constraint needed for preventing the abuse of trial licenses.

  • You can also create custom license models, where you use JSON-formatted rules to define how the license model works.

    See examples of different constraints you can apply to license use with a custom license model.

Create a floating license model out of the box

  1. In SysAdmin in the left sidebar, go to PRODUCT CONFIGURATION > License models.

  2. Go to the Floating tab and select Actions > Create.

    A dialog with steps opens. Click Next after completing each step (or Back to go back).

  3. In step 1 Name, define the basic details:

    • Name: Define a name for the license model. The name must be unique in the system.

    • Description (optional): Write a short description.

  4. In step 2 Time period, define in License term (period) how license validity should be handled in this license model.

    This field is only metadata for administrative purposes, it’s not used by the system. You define the validity period for licenses when you grant the licenses.

    Select the type of license term:

    • Fixed: Fixed-term licenses should have a start and end date.

      You would typically use a fixed license when the customer has paid a fee for an agreed term (such as 1 year) to access the software, and there’s no contract with the customer to automatically renew the license.

    • Perpetual: Perpetual licenses should have a start date but no end date.

      You would typically use a perpetual license when the customer has made a one-time purchase to acquire the software, and the license is valid until further notice.

    • Subscription: Subscription licenses should have a start and end date.

      You would typically use a subscription license when there’s a contract with the customer to periodically renew the license.

  5. In step 3 Details, define how licenses using this license model can be consumed:

    • In Token validity for online consumption, define how long (in seconds) a license token is valid in online consumption.

      This is intended for use cases where the client application is online and doesn’t need to store license tokens for a long period of time.

    • In Token validity for offline consumption, define how long (in seconds) a license token is valid in offline license consumption.

      This is intended for use cases where the end user decides to go offline and requests the client application to check out a license for a longer period of time.

    • In Devices/user/license, define how many devices an end user can consume the same license seat on simultaneously.

      For example, if you set this to 2, an end user can consume the same seat at the same time on two different hardware devices, such as their laptop and mobile device.

  6. In step 4 Confirmation, click Save to create the license model.

Create a custom license model

  1. In SysAdmin in the left sidebar, go to PRODUCT CONFIGURATION > License models.

  2. Go to the Custom tab and select Actions > Create.

    A dialog with steps opens. Click Next after completing each step (or Back to go back).

  3. In step 1 Name, define a name for the license model and optionally a description. The name must be unique in the system.

  4. In step 2 Behaviors, define how license leases behave.

    The main aspects of this are the license lease validity, settings for releasing licenses, and instructions for the client application when to try refreshing the license lease.

    See information on the behavior JSON rules and how to define them.

  5. In step 3 Contraints, define conditions that restrict the use of licenses.

    You can define, for example, licensing based on client application versioning, over-usage of licenses, how many concurrent devices a license can be consumed on, and whether consumption is limited to certain locations.

    See information on the constraint JSON rules and how to define them.

  6. In step 4 Confirmation, click Save to create the license model.

    If there are errors in the JSON format, you cannot save the license model.

Next steps

  • You can associate the license model to a product package, or even to a specific licensed item in a product package.

    A license that uses the new license model is available for consumption after the cache has been refreshed (within 10 minutes by default).

  • We recommend that you thoroughly test new license models.

On this page