Refer to the BX PRO 5.0 Installation Notes for a detailed description of the license manager installation script.
When you run the
setup script, the Builder Xcessory automatically starts the license manager installation script. To start the license manager script manually, enter the following on the command line:
license.dat text file must be accessible to the Builder Xcessory license daemons, and must be available on every system that will run the Builder Xcessory, or act as a license server . We recommend that you NFS mount the directory in
/usr/local/flexlm/licenses , which will then be accessible from any machine on your network.
Note: We do not recommend copying
datinto the local directory of every machine because this makes updating the file difficult. However, if you choose to copy the file into the local directory and want to use a directory other than
/usr/local/flexlm/licenses, you must establish a symbolic link to
licensesor use the
LM_LICENSE_FILEenvironment variable, as shown above.
For additional information, see license.dat (5) .
The installation script uses your responses to the installation prompts and generates the
dat text file. We recommend that you review this file to verify the information. The file is divided into the following three types of code:
- The server lines contain the host name, host id, and TCP/IP service port for each server. You can edit the system name and port data as you change your system configuration. However , if you add, delete, or change a host id, your activation key will become invalid and you will be unable to obtain a license.
Important: If you add, delete, or change a host id, you must contact ICS with the updated information to get a new activation key.
- The daemon lines contain the location at which your vendor daemons will be found. You may edit this data to reflect changes in your system.
The feature lines contain information for the version of the Builder Xcessory that you are licensed to run. Each feature has a line of data that includes the word
FEATURE, the feature name (for example, Builder Xcessory), the vendor daemon (
ICSBX), the version number, the expiration date, the number of licenses that may be run simultaneously, the twenty character activation key, a string describing the feature, and a string which reads "
Warning: Editing the information in the feature lines invalidates your activation key.