Independent Software Vendors
Benefits for the independent software vendors
| Technical characteristics |
Benefits |
| Extended trust management that uses standardized authentication and authorisation technologies. |
Providing more flexibility to the trusted customer while increasing the level of security.
Easy to deploy in Grid, Cloud and SOA environments. |
| Capability for defining arbitrary local policies that regulates license usage. |
More fine-grained local policies might be defined on top of the policies laid down in the contract between ISV and customer. Thus, ISV policies embedded in the license may be kept simple. |
| Increased flexibility through token mechanisms for the implementation of new usage models, e.g. pay-per-use, SaaS. |
ISVs may extend their customer base by supporting new business models, thus generating additional economical benefit. |
Benefits for the end user
End users
| Technical characteristics |
Benefits |
| Multiple ways to request a license, e.g. portal, Grid scheduler, by the application, a command-line interface, or scripts. |
Flexibility for the user embedding the licensing mechanism into his workflows. |
| Co-scheduling of licenses and computational resources |
Select the most appropriate resources depending on actual requirements and have the necessary licenses available |
| Reservation in advance |
Licenses can be reserved for latter use, and coordinated with the availability of computational resources. |
| License token |
Allows execution completely decoupled from the site that hosts the license server. |
| Trusted entity available at execution site |
Allows re-negotiation at run-time, e.g. giving up a license before the reservation period is over, trying to extend a reservation period, or adding new features. Thus, the license usage may be adapted to the real need. This allows reducing the cost either by not paying for times where the license is unused, or by avoiding an application crashing because the license was no longer valid. |