You can control how many times a user can release a license with the following Server Properties:
- maxReleaseCount: The maximum number of times an end-user can release a license.
- maxReleasePeriodInDays: When counting the number of released licenses, only count the ones that have been released in the past "maxReleasePeriodInDays" days. For example, if you want to allow a user to release a license twice per month, set maxReleasePeriodInDays to 30 and maxReleaseCount to 2.
- maxReleasePerClient: When counting the number of released licenses for a given activation key, count only the ones associated to a specific client. By default, QLM counts all the released licenses for a given activation regardless of the client system.
By default, you must set the CommunicationEncryptionKey before calling ReleaseLicense. The server property releaseLicenseUseAdminEncryptionKey can be used to configure the server to require the AdminEncryption to be set in order to call ReleaseLicense.
C#: void ReleaseLicense (string webServiceUrl, string activationKey, string computerID, string computerKey, bool logRelease, out string response)
Parameters
webServiceUrl - URL to the QLM License Server.
activationKey - the license key to activate
computerID - the unique computer identifier
computerKey - the computer key being released
logRelease- flag that determines whether the release will be logged in the history table. If you are using cloud based floating licenses, you should set this argument to false to prevent bloating of the history table.
response - XML fragment containing the result of the call. The Xml fragment schema is as follows:
<?xml version='1.0' encoding='UTF-8'?>
<QuickLicenseManager>
<result>ActivationKey A162DCF05C30D371A2D0E0461040A0 has been released.</result>
</QuickLicenseManager>
In the event of an error, the XML fragments returns:
<?xml version='1.0' encoding='UTF-8'?>
<QuickLicenseManager>
<error>Details about the error</error>
</QuickLicenseManager>
Comments
0 comments
Article is closed for comments.