Application examples

On this page we have collected some application examples of OLicense-Suite for you:

You are a manufacturer of technical software ...

Your customer group ranges from small enigneering offices up to the development departments of large companies. Your customers work individually or in teams and have high time pressure. Therefore, your software has to be flexibly applicable and highly available.

In this customer group, the floating license model enjoys great popularity. Solely the number of concurrently utilized program copies is limited. Which user utilizes the software on which computer is in the licensee's own discretion.

To gain optimal availability, your customer may apply redundant OLicense-Servers.

You are a manufacturer of database applications ...

Into the category database apllications fall e.g. commercial applications, production planning or enterprise resource planning systems. Common to all of these applications is, that they need a direct connection to the companies database. The utilization of the software outside the company's network is normally not reasonable for organizational and data confidentiality reasons. The users have to log on always with their individual account.

For these application areas the license models named-user or floating are recommended.

Your customers request an extra high availability ...

Your customers may apply redundant OLicense-Servers in any number to optimize availability. The license allocation will work as long as more than the half of the OLicense-Servers are online, e.g. 2 of 3 or 3 of 5.

Your customers work partly out of office ...

... and want to utilize your software on computers which are disconnected from the company's network.

For the license models node-locked , named-user , pay-per-use , and prepaid this is always possible as these licenses are assigned to dedicated users or computers.

Floating licenses may be checked out of the OLicense-Server in the companies network for a limited time and transferred to another computer. The licensed software then can be used on the other computer until the license is returned or the time limit has expired. Inversely, the checked-out license remains allocated in the company network for the same period.

You want to protect Java-, Delphi-, Basic-, J#-, C#- or .NET applications ...

... then you have a small - but solvable - problem:

No copy protection or license control system and no encryption is impregnable. The ambition of such systems is to make their overcoming as difficult as possible, causing an uneconomical effort for the cracker. Thus, the programming languages and development environments used to implement the protected software have to fulfill some conditions:

• The development environment has to generate binary executables (aka machine code). Otherwise it is too easy for crackers to remove the protection system with the help of de-compilers or de-obfuskators.
• The development environment has to support static libraries (LIBs). The OLicense-Client-API is delivered as a static library, because dynamic libraries (DLLs) can easily be replaced. A cracker may create a faked OLicense-Client-API DLL which just confirms every license request of the protected program.
• The applied programming language has to offer access to low level operating system functions. Otherwise the parameters for license protections cannot be investigated or may be faked too easily by crackers.

Applications which are programmed in one of the above programming languages as well as all applications compiled in a Microsoft .NET development environment do not fulfill all of these conditions. But such applications can be protected indirectly: One or more important functions of the application are swapped out into a DLL. This DLL is programmed in C or C++ and protected by the OLicense-Suite. The interconnection of the protection system to some important functions of the application makes shure, that this DLL cannot be replaced by a fake.