Sentinel License Manager (SLM) v7.2

Machine Locking & License key Installation -- Quick Instructions

	This document explains how to generate machine locking information for a license key for EMA software that uses Rainbow Technologies' Sentinel License Manager v7.2; and how to install the license key in the correct location once you receive it.

HOW DO I KNOW IF MY EMA SOFTWARE INSTALLATION USES SENTINELLM/HOW DO I KNOW IF IT IS USING V7.2?

	Using a command prompt (on either UNIX or Windows), go to the "lic" subdirectory or folder of the EMA software installation.  Run the command "lsver" to display the version information:

windows prompt> .\lsver

or

unix prompt% ./lsver

	If there is no "lic" subdirectory or folder or no command named "lsver", then your software installation may be using some other licensing system.  Contact EMA for more information.  Otherwise, proceed with the remainder of this document.

MACHINE LOCKING INFORMATION

	License keys are locked to some "machine locking information" which is unique to the machine you are running the software on (in the case of a standalone license key), or the machine you are running the license server on (in the case of a network/floating license key).

GENERATING MACHINE LOCKING INFORMATION: USE "echoid"

	Machine locking information is generated by running a command called "echoid", which is part of the set of software licensing files included in an EMA software installation.

RUNNING "echoid": Windows

	Use any of the following methods to run "echoid" on Windows:

1.	After installation of the EMA software product, there may be a shortcut on your Start Menu, something like

Start MenuProgramsEMA<ema software product>Show Machine ID (for licensing)

If this shortcut exists, you can click on it to display the locking codess for the machine.  ("<ema software product>" may be something like "EMA3D v3.0.1" or "MHarness v2.2" or something else, depending on the product and version installed.)

2. Using Windows Explorer, navigate to the "lic" folder of the EMA software installation, find the file "echoid.exe", and double-click on it to display the locking codes.

3.  Using a Windows Command Prompt, change dir to the "lic" folder of the EMA software installation and run the command "echoid.exe":

windows prompt> .\echoid.exe

RUNNING "echoid": UNIX

	To run "echoid" on unix, navigate to the "lic" subdirectory of the EMA software installation; i.e., make the "lic" directory your current working directory.  Then run the command*:

unix prompt% ./echoid

*NOTE for UNIX users:  Do not confuse "echoid" with any native UNIX command!  "echoid" is a command that is part of the Rainbow Sentinel License Manager license key system used with EMA software.  It generates machine locking information based on a proprietary algorithm, implemented by Rainbow in its license key system, which may or may not use the "hostid" or "idprom" of the machine as one of its inputs.

NOTE FOR RUNNING "echoid" FROM A COMMAND PROMPT (both Windows and UNIX):

NOTE: When running "echoid"/"echoid.exe" from a command prompt (either windows or UNIX), make sure to change dir to the "lic" folder of the software installation before running the command!  If you run the command without making the "lic" folder your current working directory (for example by using its absolute path name), incorrect locking codes will be generated.  This is because the "lic" folder contains a file called "echoid.dat" which contains data that tells "echoid"/"echoid.exe" how to generate the locking information.  "echoid"/"echoid.exe" always looks only in the current working directory for this file; if "echoid.dat" is not found, default data is used, which generates locking codes that are incorrect for an EMA software installation.

TRANSMIT THE LOCKING INFORMATION TO RECEIVE A KEY FILE

	Once you have generated the machine locking information, transmit the "lock codes" to EMA.  EMA will generate one or more license keys for the software using those locking codes.  The license key file(s) will usually be named "lservrc" or something similar.  Whatever the name of the file when you receive it, it should always be re-named "lservrc" upon receipt, and placed in the correct location.

LICENSE KEY FILE INSTALLATION - STANDALONE LICENSE KEY

	For a standalone key file, the key file should be placed in the application directory or folder.  This will typically be a folder or directory called "bin" on either a Windows or UNIX software installation.  This is the same directory or folder containing the main application executable, such as "ema3d", "ema3d.exe", "mharness", "mharness.exe", etc.  The application looks in the same directory where it lives for the license key file when it is run.

LICENSE KEY FILE INSTALLATION - NETWORK/FLOATING LICENSE KEY

	For a network/floating license key, the key file should be placed in the license server directory or folder.  This will typically be a folder or directory called "lic" on a Windows or UNIX software installation.  This is the same directory or folder containing the license server executable, usually called "lserv" or "lservnt.exe".  The license server executable looks in the same directory where it lives for the license key file when it is started*.

	*NOTE to UNIX users: it is usually recommended to specify the license key file with a full pathname in a license server startup script; see the software Installation Guide for more information.

	The license server will typically have to be stopped and re-started after installation of a license key file, to pick up the new keys.

LICENSE KEY FILE FORMAT

	The format of a license key files is important in order to be correctly read by the application (standalone key) or license server (network/floating key).  License keys sent by EMA should be in the correct format when they are sent.  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.

	Symptoms of trouble with the license key file format would be that the application or license server behaves as if there is no license installed even though all aspects of the license key file such as machine locking information, expiration date, and software product and version all seem correct.

MORE INFORMATION

	This read-me file is a very brief quick reference for generating machine locking information and installing a license key file for EMA software using SentinelLM 7.2.  For complete information about setting up licensing for EMA software, see the software Installation Guide.  For exhaustive information about the SentinelLM license key management system (including many more features of the system than are used with EMA software), see the SentinelLM System Administrator's Guide.