How and What to request on Uniface Licenses

Purpose of this document is to give information on what is required to get your version of Uniface licensed.

From Uniface version 8.4.03 (M431) the licensing is done by means of Uniface DLM. Uniface DLM is being installed by running the setup of the Uniface distribution or separately from the download site.

What is needed to get Uniface Application licensed

For license management to create a correct license, the following information is required:

1. How the license (features) will be made available to the Uniface Application.
2. Use of the latest version of the licensing software.
3. The system information file as can be created by DLM
4. The product features that need to be licensed
5. Uniface Sales and License Management needs to be contacted.
6. How to let the application know where to find a license

1. How can you license Uniface application(s)

There are three methods of Licensing Uniface:

1. a license file on the system that you are running the Uniface application on (Node-Locked).  Node-locked licenses and/or features means that the license or license feature can be used ONLY on the machine that is mentioned in the file. UServer features are always node-locked, Client features can be.
2. a central server where multiple license (features) are distributed (Concurrent). Concurrent features means that that part of the license /feature can be shared to the maximum number mentioned in the feature, among all users who need one. Users will need to have the license server available when starting the Uniface Application.
3. a borrowed local license from a central license server (only Concurrent). Borrowing can be used when the client machine has a local installed Uniface application, but not always connected to the network where the license service is available.

2. Where to find the latest DLM licensing software

The latest version of DLM licensing software and how to configure it, can be found from the central DLM page: Licensing Technical Information

Be aware,

• Uniface 64-bit application can only talk to a local installed license service when DLM is also 64-bit.
• Uniface 32-bit application can only talk to a local installed license service when DLM is also 32-bit.
• IF the license service is addressed through a TCP path (7188@hostname), then it does not matter what the bit version is of DLM.

3. How to retrieve the required System Information

To retrieve the System Information file you will have to run the executable 'dlminfo' AFTER having installed the latest version of DLM.

For Microsoft Windows environments the location of 'dlminfo' will be:
C:\Program Files\Common Files\Compuware\dlminfo64.exe
or
C:\Program Files(x86)\Common Files\Compuware\dlminfo.exe

The location of the Output file, will be mentioned in the 'Command box' the executable has opened.

Regular places where to find it will be: (Be aware of the dot in the directory name!)

• C:\Users\administrator\.compuware\system_info.xml
• C:\Users\Public\.compuware\system_info.xml

For Linux environments, the executable is started by a Script that is called: 'dlminfo.sh' and is located in the install directory of DLM.
With default installation this script will be found at: /opt/Compuware/dlm/dlminfo.sh

The location of the Output file, will be mentioned in the Terminal Session the script was running in.

4. Which Uniface Features to order

Regardless of the way your license is made available to the users, Uniface requires parts of the product to be individually licensed.
To see a complete list of which parts of the Uniface Product needs licensing, see article: <ac:link><ri:page ri:content-title="Uniface License Features"></ri:page></ac:link>

The Uniface licensing models are based on the following pillars:

• Operating System
• Development
• Deployment
• Services

For Operating Systems you will have to Specify ALL the different Operating Systems where you want to run the Uniface Application on. This is for both Development as for Deployment required.

For Development and Deployment if you do not know what you need on features, perform the next steps:

• Add the following lines in your used ASN file (for development this will probably be IDF.ASN or IDE.ASN, for deployment it is the ASN file specified in the application shortcut or batch file) under the heading 'Settings'

[SETTINGS]
$putmess_logfile		=	c:\temp\log\putmess-%h_%u_%p.log
$ioprint			    =	64

• Run your application through the different parts that you can show you that your application is fully functional.
• Close your application
• Remove both lines from your ASN file.
• Open the created putmess-xxxxxxx.log file and find ALL lines that start with: 'Checkout' and write down all the features that are checked out.

For Services the procedure is the same as for finding the features for Development and Deployment above, but the ASN file that you will need to have these settings in, is defined by the userver.asn file, or by any other ASN file specified.

5. Contacting License Management

All the above information needs to be attached to an email, accompanied by a purchase order, to license.management@uniface.com

If for any reason, License Management or Uniface Sales needs more information, they will get in contact with you.

6. How to configure Uniface application to find the license

there are two ways to tell the Uniface Application where to find its license.

1. by means of configuring DLM to point to the license file or license server
2. by means of adding the location of the license in the used ASN file.

On how to configure DLM to use a local license file (Concurrrent usage), see knowledge article: How to configure DLM license Service
When DLM is used to point to a central license service, instead of 'browse to a license file on disk' ADD in the 'Add license' editbox the 'portnumber@license host name' like for example: 7188@licensesrv.local
The local installed Uniface application will find this configuration automatically.

When DLM is NOT locally installed on the client machine, or when it is required to have it centralized defined, adding the following line to the used ASN file will do:

[SETTINGS]
$license_options 	=	LM_LICENSE_FILE=7188@licensesrv.local,LM_NOTIFICATION=7,LM_TRANSCRIPT=7,LM_LOAD=uniface

Replace the 'licensesrv.local' for the fully qualified domain name of your license server.
The lm_notification, lm_transcript and lm_load are optional. See the Uniface library for description and usage of these settings.

When the license used is a NODE-LOCKED license for local use, then the line will be something like this:

[SETTINGS]
$license_options 	=	LM_LICENSE_FILE=C:\uniface\license\LICENSE.XML

Whenever the ASN settings are used, ALL Uniface executables, like, uniface.exe, idf.exe, ide.exe, udbg.exe and userver.exe, will require the $license_options setting in the used ASN file.