Connected On-prem server [Full launch]

This epic collects actions on completing Connected On-Prem server key functionalities such as REST APIs, improved server configurations, error reporting mechanisms, and client-server communication enhancements. After this epic is completed Connected On-Prem server is ready for production.

RnD Stories:

1. Rest API for Downloading Statistics
   • As a Customer Organisation License Manager, I want the on-prem license server to provide a REST API for downloading usage statistics, so I can monitor and analyze license consumption efficiently.
   • Acceptance Criteria:
     • REST API is available for authorized users.
     • Endpoint provides data in a structured format (e.g., JSON).
     • Data includes details like active licenses, usage times, products used.
2. Parametrized Server Configuration
   • As a Qt Company Customer Success Operator, I need the ability to configure server parameters dynamically through configuration files or an admin interface, so I can adapt the server settings to different deployment requirements without manual changes in code.
   • Acceptance Criteria:
     • Configuration can be updated using a designated configuration file or UI.
     • Changes are applied without requiring a complete server restart (if feasible).
     • Parameters include license sync interval, data upload interval, login renewal interval
3. Error Reporting from On-Prem to Cloud
   • As a Qt Company IT Operator, I want the license server to report critical errors to the cloud in real-time, so I can be notified and troubleshoot issues effectively.
   • Acceptance Criteria:
     • Error logs are automatically sent to a secure cloud endpoint.
     • The report includes error details, timestamps, and relevant system data.
     • An option exists to disable or customize the frequency of error reporting for privacy or compliance reasons.
4. Server Address Configuration from Client
   • As a Customer Organisation License Server Operator, I need to be able to configure the server address dynamically to connect to the correct on-prem license server instance, so that I can ensure uninterrupted communication and license checks.
   • Acceptance Criteria:
     • Clients can specify the server address through a configuration file, input field in Installer and CLI parameter to QtLicenseTool.exe.
     • Validations are included to check the format and reachability of the server address.
5. End-to-End Testing Suite for Product Readiness
   • As a QA engineer, I need to develop an end-to-end automated testing suite for the on-prem server, so that we can ensure all new features function as expected and are reliable for release.
   • Acceptance Criteria:
     • Tests cover REST API functionality, server parameter changes, error reporting, and server-client connectivity.
     • Tests include edge cases and stress testing scenarios.
     • A test report is generated after each run with detailed results.
6. Comprehensive User Documentation
   • As a technical writer, I need to produce comprehensive documentation for the new features of the on-prem license server, so that administrators and users understand how to use and configure them effectively.
   • Acceptance Criteria:
     • Documentation covers the setup of REST API usage, server and client configuration, and error reporting.
     • Step-by-step guides with screenshots or diagrams are included.
     • Troubleshooting tips and FAQs are provided for common issues.
7. Performance Optimization and Scalability Assessment
   • As a Qt Company License Server architect, I want to assess and optimize the performance of the on-prem license server, so that it can handle increasing loads without degradation.
   • Acceptance Criteria:
     • Performance benchmarks are established for typical and peak usage scenarios.
     • Optimization techniques (e.g., caching, efficient data handling) are implemented.
     • Server scalability guidelines are documented for deployment in larger environments.

​