HLServer: Linux Server Setup

From Headus Docs

(Difference between revisions)
Jump to: navigation, search
Revision as of 01:53, 2 May 2015 (edit)
Headus (Talk | contribs)
(→Setup)
← Previous diff		 Revision as of 04:30, 21 June 2016 (edit) (undo)
Headus (Talk | contribs)

Next diff →
Line 1: Line 1:
-{{:HLServer: Menu}} Typically you'll want be '''root''' and extract the TGZ file into '''/usr/local''', though that's not a strict requirement. If you install into somewhere other than /usr/local/hlserver, you'll need to change the HEADUS_HOME variable in the hlserver startup files.+{{:HLServer: Menu}} Typically you'll want be '''root''' and extract the TGZ file into '''/usr/local''', though that's not a strict requirement. If you install into somewhere other than /usr/local/hlserver, you'll need to change the HEADUS_HOME variable in the hlserver setup files.
- +
-{{warning|Previous Linux installs of HLServer extracted to '''/usr/local/''headus''''', and were split across the '''etc''' and '''lib''' sub-directories, but now all files are in the single '''hlserver''' directory. If you are upgrading, copy your old config and keys file to the new directory, and update or replace your init.d hlserver.run script.}}+
{{warning|HLServer uses '''/usr/tmp''' to save a PID file when running. If '''/usr/tmp''' doesn't exist, then HLServer may start, but will exit soon after. Creating a symbolic link from '''/tmp''' to '''/usr/tmp''' will fix this problem.}} {{warning|HLServer uses '''/usr/tmp''' to save a PID file when running. If '''/usr/tmp''' doesn't exist, then HLServer may start, but will exit soon after. Creating a symbolic link from '''/tmp''' to '''/usr/tmp''' will fix this problem.}}
Line 15: Line 13:
; hlserver.log : This is a series of date stamped log messages from the server showing, amongst other things, who is grabbing which licenses. ; hlserver.log : This is a series of date stamped log messages from the server showing, amongst other things, who is grabbing which licenses.
-; hlserver.redhat : This is a RedHat/Fedora script that can be used to start the server on 'init' based boots, and stop it on shutdown. Installation instructions are in the file. +; setup.redhat : This is a RedHat/Fedora script that can be used to start the server on 'init' based boots, and stop it on shutdown. Installation instructions are in the file.
-; hlserver.service : This can be used to start the server on 'systemd' based boots. Installation instructions are in the file. +; setup.systemd : This can be used to start the server on 'systemd' based boots. Installation instructions are in the file.
-; hlserver.debian : Start/stop script for Debian/Ubuntu based systems. Installation instructions are in the file. +; setup.debian : Start/stop script for Debian/Ubuntu based systems. Installation instructions are in the file.
; hlmanager : This is the manager application. See [[HLServer: The Manager|The Manager]] chapter for details. ; hlmanager : This is the manager application. See [[HLServer: The Manager|The Manager]] chapter for details.
Line 27: Line 25:
</ul> </ul>
-== Setup ==+== Setup v2 ==
 + 
 +== Setup v1 ==
You will need root access on the server host to do this; read the appropriate script file for full installation instructions. You will need root access on the server host to do this; read the appropriate script file for full installation instructions.

Revision as of 04:30, 21 June 2016

Cover Page
About HLServer
Linux Server Setup
Windows Server Setup
OS X Server Setup
Server Config
Application Config
The Manager
Adding New Keys
Trouble Shooting
Download PDF
Typically you'll want be root and extract the TGZ file into /usr/local, though that's not a strict requirement. If you install into somewhere other than /usr/local/hlserver, you'll need to change the HEADUS_HOME variable in the hlserver setup files.
Image:warning.jpgHLServer uses /usr/tmp to save a PID file when running. If /usr/tmp doesn't exist, then HLServer may start, but will exit soon after. Creating a symbolic link from /tmp to /usr/tmp will fix this problem.

The following files make up the Linux license server installation:

    hlserver 
    This is the server application. It need not be run with any special privileges unless the PORT used is under 1027.
    hlserver.conf 
    The contents of this file, explained in detail in Server Config, 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.
    setup.redhat 
    This is a RedHat/Fedora script that can be used to start the server on 'init' based boots, and stop it on shutdown. Installation instructions are in the file.
    setup.systemd 
    This can be used to start the server on 'systemd' based boots. Installation instructions are in the file.
    setup.debian 
    Start/stop script for Debian/Ubuntu based systems. Installation instructions are in the file.
    hlmanager 
    This is the manager application. See The Manager chapter for details.
    .keys 
    This file holds the floating license keys.

Setup v2

Setup v1

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.

Once you have some keys, follow the instructions in whichever setup script is appropriate for your system (i.e. hlserver.redhat, hlserver.debian or hlserver.service).

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