What's New in Uniface 10.3.03
Uniface 10.3.03 features a new licensing management system as well as many infrastructure and currency enhancements.
Sentinel License Manager
The Uniface Community Edition already makes use of Sentinel license management, but this is now extended and enhanced to support the Uniface Enterprise Edition for both development and deployment.
The Sentinel Rights Management System (RMS) can be used for the Uniface Enterprise Edition to enforce and manage licensing in a multi-user environment. The Sentinel License Manager is available for Windows, Unix, and Linux platforms.
Registered users of the Enterprise Edition can download it from https://download.uniface.com/ and obtain the appropriate Sentinel license by contacting their Uniface representative.
Note: Uniface DLM continues to be supported for existing customers, but new customers will automatically be using the Sentinel License Manager.
Uniface Router Monitor and API Enhancements for TLS
The Router Monitor can now show TLS connections with profile strings of up to 54 characters. The UROUTMON API has been updated to support this change and the compiled signature of the UROUTMON API service is now delivered in the uroutmon.uar archive instead of being hard-coded.
For custom-built applications that use the UROUTMON service, you need to migrate to the new definitions:
- Import InstallDir/uniface/misc/uroutmon_entities.xml, which contains the updated definitions of the Router Monitor's entities.
- Recompile your Router Monitor application's components and entities.
uroutmon.uarto the [RESOURCES] section of the application's assignment file.
Upgrade to Tomcat 9
The version of Apache Tomcat delivered with the Uniface installation has been upgraded to Tomcat 9. The following changes may affect your web server configuration:
- Java 8 or higher is now required. If you are running on Java 7 or older (for example, for Tomcat 8.0 or 8.5), you must upgrade Java to at least version 8. The OpenJDK provided with Uniface has already been upgraded to Java 8.
- Support for
SameSitecookie attributes. Browsers that support the
SameSiteattribute can prevent other domains (or hackers) from reading the cookies set by your application (for example, to store session information, user preferences, and so on). You can set this globally for your web application. For more information, see Enabling SameSite Cookie Support .
- Supported Servlet specification is now 4.0, which requires that the web server be compliant with the HTTP/2 protocol. Most modern web browsers are already compliant with this protocol.
The Uniface servlets Web Request Dispatcher (WRD) and SOAP Request Dispatcher (SRD) have also been updated to support the Servlet 4.0 specification, as well as 3.0. You are free to use any web server you desire, but it must be compatible with one of these Servlet specifications for Uniface to work with it. For more information, see Java Servlets..
The ISAPI Redirector has been updated. The default value for attribute secretRequired is now true for AJP connectors that the ISAPI Redirector communicates with. However, the default Uniface configuration for this connector explicitly sets it to false to ensure a smooth out-of-the box experience. To take advantage of the extra security provided by this attribute, see
Configure Security for the ISAPI Redirector as well as Microsoft IIS and Uniface and Configuring Microsoft IIS to Use Tomcat.
New SLE 2.0 connector for SQLite.
A new version of the SQLite connector is available, with new and changed data mappings for Uniface packing codes B, M1-M8, N, W255 and higher, and W*.For more information, see SQLite Data Packing.
OpenSSL executable now delivered with Uniface on Windows
To make it easier to generate keys and certificates for TLS, Uniface now provides the Windows OpenSSL executable in the \common\bin directory. For more information, see Creating Certificates.
Functionality discontinued since Uniface 10.3.02:
The Buildozer service for building mobile apps is no longer supported
Since the introduction of Uniface mobile apps, the mobile development world has evolved and today there are many hybrid app frameworks for building cross-platform mobile apps around a web interface. You can now develop a responsive mobile app using Uniface and use your choice of hybrid app framework to package it into a deployable mobile app.
Mobile applications have joined the web application family, and no longer require a separate license feature.
For more information, see Developing Mobile Apps.
Application Shell for Mobile App (APM) is no longer supported
The purpose of the mobile application shell was to gather information for Buildozer. Since Buildozer is no longer supported, the mobile application shell is also no longer required and the APM application shell type is considered invalid.
When a mobile application shell is imported into this version of Uniface, the Shell Type property value
APM is marked as invalid and there is no longer a Build App action. Instead, you can Compile the application shell which produces a Windows desktop application shell. This is of no use to a mobile applciation.
For more information, see Shell Type .