Client-Server (Uniface) Inactivity Timeouts
The ISRS client-server application was initially developed to require heavy PC resources and minimal server resources. Since 1995, the trend has been to reduce the client resource requirement and rely more heavily on the server, which typically will be a much stronger technology platform. In the transition from a more heavy reliance on the client (thick client) to server reliance (thin client), we have had to add additional resources (memory and CPU) to the server to maintain an acceptable level of performance.
The reduction of inactive connections will result in better memory and CPU utilization of the application/database server as well as reducing memory consumption on the client (PC). Additionally, from a security best practice perspective, the timing out of inactive sessions will reduce the risk of someone making use of an unattended client for inappropriate access to potentially sensitive ISRS data.
There is technology available within the Uniface software to relatively easily automatically timeout server side connections when a defined period of inactivity has been reached. This project will turn on the timeout feature that is available within the product. After 2 hours of application inactivity, all back end server connections will be closed and the client application will display a message that this has happened to which the user must click “Ok”. Once the “Ok” button is pushed the client application will terminate as well.
This effort includes:
- Provide appropriate communication to users prior to implementing the mandatory timeout of Uniface sessions.
- Define and implement appropriate message that will occur when a timeout occurs.
- The definition and rollout of required parameters and forms that will support this change.
- A phased rollout starting with the Office of the Chancellor as the initial/pilot site.
This effort does not include:
- A provision that would allow for exceptions to the timeout standard of 2 hours
