License-file list redundancy
As an alternative to three-server redundancy, license-file list redundancy is available when there is limited system administration available to monitor license servers, when load-balancing is required for applications located far apart (example: Chicago and Tokyo), or when two or more license servers are required.
With license-file redundancy, each one of a group of license servers serves a subset of the total licenses. This method does not provide true redundancy in the way three-server redundancy does.
Set the LM_LICENSE_FILE environment variable to a list of license files, where each license file points to one of the license servers. FH Web Edition attempts a license checkout from each server in the list, in order, until it succeeds or gets to the end of the list. The actual licenses are generated from the product codes. Unlike with three-server redundancy, the server machines can be physically distant. The license servers on both servers need to be running.
|
Example: If ten licenses are wanted, you need to request two sets of product codes with a count of five for each set from your FIREHOUSE Software sales representative. The sample license files will look like: License 1 for Chicago: License 2 for Tokyo: |