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

Chapter 3 – Planning Application Protection and Licensing Strategy
Contents Glossary Index Troubleshooting
Protecting For Stand-alone Environments
When protecting an application for stand-alone environment, you must
note the following points:
Distribute a stand-alone key with your protected application.
The Sentinel Keys Server is not required by stand-alone applications.
68 Sentinel Hardware Keys Developer’s Guide
You must specify stand-alone access mode using the options described
below:
For API-protected applications, call the SFNTGetLicense API
function with the SP_STANDALONE_MODE flag.
For CodeCover/Quick CodeCover-protected applications, select
STANDALONE from the Access mode drop-down box.
The network API functions, like SFNTGetServerInfo will return error.
Note: The terminal clients can access both the network and stand-alone Sentinel
Keys in a network. To allow stand-alone keys (Sentinel S and ST) access, set
the SP_ENABLE_TERMINAL_CLIENT flag in the SFNTGetLicense API function.
The network keys (Sentinel SN and SNT) can be accessed without any
such setting.
Protecting for Network Environments
Distribute a network key with your protected application.
Specify network access mode using the following options:
For API-protected applications, call the SFNTGetLicense API
function with the SP_NETWORK_MODE flag.
For CodeCover/Quick CodeCover-protected applications, select
NETWORK from the Access mode drop-down box.
When network mode is set, the application looks for a Sentinel Key
with a license in the following sequence. If the required Sentinel
Key is not found or a license is not available, an error is returned:
1.The host specified in the SFNTSetContactServer API function.