Flexera Software's FlexNet Publisher, formerly known as FLEXlm, is a software license management system that enables organizations to centrally track and manage their licenses within departments and across the organization. NI supports FlexNet Publisher implementations with FlexNet Publisher compliant license files, but NI does not design or sell FlexNet Publisher. This short document will guide you step-by-step through the setup and configuration of FlexNet Publisher.If you use FlexNet Publisher instead of using Volume License Manager (VLM), there are certain features of VLM that will not be available to you, including overdraft, disconnected and home licenses. Overdraft licenses enable you to use more named-user or computer-based licenses than your agreement allows. Disconnected licenses allow you to use NI software with computers that cannot always access the license server. Home license files allow you to use your software on one computer at home without using a license. If these features are important to you, consider using VLM to manage your licenses. VLM is free of charge for volume customers to best utilize their NI software.
Send your FlexNet Publisher server name, server operating system (either Windows or Linux), and host ID (MAC address for Windows and host ID for Linux) to Agreements@ni.com. State that you prefer to use FlexNet Publisher to manage your licenses.
Create a folder on your computer that will contain all the required files for licensing.
Download the following files located on the right navigation pane of this document based on your operating system:
windows_flexlm.zip - contains lmgrd.exe (the license manager daemon) and nilm.exe (the NI License Manager vendor daemon)
linux_flexlm.zip - contains lmgrd.exe (the license manager daemon) and nilm.exe (the NI License Manager vendor daemon)
Copy the .exe files into the licensing folder created in step 1.
After receiving your license file, copy the license file into the licensing folder.
Create a new text file in the licensing folder for the debug log file. Rename the file "debug log.log".
Make sure the licensing folder contents is similar to the image below. For more information about nilm.opt, read the Create an Options File section.
Launch the LMTOOLS utility (lmtools.exe).
Navigate to the Config Services tab. Input the following information:
Type in a new Service Name such as NI FLEX License Manager
Input the paths to the lmgrd.exe, license, and debug log files.
Click Save Service.
If your license file requires computer-based permissions for the software to be used, you will have to create an options file denoting which computers have permission to use each product. For more information on the options file, see Constructing Options File for FLEXnet Publisher.
Create a new text file in the licensing folder. Rename the file "nilm.opt".
Add the following text to the file using standard FlexNet Publisher formatting:
INCLUDE <product name> HOST <host name>
<product name> is the NI product you are specifying permissions for. Product names can be found in the NI license file.
<host name> is the computer name. Note that computer names are case-sensitive.
If your license file requires named-user permissions for the software to be used, you will have to create an options file denoting which users have permission to use each product.
INCLUDE <product name> USER <user name>
<user name> is based off the Windows login name. Note that user names are case-sensitive.
The options file should be saved in the same directory as the vendor daemon nilm.exe. If you have both named-user and computer-based licenses, you can put both types of INCLUDE lines in the same options file.
Navigate to the Service/License File tab.
Under Server List, select Configuration using Services. Select the NI FLEX License Manager created in the previous steps.
Navigate to the Start/Stop/Reread tab. Make sure the desired service is selected and click Start Server.
Client software is not configured to look to the FlexNet Publisher server by default. For client machines to look for the license server, you can set environment variables, specify the server in NI License Manager, or create a Volume License Installer to automatically point the machine upon installation of the client software.
There are three locations where NI software looks for a server name and port:
Windows environment variable NILM_LICENSE_FILE
Windows environment variable LM_LICENSE_FILE
NI License Manager in the Options»Preferences»Use Volume License Servers field.
You can set this value directly at one of the following locations, based on your operating system:
<ProgramData>\National Instruments\License Manager\Data\servers.ini
HKEY_LOCAL_MACHINE\SOFTWARE\FLEXlm License Manager\NILM_LICENSE_FILE
Updates to the server name and port within the servers.ini file or in this registry key will be reflected in the NI License Manager location shown above.
Using VLM Volume License Installers adds installer steps to automatically point client computers to the FlexNet Publisher server. One benefit is that end users do not have any additional steps after installing the software. To prepare your software for Volume License installation, complete the following steps:
Note: VLM can be installed on a machine that is NOT the server machine.
Create a Volume License Installer.
Have your end users install the software from the Volume License Installer.
Note: If the software is already installed on the end user's machine, users can leave the software installed and simply run the program vlmclient.exe found in the same location as the Volume License Installer. In the created Volume License Installer folder, copy the Client folder onto the client machine, and run the vlmclient.exe in that folder.
You do not have to keep track of how many people have installed the software since the licenses are managed by FlexNet Publisher.
Borrow License from a License Server Running FLEXnet Publisher
FLEXnet BORROW in LMTOOLS for NI Volume License Agreements
Why Does "NILM License Manager" Show Up in LMTOOLS?
Configuring Communication Ports for NI VLM or FLEXnet Publisher
Collaborate with other users in our discussion forums
A valid service agreement may be required, and support options vary by country.