HLServer: OS X Server Setup

First you'll be asked to check the config file. The "GROUP lan" IP range will have been set already to match your local network, but this may need to be adjusted if you have a more complicated setup (e.g. multiple sub-nets in a larger campus network). Save the file, kill the window, then re-run the setup script to continue.
Initially you wont have license keys, so at the "Do you have the keys" question type n followed by Enter to generate the code strings. Email the 5 code strings to your vendor to get your license keys.
When you get your license keys, re-run the setup script and answer y to the "Do you have the keys" question, then type Enter to continue and the keys file will open up in the text editor. Cut'n'paste your license keys in, save the file, kill the window, then re-run the setup script to continue.
At the "Do you have updated license keys" question, answer n and then 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.

Update

Retrieved from "http://www.headus.com/doc/HLServer:_OS_X_Server_Setup"

 # Initially you wont have license keys, so at the "Do you have the keys" question type '''n''' followed by Enter to generate the code strings. Email the 5 code strings to your vendor to get your license keys.<br><br>
 # When you get your license keys, re-run the '''setup''' script and answer '''y''' to the "Do you have the keys" question, then type Enter to continue and the keys file will open up in the text editor. Cut'n'paste your license keys in, save the file, kill the window, then re-run the '''setup''' script to continue.<br><br>
-# At the "Do you have updated license keys" question, answer '''n'''.
+# At the "Do you have updated license keys" question, answer '''n''' and then 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.
-== Setup (old) ==
-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 ...