Deferred Revocation for Network Licensing
Revocation and rehosting of licenses in a network may cause unplanned downtime for existing users. The downtime can be prevented by allowing a grace period between invoking license revocation and revocation actually taking place. You can define this grace period, known as the deferred revocation grace period, at the time the permission ticket is generated. Specify a value of 1 to 30 days. For example:
> 1 means that revocation takes place a day after revocation is invoked.
>30 means that revocation takes place 30 days after revocation is invoked.
Deferred Revocation Workflow
Deferred revocation follows the same workflow as the License Revocation Workflow
You can set the deferred revocation period for each license using the VLSgeneratetPermissionTicketExt2 API. The permission ticket generated is then used in the Install API (for C, Java, or.NET). Upon successful execution, the API returns a revocation ticket to indicate that the license is "marked for deferred revocation" after the number of days specified in the license. Until the deferred revocation period has elapsed, the license will be available for use. When the deferred revocation grace period is reached, actual revocation takes place. After revocation, loading of this particular license is blocked.
At the time of actual revocation, the revocation ticket is not generated. To determine the license status, you can call the VLSgetLicenseInfo API using the license hash value. Since the license has been revoked already, the API returns error 140 (VLS_NO_SUCH_LICENSE).
Deferred Revocation of Commuter and Repository Licenses
The following deferred revocation functionality is incompatible with commuter and repository licenses:
>If the licenses are already marked for deferred revocation, commuter license tokens can no longer be checked out for the feature-version. Similarly, the repository licenses cannot be requested. This cannot be done for the feature-version until all its licenses scheduled for revocation are revoked.
>Commuter licenses whose tokens are currently checked out cannot be marked for deferred revocation.
>Repository licenses that are already requested successfully cannot be marked for deferred revocation.