, Apr 06, 2021
The Uniface Router Monitor is a small but practical Uniface Windows application that you can use to fine-tune parts of your running application. It can monitor the Uniface Router to which it is connected and the Uniface Servers that are using that Uniface Router, as well as the clients that are using those servers. Moreover, it can dynamically change Uniface Router parameters, reload the Uniface Router's assignment file, start and stop Uniface Servers, and stop the Uniface Router.
All of this can come in very handy, for example when your application is experiencing problems in the area of response times.
This useful tool has been around for quite a while and has proven its worth in application setups that involve TCP connections between the Uniface Router, its Servers, and their clients. The introduction of the new TLS connector in Uniface 10.3 opened up the possibility for more secure connections, so the need arose to upgrade the Router Monitor to handle those more secure connections.
In Uniface 10.4, the Router Monitor API will be enhanced to make it fully support both TCP and TLS connections. This involves a change in the descriptors of some entities that are used as parameters to some of the Monitor API operations. Fields that represent the port number for a TCP connection will be increased in size, to accommodate the TLS profile that accompanies the port number of TLS connections. In addition to the API change, the affected fields in the Router Monitor's Form components will be made larger so that the Router Monitor has room to display the port and profile combination for TLS connections.
The Router Monitor's Start Server utility will also get a convenient enhancement, providing an easy way to choose one of the available connections when starting a new server:
In brief, if you intend to use the more secure TLS connections between your application's Router(s), its Servers and their clients, then the 10.4 Router Monitor will offer the same services for your setup that you were already used to for setups that use TCP connections.
Important note regarding applications that use the Router Monitor API
If you have a custom application that uses the Router Monitor API then, like the Uniface Router Monitor, that application will need to be recompiled when you move to Uniface 10.4. This will require only a few simple migration steps:
- Import the updated definitions of the affected entities. These will be available in uniface/misc/uroutmon_entities.xml, under the 10.4 installation directory.
- Recompile your application.
Like for the Uniface Router Monitor, you may also want to make small updates to some of your application's Form components, specifically the Form components that show connection port numbers. You could increase those fields in size, to make them wide enough to show the combination of port number and TLS profile, for TLS connections.
More information will be available in the Uniface 10.4 documentation, under What's New in Uniface 10.4.