Floating Licenses will allow the installation and execution of your software application on multiple computers but will limit the number of concurrent users to the License <seat> setting. For example, your application could be installed on 100 enterprise computers, but with a <seat> setting of 5, only 5 concurrent users will be allowed.

The software_DNA Floating License is based on our Multi-User License model combined with a License seat "Lease" approach, where the seat "Lease" automatically expires after 2 days.

The "Lease" approach provides several benefits to the Users, including:

• If a User forgets to close the application, then the seat Lease will expire and automatically release the seat for other Users.

• If a user’s computer crashes before the lease is de-activated, the seat Lease will expire and automatically release the seat for other users.

• When Offline, or during extraordinary events (ex: no internet connectivity to the DNA Servers, unavailability of the DNA Servers), the licensed Users can continue to have access and use of the application for the "Lease" period (i.e. up to 2 days).

Seats can always be released immediately via the License Manager and via the DNA Control Panel.

The Floating License setting can be set on a per License Activation Code for any License Activation Code of a Multi-User product.

This is fully automated using enabled eCommerce Connections (recommended), or done manually by directly enabling the Floating License option from the Code View Screen for a specific License Activation Code.

Global Scope

Users can be located anywhere on the Internet, not just in a local LAN sub-network, ensuring that global enterprises, big and small, can use your Floating Licenses across their business.

Hosted solution

With software_DNA, no need to install a "Floating License" server on the Enterprise network with all the subsequent support issues. software_DNA’s Floating License solution is hosted on our Servers and maintained 24/7 by our Tech Team.

Setting up Floating Licensing

Floating Licensing requires Level 3 Validation / Protection. Once Floating Licensing is enabled for a Product in the Product Configuration screens:

• The Code View screen will display and allow you to change the Floating License setting for a License

• The eCommerce Connection Configuration screens will allow you to specify the Floating License setting to be used for each SKU received via the eCommerce connection when generating the License Activation Code

Not all License Activation Codes for a given DNA Product need to be Floating Licenses.

For implementation details, see the Floating License Implementation Guide   in our Guides section.

Daily or Continuous Validation (V6.02 DNA Library)

The Continuous Validation option (introduced in V6.02 of the DNA Libraries) provides for a stricter Floating License implementation (on a per License basis) where a mandatory DNA Server Validation is performed on every DNA_Validate() call, versus an attempt max once per day, but does require an internet connection at all times (unless specifically overriden by the App).

The Continuous Validation option changes the actions of DNA_Validate() for a given Floating License as follows and may require changes in the software_DNA implementation within your App:

• Daily Validation (default):
  1. DNA_Validate() does a local CDM License Validation, and returns an error if it fails (license is invalid, expired, or lease has expired)
  2. maximum once per day, DNA_Validate() will attempt a DNA Server Validation if an internet connection is available, and will return a success / fail result
  3. if an internet connection is not available, the result of the local CDM License Validation is returned
• Continuous Validation (new option with V6.02):
  1. DNA_Validate() does a local CDM License Validation, and returns an error if it fails (license is invalid, expired, or lease has expired)
  2. DNA_Validate() will then perform a mandatory DNA Server Validation and will return a success / fail result
  3. if an internet connection is not available, then it will return a ERR_NO_CONNECTION error, i.e. a fail
  4. on ERR_NO_CONNECTION, the App needs to decide whether to allow or not allow execution knowing the local CDM License file was valid.

Continuous Validation requires V6.02 of the DNA Library, and will revert to Daily Validation with previous versions of the DNA Library.