User Tools

Site Tools


system_requirements

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
system_requirements [2022/05/04 11:53]
antreas
system_requirements [2022/08/29 13:27] (current)
angelos [Operating system and software prerequisites]
Line 2: Line 2:
  
  
-==== On-premise installation ====+==== Operating system and software prerequisites ==== 
 +In principle any version of Windows + Internet Information Server (IIS) will do. We've got the software to 
 +run on IIS Express edition for demonstration purposes. We offer the following formal guidelines:​ 
 +^ Component ​     ^ Minimum ​      ^ Suggested ​         ^ 
 +| Operating System ​   | Windows 2016 Server ​    | Windows 2022 Server | 
 +| Web Server| IIS 7.5 | IIS 10.0| 
 +| .Net Framework | 4.7.2 | 4.7.2 | 
 +| RDBMS | Microsoft SQL Server 2014| Microsoft SQL Server 2019| 
 + 
 +=== Additional comments regarding SQLServer === 
 +The application requires the **Full-Text Search feature to be installed and available**. 
 + 
 +SQL Server Express can be used but poses two limitations which have to be taken into account: 
 +  - The maximum database size cannot exceed 10GB. 
 +  - Only one CPU core is used to execute queries. 
 + 
 + 
 +==== On-premise installation ​hardware requirements ​====
  
 ^ Component ​     ^ Minimum ​      ^ Suggested ​         ^ ^ Component ​     ^ Minimum ​      ^ Suggested ​         ^
Line 19: Line 36:
 | Network interface ​   | 100MBps | 1Gigabit| | Network interface ​   | 100MBps | 1Gigabit|
  
-=== Additional comments regarding SQLServer ​=== +=== Security considerations ​=== 
-SQL Server Express can be used but poses two limitations which have to be taken into account: +PMA.core does not offer any intrusion detection system. When installing the system on premises, it is highly recommended ​to review the security policies of the host computer and the network it belongs to and configure it accordingly
-  - The maximum database size cannot exceed 10GB+ 
-  - Only one CPU core is used to execute queries.+=== Date and time configuration === 
 +PMA.core relies on the host computer'​s date and time for all operations that involve the current time, such as logging events. Hence, in order for the system to operate correctly and reliably, it is mandatory ​to configure the system'​s time correctly and have it periodically sync with a time server.
  
 ==== Installation on an AWS Virtual Machine ==== ==== Installation on an AWS Virtual Machine ====
Line 45: Line 63:
 Additionally,​ slides can be stored either on local disks attached to the VM or in Azure Blob Storage. Additionally,​ slides can be stored either on local disks attached to the VM or in Azure Blob Storage.
 When possible, it is recommended to prefer [[https://​docs.microsoft.com/​en-us/​azure/​storage/​blobs/​data-lake-storage-introduction|Azure Data Lake Storage Gen2]] over plain Azure Blob Storage, as this type of service performs directory management operations, such as moving and renaming slides and directories,​ a lot faster. When possible, it is recommended to prefer [[https://​docs.microsoft.com/​en-us/​azure/​storage/​blobs/​data-lake-storage-introduction|Azure Data Lake Storage Gen2]] over plain Azure Blob Storage, as this type of service performs directory management operations, such as moving and renaming slides and directories,​ a lot faster.
 +=== PMA.core cache requirements === 
 +Regardless of the choice or combination of the storage media used, the system requires some space on 
 +a local or network disk where cache data will be stored and accessed. PMA.core allows you to define 
 +the cache retention policy and informs you about it's size. As a general rule of thumb, the cache 
 +capacity should be around 10% of the total size of the available whole slide images.
 ==== Client Side ===== ==== Client Side =====
  
system_requirements.1651654387.txt.gz · Last modified: 2022/05/04 11:53 by antreas