Home → More on Networks → 1.x and 4.x Networks → Specifying One or More 1.x/4.x License Servers
Applies to:
All Palisade Concurrent Network 1.x and 4.x software licensed with the FLEXnet licensing system
Question 1:
How do I tell the client machine where to find the Palisade FLEXnet license server?
Answer:
You can enter the license file location on each client machine in any of three ways:
The first time the software runs on a given client machine, the software will prompt for a license server location unless you have already set it up with method (2) or (3). Enter the server name preceded by an at sign, such as @J34BETA. Don't use quotes.
To prevent the prompt, you can pre-load the same information in the registry key
HKEY_LOCAL_MACHINE\SOFTWARE\FLEXlm License Manager
or
HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\FLEXlm License Manager
Create a string value with the name
PALISADE_LICENSE_FILE
and specify the server location in the form @J34BETA.
If you prefer not to edit the Registry but still want to avoid the prompt at run time, create a system-level or user-level environment variable called
PALISADE_LICENSE_FILE
and give it a value equal to the server location, again in the form @J34BETA.
Question 2:
I have licenses on more than one server. I would like a particular user to get a license from SERVER1, but it it's not available then I want her to get a license from SERVER2. Can this be done?
Answer:
Yes. Use any of the methods above, and specify @SERVER1;@SERVER2 as the license file location. This provides what one user has called an "automatic failover".
Caution: This does not apply to redundant three-server setups. Consult your Licensing End User Guide for setting up redundant servers.
Caution: This "automatic failover" is recommended for floating licenses only. If you have a named-user or named-computer license, you would have to name the user or computer on both servers. But the PALISADE.OPT file can't contain more entries than the number of licenses for that particular machine, so in effect you're giving up one license all the time to provide capacity for the contingency. This is not a problem for floating licenses, which are only reserved when a user actually begins using the software.
last edited: 2012-10-01