Manual Felics GB
60
UniCon Software GmbH Documentation FELICS 2.x Floating Extended Licence Server 06.06.00
-
Upload
jolustan2009 -
Category
Documents
-
view
28 -
download
0
Transcript of Manual Felics GB
UniConSoftware GmbH
Documentation
FELICS 2.xFloating Extended Licence Server
06.06.00
UniCon Software GmbHAll rights reserved. No part of this manual may be reproduced or utilised in any formor by any means without the publishers's consent.The following text and Illustrations were written with great care, however, we cannottake warranty for any errors and consequences from those.The product titles found in this manual are registered trade marks of the producers.The authors will appreciate suggestions or remarks as to the text.
Preface
We want to thank you for choosing the UniCon products and assure youthat UniCon communication software combines best functionality with amaximum of user comfort.
This detailed technical description will help you in getting used to work withthe product. However, questions will still arise especially when communi-cation components of other producers are also being used. In this caseplease contact us immediately. We will give you qualified support.
FELICS, the Floating Extended Licence Server, dynamically monitors andsupervises the application of software in NOVELL and TCP/IP networks.The software package contains the client and server components.Supported server platforms are: Netware-Server, Windows-NT, OS/2 aswell as Unix Systems. The client software is availabe on Windows 3.x,Windows 95, OS/2 and Unix.
The installation, configuration, application and interfaces for softwareprogrammers are described in this manual.
C O N T E N T S
1 Licence Management .............................................................................. 1
1.1 By FELICS.............................................................................................. 1
1.2 By Node Licencing (Software-Dongle).................................................... 2
2 FELICS...................................................................................................... 3
2.1 Installation .............................................................................................. 42.1.1 UNIX-Server ............................................................................. 42.1.2 NOVELL-Server ....................................................................... 52.1.3 Windows-NT............................................................................. 5
2.2 Start and Close....................................................................................... 62.2.1 UNIX-Server ............................................................................. 62.2.2 NOVELL-Server ....................................................................... 72.2.3 Windows-NT............................................................................. 8
2.3 Configuration (felics.cnf)......................................................................... 9
2.4 Diagnosis (felics.log) ............................................................................ 10
2.5 Backup Licence Server......................................................................... 11
3 FELICS-Tools ......................................................................................... 13
3.1 Installation ............................................................................................ 13
3.2 Licencing by FELICS............................................................................ 133.2.1 BRANDLI (Unix) ..................................................................... 143.2.2 REMBRAND (Windows)......................................................... 18
3.3 Licence Monitoring ............................................................................... 193.3.1 RAMON (Unix)........................................................................ 193.3.2 WRAMON (Windows) ............................................................ 21
3.4 Licence Management by Node Licencing............................................. 21
4 FELICS Agent......................................................................................... 23
4.1 UNIX (felicscltd).................................................................................... 24
4.2 Windows 3.x (UCWATCH) ................................................................... 254.2.1 Installation .............................................................................. 254.2.2 Automatical Installation WATCHPUB (Novell) ....................... 26
4.3 Windows NT (NTfelclt) .......................................................................... 274.3.1 User-Controlled Licencing (NTclte)......................................... 29
4.4 Windows95 / Win32s (NTfelclt)............................................................. 304.4.1 User-Controlled Licencing (NTclte)......................................... 30
5 FELICS-SDK............................................................................................ 31
5.1 General Concept................................................................................... 31
5.2 Technical Concept ................................................................................ 32
5.3 UNIX...................................................................................................... 335.3.1 Installation............................................................................... 335.3.2 Application Programmers Interface (API) ............................... 34
FELICS_init..................................................................... 34FELICS_quit.................................................................... 34FELICS_getlicence ......................................................... 35FELICS_freelicence........................................................ 35
5.3.3 Demo Program ....................................................................... 36
5.4 WINDOWS 3.x...................................................................................... 375.4.1 Installation............................................................................... 375.4.2 Application Programmers Interface (API) ............................... 38
FELICS_init..................................................................... 38FELICS_quit.................................................................... 38FELICS_getlicence ......................................................... 39FELICS_freelicence........................................................ 39FELICS_sdkversion ........................................................ 40
5.5 WINDOWS-NT / 95 and Win32s .......................................................... 425.5.1 Installation............................................................................... 425.5.2 Application Programmers Interface (API) ............................... 43
FELICS_init..................................................................... 43FELICS_quit.................................................................... 43FELICS_getlicence ......................................................... 44FELICS_freelicence........................................................ 44FELICS_sdkversion ........................................................ 45
5.6 Key Generator WLIPRI (Windows) ....................................................... 475.6.1 DDE Server............................................................................. 48
List of IllustrationsIndex
UniCon Licence Management
1
1 Licence Management
FELICS is based on the Client-Server technology. The main part is thelicence server which is installed on the corresponding server system (Unix,Netware, Windows-NT) controlling the licencing-out. Each client has exactlyone instance (FELICS Agent), which maintains the communication with thelicence server. Every PC-application subject to licencing requests a licencefrom this agent. The FELICS Agent should therefore be activated whenstarting the client PC.
1.1 With FELICS
Using a central licence server has the following advantages:• central administration and control of licences• licencing-out on request (floating licence)
The FELICS Tools allow to administrate the licence server comfortably.Your own software can easily be connected to the FELICS Agent by meansof FELICS-SDK.
FELICS
licence.db
licence
licence
licence
FELICS Agent
licence
licence
licence
FELICS Agent
Illustration 1: Licence Management with FELICS
Licence Management UniCon
2
1.2 Node Licencing (Software-Dongle)
Node licencing has been added to the licence management. Thus one cando without a central licence server, e.g. if there is no network. In case ofnode licencing the FELICS Agent manages the licencing-out and the moni-toring of licences:
You enter your licences with the FELICS tools on each node. All appli-cations which are subject to licencing may use this licence mode withoutany restrictions or adjustment.
licence
licence
licence
FELICS Agent
licence
licence
licence
FELICS Agent
Illustration 2: Licence Management by node licencing
UniCon FELICS
3
2 FELICS
The Floating Extended Licence Server (FELICS) enables you to installsoftware in your network as often as you like without having to buy newlicences. When starting the program the licence is provided by the licenceserver. The licences are held in the licence data base licence.db.The programs REMBRAND (Windows) and BRANDLI (Unix) serve to re-gister or delete licences in the data base. All you need is a licence keywhich you receive from your software vendor. If you wish to increase thenumber of licences for a product, you only have to feed the data base withthe corresponding licence key. Without restart, the licence server isinformed about the new number of licences. If software products are in-stalled on different PCs, all products can be licenced by one server,provided that the server can be reached via the network protocols IP orIPX.This version also offers the possibility to provide user-controlled licences.Thus you are free to licence your standard software according to yourrequirements.
If you have decided to use the Node Licencing (Sofware Dongle), you donot need a licence server. In this case please see for chapter "FELICSTools“.
FELICS UniCon
4
2.1 Installation
The installation procedures differ between the operation systems UNIX,NOVELL and Windows-NT. This is why they are described separately.
2.1.1 UNIX-Server
After installation, all files can be found in the directory '/usr/felics'.The FELICS installation disk has either the tar format or the DOS format(for UNIX systems without a disk drive).For installing the licence server please perform the following steps:
In SUN-Sparc systems you must first switch off the vol-daemon by the killcommand (kill vold).
tar-Diskette
cd /tar xvf /dev/fd0 (and the drive as installed in your
system respectively)
DOS-DisketteSend the file felics.tz (felicss.tz in case of FELICS with SDK) toyour UNIX system as a binary file and then enter the followingcommands:
mv felics.tz felics.tar.Zuncompress felics.tarcd /tar xvf felics.tar
cd /usr/felics./felics.install
If desired the licence server can be started automatically by the abovescript. But it may also be started later (see "Start and Close").
UniCon FELICS
5
2.1.2 NOVELL-Server
Installation is carried out by means of a Windows program. In this case theNovell system directory (e.g. f:\system) and the FELICS work directory (e.g.f:\felics) must be entered. The work directory should be on the systemdrive. For installation both directories must not have a WRITE protection.Therefore you should have Supervisor or Admin rights.
For installation perform the following steps in Windows:
a:setupThe setup program guides you through installation.
After the installation has been finished successfully the licence server canbe started on the Novell server console (see "Start and Close").
2.1.3 Windows-NT
For installation both directories - Windows and Windows\system - must nothave a WRITE protection. Furthermore, you must have the right to installNT services.
For installation perform the following steps in Windows-NT:
a:setupThe setup program leads you through installation.
When the installation has been finished successfully the licence server isavailabe on your NT server. Click on the symbol „Services“ in your SystemControl.
FELICS is loaded via the service administration of Windows-NT (see "Startand Close“).
FELICS UniCon
6
2.2 Start and Close
Already registered licences are not deleted by terminating the licenceserver. Thus licenced programs will still run without any difficulties.The licence server itself has to be supplied with a licence key. If this hasnot been carried out yet, FELICS starts in the so-called 'administrationmode'. In this case, please enter your FELICS licence directly after the startby means of the programs BRANDLI (Unix) or REMBRAND (Windows) (seechapter "Licencing").
2.2.1 UNIX-Server
The licence server can be started or closed with the root authorization only.By default the licence server is found on /usr/felics. If you wish to use adifferent work directory, the environment variable FELICSENV has to beset.
Start:cd /usr/felics./felics
Close:cd /usr/felics./felics end
Restart:cd /usr/felics./felics restart
UniCon FELICS
7
2.2.2 NOVELL-Server
Please enter the following commands on the console of the Novell server:
Start:load felics <arbeitsverzeichnis>
Enter the command in the file autoexec.ncf in order to automati-cally load the licence server during system initialisationThe work directory need only be named if it differs from the default(<nwserver>/SYS:/FELICS).
Close:unload felics
FELICS UniCon
8
2.2.3 Windows-NT
The licence server can be started and closed via the service administrationof Windows-NT. Please activate the symbol "Services“ in your SystemControl.
Start:Mark the service FELICS and click on the switch "Start“.Having started the licence server successfully the state of the service changes to "started“.
Close:Close the licence server with the switch "Close“.
If you want to remove the licence server from the service administration,start the server executable with the parameter "remove“:z.B.: c:\win32app\felics\ntfelics.exe remove
UniCon FELICS
9
2.3 Configuration (felics.cnf)
The configuration of the licence server is defined by the text file felics.cnf inthe FELICS working directory.The following parameters may be set:
Client Alive MechanismThe licence server requests a message from the client in regular intervals,in order to recognize if a licenced program has been aborted or a clientsystem is missing (e.g. has been switched off). This so-called AliveMechanism may be configured by the following parameters:
MAXALIVE= If the number of Alive requests is not replied by aclient, this client's licences are released again.Default: MAXALIVE=3 .
ALIVEFREQ= Frequency (in seconds) in which the Alive requestsare sent to the client systems.Default: ALIVEFREQ=20 .
Thus the maximum period of time for FELICS to recognize an abortionamounts to MAXALIVE * ALIVEFREQ seconds.
DiagnosisThe status information written in the logfile felics.log (see chapter"Diagnosis") can be extended by the following parameter for the purpose ofdiagnosis:DEBUG= 0: no extended protocol
1: extended protocol in felics.log
Backup FunctionThe Backup Server (see chapter „Backup Licence server“) safeguards thatthe licences are still avaiblabe even if the ‘master’ licence server shouldfail. The following parameters are only used by a backup server (FELICSwith FELICSB licence).MFELICS= Host name of the master FELICS the failure of which is to
be supervised. The parameter may be entered severaltimes, i.e. a backup server may supervise several licenceservers.
PONG= Frequency (in seconds) in which the failure of the super-vised ‘master’ licence server is checked.Default: 20 seconds
FELICS UniCon
10
Example: felics.cnf:
MAXALIVE=3ALIVEFREQ=20DEBUG=0
Example: felics.cnf of the backup licence server ucfelics3MAXALIVE=3ALIVEFREQ=20DEBUG=0MFELICS=ucfelics1MFELICS=ucfelics2PONG=30
2.4 Diagnosis (felics.log)
As long as the licence server is active all necessary data are written in thetext file felics.log in the FELICS work directory. When this file has grown toits maximum volume, writing is continued at the beginning of the file.By default the file contains generally the essential events of the licencingprocess. However, in some cases it may be useful to activate the extendedmode (see chapter "Configuration"), because it supplies detailed statusinformation of the licence server.Please note that the file cannot be read directly in the Novell environment.This is only possible with a file copy.
copy felics.log felics.txtedit felics.txt
Windows-NTThis allows to additionally show the status information of the licence serveron the window of the licence server. Enter the parameter ‘show’ whenstarting the FELICS service.
UniCon FELICS
11
2.5 Backup Licence Server
In version 2.30 another essential function has been integrated into thelicence management FELICS. Thanks to the Backup Licence Server theacquired licences are available at any time even if the licence server fails.Thus the Backup Licence Server takes over the tasks of the ‘master’licence server until it is ready again.
ConceptThe Backup Server is installed on a second PC. It is the same software ason the primary system. However, the licence server is configured by aFELICSB licence as a backup server. The parameter MFELICS in the filefelics.cnf (see chapter „FELICS configuration“) provides that the mainlicence server (master FELICS) is known to the backup licence server.
The backup server isconstantly in contact with oneor several master servers(registered in felics.cnf)supervising their functionality.All information required forlicencing-out are permanentlytransferred from the master-FELICS to the Backup-FELICS:
The failure of the master FELICS is automatically recognized from thebackup server in a configurable frequency (PONG-Parameter in felics.cnf).
Firstly, the backup server in-forms all agents about the newserver address.
Agent
FELICS
Agent
FELICSBackup
Agent
FELICS
Agent
FELICSBackup
FELICS UniCon
12
From now on the agents request alllicences from the backup server. Newlystarted agents are already familiar withthe backup server from their own localconfiguration. After the start the agenttries to contact its master FELICS first. Ifit does not succeed it applies to theBackup Server.
Now the Backup Server has exactly the same functions as a licence server.Licences may be entered or deleted by REMBRAND or BRANDLI.However, the Backup Server is not available for other master licenceservers. In this case, every other minute the Backup Server checks if themaster FELICS is ready again.
As soon as the original master FELICS has been recognized, all statusinformations on the licence are transferred to the master, the agents areinformed, and the (backup) licence server returns to the backup modeagain.
ConfigurationVersion 2.30 and further versions must include all licence components(FELICS and FELICS Agents). It is not necessary to change the configura-tion of the master FELICS. The Backup Server is to be installed on asecond PC and equipped with a FELICSB licence. The parametersMFELICS and PONG have to be adjusted in the configuration file felics.cnf(see „FELICS Configuration“). When starting the Backup Licence Serverthe connection to the master FELICS must be assured of.The configuration of the FELICS Agents is extended by the Backup Serverat the requested position (see „FELICS Agent“ ).
Agent
FELICSBackup
Agent
UniCon FELICS-Tools
13
3 FELICS-Tools
These programs (BRANDLI, REMBRAND) enable comfortable access to thefunctions of the licence server FELICS as well as to the licence data base.They also help to find out the actual need of licences (RAMON, WRAMON).Moreover, the FELICS Tools contain the FELICS SDK for Windows 3.x tohandle your own software by means of the licence server.
When installing the FELICS Tools you may select the licencing mode via node(software dongle) if you wish to manage your licences without a central licenceserver FELICS and without network connection (see chapter „LicenceManagement“).
3.1 Installation
The programs RAMON and BRANDLI are included in the delivery ofFELICS/Unix (see "FELICS Installation").Please install the Windows components by means of the setup program onthe FELICS Tools disk:
a:setup
Your PC needs network support either by TCP/IP with Winsockets or bySPX/IPX (not in case of Node Licencing).The installation program creates the program group "FELICS Tools" with thecorresponding program symbols.
3.2 Licencing by FELICS
The FELICS licence management differentiates between „key-controlled“ and„user-controlled“ licences. For this product, „key-controlled“ licences must beacquired from your software producer or vendor respectively. These licencesare provided by a licence key.„User-controlled“ licences may be supplied by the system administrator forstandard software in order to limit the number of applications or users. It is upto the system administrator to set the limit of licences.
FELICS-Tools UniCon
14
3.2.1 BRANDLI (Unix)
BRANDLI is an efficient program, which enables you to register „key-controlled“ licences by licence keys very easily.
command: /usr/felics/brandli
After the start (which is only possible with root authorization) the followingmenu is shown:
Illustration 3: BRANDLI - main menu
Select "L" to licence a product. Then you are requested to enter the key:
UniCon FELICS-Tools
15
Illustration 4: BRANDLI - Entry of product key
If the key has been entered correctly this is being confirmed:
FELICS-Tools UniCon
16
Illustration 5: BRANDLI - Licence confirmation
Provided a licence server is active, it will be immediately informed byBRANDLI about the modification.
Moreover BRANDLI is able to display the entries in the licence data base andthus offers a complete survey of all the licences acquired.You get this survey by selecting "D" in the main menu:
UniCon FELICS-Tools
17
Illustration 6: BRANDLI - Product survey
FELICS-Tools UniCon
18
3.2.2 REMBRAND (Windows)
By means of REMBRAND you administrate your key-controlled and user-controlled licences from your Windows application. Start the program via theicon „FELICS Tools“ of the program group. Please make sure, however, thatthe licence server has been initialized.
Illustration 7: REMBRAND
IMPORTANT: User-controlled licences can only be released if a FELICSELicence (FELICS end-user licence) is available.
REMBRAND offers online help for detailed information.
UniCon FELICS-Tools
19
3.3 Licence Monitoring
The monitor programs RAMON(Unix) and WRAMON(Windows) keep youinformed about the actual number of licences you need. Both programsrequire an active licence server.
3.3.1 RAMON (Unix)
RAMON (Running Application MONitor) is an additional product in order to"observe" running applications. To activate this product you need a licencekey.Enter the following command:
/usr/felics/ramon
and you get the menu:
Illustration 8: RAMON - info window
The command "m" leads you to the monitor mode. RAMON is updated auto-matically .
FELICS-Tools UniCon
20
Please select between two presentations with the option "o".
1. All active applications and additional information such as the names of thestation and the host on which the application is active.
2. The number of all active applications sorted by applications and thenumber of licences in use.
Illustration 9: RAMON Monitor Window
Quit the monitor by entering the command "q".
UniCon FELICS-Tools
21
3.3.2 WRAMON (Windows)
By means of WRAMON (Windows Running Application MONitor) you may"observe" running applications and thus find out the actual need of licences.Please start WRAMON by clicking on the icon "FELICS-Tools“ in the programgroup . Make sure that the licence server has been initialized.
Illustration 10: WRAMON
WRAMON is equipped with online help, which gives you detailed explanationsto the various functions.
3.4 Licence Management by Node Licencing
In case of node licencing (software dongle) the licence keys are registered oneach node PC by means of the program WBRANDLI into the file ucwatch.ini.The licence keys you acquired are only valid for the corresponding node PC(identified by the Host ID). The Host ID can be obtained by calling the programUCHOSTID in „FELICS Tools“. WBRANDLI also shows the Host ID in the topline:
FELICS-Tools UniCon
22
Please select[New] to enter a licence with a licence key. It is up to you to define the
corresponding product name. The licences are availableimmediately after the entry.
[Rename] to modify the product name[Delete] to delete the licences of a product[Quit] to quit the program.
Important: Every node PC must be released by entering a FELICSNlicence (Produkt-Id 66).
Illustration 11: WBRANDLI
UniCon FELICS-Agent
23
4 FELICS Agent
FELICS is based on the Client-Server concept. The main part is the licenceserver, which is installed on the corresponding server system (Unix, Net-ware, Windows-NT). Each client workstation has exactly one instance(FELICS Agent) which maintains the communication to the licence server.Every PC-application subject to key-controlled licencing requests a licencefrom this agent. For this reason the FELICS Agent should be activatedwhen starting the client PC.
Windows-PC Unix
Novell / Unix
ApplicationProduct-Id x
ApplicationProduct-Id y
licence.db
UDP/IPIPX
msgqueue
ApplicationProduct-Id x
ApplicationProduct-Id y
ucwatch watch.dll felicscltd
FELICS
Illustration 12: FELICS-Agent
FELICS-Agent UniCon
24
4.1 UNIX (felicscltd)
The FELICS Agent is either obtained by installation of the FELICS-SDK ortogether with the software of software producers or vendors who protecttheir software by FELICS. The agent is responsible for the complete com-munication with FELICS. We therefore recommend to activate the daemonwhen starting your system (in /etc/rc).
Program Parameters:
felicscltd -s <licence server> -k <msgqueue> -d
-s enter the hostname of your licence server hereIf you use a backup server, it must also be entered here (e.g.felicscltd -s ucfelics -s ucfelicsb)
-k The input of a message queue key is optional. By default we useFELICS_MSG (see FELICS-SDK/UNIX).
-d activates the trace output of the agent. The trace configuration isdefined in the file /etc/felicscltd.cnf. Example:TRACEFILE = <file name>TRACELEVEL=<trace level 0-5>TRACEFILE_COUNT=<max number of trace files>TRACEFILE_SIZE=<max size of a trace file in bytes>Example:TRACEFILE = felicscltd.logTRACELEVEL = 5TRACEFILE_COUNT = 2TRACEFILE_SIZE = 500000
Important: You need root authorization to start the FELICS Agent.
If you need to close the daemon, you may do this by signal 15.
UniCon FELICS-Agent
25
4.2 Windows 3.x (UCWATCH)
In addition to the server component (FELICS) you have to install the clientcomponent (UCWATCH) for user-controlled licencing on each PC which isto support this mode of licencing. UCWATCH informs your licence serverabout the events which are relevant for the user-controlled licencing (e.g.Start and Terminate Windows applications). If the number of licencesshould be exceeded , the user will be informed by a message.UCWATCH requires a network connection via TCP/IP-Winsockets orSPX/IPX-Netware.Alternatively, you may choose the Node Licencing (software dongle) duringinstallation. In this case a licence server and a network connection are notnecessary. The agent itself is performing the licence management.
4.2.1 Installation
The UCWATCH is shipped with the disk FELICS Agent. During the instal-lation of FELICS Agent the UCWATCH program components are beingcopied into the target directory:
watch.dll: Dynamic library of functionsucwatch.exe: client daemon (WINDOWS)toolhelp.dll: Windows tools libraryucwatch.ini: configuration file
Before the first start of the agent the name of the licence server (and thename of the backup server respectively) must be entered into theconfiguration file ucwatch.ini in the Windows directory (unless you havechosen the Node Licencing).
Example ucwatch.ini:
FELICS=192.92.1.1orFELICS=NWSERVER
Please make sure that the program ucwatch.exe will be initialized auto-matically when starting Windows (entry in win.ini):
Example win.ini:[windows]run=UCWATCH.EXE
Please restart Windows.
FELICS-Agent UniCon
26
4.2.2 Automatical Installation WATCHPUB (Novell)
The Novell environment allows an automatical installation procedure. Theprogram watchpub.exe copies the UCWATCH files during the login proce-dure of the user into his Windows directory and modifies the win.ini.
Call: watchpub -w <work directory> -u
-w The mentioned directory must contain the following files:ucwatch.ini, ucwatch.exe, watch.dll, toolhelp.dll
-u The modifications in the win.ini of the user are canceled.
We recommend the following approach:• First copy the UCWATCH program files and the program watchpub.exe
into an appropriate Novell server directory (e.g.<nwserver>/SYS:/PUBLIC/WATCH).
• Edit the file ucwatch.ini in the above directory as described in thechapter "Installation".
• Enter watchpub.exe into the system login script:#<nwserver>/sys:/public/watch/watchpub -w <nwserver>/sys:/public/watch
Watchpub.exe can be called more than once without causing anydifficulties.
UniCon FELICS-Agent
27
4.3 Windows NT (NTfelclt)
Like the licence server itself the FELICS Agent is an NT service installed bythe FELICS Agent installation program. Before the first start of the agentyou have to modify the starting mode of the service:
Starting mode[• ] Automatically
Login as[• ] System account
[• ] allow interactive relation by desktop
After the starting procedure the service may be started and closed via theservice management of Windows NT. We recommend the starting mode„Automatically“, because the agent will then be activated during systeminitialization.
The FELICS Agent is configured in the file UCWATCH.INI in the Windowsdirectory. If not already done during installation, please enter the name ofthe licence server here and - if required - the name of the backup licenceserver as well.
Example ucwatch.ini:
[UCWATCH]FELICS=ntserver primary licence serverFELICS1=ntserver2 1st Backup-Server (optional)FELICS2=ntserver3 2nd Backup-Server (optional)
:SHOW=<0|1>
If you have chosen the Node Licencing during the installation of theFELICS Agent, the agent uses this ini-file to save the acquired licences.The name of the licence server is ignored.
FELICS-Agent UniCon
28
Service Start Parameter:
show The FELICS Agent is made visible for debug purposes.
Command line Parameters:
call: ntfelclt.exe [ remove | install <exename> ]
install installs the exe file <exename> as FELICS Agent-Service.The exe file must be named together with the completedirectory. Example:
ntfelclt.exe install c:\win32app\felics\ntfelclt.exe
remove removes the FELICS Agent service from the service mana-gement of Windows-NT.ntfelclt.exe remove
UniCon FELICS-Agent
29
4.3.1 User-Controlled Licencing (NTclte)
By means of the additional program NTCLTE, the FELICS Agent may beused for the control and the licencing of standard software (Winword,Access etc.). NTCLTE supervises the calls of every Windows applicationand requests a licence if necessary. If the limited number of licences isexceeded, the user is informed by a message window, and the Windowsapplication is aborted:
call: ntclte
The program should be called in the user’s login script. The program re-quires an active FELICS Agent (Ntfelclt) and is not visible for the user.
Windows applications are identified by their module names (e.g.MSACCESS) and licenced (see REMBRAND). To find out the modulename of a Windows application, use the program NTWINAPP, which isincluded in the FELICS Tools package.
Remark: The FELICS-E function must be released by a licence key onthe licence server.
Illustration 13: Limit of licences exceeded
FELICS-Agent UniCon
30
4.4 Windows95 / Win32s (NTfelclt)
In Windows95 / Win32s the FELICS Agent/NT is used. The installation isdone by the FELICS/NT installation program. However, the agent cannot beinstalled as a service but should be integrated in the autostart group. Whencalling the agent the parameter ‘noservice’ must be entered:
Call: ntfelclt.exe /noservice
The FELICS Agent is configured in the file UCWATCH.INI in the Windowsdirectory. If not already done during installation, please name the licenceserver und - if required - the backup server, too.
Example ucwatch.ini:
[UCWATCH]FELICS=ntserver primary licence serverFELICS1=ntserver2 1st Backup-Server (optional)FELICS2=ntserver3 2nd Backup-Server (optional)
:SHOW=<0|1>
If you have chosen the Node Licencing during the installation of theFELICS Agent, the agent uses this ini-file to save the acquired licences.The name of the licence server will then be ignored.
4.4.1 User-Controlled Licencing (NTclte)
The FELICS Agent also takes charge of the licencing of standard software(Winword, Access ...), provided you additionally start the program NTCLTE(see „Windows-NT -> User-controlled Licencing“).
UniCon FELICS-SDK
31
5 FELICS-SDK
5.1 General Concept
The Floating Extended Licence Server (FELICS) allows you to install softwarein the network as often as you like without having to acquire licences. Whenyou start the application, you get an authentication from the licence server viathe FELICS Agent.For the purpose of a dynamic licencing the licence server checks the licencedata base containing the information on all licenced products. The end-userenters a licence key. Thus the licences are registered in the data base. Thislicence key includes a product ID, the number of licences and - if required -the validation date of the licences. The software producer is the only onebeing able to generate keys for the corresponding product ID (see chapter„key generating“). Product-IDs are unique worldwide and are only provided byUniCon. A licence key is only valid for the server or node for which it has beencreated.
If further licences are requested, the user may increase the number oflicences for his products by entering the new key even when the licence ser-ver is running.
The application which is to be licenced (client) acquires an authentication fromFELICS (Licence Server) and releases the licence when closing theapplication. As long as the application is active the licence is in use. After theapplication has been closed, the licence is available again for users in thecomplete network. The FELICS Agents provide for the entire communicationbetween application and licence server.
Software Producer CustomerUniCon
Licence Key
FELICS
Authentication KeyWLIPRI
FELICS KeyBRANDLI /REMBRAND
FELICS Key
ProductAuthentication
licence.db
Illustration 14: Providing a licence key
FELICS-SDK UniCon
32
In case the application has not been closed properly, e.g. by switching off theclient PC, the licence will automatically be available after a defined period oftime.Closing the licence server does not affect the running applications. After therestart of the licence server the active applications are recognized automati-cally.
5.2 Technical Concept
Each client PC has exactly one instance (FELICS-Agent) maintaining thecommunication to the licence server. Any client application to be licencedapplies to the FELICS Agent via the SDK. The instance „FELICS Agent“ pro-vides the following services:
INIT: initializes the communication between the agent and thelicence server
GETLICENCE: orders a licence for the product IDFREELICENCE: releases the licence of a product IDQUIT: The communication to the agent is closed.
The licence server controls all FELICS Agents in a period of time to be definedand thus all applications (ALIVE procedure). If applications or complete clientsshould be shut down abruptly (e.g. by program or system abortion), thelicence server again releases all licences in use.In case the server PC has been aborted and restarted, all active licences arerecognized in the whole network and registered again. Running applicationsare not affected.
Remark: After the installation of the SDK you may first use the product ID4711 (DEMO- product) for your own applications. FELICS provides2 licences of this product for testing purposes.
UniCon FELICS-SDK
33
5.3 UNIX
In this version the SDK under Unix consists of the following components:
Software Development:wlipri: Key generator for product keys
(WINDOWS)felicslib.a: Functions Library (UNIX)felicslib.h: Header File (UNIX)felicscltd: FELICS Agent (UNIX)sdkbsp.c: Demo Program (UNIX)
5.3.1 Installation
Make sure that the licence server is active before installation. If you have notyet acquired a FELICS licence key, please use the product ID 4711 (Demoproduct) for programming. FELICS provides 2 licences for this product ID:
The installation of the Unix components is integrated in the FELICS installa-tion (see chapter "FELICS Installation"). All files are copied into the file/usr/felics. Afterwards you copy the files which are important for the softwaredevelopment (felicslib.a, felicslib.h) to the corresponding directories and startthe FELICS Agent felicscltd (see chapter "felicscltd").The key generator WLIPRI (Windows) allows to produce licence keys for yourproducts (see chapter "Key Generator WLIPRI"). We recommend defining aWindows program symbol to start with the work directory.
FELICS-SDK UniCon
34
5.3.2 Application Programmers Interface (API)
The library "felicslib.a" offers simple and comfortable communication with thelicence server FELICS via the FELICS Agent. felicslib.h contains prototypesand constants.
Important: Before using API make sure that the FELICS Agent is activeunder Unix (e.g.: start by the file „rc“ during system initialization)
FELICS_init
Prototype: extern int FELICS_init ( unsigned long msg )
Parameters: msg: Message Queue Key,required for the communication with the FELICSAgent unter Unix (e.g. FELICX_MSG).
Rückgabewert: 0: ok2: Licence server does not answer-1: Errors can be looked up via the errno
Description:The function must be called to initialize the communication between appli-cation and FELICS Agent. The address of the licence server is defined by theagent.
FELICS_quit
Prototype: extern void FELICS_quit ( void )Parameters: -Return value: -
Description:The communication to the FELICS Agent is closed, the resources are re-leased. All licences which have not been released up to now by the applica-tion process, are being automatically released now.
UniCon FELICS-SDK
35
FELICS_getlicence
Prototype:extern int FELICS_getlicence ( unsigned long productid, char *text )
Parameters: productid: Product identificationtext: additional text describing the application.
The text must be unique within one appli-cation (e.g. „Session 1“).
Max. Length: FELICS_MAXTEXT.Return value: 0: ok
1: No more licences available2: Licence server not available1: Errors can be looked up via errno
Description:The FELICS Agent registers the requested licence for the application. Thelicence is reserved until the function FELICS_freelicence or FELICS_quit isbeing called. If no licence is available, it is up to the application what to do(user infos, terminate etc.).
FELICS_freelicence
Prototype:extern int FELICS_freelicence ( unsigned long productid, char *text )
Parameters: productid: Product identificationtext: additional text which had been used in
FELICS_getlicenceReturn value: 0: ok
2: Licence server not available-1: Errors can be looked up via errno
Description:The specified licence is released again.
FELICS-SDK UniCon
36
5.3.3 Demo Program
The following example shows how simple the procedure of licence requestand licence authentication is:
#include <stdio.h>#include <stdlib.h>#include <unistd.h>
#include "felicslib.h"
int main (void);
int main(){ int rc; char buf[FELICS_MAXTEXT];
rc = FELICS_init(FELICS_MSQ);
switch (rc) { case -1: perror("FELICS_init"); exit(1); case 2: fprintf(stderr, "FELICS not running!\n"); exit(1); case 0: break; }
sprintf(buf, "Hallo Test from FELICS-SDK (%d)", getpid());
rc = FELICS_getlicence(4711L, buf); switch(rc) { case -1:
perror("Error from FELICS_getlicence ");FELICS_quit();exit(1);
case 0:fprintf(stderr, "got licence\n");break;
case 1: fprintf(stderr, "no free licence\n"); FELICS_quit(); exit(0); case 2: fprintf(stderr, "FELICS not available\n"); FELICS_quit(); exit(0); break; }
/* do your work here */ sleep (10);
if (FELICS_freelicence(4711L, buf) < 0) {perror("Error from FELICS_freelicence");FELICS_quit();exit(1);
} FELICS_quit(); return 0;}
UniCon FELICS-SDK
37
5.4 WINDOWS 3.x
The SDK under Unix consists of the following components:
Software Development:wlipri: Key generator for product-IDs
(WINDOWS)watch.dll: Dynamic functions library (WINDOWS)watch.lib: Static link of the watch.dll (WINDOWS)watchs.lib: Static library with additional functionswatch.h: Header file (WINDOWS)ucwatch.exe: FELICS Agent (WINDOWS)bsp.c: Demo program (WINDOWS)toolhelp.dll: Dynamic Windows tool librarytoolhelp.lib: Static Windows tool library
The files ucwatch.exe, watch.dll, toolhelp.dll are absolutely necessary to gua-rantee the functions of the FELICS Agents. Therefore they must be included inthe delivery.
5.4.1 Installation
If not done already, install your licence server FELICS (see chapter "FELICSInstallation").If you have not yet acquired a FELICS licence key, please use the product ID4711 (Demo product) for programming. FELICS provides 2 licences for thisproduct ID:
The installation of the FELICS tools installation (see chapter „FELICS ToolsInstallation“) implies the installation of the Windows components. Then copythose files essential for the software development (ucwatch.exe, toolhelp.dll,toolhelp.lib, watch.dll, watch.lib, watch.h) into the corresponding developmentdirectories. Now configure and start the agent "ucwatch" under Windows (seechapter "FELICS Agent Windows").
The key generator WLIPRI (Windows) allows to produce licence keys for yourproducts (see chapter "Key Generator WLIPRI"). We recommend defining aWindows program symbol to start with the work directory.
FELICS-SDK UniCon
38
5.4.2 Application Programmers Interface (API)
The library "watch.dll" offers simple and comfortable communication with thelicence server FELICS via the FELICS Agent. watch.h contains prototypes andconstants.
Important: Before using API make sure that the agent ucwach.exe isactive under Windows.
FELICS_init
Prototype: extern int FELICS_init ( void )
Parameters: -
Return value: 0: ok2: Licence server not available
-1: Error
Description:The function has to be started to initialize the communication of the appliactionto the FELICS Agent. The name of the licence server is specified byconfiguring the agent (in ucwatch.ini).
FELICS_quit
Prototype: extern void FELICS_quit ( void )Parameters: --Return value: -
Description:The link to the FELICS Agent is quit again, the resources are released. Alllicences which have not been released so far by the application (process) arebeing automatically released now.
UniCon FELICS-SDK
39
FELICS_getlicence
Prototype:extern int FELICS_getlicence ( unsigned long productid, LPSTR *text )
Parameters: productid: Product identificationtext: additional text describing the application.
The text must be unique within this appli-cation (e.g. „session 1“).
Max. Length: FELICS_MAXTEXT.Return value:: 0: ok
1: No more licences available-1: Errorr
Description:The FELICS Agent registers the requested licence for the application. Thelicence is reserved until the function FELICS_freelicence or FELICS_quit isbeing called. If no licence is available, it is up to the application what to do(user infos, terminate etc).
FELICS_freelicence
Prototype:extern int FELICS_freelicence ( unsigned long productid, LPSTR *text )
Parameters: productid: Produkt identificationtext: additional text which was used in
FELICS_getlicence.Return value: 0: ok
-1: Error
Description:The specified licence is released again.
FELICS-SDK UniCon
40
FELICS_sdkversion
Prototype: extern int FELICS_sdkversion ( LPSTR dllname,WORD *version,LPSTR description)
Parameters: dllname: Name of the SDK-DLL the version of which is to befound. You may enter NULL, then the default nameWATCH.DLL is used.
version: Pointer to a buffer variable to register the SDK ver-sion number. In case of entering NULL the para-meter is ignored. The high-value byte contains thenumber of the main version, the low-value byte thenumber of the sub version.
description: Buffer for a short description of the version. Thebuffer must be allocated by the calling program andshould have a minimum length of 64 Bytes. If youenter NULL, the parameter is ignored.
Return value: FELICS_OK: The SDK-DLL was checked and theversion found.
FELICS_BADSDK: The SDK-DLL does not support thisfunction or what we have is a non-authorized library of a softwarevendor.
Description:This function finds out the actually valid SDK version and at the same timechecks the SKD-DLL for authenticity.
Remark: For reasons of security you do not find this function in the SDK-DLL (WATCH.DLL) but in the static library WATCHS.LIB, which isused to link your program.
UniCon FELICS-SDK
41
5.4.3 Demo Program
The following example shows how simple the procedure of licence requestand licence authentication is:
#include <stdio.h>#include <stdlib.h>#include "windows.h"#include "watch.h"
int PASCAL WinMain(HANDLE, HANDLE, LPSTR, int);
#define DEBUG(a) MessageBox((HWND)NULL,(LPSTR)a,(LPSTR)"BEISPIEL",MB_OK)#define PRODUCTID 4711L
int PASCAL WinMain(hInstance, hPrevInstance, lpCmdLine, nCmdShow)HANDLE hInstance;HANDLE hPrevInstance;LPSTR lpCmdLine;int nCmdShow;{
int rc;char buf[FELICS_MAXTEXT];
if ( FELICS_sdkversion(NULL,NULL,NULL) != FELICS_OK ){
DEBUG("FELICS-SDK DLL invalid");return FALSE;
}
rc = FELICS_init();switch (rc){
case -1:DEBUG("FELICS_init() failed");return FALSE;
case 2:DEBUG("FELICS unreachable");return FALSE;
case 0:break;
}
sprintf(buf, "Instanz=%d", hInstance);rc = FELICS_getlicence ( PRODUCTID, buf );if ( rc == 0 ){
DEBUG("got licence");}else{
DEBUG("no free licence");FELICS_quit();return FALSE;
}
rc = FELICS_freelicence( PRODUCTID, buf );DEBUG("licence freed");
FELICS_quit(); return TRUE;}
FELICS-SDK UniCon
42
5.5 WINDOWS-NT / 95 and Win32s
The SDK presently consists of the following components:
NTWATCH.dll: Dynamic Functions Library(Windows-NT)
NTWATCH.lib: Static link to the NTWATCH.dllNTWATCHS.lib: Static library with additional functionsWATCH.h: SDK Header-Filentbsp.c: Demo program (Windows-NT)ntbsp.exe: Demo program (Windows-NT)
wlipri: Key generator for product IDs is integrated in theFELICS-Tools/Windows
5.5.1 Installation
Before installation make sure that the licence server is active. If you have notyet acquired a FELICS licence key, use the product ID 4711 for programming.FELICS provides 2 licences for the demo product.
The installation of the Windows components is covered by the FELICS in-stallation (see „FELICS Installation/Windows-NT“).The key generator WLIPRI (Windows) allows to produce licence keys for yourproducts (see "Key Generator WLIPRI"). We recommend defining a Windowsprogram symbol to start with the work directory.
The link to the licence server can only be realized by the FELICS Agent forWindows-NT. Therefore make sure that the agent is active.
UniCon FELICS-SDK
43
5.5.2 Application Programmers Interface (API)
The communication with the licence server FELICS runs via simple andcomfortable functions of NTWATCH.dll. Prototypes, constants and variablesare found in WATCH.h .
FELICS_init
Prototype: extern int FELICS_init ( HWND hwnd, UINT msg)
Parameters: hwnd: When the agent is closed this window receives thespecified Windows messsage. If you do not needthis function you may enter NULL.
msg: A message is sent when the agent is closed. Thisparameter is not evaluated unless hwnd != NULL.
Return value: FELICS_OK: okFELICS_NO_SERVER: Licence server not availableFELICS_NO_AGENT: Agent not available
Description:The function must be called to initialize the communication of the applicationto the FELICS Agent.
FELICS_quit
Prototype: extern void FELICS_quit ( void )Parameters: -Return value: -
Description:The link to the FELICS Agent is quit again, the resources are released. Alllicences which have not been released for now by the application (process)are being automatically released now.
FELICS-SDK UniCon
44
FELICS_getlicence
Prototype:extern int FELICS_getlicence ( unsigned long productid, char *text )
Parameter: productid: Product identificatortext: additional text describing the application.
The text must be unique within an applica-tion (e.g. "session 1" ).
Max. Length: FELICS_MAXTEXT.
Return value: FELICS_OK: Licence receivedFELICS_NO_LICENCE: No more licences availableFELICS_NO_AGENT: Agent not availableFELICS_NO_SERVER: Licence server not available
Description:The FELICS Agent registers the requested licence for the application. Thelicence is reserved until the function FELICS_freelicence or FELICS_quit isbeing called or the process terminates itself. If no licence is available, it is upto the application what to do (user infos, terminate etc).
FELICS_freelicence
Prototype:extern int FELICS_freelicence ( unsigned long productid, char *text )
Parameters: productid: Product identificatortext: additional text used in FELICS_getlicence
Return value: FELICS_OK: Licence releasedFELICS_NO_AGENT: Agent not availableFELICS_NO_SERVER: Licence server not available
Description:The specified licence is released.
UniCon FELICS-SDK
45
FELICS_sdkversion
Prototyps:extern int FELICS_sdkversion ( LPSTR dllname,
WORD *version,LPSTR description)
Parameter: dllname: Name of the SDK-DLL the version of whichis to be found. You can enter NULL, thenthe default name NTWATCH.DLL is used.
version: Pointer to a buffer variable to register theSDK version number. In case NULL isentered, the parameter is ignored. Thehigh-value byte contains the main versionnumber, the low-value byte the sub-versionnumber.
description: Buffer for a short description of the ver-sion. The buffer must be allocated by thecalling program and should have a mini-mum length of 64 Bytes. If you enterNULL, the parameter is ignored.
Return value: FELICS_OK: The SDK-DLL was checked and theversion found.
FELICS_BADSDK: The SDK-DLL does not support thisfunction or what we have is a non-authorized library of a softwarevendor.
Description:This function finds out the actually valid SDK version and at the same timechecks the SDK-DLL for authenticity.
Remark: For reasons of security you do not find this function in the SDK-DLL (NTWATCH.DLL), but in the static library NTWATCHS.LIB,which is used to link your program.
FELICS-SDK UniCon
46
5.5.3 Demo Program
#include <stdio.h>#include <stdlib.h>#include "windows.h"#include "watch.h"
int PASCAL WinMain(HANDLE, HANDLE, LPSTR, int);
#define DEBUG(a) MessageBox((HWND)NULL,(LPSTR)a,(LPSTR)"BEISPIEL",MB_OK)#define PRODUCTID 4711L
int PASCAL WinMain(hInstance, hPrevInstance, lpCmdLine, nCmdShow)HANDLE hInstance;HANDLE hPrevInstance;LPSTR lpCmdLine;int nCmdShow;{
int rc;char buf[FELICS_MAXTEXT];
if ( FELICS_sdkversion(NULL,NULL,NULL) != FELICS_OK ){
DEBUG("FELICS-SDK DLL invalid");return FALSE;
}
rc = FELICS_init(NULL,0);switch (rc){
case FELICS_NO_AGENT:DEBUG("FELICS-Agent unreachable");return FALSE;
case FELICS_NO_SERVER:DEBUG("FELICS unreachable");return FALSE;
case 0:break;
default:DEBUG("FELICS_init() failed");return FALSE;
}
sprintf(buf, "Instanz=%d", hInstance);rc = FELICS_getlicence ( PRODUCTID, buf );if ( rc == 0 ){
DEBUG("got licence");}else{
DEBUG("no free licence");FELICS_quit();return FALSE;
}
rc = FELICS_freelicence( PRODUCTID, buf );DEBUG("licence freed");
FELICS_quit(); return TRUE;}
UniCon FELICS-SDK
47
5.6 Key Generator WLIPRI (Windows)
WLIPRI is the key generator which allows you to create the licence key foryour customer.
The key is generated based on the unique address (Host ID) of the licenceserver, the prouct ID, the number of licences and the validation date (if any).With the button „per call“ you specify that every call of the application requestsone licence. The button „per workstation“ allows the multiple start of theapplication on one client requesting only one licence. After entering the dataselect "Create". Now you receive the required key. This is also written to thefile 'lipri.log' and may be used for further process (e.g. fax) by Windows paste.
Important: You can only use product IDs which have been licenced byUniCon Software. If you need another product ID, please re-quest the authentication key from UniCon.
The key generator administrates all product IDs you have received fromUniCon in the 'products.db' (in the work directory). At the same time WLIPRIcreates the file 'newprod' (in the work directory). This file can be delivered toyour user.
Illustration 15: Key generator WLIPRI
FELICS-SDK UniCon
48
5.6.1 DDE Server
Starting with version 2.02 the key generator WLIPRI provides a DDE serverand may be controlled by DDE commands from other Windows applications.This allows automatic licencing processes (e.g. in DDE connectivity with adatabase and a word processing application). The table below shows the DDEfunctions.
Topic: "System"
Initiate WLIPRI Create the DDE connection
Terminate Terminate connection
Execute CreateKey Create licence key based on the speci-fied data.
Execute Quit Terminate Wlipri
Execute Hide Hide Wlipri
Execute Show Show Wlipri in full size
Execute Icon Show Wlipri as icon
Poke SrvAddr State the address of the licence server.Format Host-ID:xxxx-xxxx-xxxx
Poke Licence Define number of licences
Poke Date Set test dateFormat: dd.mm.yy
Poke Product Name product. The name must be inclu-ded in the list of the licenced products.
Request Key Request the licence key. It is createdwith CreateKey.
List of Illustrations
ILLUSTRATION 1: LICENCE MANAGEMENT WITH FELICS 1ILLUSTRATION 2: LICENCE MANAGEMENT BY NODE LICENCING 2ILLUSTRATION 3: BRANDLI - MAIN MENU 14ILLUSTRATION 4: BRANDLI - ENTRY OF PRODUCT KEY 15ILLUSTRATION 5: BRANDLI - LICENCE CONFIRMATION 16ILLUSTRATION 6: BRANDLI - PRODUCT SURVEY 17ILLUSTRATION 7: REMBRAND 18ILLUSTRATION 8: RAMON - INFO WINDOW 19ILLUSTRATION 9: RAMON MONITOR WINDOW 20ILLUSTRATION 10: WRAMON 21ILLUSTRATION 11: WBRANDLI 22ILLUSTRATION 12: FELICS-AGENT 23ILLUSTRATION 13: LIMIT OF LICENCES EXCEEDED 29ILLUSTRATION 14: PROVIDING A LICENCE KEY 31ILLUSTRATION 15: KEY GENERATOR WLIPRI 47
Index
A
agent....................................... 23alive mechanism....................... 9ALIVEFREQ.............................. 9
B
backup licence server11; 24; 27; 30BRANDLI .......................... 13; 14
C
client ....................................... 32
D
DDE ........................................ 48debug........................................ 9diagnosis .................................. 9
E
exceeding licences ................. 25
F
FELICS ..................................... 3close...................................... 6diagnosis............................. 10installation ............................. 4start ....................................... 6
felics.cnf.................................. 10felics.log.................................. 10FELICS_freelicence
Unix ..................................... 35Windows 3.x........................ 39Windows-NT ....................... 44
FELICS_getlicenceUnix ..................................... 35Windows 3.x........................ 39Windows-NT ....................... 44
FELICS_initUnix ..................................... 34Windows 3.x........................ 38Windows-NT ....................... 43
FELICS_quitUnix......................................34Windows 3.x ........................38
Windows-NT............................43FELICS_sdkversion
Windows 3.x ........................40Windows-NT ........................45
FELICS-Agent .............23; 24; 32felicscltd ..................................24FELICSE ...........................29; 30FELICSENV ..............................6felicslib.a .................................34FELICS-SDK ...........................31FELICS-Tools..........................13
K
key generator ..........................47key-controlled licence........13; 25
L
licence database .....................31licence in use ..........................19licence key...............................13licence need ............................19licence server ..........................32licencing ..................................13logfile .......................................10
M
MAXALIVE.................................9monitoring................................19
N
node licencing .....................2; 21NT service ...........................8; 27NTCLTE...................................29NTfelclt ..............................27; 30NTWINAPP .............................29
P
product-id ................................31
R
RAMON .............................13; 19REMBRAND ......................13; 18
S
SDK .........................................31Unix......................................33Win32s.................................42Windows 3.x ........................37Windows95 ..........................42Windows-NT ........................42
software development kit.........31
T
trace ..........................................9
U
UCWATCH.............................. 25UNIX-SDK ............................... 33user-controlled licence 13; 25; 30
W
WATCHPUB ........................... 26WBRANDLI ............................. 21WINDOWS-SDK ............... 37; 42WLIPRI.................................... 47working directory ................... 6; 7WRAMON ......................... 13; 21
