mv serv­er_­da­ta serv­er_­da­ta.old 

Copy the new “serv­er_­da­ta” li­cense file ob­tained from LSTC in­to the cur­rent When the serv­er is restart­ed next, it will pick up the new li­cense file. Check the per­mis­sions and own­er­ship of this file in or­der to guar­an­tee that the li­cense serv­er will be able to read the new li­cense file. The best prac­tice is to match the per­mis­sions and own­er­ship of the old li­cense da­ta.

*** WARN­ING *** If there are any user-spec­i­fied lines in the pre­vi­ous li­cense file, then you must man­u­al­ly copy these lines in­to the new li­cense files. Such lines start with HOST:, HOST1:, HOST2:, HOST3:, PORT:, PORT1:, PORT2: and PORT3:.

UP­GRADE THE LI­CENSE SOFT­WARE (op­tion­al): We rec­om­mend that you up­grade the li­cense serv­er at the same time that you ob­tain a new li­cense file from LSTC. Re­gard­less of whether or not you up­grade the ex­ist­ing li­cense soft­ware, you must stop and restart the li­cense serv­er when­ev­er you ob­tain a new li­cense. If the serv­er is down for a few min­utes on­ly, then run­ning li­cens­es should not be lost in the process.

Af­ter down­load­ing the soft­ware archive which is ap­pro­pri­ate for you plat­form, move the archive in­to the cur­rent in­stal­la­tion di­rec­to­ry. In prepa­ra­tion for the up­grade, re­name the ex­ist­ing li­cense serv­er ex­e­cutable:

        mv lstc_­serv­er lstc_­serv­er.old 

Now un­pack the new soft­ware archive. For ex­am­ple,

        gun­zip LSTC_­Li­cense­M­an­ag­er_­77918_­hp8000_­11.tgz         tar xvf LSTC_­Li­cense­M­an­ag­er_­77918_­hp8000_­11.tar  

Check the per­mis­sions on the LSTC Li­cense Man­ag­er ex­e­cutable “lstc_­serv­er” in or­der to en­sure that the serv­er will start prop­er­ly.

STOP AND RESTART THE SERV­ER: You will now have a new li­cense file “serv­er_­da­ta” and, op­tion­al­ly, a new serv­er ex­e­cutable “lstc_­serv­er”.

If there are start and kill scripts “serv­er_­start” and “serv­er_­kill”in the cur­rent work­ing di­rec­to­ry, then ex­e­cute them in or­der

        ./­serv­er_­kill ; ./­serv­er_­start 

The new serv­er should now be run­ning, which you can ver­i­fy us­ing

        ./­lstc_­qrun -q 

If this does not work, then check “serv­er_­da­ta” for any non-stan­dard port num­ber “PORT:” spec, and con­nect di­rect­ly to this port

        ./­lstc_­qrun -s port@lo­cal­host -q 

The out­put from this com­mand will in­clude the ver­sion num­ber of the serv­er. If this serv­er num­ber does not match the ver­sion num­ber on the archive you just down­loaded, then the serv­er_­kill script failed. In that case, then pro­ceed to the next case, ig­nor­ing the scripts “serv­er_­start” and “serv­er_­kill”.

If you do not have “serv­er_­start” and “serv­er_­kill” scripts in the cur­rent work­ing di­rec­to­ry,find the PID of the “lstc_­serv­er” process, and use that PID to kill the process man­u­al­ly

        ps -lef | grep lstc_­serv­er         kill -TERM PID 

Then start the process man­u­al­ly

    SYN­TAX:  ./­lstc_­serv­er [-l job_­log_­file_­name] [-a|-n|-N] [-q]         where the com­mand line op­tions are           -l file : log job re­quest/­com­ple­tion/­er­ror/­war­rn­ing to 'file'                -a : Al­low pro­grams to be killed by any­one.                -n : Al­low pro­grams to be killed based on user name alone (de­fault).                -N : Re­quire user/­host to match in or­der to kill jobs.                -q : Do not al­low pro­grams to be queued when there are                     no avail­able li­cens­es. 

The start op­tions will be saved to a new script “serv­er_­start” so that you may restart the serv­er us­ing the “serv­er_­start” script.

VER­I­FY THE NEW LI­CENS­ES:You should be able to con­tact the li­cense serv­er di­rect­ly us­ing

        ./­lstc_­qrun -r 

If this com­mand fails, then look for any non-stan­dard port num­bers for your serv­er which are spec­i­fied in “serv­er_­da­ta”, and try to con­nect to the port di­rect­ly

        ./­lstc_­qrun -s lo­cal­host -r    or   ./­lstc_­qrun -s port@lo­cal­host 

*** WARN­ING *** If the new serv­er fails to start for some rea­son, then re­store the old­er serv­er, start the old serv­er, and con­tact LSTC.

        mv lstc_­serv­er lstc_­serv­er.new         cp lstc_­serv­er.old lstc_­serv­er         ./­lstc_­serv­er [-l job_­log_­file_­name] [-a|-n|-N]