Installing lmadmin License Server Manager as an Operating System Service

While it is possible to manually start and stop the lmadmin license server manager, it is recommended that you install it as a service on the operating system so that it will automatically start whenever the operating system restarts.

Important:For security reasons, Revenera recommends that the license server be run with non-elevated user privileges (which, in turn, the vendor daemon inherits). See the later section, Running FlexNet Publisher License Server as a System Service With Non-Elevated Privileges, for details on enabling the lmadmin operating-system service to run under a non-Root or non-administrator user account.

Windows Systems

As part of the lmadmin installation process on Windows systems, the lmadmin installer might provide the option to configure the lmadmin license server manager as a system service. However, only users in the Windows Administrators group can successfully perform this action. The Startup Type is set to Automatic so that the service starts automatically when the system is restarted.

As an alternative, use the following lmadmin command-line arguments to install and uninstall the service (see the table below).

Important:After you execute the command to install the license server manager as a Windows service, the service is not started automatically. You must manually start the service for the first time using the Windows Services Console.

lmadmin command-line arguments to configure lmadmin as a Windows service.

lmadmin Command-Line Argument	Description
–installService service name	Creates a Windows service (with the name you provide) to run the license server manager. The service will run under the LocalService account.
–removeService	Uninstalls the Windows service with the name you specified. Make sure you stop the service before removing it.
–delay nn	Sets the number of seconds (nn) to delay between the time you start the service and the time it actually begins running. This delay is helpful when a FlexNet ID dongle is used to lock the license server to a machine (that is, when the FLEXID is used on the SERVER line). The license server can sometimes fail to start when a system reboots because the license server loads before the dongle device driver has a chance to load properly. Note:Use this option with the -installService argument.

To run lmadmin with any of the command-line arguments used to configure lmadmin as a Windows service requires that the user has administrator privilege. (Windows versions enforce administrator privileges for installation or removal of a service.) Therefore, to use these arguments you must do the following:

•

Sign in as an administrator before running lmadmin with these arguments.

•

Start the command prompt using the option Run as Administrator.

Linux Systems

For supported LSB platforms, a subdirectory of <lmadmin_install_dir>/examples/ provides the script files that contain service control instructions, and details on where each script file should be installed.

Depending on your platform, you need to install either of these script files:

•

<lmadmin_install_dir>/examples/service/lmadmin—for platforms using the old BSD startup script.

•

<lmadmin_install_dir>/examples/systemd/lmadmin.service—for use on platforms using the new systemd service startup.

(Do not confuse the lmadmin file with the executable for the license server manager.)

Additionally, see Running FlexNet Publisher License Server as a System Service With Non-Elevated Privileges for instructions on modifying the required script to run the lmadmin system service with non-elevated privileges.

Note:The instructions in these sample scripts should work on other lmadmin-supported UNIX platforms with minor changes.

OS X Systems

On OS X Systems, administrators have to create their own startup script in a directory such as /Library/StartupItems/lmadmin. The installed <lmadmin_install_dir>/examples/service script is the same script as installed for Linux and Solaris systems and is provided for reference only; it will not work properly on OS X systems. For more information on installing an executable file as a system service (and running it with non-elevated privileges) on OS X systems, see any of the many publicly available references such as http://www.oreilly.com/pub/a/mac/2003/10/21/startup.html.

Note:Revenera is not responsible for the accuracy of information obtained from such reference sources or for the results of the startup script that you write.