Contents - Index
As you can see, part of the licensing process involves creating a Licence Policy. The Licence Policy defines exactly how the user will be able to operate your Sheriff-protected application, for example whether use of the application will be restricted to a particular machine or whether the licence will expire after a certain number days.
Please note the following important points:
Software runs for a specified number of days (E.g. 21 days).
Licence - Unit Meter
Each chargeable event is known as a 'unit' (E.g. an execution of the software, viewing/printing a document, or any specified period of time). Note that any additional days/units you will overwrite those already issued. E.g. if you first issue a licence key for 180 days and during this time the user requests that the licence be extended to a total period of one year, you must take into account the units already consumed when issuing the new licence. This is not a problem because you can verify the user's Status Code prior to issuing the new licence key.
Licence - Expiry Date
The licence will expire on the selected date.
Licence - Concurrent User Limit
Limits the maximum number of concurrent network users. If this box is not checked then the number of concurrent users will be unlimited. If you check the box and the limit is set to "1" you have the option of restricting usage to a single machine i.e. the licence will be tied to the machine on which it is installed and cannot be shared over a network (see Standalone Licence Key below).
Note that unless the Disable Export option is "on" (see below) licence keys up to the maximum number of permitted concurrent users will be exportable to other machines and the number of concurrent users permitted on the source machine will be decremented accordingly (see the Sheriff Administrator help for further details).
Licence - Feature Access Key
Software can be licensed as shareware, demo software or buy-as-you-need.
Licence - Extend Existing Licence
Licence - Extend Existing Licence
Enables publishers to extend rather than replace an existing licence, so that the client's existing licence policy is not overwritten when the new Licence Key is issued. This is used when the clients' licence is controlled by day or unit metering and the publisher wishes to incrementally add new days/units to the existing licence.
Options - Reusable Key
The user should keep a record of the licence key number. Provided you enable the 'Reusable Key' option when defining the Licence Policy, the user will be able to regenerate the key on the original hardware using the Licence Administrator (this can be done if, for example, the licence file is accidentally deleted). The 'Reusable Key' option can only be enabled if the key is to last indefinitely (not metered). Note that even a reusable key cannot be restored if the user's hard disk has been reformatted.
Options - Reusable Reference Code
This option is only available when Expiry Date metering has been selected. It is used when you want to be able to extend the date on which the licence will expire without first contacting the user for a new Reference Code. In this way you can at any time extend the period for which your application will run simply by generating a new licence key for the user.
Options - Disable Export
You can disable the user's ability to export a licence key to another machine, so locking the licence to one machine only.
You can disable the user's ability to move a licence to another machine using the Move function. This prevents a user from permanently relocating a licence to another machine E.g. when they upgrade their hardware.
Options - Standalone Licence Key
When the Concurrent User Limit is set to "1", checking the Standalone Licence Key box ensures that the protected application can only execute on the machine on which it is installed i.e. the application is not available over a network and the licence file must reside on the same machine as the application.
You can add any comments to the log file (SlsGen.log), an ASCII text
file which automatically keeps track of all transactions in the Licence Generator.
NB. The publisher's data may be saved or retrieved by using the appropriate Sheriff API functions. The sole function of the Publisher Data edit box in the Sheriff Licence Generator is to allow the publisher's data to be logged together with the details of the Licence Key. In other words, the publisher's data entered into the License Key Generator does not become part of the Licence Key, it is only logged in "slsgen.log". To use the publisher data you have to call the API functionSls_SetPublisherData