Page tree

Uniface support announcements and messages , Information , Documentation , Samples , Forums , Support pages
are available via our online Uniface Community site:
Life cycle information:
Uniface product availability information:
Support Processes and Contact Information:
Uniface Downloads:
Patches, service packs can be downloaded via
after registration
For example Uniface 10.3.02 for Windows:
The zip files are the distributions:
The MD5 and SHA-1 files can be ignored:
They are more usual in the UNIX/LINUX world.
MD5 and SHA-1 can be used to check zip size:

Before Installing Uniface
There is Uniface installation and configuration information placed online.
This online documentation is placed on
There are also several pdf files per version including installation guides:
In the online library there is a section Installing and Configuring Uniface.
In Getting Started there is also info on installing , developing and there are tutorials.
In Uniface deployment you can only run applications developed with the Uniface development environment.
Using the Uniface development environment one can test the objects created.
Development is available in 32-bits version for Windows (W32).
Deployment is available for several platforms:
This is documented in the Uniface product availability information:
It is not needed to uninstall older Uniface versions.
When using multiple Uniface versions use different port numbers for urouter and Tomcat for each version.
Extract the zip file with the electronic distribution to a temporary directory , study the readme file and run setup.exe.

During installation
In the Account for UServer and Account for the URouter screens from the Uniface Setup User name and Password must be specified:
When userver and urouter User Accounts already exist use their existing passwords.
When the userver and urouter User Accounts are new do not forget to apply password policy for the password specified.
Use accounts with names like userver , urouter with for example password Un1face! in the installation so password policy is applied.
Some configuration files will contain the UServer user and password specified :
Two examples:
web.xml in {unifaceinstalldir}\uniface\webapps\uniface\WEB-INF\web.xml uses the userver account in the MIDDLEWARE parameter:
A network path in a client asn file to connect to the urouter process:
$TCP TCP:localhost+13001|userver|Un1face!|myust
It’s not so good to have your own Windows password in configuration files.

After installation
After running setup "as Administrator" one can modify the Permissions on the Uniface installation folder after installation:
Allow modifying configuration files , add files to the virtual web directory, write log files , ...
If you choose not to do this for security reasons you'll need your own local configuration files to change settings.
Configuration files are for example usys.asn, usys.ini, wasv.asn, idf.asn in in {unifaceinstalldir}\uniface\adm
Specifying your Uniface license
The Uniface processes must be able to find a license else they will not start.
One way is to add a line in the section [SETTINGS] from the file usys.asn in
$license_options LM_LICENSE_FILE="C:\Users\windowsuser\Documents\mylicense.xml", LM_NOTIFICATION=3
$language USA
Another way is to add the license file via the Distributed License Management program in “Run as administrator” mode.
The “Run as administrator” mode is required for services running on Windows.
Restart the urouter process in the Windows services after specifying the license.
After installation there should be a folder like
C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Uniface\Uniface 10.3.02 Development\Uniface
with shortcuts including a shortcut for development.