K N O W - H O W
Best Practices: Lending and Borrowing Licenses
The last edition of KEYnote introduced you to the fundamental concept of the CodeMeter License Transfer function. Today, we
will present the best practices for creating transferable licenses with CodeMeter License Central. All you need is CodeMeter
License Central 2.20b, CodeMeter 6.10a, and a Universal Firm Code.
The Bigger Picture
As a software developer or vendor, you are
using CodeMeter License Central to create
licenses. Your users activate those licenses
on a networked server, and it is up to you
to define whether these licenses can be
deactivated again.
On the network, the user can either use the
license directly on the server, or the license
can be borrowed locally by being transferred
into a local CmContainer. When a license is
License
Central
borrowed, it is flagged as used for a period
of time and can be used locally offline without
any need for a standing connection with the
server. After the prescribed borrowing period
has elapsed, the license automatically reverts
back to its original state: It has expired locally,
but is available again on the server. The user
also has the option to return a license earlier.
You, the software vendor, define the maximum
period of time a license can be borrowed.
Firmware 3.0 and CodeMeter 6.20 are required
to use a CmDongle with borrowed licenses.
Creating the CmContainer Type
Let us consider the CmContainer types in
CodeMeter License Central. There are three
pre-defined types for the evaluation of Firm
Code 6.000.010:
■■ CmDongle 6.000.010
■■ SmartBind 6.000.010
■■ BorrowClient 6.000.010
Activate
Borrow
License
Activation
License
Transfer
Deactivate
Return
License Server
Vendor
8
PC / Client
User