When a client requests a license from a license server list, the client must wait a
certain amount of time for the response from the first license server (the server
replies that the license is available or not available) before contacting another
server. A slider lets you specify approximately the amount of time (less or more) the
client should wait for a response from the license server.
If you have a high-performance network, and servers that are not heavily loaded, we
recommend that you reduce the value: this will allow the client to contact other
servers more quickly, instead of waiting too long for a response from the first
server. If you have a low-performance network, or servers that are heavily loaded, we
recommend that you increase the value: this will allow the client to wait long enough
for a response over a slow network or from heavily loaded servers.
Allows you to set the heartbeat duration. In principle, a shareable license
granted by a DS License Server to a session is released when the session stops. The license is also automatically
released when a session crashes. However, it may occur in the event of certain severe
crashes or network problems, that the session cannot instruct the license server to
release the license, so the shareable license is not immediately released. To prevent
the shareable license from being retained by the license server, there is a specified
period of time (referred to as the "heartbeat") after which the license server
considers the session to be dead, and releases the shareable license.
This
heartbeat is communicated to the license server by the session when the license is
first requested. You can set the heartbeat using the Frequency option. The default
value is approximately 17 mins. This is the maximum value (represented by the value
MAX in the list) and cannot be increased. Decreasing the heartbeat value will decrease
the maximum period of time during which a shareable license can be inadvertently
retained by the license server. You can set the appropriate value by increments of 1
min. Consequently, the heartbeat can be set to any of the following range of values:
1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16 and MAX.
Note:
decreasing the
heartbeat leads to increased network load and to increased license server
workload.
Furthermore, a mechanism exists to allow saves if the license
server goes down.
When a license server or the network goes down, a session
enters a special mode giving users the opportunity to save their work before exiting.
Every heartbeat period, the session checks that the license is still granted to it. It
may occur that, for example, the license server or the network are down. In that case,
the license check fails.
The session then enters a "countdown" mode. A popup is
displayed informing the user that the license check has failed. The user must then
save any work in progress. Five checks are performed at one minute intervals. If all
checks fail, the session is set to a special mode in which only saving and exiting
commands are available.
If the license server administrator inhibits access to a
license which is currently being used by an ALLOW or DENY rule, the native app process
will enter the above countdown mode at the next heartbeat.
Notes:
- processes such as batches and macros do not support this mechanism: automatic exit
is still performed
- even if the problem which led to the license check failure is solved, it is
impossible to return to the normal mode after the session has been set to the
special mode in which only saving and exiting are allowed: no other license request
is performed after entering in this mode.