Start FlexNet Publisher

The procedure to start a FlexNet Publisher depends on the platform you are using.

NOTE:

• The lmtools.exe program must be run either directly on the file server desktop or from a client PC using an application such as Windows Remote Desktop. Administration access to the file server is usually required.

Starting a Windows server using lmtools.exe

1. Start the lmtools.exe program.
2. On the Server/License File tab, select the Configuration using Services option.

   

3. Click the Config Services tab to display the dialog. This example assumes the FlexNet tools were installed in the C:\Flexnet\ folder. Make sure the Path to the lmgrd.exe file is the same as the path where you installed the FlexNet tools. The paths to the license.dat file and the debug.log file do not have to be in the same folder, but you should include the file names and extensions (license.dat, debug.log) as shown in the example.

   

4. Enter the paths that specify the required files, or click the browse buttons to locate and select the files. You must specify paths for the:
   • executable file lmgrd.exe.
   • license file license.dat.
   • log file (must first be manually created by you), which is debug.log in this example.
5. If you require the server software to start running automatically when the server computer is turned on:
   • Enable Use Services.
   • Enable Start Server at Power Up.
6. Click Save Service.
7. At the prompt, confirm saving the FlexNet License Manager service.
8. Click the Start/Stop/Reread tab, and ensure that the FlexNet License Manager service is selected.
9. Click Start Server to start running the floating license server software.
10. Check whether the floating license server started successfully:
    • Click the Server Status tab
    • Click Perform Status Enquiry

      The status information shows that the floating license server and vendor daemon are both UP, followed by a licensed feature usage list. Any floating license server errors are shown in the status information.

After you have started the license server, you can use a text editor, such as Notepad, to inspect the server debug log file.

Starting a Windows server from the command line

To start the floating license server on Windows using the command line:

1. Go to the directory where the floating license server software is installed.
2. Type:

   lmgrd -c license_file_name -l logfile_name

   Where

   license_file_name	specifies the fully qualified path name of the license file
   logfile_name	specifies the fully qualified path name to a server debug log file. The server log file can become very large, so it might be necessary for you to control its size.

After you have started the floating license server, you can use a text editor, such as Notepad, to inspect the server debug log file.

Starting a Unix/Linux server

To start the floating license server software on a Unix/Linux server:

1. Go to the directory containing the floating license server software.
2. Type:

   nohup lmgrd -c license_file_name -l logfile_name

   Where

   license_file_name	Specifies the fully qualified path name of the license file.
   logfile_name	Specifies the fully qualified path name to a server debug log file. The debug log file must be on a local storage device to avoid network problems. The server log file can become very large, so it might be necessary for you to take action to control its size.

    

   • lmgrd does not require root privileges, ARM recommends that you start the server as a non-privileged user, instead of giving it root privileges.

After you have started the floating license server, you can type, for example:

tail -f logfile_name

to see the most recent output from the floating license server.

For more details on how to start and configure a floating license server on Unix/Linux, see the Flexera Software documentation.

Note

• If you are adding a new license to a system with a running floating license server, you must
  1. Shut down the server.
  2. Point the server to the new license file.
  3. Restart the server.

  If this is not done, the new license information might not be recognized by the license daemons.

• ARM does not recommend the use of the lmreread command.