forms and programming languages , offers modular licensing not just as a way to license application features separately ; it also increases their level of protection with separate encryption : You can monetize your features and make them safer in the market at the same time .
AxProtector works by taking the unencrypted executable or library and turns it into encrypted , protected software . When end users want to use that software , they need the right license entries in their license containers .
It does not matter whether you as the software vendor use a hardware CmDongle , a software-only CmActLicense , a CmCloudContainer , or any combination of the three as the secure place to store your software ’ s license entries , the structure of the entries is essentially similar and fully compatible . The Firm Code is a globally unique identifier of the license publisher , created by Wibu-Systems . As the vendor , you yourself define the Product Codes that AxProtector can assign to individual features .
The Route to the Client One aspect that should never be neglected , not just for feature-on-demand licenses , is the necessary product structure in the order handling system used by your company ( e . g . an ERP system like SAP , Oracle , Microsoft Dynamics , …) and the effective link between this system and the license management system , CodeMeter License Central .
Each individual marketable feature ( represented by the Product Code ) should be given its own product number , which would be known to both systems to form the logical bridge between both . The order management system would have all of the information about the order , and License Central would have the details about the licenses . When an order is received , the order management requests the generation of a ticket ID ( activation code ) and feeds it back to the lead system . The clients receive the licenses they paid for that they can then activate on their devices with the ticket
ID . The process can be fully automated with the simple integration of CodeMeter License Central and the vendor ’ s ERP system . Should the client pay for another feature at some point in the software ’ s life , the same process springs back into life .
This gives the Latin adage “ Divide et impera ” a completely new meaning : You can conquer your market by dividing your software ’ s capabilities up with CodeMeter ’ s modular licensing .
|
Each feature is protected with its own cryptographic key for the Product Code . A simple license entry would be a combination of the vendor ’ s Firm Code and a Product Code . This would suffice to create a feature-on-demand model without having to change anything about your software . Every feature that you can sell separately is given its Product Code , and the end users only need the right license entries in their license containers . You also have an API available as software vendor to make direct use of the information in the license container .
Licensing Models on Top By defining the feature-on-demand licensing model , you have created the perfect foundations for more sophisticated licenses . Product Codes can be given additional properties by way of the Product Item Options . For example , adding an expiry date lets you offer a subscription model and adding a use counter allows billing by the number of uses or the active time in use . Many other Product Item Options are available to give you a toolkit to construct your chosen licensing system . Ideally , the application does not have to know the underlying licensing model at all and only expects the right Product Code . You can then pick and mix the licensing models for each market or industry without having to change anything in the software itself .
|
Python Syntax
Highlighting
Hex View
Java Syntax
Highlighting
|
Basic
C / C ++ Syntax
Highlighting
Debugging
|
Code
Analyzer
Change font
C # Syntax
Highlighting
|
13