In 10Duke Enterprise, the product configuration describes the products you’re licensing and the terms of licensing.
The product configuration consists of the following:
Licensed items, each representing a resource that you’re licensing separately, such as a product or feature.
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.
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.
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.
You create and manage licensed items using the 10Duke SysAdmin tool.
License models define the rules for how end users 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 can use the license concurrently, if a license is node-locked, and other similar rules and constraints.
Using SysAdmin, you can easily create a variety of license models that can be easily applied to your product packages.
An individual product package bundles together one or more of your licensed items 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.
You create and manage product packages using SysAdmin.
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 affect those licenses:
If you add or remove licensed items in a product package, new licenses are not automatically granted nor existing licenses revoked.
If you have use cases where you will need changes to also apply to existing licenses, we recommend that you use aggregated licensed items.
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 package to use a different license model.
If you want license model changes to existing licenses, you must edit the license model itself.