Migrating from lmgrd to lmadmin
A Fundamental Mode Change
The lmadmin license server manager combines all the functionality of the lmgrd license server manager with a Web-based, administrative interface. However, the lmadmin license server manager operates in some fundamentally different ways than the lmgrd license server manager.
The obvious change is that previous versions of the license server manager (lmgrd) used a command-line interface and the new license server manger (lmadmin) supports a browser-based client connection over HTTP. A more fundamental change in operation is that configuration options are now persistent—if you change settings and relaunch the tool, the previously set options stay in effect.
With lmgrd, the primary mode of operation is to run one instance of lmgrd for each vendor daemon where lmgrd obtains its configuration information from the command-line options used when the program is started, including the required specifying of a license file. To change settings you typically stop the license server, edit the license file and/or the script containing your command-line options, and relaunch the tool.
In contrast, the lmadmin license server manager is designed to:
| • | Support multiple vendor daemons with one lmadmin process. |
| • | Launch without requiring any configuration options. |
| • | Perform all server configuration and administration functions from the browser. (For special circumstances, the lmutil package provides additional functions.) |
| • | Import existing license files (the new lmadmin license server manager is compatible with license files and vendor daemons produced using FlexNet Publisher 9.2 and later). |
| • | Keep configuration options persistent. |
Persistent configuration options is a significant change. Once set, settings remain in effect until changed. For example, if two vendor daemons are specified to use the same TCP port, only one will run. With lmgrd, this requires making changes to at least one of the license files as well as stopping and restarting the server. With lmadmin, you can change the TCP port for a vendor daemon while the license server is running. The manually specified port is then persistent and will remain as it was manually set the next time the license server is started, even if the license file is changed. The changes set in the license server manager override the license files.