Basic Process for Granting Licenses

When reservations have been added and the license server receives a capability request from a client device, the server uses the following basic process in its attempt to grant the license count requested.

Note:The process described here assumes that the capability request is defined with no special capability request options that can control aspects of the license server’s behavior in determining which licenses are sent in the capability response. Consult the software producer for information about any such options that client code includes in the request and their effect on the basic fulfillment process.

1.

Validates that the capability request contains the appropriate content for processing.

2.

Returns all licenses currently served to the client device. (Reserved licenses remain reserved. Shared licenses are returned to the pool.)

3.

Searches for reservations assigned to the client device and to the user sending the request from that client.

4.

Determines whether desired features are specified in the request.

If no desired features are requested, the server grants the client device whatever licenses have been reserved for it through device-based reservations and through user-based reservations. If no reservations exist, no licenses are granted.

If a desired feature is specified, the server determines whether the specified feature is available through a reservation. If not, it determines whether any shared counts are still available. In summary, the server does the following:

a.

Checks for the device-based reserved count first.

b.

If device-based reserved count is not sufficient, checks the user-based reserved count for an additional count.

c.

If the sum of device-based and user-based reserved counts is not sufficient, checks the available shared counts to fulfill the remaining requested count.

d.

If enough reserved and shared counts are available, grants the licenses.