Simplified DLM licensing information
Purpose of this document is to give simplified basic information around the Uniface Licensing system.
For more detailed information on how the license system and its components are build up and be used, see the documentation in the: DLMUserGuide.pdf
The licensing of Uniface Applications are done by a licensing system called DLM, that consists of four major components:
- License File
- License Service
- Uniface Client Connectors
- DLM Tools
The license file is a secured XML file that contains different Uniface License Features.
Every license feature is specific for the purpose that requires to be licensed.
An example of a license feature can be the Operating System platform where the Uniface application is to be used on.
License features that can typically be found in the license file and can be used by Uniface applications, are described in 'Uniface License Features'.
As the purpose of the features can be different, there are different feature models.
Different license feature models
- Concurrent license features (features contains the <count> tag)
- Named Based license features (features contains the <fcfs/> and the <count> tags)
- Server features (features names start with USRV.... and which does not contain the <count> tag)
- Node-locked license features (features does not contain a <count> tag)
- License features that can be borrowed (features contains the <borrowing/> tag)
- License features that will only be counted once per unique user (feature contains the <dup_usr> tag)
License Service is the part of the licensing system, that will supply license features (defined in the license file) to the requesting Uniface application(s).
The License Service ('cpwr' process) can run on the same machine that the Uniface Application is executed on or on a different (separate) machine.
on Windows Systems this is a service with the name: 'Uniface License Service' (cpwr.exe),
on Linux and Unix system, this service will show as 'cpwr'.
The license service is required for the use of license models: 1, 2, 5 and 6 described above. For feature model 3, the service is not required, but is optional.
With default configuration, the license service will be available at port 7188 of the server that the cpwr process is running on.
The DLM Client Connectors are library files of the license system that are required within the Uniface product.
For Windows applications, there are 3 library files required within the Uniface Application (driveletter:\<uniface_install_path>\common\bin\) to be able to connect to a license system or license file.
For 32-Bit Uniface Windows applications these will be: libdlm32.dll, softkey32.dll and tss.dl
For 64-Bit Uniface Windows applications these will be: libdlm64.dll, softkey64.dll and tss64.dll.
For Unix and Linux applications, dependable on the version of Linux and of Unix, Uniface requires one or two files in the Uniface Application directory (/uniface_install_path/common/bin) to be able to connect to a license system or file.
These files are: libdlm64.sl and/or libdlm64.so
It is strongly recommended to have the versions of the Client Connectors to be the same as the License Service!
Be notified: Uniface does ship with every Uniface patch these dlm client library files. This could mean that the license server will fall behind of versions updates! Check after installing of Uniface Patches, if the license service is still up to date and running the latest version of DLM.
DLM license Tools
Tools that will help in identifying the license server and managing the Uniface licenses.
The tool 'dlminfo' (on windows dlminfo.exe, on Unix this is dlminfo.sh) will gather all information to identify the server. This information is required for Uniface License Management in order to create a license file.
The tool 'dlm.exe' on windows and the tool 'dlmcv.sh' on Linux and Unix systems, is used to configure the license service. Among the configuration is the assigning of the license file or locate the license server when the license file is not on the local machine.