SLM Configuration

The SLM configuration is, in fact, the representation of the Software License and Support Agreement (SLA) between the customer and Infor. The SLM server uses the SLM configuration to validate the license requests. SLM configuration is carried out through the SLM MMC snap-in.

The SLM configuration is specific for an SLM Cluster. The Activation key created by Infor Validation for that SLM configuration can only work on that specific SLM Cluster. The SLM configuration contains data about the customer, for example, customer code and license number, and data about the licensed applications, for example, license type or maximum number of users as well as identifiers for the hosts the SLM Servers are running on.

Customer specific entries

The customer-specific entries keep track of, for example, the SLM server ID for which this SLM configuration is created, the number under which the Customer is registered with Infor and whether High Availability Support (HAS) is enabled.

Application specific entries

The SLM configuration contains all the licensing details by licensed application. Every licensed application can have one or more product IDs. /baanerp/baan.fullversion has, for example, a product ID for the runtime environment and one for the development environment. A product ID can have only one entry in the SLM configuration, which means that you can link only one license type to a product ID. Together with that license type, you must specify in the SLM configuration the amount of licenses and the start and end date of the licensing period.

The SLM server keeps track of what is already validated in the SLM configuration, in other words, for which entries a validated Activation key is available, and which entries have been changed. Changed entries only become active if a new SLM activation key is requested and provided by Infor, and this new key was submitted to the SLM server.