Efficient Reservation

RESERVATION on features can also be applied at runtime from remote machine. Once request reaches to the license server, it moves the licenses from the floating pool to reserve pool. There is no requirement for running whole re-read process on the license server for it. Once the purpose of reservation is completed, the licenses can be moved back to the floating pool. Producer has to provide the tool, which is implemented as wrapper on the FNP provided API. To get the tool, contact your software producer. The functionality is based out of RESERVE line in the Options file reserves license for a specific type.

The lifetime of these reservations on license server can be any of the following:

•

Lifetime of the vendor daemon process on which efficient reservation is applied.

•

Intentionally removed with the producer provided tool.

•

The reservation will be removed automatically once duration has expired.

Efficient reservation does not have any dependency on Options file and can be applied without it. The only exception is if reservation is applied for type GROUP. In that case, the Options file is required to enable that GROUP in vendor daemon.

Single efficient reservation request can have multiple RESERVE lines for different features. The request will be considered successful if all the RESERVE lines are successfully reserve licenses on the license server. In case any of the RESERVE lines fails , the license server will reject whole reservation request.