Definitions, acronyms, and abbreviations

Term	Definition
API	Application Programming Interface.
BAANHOME	Replaced by SLMHOME. Supported for upgrade situations of SLM 2.5 and earlier: Environment variable for SLM installation directory, which is %BAANHOME% for Windows and $BAANHOME for Linux and UNIX
BCLM	The former name of the SLM.
Concurrent User License	A user license for use by a pool of users.
DNS	Domain Name Service
HAS	High Availability Support
Heavy User License	A named user license for users in the heavy user role. The adopting application specifies what this role implies.
License file	The XML data file that contains all license information of the license agreement with Infor. Information such as the version number, the activation key, the customer, the host IDs, and the various application licenses
Light User License	A named user license for users in the light user role. Still available for historical reasons. Use Heavy user license instead.
Maintenance Mode	Status of an SLM Server when it’s running but not active and cannot validate license requests.
MMC	Microsoft Management Console
Named User License	A license type in which a product license is linked to specific users.
Server License	A license type in which a product license is linked to specific servers
Servers File	The XML data file with all the servers of a Server License, including the name and identification number of the server machine.
SLM	Solution License Manager
SLMHOME	Environment variable for SLM installation directory, which is %SLMHOME% for Windows and $SLMHOME for Linux and UNIX.
SLM_RUNTIME	Windows only environment variable for SLM program data (license files, log files etc). Default location is %PROGRAMDATA%\infor\slm
SLM Cluster	A SLM cluster consists of one to four SLM servers. It acts to the applications that require licensing as one license server, validating license requests against one license file and license key. The SLM cluster contains one master SLM server and zero or more slave SLM servers. An SLM cluster enables high-availability and load-balancing. Infor strongly advises you to spread the SLM servers across several systems.
SLM MMC snap-in	The graphical user interface that runs as a snap-in in Microsoft Management Console, in MMC and Windows only, to manage the SLM.
SLM product-id	The unique SLM product-IDs are the link between an Infor product and the registered license type, identified/validated by the SLM server.
SLM server	The SLM engine that handles license requests and management requests.
SLA	Software License Agreement. The contract between the customer and Infor. In this contract is stated, among other things: the applications that are used, the type of licensing, and the amount of licenses. Usually, you can find that information in Schedule A of the SLA.
UI	User Interface
Users File	The XML data file with all the users of a Named User License for a particular product. It includes the user name, the user type, and the number of licenses a user is permitted to use.
XML	Extensible Markup Language

API

Application Programming Interface.

BAANHOME

Replaced by SLMHOME. Supported for upgrade situations of SLM 2.5 and earlier: Environment variable for SLM installation directory, which is %BAANHOME% for Windows and $BAANHOME for Linux and UNIX

BCLM

The former name of the SLM.

Concurrent User License

A user license for use by a pool of users.

DNS

Domain Name Service

HAS

High Availability Support

Heavy User License

A named user license for users in the heavy user role. The adopting application specifies what this role implies.

License file

The XML data file that contains all license information of the license agreement with Infor. Information such as the version number, the activation key, the customer, the host IDs, and the various application licenses

Light User License

A named user license for users in the light user role. Still available for historical reasons. Use Heavy user license instead.

Maintenance Mode

Status of an SLM Server when it’s running but not active and cannot validate license requests.

MMC

Microsoft Management Console

Named User License

A license type in which a product license is linked to specific users.

Server License

A license type in which a product license is linked to specific servers

Servers File

The XML data file with all the servers of a Server License, including the name and identification number of the server machine.

SLM

Solution License Manager

SLMHOME

Environment variable for SLM installation directory, which is %SLMHOME% for Windows and $SLMHOME for Linux and UNIX.

SLM_RUNTIME

Windows only environment variable for SLM program data (license files, log files etc). Default location is %PROGRAMDATA%\infor\slm

SLM Cluster

A SLM cluster consists of one to four SLM servers. It acts to the applications that require licensing as one license server, validating license requests against one license file and license key. The SLM cluster contains one master SLM server and zero or more slave SLM servers. An SLM cluster enables high-availability and load-balancing. Infor strongly advises you to spread the SLM servers across several systems.

SLM MMC snap-in

The graphical user interface that runs as a snap-in in Microsoft Management Console, in MMC and Windows only, to manage the SLM.

SLM product-id

The unique SLM product-IDs are the link between an Infor product and the registered license type, identified/validated by the SLM server.

SLM server

The SLM engine that handles license requests and management requests.

SLA

Software License Agreement. The contract between the customer and Infor. In this contract is stated, among other things: the applications that are used, the type of licensing, and the amount of licenses. Usually, you can find that information in Schedule A of the SLA.

UI

User Interface

Users File

The XML data file with all the users of a Named User License for a particular product. It includes the user name, the user type, and the number of licenses a user is permitted to use.

XML

Extensible Markup Language