HLServer: Server Install
From Headus Docs
|
If your users encounter any problems accessing the floating licenses, see Trouble Shooting for steps you can follow to track down the problem. Linux InstallTypically 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 hlserver.run.
The following files make up the Linux license server installation:
OS X InstallSelect 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-??????.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:
Windows InstallLogin as a user with Administrator privileges, and run the EXE file. The following files make up the Windows license server installation:
ConfigurationThe config file is used to control access to the server and licenses. The simplest config file looks like this: PORT 11668 LOG 1 ACC 0 IDLE 0 GROUP lan 192.168.0.* GROUP Manager root@lan PRODUCT cyslicev3 lan
The following shows a more complex example of a config file.
PORT 11668
LOG 1
ACC 1
IDLE 6
GROUP cg-lab 192.168.0.1-23
GROUP office fred,barney
GROUP offsite 112.56.22.{12-15,21}
GROUP Manager julie@office,jimbo@cg-lab,root@hlserver
PRODUCT cyslicev3 cg-lab,{phil,jill}@offsite
PRODUCT plyedit jimbo@cg-lab
Anyone currently logged into a cg-lab machine can request a cyslicev3 license, but only phil or jill can from the handful of offsite machines. Whenever jimbo is logged into a cg-lab machine, he can request a cyslicev3 or plyedit license as well as run the license manager. KeysFloating licenses, stored in the .keys or keys.txt file, look something like this: Products System Expire Num # uvlayoutv2 sysid=690ca1ab expire=101226 [000 4] 8MFP LCDY A0GZ 553N QQ6Z BLMB A1A6 GF1G # 6200 74QX SEPD GEC4 AK1W QJK8 3E5N 2LLF 345C JQX5 24SA # 6201 You might also have the older style license keys that look like this:
<- 21 hex numbers -> Product System Expire Ref# Num
#v2# 3a d6 ........ a9 42 # cysurf 690ca1ab never 0920 [001 3]
#v2# 5d da ........ 32 6a # cyslicev3 690ca1ab never 0921 [001 1]
#v2# 37 db ........ 71 5b # cyslicev3 690ca1ab 110216 0922 [002 1]
The Product names go into the config products section, System is the sysid of the license server, Expire is when each floating license runs out, Ref# is a database reference number used by the issuer, and Num is the sequence id and number of floating licenses in that key. In the first example there are 4 uvlayoutv2 floating licenses. In the second example above, there is 1 cyslicev3 and 3 cysurf floating licenses that will never expire, and 1 additional cyslicev3 license that runs out on the 16th of Feb, 2011. Even though there are multiple cyslicev3 keys, you would normally only have one cyslicev3 access list in the config products section. PartitioningRequires hlserver v1.15+. In the examples shown to this point, all licenses for a particular product are available to all the users listed on the PRODUCT line. For example, in the following config file all of the uvlayoutv2 licenses are available to everyone from cg-lab and offsite:
GROUP cg-lab 192.168.0.1-23
GROUP offsite 112.56.22.{12-15,21-*}
PRODUCT uvlayoutv2 cg-lab,offsite
With partitioning, you can allocate a different number of licenses to the different groups. In the following example, 10 licenses in total are available (this is determined by your license keys), but 7 have been reserved for users from cg-lab, and 3 for offsite users: PRODUCT uvlayoutv2 cg-lab[7],offsite[3] The number inside the square brackets defines the number of licenses allocated to that group. In the above example, if a fourth offsite user tries to grab a license, they will be denied access, even if none of the cg-lab licenses have been used. You can also choose to restrict some groups but not others. In the following example, offsite users are restricted to 3 licenses maximum, but cg-lab users could grab all of the 10 licenses if they are free. PRODUCT uvlayoutv2 cg-lab,offsite[3] Another way to define the above partitioning is via the use of negative allocations. In the following example, offsite users can have all but 7 of them, or in other words, cg-lab users are guaranteed to have at least 7 licenses: PRODUCT uvlayoutv2 cg-lab,offsite[-7] By License Key GroupsYou can also partition according to license key groups. In the following keys file there are two groups, a pair of permanent keys with an ID of 000, and 4 temp keys with an ID of 001. You can find this information inside the square brackets: # hlserver,uvlayoutv2 sysid=5b83f8dd expire=perm [000 2] R6LZ PF0Q HZ65 8H55 463T E69W 07WF 5R9C # 10395 NTRC 4H24 5R9C 1KZF RJ0Y C0CW 8H55 G1SE 76GZ F6AA # 10396 # uvlayoutv2 sysid=5b83f8dd expire=100602 [001 4] F913 2LLB 71WC 71FG PF0Q XYPL WAYH HCTQ D7PA 6RAA # 10398 To allocated each of the key groups to different groups within the config file, create multiple PRODUCT lines and append the key group ID to the product name, separated by a period character. In the following example, users from cg-lab are allocated the 2 permanent keys, and users from offsite get the 4 temporary keys: PRODUCT uvlayoutv2.000 cg-lab PRODUCT uvlayoutv2.001 offsite You can combine all partitioning methods if you wish. In the following example, users from cg-lab are guaranteed their 2 permanent key, but can also grab up to 2 of the temporary keys if they are free. PRODUCT uvlayoutv2.000 cg-lab PRODUCT uvlayoutv2.001 offsite,cg-lab[2] By Client Side GroupsRequires hlserver v1.16+. In some environments, such as those using DHCP to assign IPs, trying to partition with a static list of IP addresses is not feasible. HEADUS_HLGROUP |
