A FLEXlm binary distribution kit consists of a single directory which contains all the libraries, include files, and programs. To install FLEXlm, you will create a directory for the kit, read the distribution media, then run the FLEXlm installation program.

Appendix A, “Distribution Kit Contents,” lists the contents of the binary distribution kit.

There are two installation scripts on the distribution kit: INSTALL and CONFIG_DAEMON. INSTALL is used when first installing the kit. CONFIG_DAEMON is used to configure and build your vendor daemon, either when running the initial installation or any time later.

INSTALL will ranlib the libraries and ask if you want to continue and build your daemon. If you reply “y”, the CONFIG_DAEMON script will be run. CONFIG_DAEMON will prompt you for the parameters associated with your vendor daemon (encryption seeds, vendor keys, and other parameters). CONFIG_DAEMON then edits all the appropriate files (makefile, lm_code.h, and ls_vendor.c). In addition, CONFIG_DAEMON will create the file “daemon.dat”, which contains a log of the options selected, for your review.

You can manually edit ls_vendor.c, lm_code.h and the makefile, in place of running CONFIG_DAEMON. (This is required on VMS and Windows NT systems, where CONFIG_DAEMON is not supported).

A FLEXlm distribution kit consists of a single directory which contains all the libraries, include files, and programs. To install FLEXlm, you will create a directory for the kit, read the distribution media, then run the FLEXlm installation program.

Globetrotter Software ships FLEXlm VMS kits on CD and on tape in UNIX tar format.

$ mount/over=id/media=cdrom dka400:

$ set def [xxx]
$ copy dka400:[vms.v_4]vax_v6.mft []
$ copy dka400:[vms.mftu]mftu.com []
$ set file mftu.com/attributes=(rfm:stmlf,rat:cr)
$ set file vax_v6.mft/attributes=(rfm:stmlf,rat:cr)
$ @mftu
$ @mftumake
$ mftu :== $disk:[xxx]mftu
$ mftu
MFTU> decode vax_v6.mft

On Windows systems, this version of FLEXlm supports only the client library. Both 16 bit and 32 bit Windows applications are supported. FLEXlm supports the 32 bit Windows applications through its NT offering, which contains the 32 bit client library as a WIN32s DLL. To install FLEXlm 16 bit client library for Windows on to your C: drive from A:, for example, follow the following steps: (Note: if the destination directory is not C:\lmgr, you will need to change some FLEXlm sample makefiles manually to reflect this difference).

A pre-compiled wintest.exe is also included in \lmgr\bin directory for your reference.

Both client and server are supported on Windows NT. The Microsoft C/C++ compiler is required to build your customized vendor daemon. Your client application can be written in any language that can interact with the FLEXlm client DLL lmgr32.dll, which is a standard Windows NT 32 bit mode DLL. To install FLEXlm for Windows NT systems, follow the procedure below:

A FLEXlm source distribution kit consists of a single directory which contains subdirectories for the client library, include files, and both license and vendor daemons. The BINARY_KIT script will produce a binary kit identical to the binary distribution in the subdirectory arch_os. arch is the machine architecture and os is the operating system version, as specified in the BINARY_KIT command. For example, arch could be one of sun4, hp700, vax, apollo, etc., and os could be u4 (for SunOS4). To install the source kit, you will create a directory to hold it, read the distribution media, then perform the build, which will result in a binary kit for the target platform.

It is important to use the correct arch_os value when running BINARY_KIT, since the BINARY_KIT script may change make parameters depending on the machine architecture.

The gplatargs script in the utils directory is used to determine architecture specific flags. gplatform in the utils directory is also used to determine arch_os. Both gplatform and gplatargs may require modification for new platforms.

Appendix A, “Distribution Kit Contents,” lists the contents of the source distribution kit.

This example illustrates the use of INSTALL to complete binary kit installation for a sun4, sunOS4 kit. Data you enter is typed in bold.

% cd lmgr/machind
%  INSTALL
Flexible License Manager binary kit installation
Copyright (C) 1988 - 1994 Globetrotter Software, Inc.
All rights reserved.
Your FLEXlm kits are in:
../sun4_u4
Which kit would you like to install? ../sun4_u4
Installing FLEXlm kit ../sun4_u4
ranlib-ing libraries
Do you want to continue and configure your daemon now [y/n]? n

The following example shows the configuration of a vendor daemon (demo) that uses the default values for all parameters. The meanings of the parameters are described in “Configuring Your Vendor Daemon”.

---

Note: You can manually edit ls_vendor.c in the /lmgr/machind directory, lm_code.h, and the makefile, if you do not want to run CONFIG_DAEMON. (This must be done manually on VMS and Windows NT, where CONFIG_DAEMON is not supported).

---

In FLEXlm v2.4 and later, the CONFIG_DAEMON script only prompts for the daemon name, one set of encryption seeds, and the vendor keys. This is done to simplify installation when all the defaults are desired. If you wish to specify all the daemon options, use the “-x” option to CONFIG_DAEMON, which will cause it to prompt for all options as in prior FLEXlm versions. This example does not use the option to illustrate all selections. All data that you type is in bold.

% cd lmgr/machind
% CONFIG_DAEMON

Flexible License Manager vendor daemon configuration.
Copyright (C) 1988, 1994 Globetrotter Software, Inc.

This script will configure and build your vendor daemon, and
leave the resulting configuration information in the file
daemon.dat.  To get the default value for any selection, simply
enter <CR>.

