| # License management and validation A license management mechanism is a copy protection mechanism used to regulate the commercial use of LN. For testing and demonstration purposes, unprotected software is dispatched with limited validity. The unprotected software must be validated before a specified expiration date. To license and validate LN LN uses a license management mechanism, and a validation mechanism to regulate the commercial use of LN. You validate and license your LN software with the Infor Solution License Manager (SLM). The SLM is a stand-alone product capable of licensing various Infor products. It’s strongly advised to install at least two physical SLM servers on two separate systems, combined as one logical SLM server, if you use SLM to validate several Infor products. Licensing solution Solution License Manager (SLM) is the central license manager for the majority of the Infor products. SLM is a central license manager in the sense that one license manager can provide licenses to a variety of products. Installing and configuring a dedicated license manager individually by product is unnecessary. To establish a licensing solution, you require the following three components: The Infor application or product that has adopted SLM licensing The Solution License Manager product itself for handling the licenses. The License Manager checks the license requests from the adopting applications, according to the information stored and validated with Infor. The Activation key that enables the Solution License Manager. Submission of the Activation key enables the licenses that your adopting applications require to work. SLM license types Infor applications can be licensed in various ways. To see how your application must be licensed, refer to the Software License and Support Agreement (SLSA). Depending on the Infor pricing strategy, a restricted set of license types can be assigned to a specific application. For example, some applications can be licensed through any license type, while others can only be licensed through a server license. In general, the license types are distinguished in node locking and user locking. With a node-locking license, the adopting application can only work on a specific node in your network. A network node can be a server but also a desktop. With a user-locking license, the adopting application can only work with specific named users or with a limited amount of concurrent users. Currently, the Solution License Manager supports the following license types: Concurrent User license A user-locking license in which a pool of concurrent users can use the adopting application. Named User license A user-locking license in which a pool of specific named users can use the adopting application. Server license A node-locking license in which a pool of specific named server or desktop computers can use the adopting application. Instance license An instance-locking license in which a pool of specific named instances can be used for the adopting application. Note: With SLM 2.5, instance licensing is registered by means of server licensing. Desktop license A node-locking license in which a set of adopting applications are linked to a pool of specific named server or desktop computers. When a license request is made, the SLM server checks the license configuration (License file) to see how many desktops, users, servers, or instances can use the application, and then, according to the license type, checks the specific named user, server, or desktop. Some adopting application can be licensed with all the various license types, while others can handle only a selection of licenses. Named User license If an adopting application uses Named User licensing, the SLSA states the number of named users that can use that application. The SLM server keeps track of a list of all specific users that are permitted to use that application. The server will reject a license request from an adopting application if the SLM server does not know the specific user name. Infor only validates the amount of named users. Infor never knows the specific names of these users. Some applications automatically synchronize the user names of their authorization module with the SLM server. The SLM server checks for a specific user name in combination with the desktop name where the application is running. You can specify that a specific user can run the application concurrently from multiple desktops. Each desktop on which this user runs the application decreases the number of licenses by one. License Administration in LN In case of a Named User Licence, you can use the the License Administration sessions in LN to keep the Named User list in SLM up to date. The following is a short description of the License Administration sessions. SLM Product IDs by User (ttslm0130m000) Use this session to display or edit the SLM Product IDs that are used by a user. Link SLM Product IDs to Users (ttslm0230m000) Use this session to link SLM Product IDs to Users based on the Authorization Management System. This session links the product IDs to users, based on which sessions the users are authorized for. Synchronize User Data with SLM (ttslm0230m100) With this session you can synchronize user names with the Solution License Manager for product IDs that require a Named User License. |