-d 

Run as a background daemon process. This is recommended, but applicable to Linux installations only.

-c,<filename> 

Use this config file.

-l,<num>,<days>,<log> 

Number of log files, how many days between switches, and filename format string. A typical value for this argument would be -l,4,7,hlserver-%d.log, meaning use 4 log files, switching after a week, and cycle between hlserver-0.log, hlserver-1.log, hlserver-2.log and hlserver-3.log.

Running under Linux

The install file comes with a couple of sample start-up scripts, one for Redhat based systems, and another for Debian flavors. You will need root access on the server host to do this; read the appropriate script file for full installation instructions.

Copy sample-hlserver.conf into hlserver.conf and edit to suit your network setup. You should at least change the IP range for the lan group.

Run 'hlserver' from the command line when first installed. You'll get a "License not found" type error, and 5 rows of hex numbers; email these to your vendor to get your license strings.

Running under OS X

The install file comes with a setup script that will take you through the steps required to get hlserver up and running. See the previous chapter for details.

Figure 1. Windows Vista Install

Figure 2. Services Control Panel

Figure 3. headus Floating License Server

Figure 4. Windows Vista Firewall

Running under Windows

After running the ihlserver.exe file to install the software, you'll need to perform the following steps to get the server going:

1. Edit hlserver.conf to suit your network setup. You should at least change the IP range for the lan group, and change Administrator to your login username in the Manager group.
   
   
2. Edit hlserver.ini to change the command line args to suit your setup (see explanation of command line args above). Most people should be able to get by with the defaults. If you don't move hlserver.conf from the installation directory, then you don't need to define a '-c' config file location.
   
   
3. Run Start -> Programs -> headus License Server -> 1) Install service; the first time you do this you'll get a "License not found" type error. Email the 5 rows of hex numbers to your vendor to get your license strings.
   
   Note: To cut'n'paste from the Windows command shell window, click on the icon at the top left of the window, pick Edit->Mark from the popup menu, click'n'drag the left mouse button to select the text, then hit the Enter key. You can then paste that text into email.
   
   Or: If you are using a recent release, the hex codes are written into a temporary file, and the path to that file will be displayed. You can then attached that text file to your email.
   
   
4. Once you get your licenses, run 1) Install service again, and answer "y" to the edit keys file question. Paste the license keys provided into the keys.txt file, and save it.
   
   
5. Run 1) Install service one more time, but this time you should get a "service installed" message.
   
   

   If you get a permission denied type error at this step, right click on the menu option and select "Run as Administrator" (see Figure 1).

   
   
6. Run 2) Start service to open up the Services control panel (see Figure 2).
   
   
7. Double click on headus Floating License Server to bring up the Service window (see Figure 3) and select Automatic, then OK, so that hlserver restarts whenever the system is rebooted.
   
   
8. Click on the Start button to start hlserver.
   
   
9. Run 3) Run HLManager to check that hlserver is running OK, and that the licenses have loaded correctly.
   
   If you can't get a connection, check the log files in the hlserver install folder for errors. If you see a "Denied - manager access to user@host" message, then check that the user name listed in the error matches that in the Manager group in hlserver.conf. Use the Services control panel to restart hlserver if you need to make any changes to hlserver.conf. See The Manager for details.
   
   
10. If you have a firewall installed on the server, you'll need to allow access to the port specified in the hlserver.conf file (default 11668). See Figure 4. for the Windows Vista firewall configuration.

Users should now be able to access the license server from others systems on the local network.

A user has reported that HLServer didn't work on his XP x64 system when IPv6 was enabled for the Local Area Network. We haven't confirmed or fixed this yet, but keep it in mind if you also experience problems.

Updating under Windows

If you already have hlserver installed, but need to install a newer version, follow these steps:

1. If hlserver is currently running, first inform your users that you are stopping the floating license server, and that they should save all their work. Applications using floating licenses will exit when hlserver is stopped.
   
   
2. Run 4) Stop service to open up the Services control panel; right click on headus Floating License Server and select Stop to stop hlserver.
   
   Note: If you have an old version of HLServer, with no Start menu options, use "Start->Programs->Administrative Tools->Services" to open up the Services control panel.
   
   
3. Run 5) Remove service and you should get a "service removed" message.
   
   Note: Under Windows Vista you will need to right click on the menu option and select "Run as administrator".
   
   Note: If you have no Start menu options for HLServer, open a command shell window and remove the service by running hlserver -remove.
   
   
4. Run 6) Uninstall software to remove the old executables, leaving your config files untouched.
   
   Note: If you have no Start menu options for HLServer, use the system control panel's "Add/Remove Programs" to uninstall the old version. You will most likely have to move your old config and keys files into the new install directory too; by default its different to the older installs of HLServer.
   
   
5. Run the new ihlserver.exe file to install the new software.
   
   
6. Run 1) Install service and 2) Start service to get the hlserver service installed and running.

Users should now be able to access the new license server.