Your daemon must have a DAEMON name.  This name will appear in
the license file that you generate for your customers as the
name in the DAEMON line.  The name will also appear in the
executable for the daemon, in order for the Flexible License
Manager to do consistency checking.

The daemon name for an evaluation kit MUST BE "demo".

Please enter your daemon's DAEMON name: demo
Updating ../alpha_u1/makefile for daemon name "demo"

Your daemon (demo) will support some number of product features.
Your daemon will support only the features listed in the
license file that encrypt correctly with the codes you build
into your daemon.  Please enter your encryption code at the
following pair of prompts. 

DO NOT ENTER THE LEADING 0x in the encryption codes.

To get the default answer to any question, type a <CR>.

Encryption code first 32-bits (data[0]) [hexadecimal, <CR> to quit]: 12345678 
Encryption code second 32-bits (data[1]) [hexadecimal]: 87654321

If you want to leave the FLEXlm vendor keys unchanged in
lm_code.h, simply enter <CR> to the next prompt.

DO NOT ENTER THE LEADING 0x in the vendor keys.

FLEXlm vendor key #1 for demo [hexadecimal]: 12345678
FLEXlm vendor key #2 for demo [hexadecimal]: 87654321
FLEXlm vendor key #3 for demo [hexadecimal]: 12344321
FLEXlm vendor key #4 for demo [hexadecimal]: 43211234
FLEXlm vendor key #5 for demo [hexadecimal]: aabb33ee


The configuration information for your daemon is in daemon.dat
The data file used to build the daemon is ls_vendor.c

Do you want to continue and build the daemon now? [y/n, default: n]: y

You are running on an alpha-osf1 system

FLEXlm binary directories are:
../alpha_u1

Which daemon would you like to build? [default: ../alpha_u1, e to exit]: 

Building kit in directory ../alpha_u1
cc -c -g -I../machind  ../machind/create_lic.c
cc -o create_license create_lic.o liblmgr.a 
rm create_lic.o
cc -c -g -I../machind  ../machind/create_pkg.c
cc -o create_pkg create_pkg.o liblmgr.a 
rm create_pkg.o
cc -c -g -I../machind  ../machind/lmclient.c
cc -o lmclient lmclient.o liblmgr.a 
rm lmclient.o
cc -c -g -I../machind  ../machind/lmcrypter.c
cc -o lmcrypter lmcrypter.o liblmgr.a 
rm lmcrypter.o
cc -c -g -I../machind  ../machind/lmfeatset.c
cc -o lmfeatset lmfeatset.o liblmgr.a 
rm lmfeatset.o
cc -c -g -I../machind  ../machind/lmrandom.c
cc -o lmrandom lmrandom.o
rm lmrandom.o
rm -f lsr_vendor.c
lmrandom < ../machind/ls_vendor.c > lsr_vendor.c
cc -c -g -I../machind  lsr_vendor.c 
rm -f ls_vendor.o
mv lsr_vendor.o ls_vendor.o
cc  -o demo ls_vendor.o  liblmgr_as.a liblmgr_s.a liblmgr.a 
strip demo
strip create_license create_pkg lmclient isvaliddate lmcrypter lmfeatset lmrandom  
strip: Info: isvaliddate already stripped
ln -f lmutil lmhostid
ln -f lmutil lmver
ln -f lmutil lmcksum 
ln -f lmutil lmdown
ln -f lmutil lmhostid
ln -f lmutil lmremove 
ln -f lmutil lmremove 
ln -f lmutil lmreread 
ln -f lmutil lmswitchr 
ln -f lmutil lmstat 
ln -f lmutil lmdiag
ln -f lmutil lmver 
Done building kit ../alpha_u1

All FLEXlm kits require a set of FLEXlm Vendor Keys in order to operate. Globetrotter Software will supply you with the FLEXlm Vendor Keys for the vendor name you select, or “demo” if it is a demo kit. The FLEXlm Vendor Keys consist of five hex numbers which are coded to the vendor name. CONFIG_DAEMON installs these keys in your vendor daemon via the include file lm_code.h.

The FLEXlm Vendor Keys are the fourth through eighth parameters to the LM_CODE macro, as in this example:

LM_CODE(vcode, ENCRYPTION_CODE_1, ENCRYPTION_CODE_2,
VENDOR_KEY1, VENDOR_KEY2, VENDOR_KEY3, 
VENDOR_KEY4, VENDOR_KEY5)

(The ENCRYPTION_CODE_x and VENDOR_KEYx values are defined in lm_code.h as a result of running CONFIG_DAEMON). The LM_CODE macro creates a static variable with the name of its first parameter. If you want a global variable, use the LM_CODE_GLOBAL macro, which takes the same parameters as LM_CODE.

Once you have coded this LM_CODE macro, call lc_init as follows:

lc_init((LM_HANDLE *)0, VENDOR_NAME, &vcode, &lm_job);

The first argument to lc_init() is the current job, and is used in cases where multiple jobs are used.

This call to lc_init() must be included in any program that uses the FLEXlm libraries, and it must be the first FLEXlm function you call (unless you are using the Software License Working Group or LSAPI calls).

If you use any of the FLEXlm symbolic definitions, macros, or data structures, you must include lm_client.h and lm_code.h in your C module. lc_set_attr() calls require you to include lm_attr.h. Your encryption seeds, FLEXlm vendor keys and vendor name are in lm_code.h.

In order to build your application: