Sentinel License Manager (SLM) v7.2

    License Server Installation/Startup -- Quick Instructions

			 for UNIX

	This documents explains how to start the SentinelLM 
license server for managing licenses for EMA software.  For
information on installing a standalone license key (rather
than a server key), see the software Installation Guide.

INSTALLATION

	The license server files are installed by the installation
script, in the following subdirectory of the EMA software
installation directory:

	<install_dir>/<application_dir>/lic

Here, <install_dir> is the directory where the application was
installed (for example, could be something like "/opt/emasoft").
<application_dir> is the name of the top-level directory
containing the installation files.  It could be something
like "ema3d300" or "mharness220", for example, depending on
which software application you have.

	The license server executable file is "lserv".  It is
recommended that its permissions be set so that only authorized
users may execute the license server.

STARTUP

	The license server runs as a background process.  To
launch the license server manually, just invoke the executable
file by name.  Use the "-s" option to specify the license
key file.  In the example below, "lservrc" is a license key
file which has been obtained from EMA, Inc. (see LICENSE
KEY FILE, below).  Also in the example below, the directory
pathname is an example only and could vary depending on your
installation and software product(s) purchased.

example (for starting the server manually from a command
prompt):

unix prompt% cd /opt/emasoft/ema3d300/lic
unix prompt% ./lserv -s ./lservrc

	To make the license server start whenever the
operating system starts, a command line to launch the license
server executable may be placed in an appropriate system startup
script.  In this case, use full pathnames for the license
server and the license key file.

example (for starting the server from an operating system
startup script):

/opt/emasoft/ema3d300/lic/lserv -s /opt/emasoft/ema3d300/lic/lservrc

	See your system documentation or UNIX documentation
for more information about system startup scripts.

LICENSE KEY FILE

	You will be issued one or more license keys to activate
the EMA software you have purchased.  Each license key is an
alphanumeric string, usually e-mailed as ASCII text.  All of
the license keys for the various products must be placed into a
single text file which the license server reads upon startup.
The file should be named "lservrc" and should be placed in the
same directory as the license server executable (the "lic"
subdirectory of the installation).  (In the examples above,
this was "/opt/emasoft/ema3d300/lic".)

LICENSE KEY FILE FORMAT

	License key files sent by EMA should already be in the
correct format.  However, if there is trouble, the following
are the important points to check regarding the format of
the license key file.

- Each line in the key file consists of a license key code,
optionally followed by a comment.  A '#' marks the
beginning of a comment.

- Every line in the key file must begin with a license key code
and not some other text, not even a comment.

- There should be exactly one license key code per line in the
file.

LICENSE KEY FILE PERMISSIONS

	The permissions of the license key file should be set
 so that the lserv process has permission to read it.

MACHINE LOCKING CODES

	In order to obtain a license for the software you have
purchased, you will need to obtain some machine locking codes
for the machine on which the license server will run.  This is
done with the utility "echoid" which is part of the software
delivery and lives in the same directory as the license server.
To generate the fingerprinting information, change dir to that
subdirectory, and invoke the utility by name.  Transmit the
resulting "Lock Codes" to EMA, and EMA will generate one or
more licenses for the appropriate product(s) based on the
locking code(s).
	Be sure to run the utility "echoid" on the machine
on which the license server will be running.  This could be
a different machine from the one(s) the software application(s)
will be used on.

example:

unix prompt% cd /opt/emasoft/ema3d300/lic
unix prompt% ./echoid

NOTE about "echoid":

	In order to generate the correct locking codes, it
is important that you first change dir to the "lic"
subdirectory where the command "echoid" lives!  There is a
file "echoid.dat" that also lives in that directory.  This
file tells "echoid" how to generate the locking codes.
"echoid" always looks in the current working directory for
this file.  Running "echoid" from some other directory will
result in incorrect locking codes.  (As an alternative, the
file "echoid.dat" may be copied to the current working
directory before the "echoid" command is run.)

MORE INFORMATION

	This read-me file is a very brief quick-start guide.
For more complete information about the licensing system
used with EMA software, see the software Installation Guide.