License Server Sockets

When using TCP/IP ports, each FlexEnabled application connected to a license server uses one or more sockets. Depending on how the publisher implemented licensing, the FlexEnabled application may need one or more sockets. Ask the publisher for this information. The per-process system limit for file descriptors determines the number of sockets available to the license server. The total number of sockets that the license server uses is slightly larger than the total number needed by the FlexEnabled applications that connect to it.

If the number of sockets required by the license server on a single system becomes excessive, then one solution is to run multiple license servers and split the licenses between them. This reduces the networking traffic to each license server. See Redundancy Using the License Search Path for instructions and information about this configuration. Your publisher will need to agree to issue new license files, if you want to move licenses from an existing license server. If the licenses are held in trusted storage, the publisher may provide an automated process for returning them and activating them on another license server.