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

Chapter 3 – Planning Application Protection and Licensing Strategy
Contents Glossary Index Troubleshooting
However, note that SFNTSetContactServer has higher priority over
the client-side configuration file.
About Client-side Configuration File
66 Sentinel Hardware Keys Developer’s Guide
The client-side configuration file is meant for your customers—the protected
application users. By default, this configuration file exists, by the
name sntlconfig.xml, in the same directory where your protected application
is installed. However, you can specify a different name and path for the configuration
file by using either the SFNTSetConfigFile Business Layer API or
the Customize Sentinel configuration file path and name option
available in the Toolkit during CodeCover protection.
The protected application users can set the parameters (tags) described
below:
Protocol
Sets the network protocol for client-server communication. If a protocol is
specified here, the same must be set in the server configuration file.
Tag Values
For Windows/Linux/Macintosh, the following protocols (tags) are
supported.
TCP/IPv4 (SP_TCP_PROTOCOL) - The default protocol supported.
TCP/IPv6 5 (SP_TCP6_PROTOCOL)
ContactServer
Sets the Sentinel Keys Server host (the system where the Sentinel Key is
attached). It can be set across LAN and WAN.
Multiple entries (up to 100) can be specified, separated using a new line
character (the Enter key). The license will be searched for in the order mentioned
(top to bottom).
5.Supported only on the same subnet