1. Describe your environment: What is your industry? What is your role in your organization? Describe your stakeholders.
---
2. We are RV&S, server-sided Release 12.5.0.2, Client-sided in Preparation of rolling out same Version.
Former Version used has been server-sided 11.2, client-sided 10.7 and 10.9
3. Describe the problem you are trying to solve. Please include detailed documentation such as screenshots, images or video.
Today server-sided a Policy is to define, which Client Version are allowed to connect. But the check isn't done on the Server. Policy for Server 12.5 is a Client of at least 11.0, recommended is 12.4 or higher.
If now a client try to connect, Server open Connection, is sending back the Policy to Client and Client identify whether it fulfill Policy Definition. IF not, Client throw an Error and refuses to show Server Data.
Problem is, that Server still hold the Connection in the Background, incl. counting the number from that Client. IF now an automated System does not have correct Client Version, it connects as often as it is defined as maximum Client Connection.
4. What is the use case for your organization?
Especially for Server Version 12.4 and later, Connections from older Clients are critical and can lead to Performance Loss, and -before CPS 12.5.0.2- to Deadlock Situation of Server Application.
It is inefficient to let the Client check the Policy, since today's Implementation for each check create a Connection on the Server and hold the Connection till defined automatic disconnect.
This block Resources on the Server. The check should be done Server-sided, combined with not creating a connection if Policy is not fulfilled.
5. What business value would your suggestion represent for your organization?
- Easier Administration of Client Connections.
- Rejection of Clients not fulfilling the policy
-
