Skip to end of metadata
Go to start of metadata

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

Compare with Current View Page History

« Previous Version 8 Next »

A floating license for a software application is not linked to a specific computer, but can be used by different computers on the network.  A particular floating license can be used by only one computer (or client) on the network at any given time, two licenses can be used by any two clients on the network at any given time, and so on.

In a floating-license environment, one machine acts as the floating license server; its job is to keep track of how many floating licenses are available, how many are in use, and who is using the license.

When a client needs a license, it will contact the server and request a license—this process is called a check-out. If a license is available, the server will assign it to the client, and the license will no longer be available to other clients. If all the floating licenses are checked out, the request for a license is denied.

When a client no longer needs the license, it will return the license to the server—this process is called a check-in. Typically, a check-in occurs when the user exits SpinFire Ultimate. (Note that even if SpinFire Ultimate shuts down unexpectedly, the floating-license server will reclaim the license.)

Server and client are configured through a floating-license file, license.al. This file contains the following information:

  • Server Hostname - The network name of the machine acting as the floating-license server.
  • Server Host ID - The server MAC address; also referred to as the physical address.
  • Vendor Name - A name that uniquely identifies the company whose product is licensed—in our case, the vendor name is actifyd. The vendor name is needed to determine the service name.
  • Number of Licenses - The number of available licenses.
  • Licensed Feature - A feature is any software component that can be licensed; for example, SpinFire Ultimate is a feature. Specifically, any component that gets checked out/checked in is considered a feature.
  • Borrowing Flag - A flag that indicates whether or not a feature can be borrowed.
  • Borrowing Time - Specifies how long (in hours) a feature can be borrowed.

SpinFire Ultimate determines if a license "floats" by looking at the configuration code. If the license is a floating license, then the license.al file will include an xml node that is the floating-license text. SpinFire Ultimate will extract the text and save it to disk as a new file, sfpflv2.dat, which is then used by the floating-license system.

Related Topics

Floating License Installation

/wiki/spaces/SF1100/pages/3233285509

/wiki/spaces/SF1100/pages/3233338911

/wiki/spaces/SF1100/pages/3233303337

Borrowing/Returning Licenses

The Borrow License command allows a floating license to be used temporarily when a computer is disconnected from the network that runs the license server. This is a useful feature for mobile users.

When SpinFire Ultimate is in floating-license mode, the Borrow License command appears on the Tools menu. A user can borrow the license for one to 45 days, and will not be available to other users until it is either returned or it expires. If more time is needed to run SpinFire Ultimate off the network, consider purchasing a standalone seat of SpinFire Ultimate.

A user can return the license anytime within the two-week borrowing period by connecting to the network that runs the license server and selecting Tools > Return License.

Upon return or expiration, SpinFire Ultimate will no longer operate without a network connection.

Loss of Network Connection

If the network connection between SpinFire Ultimate and FLEXlm (see /wiki/spaces/SF1100/pages/3233285509) is broken, the floating license will remain checked out for two hours. The license will be unavailable to other users, even if the network connection is re-established within the two-hour time period.

After a period of time, an error message will announce that SpinFire Ultimate is unable to connect to the FLEXlm server and the application will close. Any work that has not been saved will be lost. This does not apply to a borrowed floating license.

  • No labels