Uniface Router Monitor

Features

Once you have connected the Router Monitor to a Uniface Router, you can use it to perform the following tasks:

• Monitor the performance of the following:
  • The Uniface Router to which the Router Monitor is connected
  • The Uniface Servers that are using the Uniface Router
  • The clients that are using the Uniface Servers
• Dynamically change Uniface Router parameters (privileged user only). These parameters are the ones that the Uniface Router reads from the [SETTINGS] section and [SERVERS] section of its assignment file urouter.asn. The changes that you make are not written to the assignment file; they apply only to the currently- monitored Uniface Router.
  • Uniface Router settings—you can change the maximum number of clients, of Uniface Servers, and of Router Monitors that are attached to a Uniface Router, and you can change the value of $IOPRINT.
  • Uniface server types (USTs)—you can add new USTs, and change existing USTs, to modify the maximum number of Uniface Servers, maximum idle time, maximum number of requests, working directory, and command line switches.
• Stop and start Uniface Servers (privileged user only)
• Stop the Uniface Router (privileged user only)
• Reload the Uniface Router’s assignment file (privileged user only)—you can reload the assignment file if you have changed Uniface Router parameters dynamically and wish to revert to the original settings. You can also make changes to the assignment file while the Uniface Router is running, then reload the assignment file to make them active.

Restrictions and warnings

• NLS and double-byte characters not supported

  Like the Uniface Router, the Router Monitor does not provide NLS support. Clients have to use the same $SYS_CHARSET as the Uniface Router.

  Double-byte characters cannot be used, even if the user name is supplied in the assignment file. This means that server names, user names, and passwords cannot contain double-byte characters, for example Japanese characters, because you cannot log on to them using the Uniface logon form.

• Performance degradation using Router Monitor

  The Router Monitor is seen as another client in the Uniface Router. Each client has its own thread, including the Router Monitor. As each Monitor scans the other threads, it has to temporarily block that thread.

  If you are running multiple Router Monitors unnecessarily, stop the unnecessary ones and limit the problem by specifying the $MAXMONS assignment setting in urouter.asn.

• The Uniface Router can start exclusive servers and connect clients to them directly. As the clients are disconnected from the Uniface Router, they are removed from its administration and disappear from the view in the Router Monitor.

• If a security driver is defined in the client and/or Uniface Router, it is not used. If TCP is used for the connection to the Uniface Router, plain text user names and passwords are sent over the network during the Router Monitor admlogon operation and during the Start servers operation.

  To prevent this, consider using a TLS connection. This can be configured in the assignment files of the Router Monitor and the Uniface Router. For more information, see Configuring Uniface Applications to Use TLS.