Daylight v4.9
Release Date: 1 February 2008

Name

licensing - Daylight License Processing and Options

Description

Usage of Daylight programs, servers, toolkits, web services, 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 denies access to Daylight programs and features.

STANDARD LICENSE OPTIONS:

Standard license processing is controlled by the following environment 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 (e.g. 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 program 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 program option to use is -DALI_TOMS.

FLEXNET LICENSE OPTIONS:

Daylight supports Macrovision's FLEXnet Served License Component Model.

Environment variables allow client applications to access the FLEXnet license server and license file. Upon connection to a valid license server, a .flexlmrc file is written in the Daylight user's home directory. This file will augment the FLEXnet environment variables:

DAYLIGHT_LICENSE_FILE

This is the Daylight's vendor-specific FLEXnet environment variable. It may be set to the name of the license server (@servername) , a TCP/IP port and license server (port@servername), or a path to a directory which contains license files.
LM_LICENSE_FILE
This is Macrovision's general-purpose FLEXnet environment variable. It may be set to the name of the license server (@servername) , a TCP/IP port and license server (port@servername), or a path to a directory which contains license files.
DY_FLEXQUEUE
If this environment variable is set to any string the client will wait till the unavailable license FEATURE is checked back in before proceeding. If the variable is not set and the requested license is not available, the client will fail immediately.

Examples

$ export DY_LICENSEDATA=/usr/local/daylight/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
$ export DAYLIGHT_LICENSE_FILE=@myhost (uses a default port)
$ export LM_LICENSE_FILE=40000@myhost (uses port 40000)
$ export LM_LICENSE_FILE=/usr/local/daylight/licenses/flexnet
$ export DY_FLEXQUEUE=TRUE
$ testlicense -LICENSEDIR /usr/local/daylight/licenses

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 or FLEXnet 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 processed.

5. If set, the data returned from DY_DALI_AUTHORITY is processed.

6. All of the FLEXnet resources ( including DAYLIGHT_LICENSE_FILE, LM_LICENSE_FILE, /usr/local/daylight/daylight.lic and $HOME/.flexlmrc) are merged into the FLEXnet License Search Path which is consulted last.

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.

Related Topics

testlicense(1) options(5)