LiveWire floating license - User Guide - LiveWire - 26.2.0

LiveWire User Guide
ft:locale
en-US
Product name
LiveWire
Version
26.2.0

About floating license

LiveWire products can now be activated using a new type of license called a Floating License.

Floating Licenses allow for a more centralized licensing scheme, where system administrators manage licenses rather than the end-users of the application. The Floating License server can be enabled on the LiveWire host. License Servers serve licenses to clients upon request. When a client disconnects, it forfeits its license, allowing other clients to check out that same license. License Servers must not be exposed to the Internet.

Floating licenses are based on product and version, meaning a client running LiveWire 25.2.x must check out a license specifically for LiveWire 25.2.x. When a new version releases, you must delete your old licenses and replace them with a new version.

Note: Licenses are based on <major>.<minor> version, meaning patch releases do not require a new license. For example, a LiveWire 25.2.0 license is still valid for a hypothetical 25.2.1 patch release.

A client needs the License Server’s address in order to check out a license. This can be entered manually by a user, synced via Grid, or synced via Engine Configuration sync.

Note: Example - If two licenses exist: one with CTD and one without, the client will attempt to check out the license with CTD first since it is considered “less restrictive.”

The client must remain in constant contact with the license server to maintain its activated state. If the client loses connection for more than five minutes, then the client is at risk of losing its activated state - potentially leading to a diminished operating state. Therefore, it is important that license servers remain highly available.

A floating license is different from standalone licenses. Floating and standalone licenses are not interchangeable. You cannot install normal “standalone” licenses on a floating license server. Floating licenses lock to the license server they are installed on.

Example of Floating License use case: If we have one Remote Capture Engine (RCE) floating license installed on a license server, only one RCE installation can be licensed at a time. If an RCE installation has the license “checked out” from the license server and they disconnect, then another RCE instance may “check out” that license.

High level workflow

  1. Enable the floating license server on a host device.
  2. Retrieve the server’s locking code.
  3. Retrieve the product key for the version of the product you are activating.
  4. Retrieve a license file using the product key and locking code.
  5. Install the file onto your license server.
  6. Use the license.

Prerequisites

Before you begin, ensure that you have logged into MyPeek to obtain your Remote Capture Engine product key. This will be required to enter the license.