HLServer: Server Install

Revision as of 03:29, 15 January 2014 (edit)
Headus (Talk | contribs)

← Previous diff

Current revision (04:08, 15 January 2014) (edit) (undo)
Headus (Talk | contribs)
(Removing all content from page)

(3 intermediate revisions not shown.)

Line 1:

-

{{:HLServer: Menu}} {{TOC}} To correctly install and run hlserver you should follow these steps:

-

# Install the hlserver files. See below for OS specific instructions.

-

# 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.

-

# Put the keys provided into .keys (Linux/OS X) or keys.txt (Windows). See below for an explanation of the key strings.

-

# Start hlserver up. See the following chapter, [[HLServer: Running the Server|Running the Server]] for OS specific instructions.

-

# Pass on to your users the information in [[HLServer: Application Config|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

-

[[HLServer: Trouble Shooting|Trouble Shooting]]

-

for steps you can follow to track down the problem.

-

== Linux Install ==

-

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.

-

{{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.}}

-

The following files make up the Linux license server installation:

-

<ul>

-

; hlserver : This is the server application. It need not be run with any special privileges unless the PORT used (see below) is under 1027.

-

; 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.

-

; 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.

-

; hlserver.service : 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.

-

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

-

; .keys : This file holds the floating license keys.

-

</ul>

-

== 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:

-

<ul>

-

; 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.

-

</ul>

-

== Windows Install ==

-

Login as a user with

-

'''Administrator'''

-

privileges, and run the EXE file.

-

The following files make up the Windows license server installation:

-

<ul>

-

; hlserver.exe : This is the server application. It need not be run with any special privileges unless the PORT used (see below) is under 1027.

-

; 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.

-

; hlserver.ini : Edit this file to change the server start-up command line arguments.

-

; hlmanager.exe : This is the manager application. See "The Manager" chapter for details.

-

; keys.txt : This file holds the floating license keys.

-

</ul>

-{{:HLServer: Menu}} {{TOC}} To correctly install and run hlserver you should follow these steps:
-# Install the hlserver files. See below for OS specific instructions. <br><br>
-# 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. <br><br>
-# Put the keys provided into .keys (Linux/OS X) or keys.txt (Windows). See below for an explanation of the key strings. <br><br>
-# Start hlserver up. See the following chapter, [[HLServer: Running the Server|Running the Server]] for OS specific instructions. <br><br>
-# Pass on to your users the information in  [[HLServer: Application Config|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
-[[HLServer: Trouble Shooting|Trouble Shooting]]
-for steps you can follow to track down the problem.
-==  Linux Install ==
-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.
-{{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.}}
-The following files make up the Linux license server installation:
-<ul>
-; hlserver :  This is the server application. It need not be run with any special privileges unless the PORT used (see below) is under 1027.
-; 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.
-; 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.
-; hlserver.service : 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.
-; hlmanager :  This is the manager application. See "The Manager" chapter for details.
-; .keys :  This file holds the floating license keys.
-</ul>
-== 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:
-<ul>
-; 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.
-</ul>
-==  Windows Install ==
-Login as a user with
-'''Administrator'''
-privileges, and run the EXE file.
-The following files make up the Windows license server installation:
-<ul>
-; hlserver.exe :  This is the server application. It need not be run with any special privileges unless the PORT used (see below) is under 1027.
-; 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.
-; hlserver.ini :  Edit this file to change the server start-up command line arguments.
-; hlmanager.exe :  This is the manager application. See "The Manager" chapter for details.
-; keys.txt :  This file holds the floating license keys.
-</ul>

HLServer: Server Install

HLServer: Server Install

From Headus Docs

Current revision