Home7.x Network GuideFAQsMultiple License Servers? (7.x)

3.5. Multiple License Servers? (7.x)

Applies to: All Palisade Concurrent Network software, release 7.x

Can a client get its license from multiple servers?

For an Enterprise Network, the issue does not arise because the license is obtained in a one-time activation rather than dynamically when the application is run.

For a Concurrent Network, you can specify multiple servers. You allocate your licenses among the servers, but if one server is unavailable the client will try to get a license from the next. FLEXnet documentation says that the license software looks at multiple servers in the order listed.

Servers are separated by semicolons, as in this example:

27000@Alpher;@Bethe;27010@Gamow

In this example, the end-user (client) software will try to get a license from server Alpher, using port 27000 only. If no license is available, it will try server Bethe, all ports 27000 through 27009. Lastly it will try server Gamow, port 27010 only. (The port numbers must match those chosen on the respective servers; different servers can use the same port number or different port numbers.)

For new clients, the easiest thing is to edit the SERVERNAME line in the Palisade_NetworkClient.ini file on the server and use the modified file with the client installer. For existing clients, use one of the methods in How do I change port numbers or server names on existing Concurrent Network clients?

From the end user's point of view, there's no difference between one license server and multiple license servers. A user trying to run @RISK Industrial doesn't know which server is providing the license. If the user runs License Manager and clicks Select License, the display will show all available network licenses on all the listed servers, with no indication of the location of any particular license. (Which License Gets Used? tells much more about Select License.)

Future Needs

If you have only one server now, but you want to plan ahead for future configurations, you can list all servers now, even servers that don't exist yet. The client software will not report an error as long as at least one of the listed servers is reachable and has a license available.

For example, even before purchasing a disaster-recovery server, you can preconfigure clients to reach a disaster-recovery server if the regular server is off line. All you'll need to do if the regular server fails is bring the disaster-recovery server on line, and clients will connect to it automatically when they launch the software. (If the disaster-recovery server won't be connected until the production server fails, a simpler alternative is just to give them the same name. The client software reaches a server by name and port number only.)

Last edited: 2015-04-27

This page was: Helpful | Not Helpful