Adding a Vendor Daemon to lmadmin

The lmadmin license server must be configured with data about vendor daemons and license files. To add a vendor daemon, you must import it using a license file. You can do this from the command line (or from the lmadmin user interface.)

Note:FlexNet Publisher provides a sample vendor daemon (demo or demo.exe) that you can use with lmadmin. To use this vendor daemon, first copy it and its associated library from the <platform_dir> directory to the <platform_dir>\lmadmin\demo directory. (The associated library is one of the following: demo_libFNP.so for UNIX, demo_libFNP.dll for Windows, demo_server_libFNP_notr.so for AIX, or demo_libFNP.dylib for Mac.) Then, issuing the command described in the following procedure, import the vendor daemon, using the sample license file lmadmin\demo\demo.lic.

To add a vendor daemon from the command line:

1. Create or locate a valid license file (for example, mylicense.lic) with the appropriate SERVER lines, VENDOR lines, and feature definition lines.
2. Make sure that the vendor daemon executable is in the correct location relative to lmadmin. This location is defined in the VENDOR line.
3. Import the license file by executing the following command:

lmadmin -configDir <conf_path> -import <mylicense.lic>

where <mylicense.lic> is the path and name of the license file, and <conf_path> is the path to the conf folder. This command imports the license file, but does not start the license server.

When you import a license file, the license server configuration file (Windows: <lmadmin_runtimedata_dir>\conf\server.xml; non-Windows: <lmadmin_install_dir>/conf/server.xml) is populated with the vendor daemon information (vendor name, vendor daemon path, port number, etc.).

4. Start the license server. See Manually Starting the License Server Manager.

Note:For information about how to import a license file using the license server management interface, see the Online help available from within the license server management interface.

Note:The following behavioral modifications to lmadmin as part of the RCE vulnerability fix are:

• The vendor daemon executable, which needs to be started by lmadmin, must be located by default within the lmadmin root directory or its child directories.
• Remote sites, including Windows network share paths, are not permitted by default.
• If a vendor daemon location, other than ones permitted by default is necessary, the License administrator can use the newly-added -vdSearchPaths command-line option of lmadmin to specify absolute paths of the required vendor daemon location. This will result in the specified path(s) being whitelisted as an allowed path.