#Flexlm license.dat file license#

This is the Solstice AutoClient 2.1 license daemon startup script. It is located in the /usr/opt/SUNWadm directory, and it is started automatically at boot time by the S86ac_licensed script, or it can be started by Host Manager when an AutoClient is first added to the server. This is the Solstice AutoClient 2.1 license daemon.

#Flexlm license.dat file software#

Licensing is managed on the AutoClient server by the following software components. This occurs when an AutoClient is first added to the server. Host Manager automatically installs the AutoClient server with the supporting software required by the license process described in Figure 4-1. Since the Solstice AutoClient 2.1 product does not deny service if a license is unavailable, the functionality provided by the AutoClient server to the AutoClients it supports is unaffected. This message is also written to the message file stored in the /var/adm directory on the AutoClient server. If the AutoClient server is not configured to contact the license server and request a license, a message similar to the following is displayed.Дec 22 13:34:53 server-name License Error : Cannot find license fileДec 22 13:34:53 server-name which contains the featureДec 22 13:34:53 server-name Cannot find license file (-1,73:2) No such file or directoryДec 22 13:34:53 server-name ac_licensed: Дec 22 13:34:53 server-name The product has not been installedДec 22 13:34:54 server-name Cannot find license file (-1,73:2) No such file or directoryДec 22 13:34:53 server-name ac_licensed: There are noДec 22 13:34:54 server-name /opt/SUNWadm/license_dir/sunpro.lic,1Дec 22 13:34:53 server-name ac_licensed: license refused Figure 4-1 The Solstice AutoClient 2.1 License Process The license server receives the request to provide a license for an AutoClient from the AutoClient server, and it grants or denies this request.ДЇigure 4-1 describes the events that cause the AutoClient server to request a license.

It obtains this information from the bootparams database. The AutoClient server requests a license for each AutoClient it is configured to support. When an AutoClient is added to the AutoClient server Solstice AutoClient 2.1 product licensing entails the following system components.ДЄ license request is generated by the AutoClient server in the following cases: Solstice AutoClient 2.1 License Components An AutoClient can function without licensing. Solstice AutoClient 2.1 licensing does not deny service. Solstice AutoClient 2.1 uses the latest Globetrotter FLEXlm TM licensing packages to make licensing as easy as possible. Have configured the application to search local trusted storage first and then look for license files as previously described.When you add an AutoClient to a server using Host Manager, a license, if one is available, is automatically checked out by the server. When licenses are held in trusted storage on the same machine as the FleењЋnabled application, normally the publisher will

On UNIX-/usr/local/flexlm/licenses/license.dat.

License, then the following default locations are searched: When the environment variables are not set and the FleењЋnabled application does not specify the location of the Any FEATURE and INCREMENT lines entries after the USE_SERVER lineД¤. The license server specified in the SERVER line. When any license file specified in a license search path contains a USE_SERVER line, then a license is requested from The items in a license search path set in the LM_LICENSE_FILE environment variable are searched in order.ДЈ. The license search path set in this environment variable are searched in order.Дў. When the VENDOR_LICENSE_FILE environment variable has been set for the publisher of the application, then items in Whenever we run 'lmpath', it will show the path set for vendor daemon as well as the LM_LICENSE_FILE path set.ДЄ FleењЋnabled application looks for a license file as follows:ДЎ. VENDOR_LICENSE_FILE and other is the global one i.e. FNP has 2 different environment variables to search the license file.