Altair License Server (ALS)

The ALS is built on X-Formation’s LM-X license manager suite.

The main components of the system are:
  • License server (lmx-serv and
  • Configuration files (alus.conf and optional .cfg file)
  • License file (altair_lic.dat or equiv.)
  • Application programs (HyperWorks, PBS Professional, FEKO...)
  • Supplied utilities (almutil, almutilGUI...)

License Server Daemon (lmx-serv)

The Altair License Server (ALS) serves network licenses. It runs on a license server machine that can be reached by network clients. It is typically setup to automatically restart on machine restart and to communicate via a specific TCP/IP port. The default port is 6200. The server process requires one (optionally, two) configuration file to run. These are alus.conf (required) and a command line specified .cfg file, if used. The alus.conf file contains Altair specific configuration information and the .cfg file contains generic LM-X configuration data.

Multiple LM-X servers from different vendors may run on a single machine by specifying different ports. However, only a single server from any specific vendor may run on a machine at one time. An LM-X based server may also run side-by-side with the licensing systems of other licensing system vendors such as FLEXlm and others.

The ALS also creates transaction logs that provide detailed license usage information. These logs are plain readable text and documented for ease of use. Two versions of these logs are available: anonymous and detailed. By default, only the anonymous logs are written. This can be changed in the alus.conf file. Command line options for theALS are listed in Altair and LM-X Programs.

Configuration Files

The alus.conf file stores configuration information required by the ALS and the URT to function properly. The ALS needs to find the alus.conf file in order to start. By default, it is located in the current working directory or you can specify the location (the preferred method) by setting the environment variable ALUS_CONF_FILE on all platforms or by specifying the following registry key on Windows.

Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Altair Engineering, Inc.\Licensing\, set ALUS_CONF_FILE to the full pathname of the alus.conf file.

The example alus.conf files for Windows and UNIX are listed in Appendix: Example of alus.conf Files.

By default, the installer also creates altair-serv.cfg. This file contains information that designates the location of the license file, the location in which to place the log files, and which TCP/IP port to use. It also provides other information used to configure the server. A sample_config.cfg is also placed in the installation directory that contains all the options available in the config file. This file has much of the same functionality as the FLEXlm options file. It is also used to configure Highly Available (HAL) server setups. This setup uses three servers to provide redundant license servers that continue to work in the event of the primary server going down.

License File (altair_lic.dat)

The license file is a plain text document that contains license information. Each block of text in the file is known as a feature block. It contains all the details for that feature including its name, quantity, sharing, extra details, and whether it is server or nodelocked. A server based license file can be identified by its feature blocks containing the keyword COUNT=value. The default name that Altair products use for this license file is altair_lic.dat.

Using the Altair License Server

In order for applications to use the ALS, the environment variable, ALTAIR_LICENSE_PATH, must point to the appropriate location. Multiple license paths are allowed and should be separated by a semicolon (;) on Windows and a colon (:) on Unix/Linux. The proper format for a network license location is port@hostname. If you are using a local license file, simply set the value to the full pathname of the file.

A few examples of license paths:
Table 1.
On Windows
ALTAIR_LICENSE_PATH=c:\Program Files\Altair\Licensing12.0\altair_lic.dat
Table 2.
On Linux/Unix:

For HAL setups list the three servers in the order: primary; secondary; tertiary.