System requirements - 2024.06
This document describes requirements and recommendations for running Easit GO, release 2024.06. If you have questions or need other environments, you can contact Easit support at support@easit.se. Our ambition is to support the latest versions of operating systems and necessary software as soon as they are generally available and have been tested.
Client
Easit GO is completely web-based, and all that is needed to use the system is a web browser. The product does not depend on any browser plug-in or other external software. For the best experience, we recommend that you use the latest version of the following browsers:
- Google Chrome
- Mozilla Firefox
- Edge Chromium
- Safari (macOS/iOS)
For the best experience, a screen resolution of 1920x1080 or greater is recommended.
Server
If you as a customer choose to run our server on-premise, the technical platform needs to meet certain requirements in order for support and maintenance to be obtained. Performance is important and is affected by many factors. In additions to the server requirements, we have also collected some recommendations around performance in the text below.
Operating System
The recommended operating system is windows, in this release of Easit GO, the following versions are supported:
- Windows Server 2019, 2022
Standard edition or higher.
Database
Easit GO needs a database for storage. SQL Server is the recommended database, and in this release of Easit GO, the following versions are supported:
- Microsoft SQL Server 2017, 2019, 2022 and Azure DB
Web, Standard, Enterprise & Datacenter editions, with the latest service pack installed.
Web server
Microsoft Internet Information Server (IIS).
Application Server and Java
Easit GO is a Spring Boot application, and therefor a java application with an embedded Apache Tomcat server.
- Tomcat 10
- Java 17
Support for other server configurations
We do support Linux. Please contact Easit if you have any questions regarding supported server configurations.
CPU, RAM and Storage requirements
These recommendations apply as starting values for a physical server used only for Easit's applications and connected to a network with good bandwidth. Easit GO is a general system with many configuration options and depending on which workflows are run, how many users are added and how intensive the use is, adjustments may need to be made. Disk system size requirements are greatly affected by the amount of attached documents.
Application server
| Start configuration for 50 Agents | |
|---|---|
| HDD | RAID system with > 20GB |
| RAM | > 10 GB |
| CPU | Modern multicore processor |
| Start configuration for 100 Agents | |
|---|---|
| HDD | RAID system with > 20GB |
| RAM | > 13 GB |
| CPU | Modern multicore processor, atleast 4 cores |
| Start configuration for 200 Agents | |
|---|---|
| HDD | RAID system with > 20GB |
| RAM | > 20 GB |
| CPU | Modern multicore processor, atleast 4 cores |
Database server
The hardware needs of the database server roughly follow the needs of the application server. Measure resources/performance, and follow the vendor's recommendations for configuring the database to achieve good performance.
For good performance, the network latency between the application server and database should be low, as there are many calls in between these servers. A good guideline is a delay of less than 1ms per call. Contact Easit if you are unsure and want help with recommendations or measurement.
Virtualization
Easit GO supports virtualized and cloud environments. In cases where the server is run in a virtualized environment, the virtual server must deliver the same performance as our recommendations above. It is then also important to follow the supplier's recommendations (for Java performance, for example). Feel free to contact Easit for further advice.
Antivirus programs, proxies and filters
Antivirus programs and filters that scan network traffic in real time will negatively affect system performance. Even live scanning of files (antivirus) will affect performance negatively as it continuously scans our cache files.
Our recommendations:
- Antivirus running in nightly batch jobs OR Antivirus activated with program folders for our application omitted from active scan.
- The server has a security level that restricts users from running anything directly on the server
- Proxies are not used, or are excluded for our application.
- Functionality for filtering network traffic are not used on traffic between components of our application.