Floating licensing: concurrent seats and automatic reclamation

Device binding limits registered devices. Floating licensing counts concurrently occupied device seats; multiple sessions on the same device share one seat.

Example

With 100 computers and 10 floating seats, the first 10 devices can obtain seats; the eleventh receives “Seats full”. Under the same license, process sessions with the same hardware identity share one seat, so restarting does not occupy another seat. Without hardware identity, the device identity is used. The seat becomes available to another device only after every session on the original device has been released or has expired.

Set in the policy

Select Floating seats and set the device / seat limit. The default heartbeat interval is 600 seconds (10 minutes), and the seat lease is 1800 seconds (30 minutes). Each successful renewal resets the seat expiry.

On normal exit, closing the SDK correctly returns the seat immediately if the release request succeeds. A crash, forced termination, power loss or network outage cannot guarantee immediate return: reclamation may take until 30 minutes after the last successful renewal. Custom leases follow the license policy.

Floating licenses allow brief disconnection within their lease. Offline time is also bounded by that lease; permanent offline use and file-based fully offline first activation are not supported.

What else should application code handle?

Use Open/Start and the normal close method. The SDK creates a separate session ID for each client. Do not create a client for every export; keep one for the application's lifetime.

An old floating cache does not restore a seat automatically on the next process start. If its lease expired, activate again and acquire a seat before resuming work.