| Operating system |
Microsoft® Windows Server® 2019 Version 1809 (OS Build 17763.2565) or later
Microsoft® Windows Server® 2022 Version 2009 (OS Build 20348.2031) or later
|
| CPU |
4 cores or more |
| RAM |
16 GB or more |
| HDD |
512 GB or more
Depends on the actual amount of data loaded into the application. Production environment may require more disk space, depending on the actual volume of data loaded into the application.
|
Browser (to access the ABBYY Timeline website) |
- Google Chrome 118 or later
- Microsoft Edge 118 or later
|
| Additional software |
- Microsoft Windows Subsystem Linux
If this Windows feature is disabled, the ABBYY Timeline Setup will prompt you to enable it. After that, you will need to restart your computer to apply the changes.
- Redis 6*
Important. Do not preinstall Redis on your own, as Timeline distributes Redis within the installation process. For details, see Before you begin.
- Microsoft .NET Framework 4.6.2*
- PostgreSQL 13*
- NodeJS 18.18.2*
- Microsoft Visual c++ 2015-2019 Redistributables (x64)*
- SMTP Server
ABBYY Timeline needs access to a running SMTP server to be able to send verification emails, notifications, invitations, and alerts, etc.
|
| Other requirements |
- To install ABBYY Timeline on Windows successfully, make sure the user you are installing under is able to set the PowerShell Execution Policy to RemoteSigned. This user must also have assigned Log on as a service right in Local Security Policy. For details, see Installing Timeline.
- Obtain Twilio account
You need to have a configured Twilio account if you want to enable SMS notifications feature in Timeline.
|
* included with the ABBYY Timeline installer.
Scaling guidelines
The exact calculation of necessary hardware requires multiple parameters such as data volume and usage patterns. However, the general guidelines could be defined as following:
- If the number of concurrent users is less than 10 and the data update frequency is once per day or less, a single server should be sufficient.
- For more users or more frequent data updates, a separate server for DBMS is recommended.