How to configure Uniface application Licensing
Purpose of this document is to give simplified steps on configuring Uniface to gain valid license.
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
Configuring license servers / license service will be described in another document.
The Uniface product is a product that requires a valid license.
The validation of the license is done by the Uniface application through the use of the DLM client license connector.
These client license connectors need to be configured to be able to find the licenses and license features it requires.
Uniface License features can be distributed to requesting applications by means of a license service (license server) or by accessing the license file directly, this dependable on the type of license feature(s) in the used license file).
Every license file is bound to the server/system it is requested for, but license features can be supplied to applications running on other workstations in case of concurrent licensed feature with the use of DLM license services.
Default Uniface installations on windows environments will also install DLM license software.
Configuring Uniface in such a way that it can get a valid license, can be done by two scenarios.
Scenario one: Configuring DLM Client
Find and start program (C:\Program Files (x86)\Common Files\Compuware\) DLM.EXE (it is advised to start it with "Run as administrator" to gain full access) on every system that will run the Uniface application.
In the 'Local Environment' tab select the 'Add..' button
- In cases of 'Node-locked' license files, use the link 'Browse for a license file on disk' and browse and open your local license file and press 'ok' in the 'Add license' window.
- In cases of 'Concurrent' license files, type in the 'drop down box': 7188@licenseservername and press 'ok'. (as the screenshot shows, the servername can be FQDN).
- In cases of multiple license servers and in case of redundant license servers, repeat the step for 'concurrent' license files for every license server.
In the top part of the DLM window, you will now see the license status and in the lower part it will show the features (per server) available in the license system.
By selecting a feature in the lower part and using button 'Status', you can check if the license feature is ok and can be checkout by Uniface applications.
Unix / Linux Systems
Find and start program ./dlmcv.sh (default in /opt/Compuware/dlm/
- Select C for Client
- Select L for License path
- A to Add
- in case of 'Node-locked' license file type path and filename and press <enter>
- in case of 'concurrent' license type port@hostname (7188@servername)
- in case of multiple license servers and in case of redundant license servers, repeat step b for every license server.
- press <enter> to return to ---Client command List---
- Select V for Verify
- Enter for feature name: uclient
- Enter for version: 9
This should give you the line: "This feature is working properly" if it is OK and can be checkout by Uniface applications.
- Hit <enter> until back to the prompt.
Scenario two: Configuring in the Uniface applications ASN file
on systems where no DLM license software is installed and a Uniface application (idf, ide, uniface, userver) is to be used, it is possible to let Uniface know by means of the entry $license_options in the ASN file, where to find licenses.
By default this would mean for:
- Development the idf.asn or ide.asn file in <installdir>\uniface\adm\
- Runtime/deployment the asn file specified in the commandline switch /asn=......\runtime.asn
- userver the userver.asn file in <installdir>\uniface\adm\
or any other ASN file that is defined in the command line of the application.
Open this ASN file with a standard text editor (notepad.exe or vi) and add to section SETTINGS when using single license server:
When using multiple license servers or in situation of Redundant license servers:
In case of a local license file (node-locked):
Notify, that by adding this to the userver.asn file, you may need to restart the urouter process to have this take effect.