% man licensing
licensing(5) Daylight Languages and Formats licensing(5)
NAME
licensing - Daylight License Processing and Options
DESCRIPTION
Usage of Daylight programs, servers, toolkits, and databases
is controlled through the Daylight License Manager. The
Daylight License Manager reads licenses from multiple
sources (files, web servers) and then, based on the content
of the license sources, allows or denys access to Daylight
programs and features.
LICENSE OPTIONS:
License processing is controlled by the following environ-
ment variables (or options for programs). They are:
DY_LICENSEDATA
This environment variable refers to a file which is
expected to contain one or more concatenated license
sections. The program option to use is -LICENSEDATA.
DY_LICENSEDIR
This environment variable refers to a directory which
is expected to contain one or more files. Every file
in the directory is read as a license. Each license
file in the directory may have multiple sections. The
program option to use is -LICENSEDIR.
DY_DALI_SERVER
This is the full URL of a web source for licenses. The
license server performs an HTTP/1.0 GET request of that
website, and processes the body of the response as
license data. If the body is valid, the local client
program will attempt to cache the license data (eg. the
body of the response) in the file /tmp/dy_license.dat.
The program option to use is -DALI_SERVER.
DY_DALI_AUTHORITY
This is the full URL of a web source for licenses. The
license server performs an HTTP/1.0 GET request of that
website, and processes the body of the response as
license data. The authority data is not cached. The
program option to use is -DALI_AUTHORITY.
DY_DALI_PROXY
The hostname and optional port (hostname:port) of an
HTTP proxy server which will be used for both the
DY_DALI_SERVER and DY_DALI_AUTHORITY HTTP requests. If
the proxy port is not specified, 80 is used. The pro-
gram option to use is -DALI_PROXY.
DY_DALI_TOMS
The timeout, in milliseconds, used for the network
request. If a response is not received from the HTTP
server before this timeout the request fails. The pro-
gram option to use is -DALI_TOMS.
Examples include:
$ export DY_LICENSEDATA=$DY_ROOT/etc/dy_license.dat
$ export DY_LICENSEDIR=/usr/local/daylight/licenses/
$ export DY_DALI_SERVER=myhost:9000
$ export DY_DALI_AUTHORITY=www.daylight.com:9000
$ export DY_DALI_PROXY=myhost:8080
$ export DY_DALI_PROXY=myhost (uses port 80)
$ export DY_DALI_TOMS=1000
$ testlicense -LICENSEDIR /usr/local/daylight/lics/
LICENSE PROCESSING:
The license sources are checked in a fixed order. Once the
requested feature license is found in one of the license
sources, checking stops. Local sources are checked first,
network sources last. This means that if the feature is
licensed based on a local license the network requests are
not generated, even if the DALI options are set.
The order of processing is as follows:
1. If set, the file referred to by DY_LICENSEDATA is
checked.
2. If set, the files in the directory referred to by
DY_LICENSEDIR are
checked.
3. Several default locations are checked and the files are
processed
if present. These are:
/usr/local/daylight/dy_license.dat and
/tmp/dy_license.dat (the DALI cache).
4. If set, the data returned from DY_DALI_SERVER is pro-
cessed.
5. If set, the data returned from DY_DALI_AUTHORITY is pro-
cessed.
Again, at any point if the needed feature is found to be
valid in one of the license sources then processing stops
and returns successfully.
CHECKING LICENSES / ERRORS:
The program testlicense(1) is the main tool for debugging
license issues and problems. Using the '-v' option gives
details about each of the five license-checking steps,
including the source used, the license data found, and
whether or not the license data was valid and why. For any
license-related problem, please include the output from
'testlicense -v' in your support request to Daylight at
support@daylight.com.
SEE ALSO
testlicense(1), options(5)
Daylight v4.81 Release Date: 20 Dec 2002 3