1. Install the hlserver files. See below for OS specific instructions.
   
   
2. Using the sample provided, create hlserver.conf. You should at least change the IP range for "GROUP lan" to reflect your local setup. See below for an explanation of the hlserver config file.
   
   
3. Put the keys provided into .keys (Linux/OS X) or keys.txt (Windows). See below for an explanation of the key strings.
   
   
4. Start hlserver up. See the following chapter, Running the Server for OS specific instructions.
   
   
5. Pass on to your users the information in Application Config so they can configure their software installs to access the floating license server.

If your users encounter any problems accessing the floating licenses, see Trouble Shooting for steps you can follow to track down the problem.

OS X Install

Select or create a new user that will be used to run the hlserver daemon. Login as that user, open up a shell window, extract the TGZ file into a temporary directory, change to that directory and run the setup script ...

 tar xvfoz hlserver-osx-111202.tgz --directory=/tmp
 cd /tmp/hlserver
 ./setup

First you'll be asked to edit the config file. If you are familiar with vi, then run 'vi hlserver.conf' from the shell window. If you prefer to use Finder, double click hlserver.conf; if prompted for an editing application, select TextEdit. You should at least change the IP range for "GROUP lan" to reflect your local setup.

Re-run the setup script and the keys file is checked. If you have your license keys already, cut'n'paste them into the sample-keys file, otherwise email the 5 code strings to your vendor for some license keys. As with the config file above, you can either use vi from the shell window, or TextEdit from Finder, to edit the sample keys file. Once the keys are in the sample keys file, use the shell window to rename it to '.keys' ...

 mv sample-keys .keys

Re-run the setup script and you'll be asked for an installation location. By default the script will want to put the binaries and config files into /usr/local/hlserver, but you can type in a different path at the prompt if you wish.

If the setup script runs smoothly, hlserver will be started and hlmanager is run as a final check. You should see something like the following as output ...

 Waiting for HLServer to start ... 10 9 8 
 Trying HLManager ...
 Trying architec@localhost ...
 Server localhost up 4 seconds
 <--------- Licenses ---------->  <------------------------- Users ------------------------->
 Name        Status    Free Used  Id Hostname        User     App           Age       Idle   
 uvlayoutv2  29 days      4    0

hlserver will be automatically restarted whenever the system is rebooted, and you can stop and start it via the launchctl command.

The following files make up the OS X license server installation:

hlserver 

This is the server application.

hlserver.conf 

The contents of this file, explained in detail below, controls the behavior of the server.

hlserver.log 

This is a series of date stamped log messages from the server showing, amongst other things, who is grabbing which licenses.

hlmanager 

This is the manager application. See "The Manager" chapter for details.

.keys 

This file holds the floating license keys.