Sentinel Hardware Keys Developer's Guide - Customer Connection ...

Chapter 4 – Protecting Applications Using CodeCover
Contents Glossary Index Troubleshooting
Note: The above binaries should be copied to the folder where the files CMD-
Shell.exe, and ShellCommandLine.jar reside.
Required Installations:
92 Sentinel Hardware Keys Developer’s Guide
Sentinel System Driver 7.5.1: Sentinel System Driver version
7.5.1, the Device Driver for the hardware keys should be installed
on the system so as to detect the keys.
JRE version 1.6.0: Apart from the above files, please make sure to
install JRE version 1.6.0 on your system so as to launch the
Command-Line CodeCover utility.
Attached Key Specifications: A Developer - User key pair of same
Developer ID, should be attached to the system. If the utility is being
used to protect applications at the customer’s location, then only a
Custom CodeCover key is attached.
File to be Generated: Sentinel keys License template file (.ltm file),
created using Toolkit and programmed using the Developer - User key
pair.
Default path of .ltm file on a Windows system is: :\Documents and Settings\\My
Documents\Sentinel Keys 1.3\My License
Templates\LICENSE_NAME_FOLDER\LICENSE_NAME.ltm.
Note: You may also use a strategy created (and saved as a License Template) in
the Quick CodeCover screen of the Toolkit.
Using the Command-Line CodeCover Utility
This section provides details on using the Command-Line CodeCover Utility.
1. Attach the hardware key(s) as specified below:
For building protection strategy or programming Sentinel
Keys: Attach the Sentinel Hardware Key and the Developer key to an
available USB port on your system. The developer ID of the Sentinel