Select a License Server System

When you select a license server, take the following resources into consideration:

Sockets

Each licensed application connected to a license server uses one or more sockets. The number of sockets available to the license server is defined by the per-process system limit for file descriptors. The total number of sockets used by the license server is slightly larger than the total number needed by the licensed applications that are served by it. If the number of sockets required by the license server on a single machine becomes excessive, the license file can be split into more than one file, on multiple servers.

CPU Time

For small groups of clients, the license server uses very little CPU time, perhaps only a few seconds of CPU time over many days. For a large number of clients, or for high check-out/check-in activity levels, the amount of CPU time consumed by the server may become significant. If such a situation occurs, you may need to ensure that the server machine you select has an adequate number of CPU cycles.

Disk Space

The license package requires about 100 MB of disk space to install. The log files created by the system vary in size, depending on activity. It is recommended that the file system where the log files are to be written has sufficient space to store many days or months worth of log files. There should be a minimum of 500 MB of space for this purpose.

Memory

The license manager daemon uses a variable amount of system RAM. Typical memory usage is in the range of 15-50 MB resident and a virtual set size of 90-150 MB. For very busy servers with a lot of clients the Resident set size could grow to several 100MB.

Network Bandwidth

The licensing process requires a fairly small amount of network bandwidth. Typical networks running over Ethernet should not produce any problems. The system uses TCP/IP for all communications on the configured port, and uses this one port for all communications.

Remote Mounted Disks

Altair highly recommends that the software and all logs reside on disks local to the license server. Testing is only done on local disks/directories. Although remote ones may work, they are not tested

Redundant License Servers

The system supports both HAL (High Availability) servers and server lists. HAL servers act as a quorum to serve up one pool of licenses, allowing one machine to go down without affecting license availability. Multiple independent servers can be used to split up the total license pool and clients can access them via a server list.