You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Next »

Queuing token-based licenses is similar to queuing regular (exclusive) licenses, with the following additional rules:

  • Each token dependency must be able to be queued in accordance with any set limitation, reservation or license total count.
  • When you queue a token-based license, only the requested token-based license is queued. All of its dependencies, including token-based dependencies, remain unaffected; however, you can queue the dependencies separately.
  • When multiple alternate licenses are queued, the first available will be queued and all others will be removed from the queue.
  • Fast queuing does not apply to token-based licenses.

Successful checkout of a token-based license does not remove its dependencies from the queue when dependencies are queued by a separate request (as in example 1 below), unless the checkout results in the pending queued license requests exceeding the total license count (see example 2, below.) In this case, the dependencies are removed from the license queue to prevent blocking the dependency license queue, because the current client cannot check out more licenses of the dependency feature without returning some of the token-based licenses currently in use.

Examples

The following examples illustrate how token-based license checkout queues are handled. 

Example 1

This example illustrates cases where a token checkout does not remove the dependency from the queue. 

  1. Client1 takes three of the five token licenses.
  2. Client2 takes the remaining two token licenses.
  3. Client3 queues the token licenses and dependency licenses for three licenses. 
  4. Client2 returns its two licenses.
  5. Client3 takes the two licenses that Client2 returned.
  6. Client3 remains in the dependency's queue, because it will be able to take the additional license it needs after Client1 returns its licenses.

Example 2

This example illustrates cases where a token checkout removes the dependency from the queue.

  • Client1 takes all licenses from the token.
  • Client2 queues the token licenses and the dependency licenses.
  • Client1 returns all the token licenses.
  • Client2 takes all the token licenses.
  • Client2 cannot take more dependency licenses, because this would necessitate that it return token licenses. Therefore, Client2 is removed from the dependency's queue to prevent it blocking the queue indefinitely.
  • No labels