Product configuration

In 10Duke Enterprise, the product configuration describes the products you’re licensing and the terms of licensing.

The product configuration consists of the following:

1. Licensed items, each representing a resource that you’re licensing separately, such as a product or feature.

2. License models, which define the business rules for how you provide those resources to your customers.

   For example, you might be using a simple perpetual license model, a subscription-based model, or a model with floating seats.

3. Product packages, each consisting of one or more licensed items and the license model (or models) to be applied.

   A product package is what you license to your customers, and it typically corresponds to what they understand to have purchased from you.

You create and manage your product configuration using the 10Duke SysAdmin tool.

Licensed items

Licensed items provide the basis for how you break down access to your product with licenses. A licensed item represents an individual item that you want to issue a license for, whether it’s a complete product, a specific feature in a product, or some combination of your products or features.

Using different combinations of your licensed items, you then build product packages to match how you’re selling your product. A product package is just a “container” though: your customer gets a separate license per licensed item.

The licensed item itself doesn’t contain any information on what type of a license will be granted with it, or what license model will be applied. All this information is defined in the product package that the licensed item is associated to. This allows granting different licenses using the same licensed item, for example, by creating product packages that use the same licensed item to grant different types of credit.

See how to create licensed items.

License models

License models define the rules for how users and device clients can consume the licenses for your products and how your customer organizations can manage their licenses.

When you put together product packages, you associate a license model to each package. The license model determines how licenses created with that package work, for example, whether seat-based licenses have floating or named seats, how many users or device clients can use the license concurrently, if a license is node-locked, and other similar rules and constraints.

See how to create a variety of license models that can be easily applied to your product packages.

Product packages

An individual product package bundles together one or more of your licensed items and a license model to define one commercial product that you’re selling.

As a simple example, let’s say you have a software application that consists of five modules, configured as your licensed items. You could create a “Basic” package that gives access to modules 1 and 2, and a “Pro” package that gives access to all five modules.

For each licensed item within the product package, you define what type of a license it will grant—most importantly, the type of credit granted (seats, use count, or use time). You can also override the product package’s license model for an individual licensed item if needed.

See how to create product packages and how to grant licenses with them.

Changes to product packages

It’s important to note that after licenses have been granted using a product package, changes to the product package don’t automatically affect those licenses:

• If you add or remove licensed items in a product package, new licenses are not automatically granted nor existing licenses revoked.

  You can use SysAdmin or the 10Duke Entitlement Management REST API to run a license update to grant new licenses based on new licensed items in the product package. You can also revoke licenses as needed.

  If your use case requires that the changes automatically apply to existing licenses as well, we recommend that you use aggregated licensed items.

• If you change a licensed item’s settings in the product package, these changes are not reflected in existing licenses. For example, changing the credit type or amount for a license item doesn’t automatically update the credit in corresponding licenses.

  If needed, you can update the credit changes to licenses using SysAdmin or the Entitlement Management REST API.

• If you change the product package to use a different license model, existing licenses continue to use the old license model. The same applies if you change a licensed item in the product package to use a different license model. If needed, revoke the existing ones and grant new ones.

  If you want license model changes to automatically affect existing licenses, you must edit the license model itself.