Table of Contents
Installation check
The installation check section performs various tests to ensure the correct installation of the system as well as to verify the presence of all the required libraries.
Several of these parameters are only available from PMA.core 1.1 and onwards, including: Operating System, IIS version, Application init time, Allow nested root directories, Application path, and Recognized file extensions.
The Webforms Timeout value indicates the amount of time after which an idle user gets logged out of the administration UI of PMA.core.
See below for a comprehensive list of all paramters and checks performed by PMA.core
Settings
| Parameter | Description |
|---|---|
| Operating System | The operating system version |
| IIS Version | The version of the IIS server |
| PMA.UI Version | PMA.UI was found and the version |
| .NET Framework | The .NET version found |
| Application init time | The time it took for the PMA.core to initialize properly |
| Allow nested root directories | Whether the server is configured to allow for nested root directories |
| Session timeout | The inactive timeout period for a PMA.core session |
| Webforms timeout | The inactive timeout period for the admin GUI |
| Current user | The windows user that is running the server |
| Database connection string | The main database connection |
| Trace database connection string | The secondary database connection used for logging |
| Application path | The windows path the server is running |
| Cache path | The path used by PMA.core for caching |
| Log path | The path used by PMA.core for logging |
| Recognized formats | All known slide formats by PMA.core |
Checks
| Check | Description |
|---|---|
| Database schema | Checks that the databases are readable and the schema is correct |
| Database write | Checks that the databases have write permissions |
| Cache directory create file | Checks whether PMA.core has permissions to create files in the cache folder |
| Cache directory delete file | Checks whether PMA.core has permissions to delete files in the cache folder |
| Cache directory create subdirectory | Checks whether PMA.core has permissions to create folders in the cache folder |
| Cache directory delete subdirectory | Checks whether PMA.core has permissions to delete folders in the cache folder |
| Log directory create file | Checks whether PMA.core has permissions to create files in the log folder |
| Log directory delete file | Checks whether PMA.core has permissions to delete files in the log folder |
| IIS Logfile configuration | Checks whether PMA.core can locate and has access to the IIS log files |
| TraceHandler available | Checks whether PMA.core has read and write access to the trace database |
| Zeiss Image Library | Checks whether the Zeiss Image Library can be found and is configured properly |
| Check PMA.core API | Checks whether the PMA.core API is accessible and configured properly |
Audit trail vitals
| Audit trail vitals | Description |
|---|---|
| Trace database write | Checks if the trace (audit trail) database is writable |
| Oldest recorded entry | The oldest entry in the audit trail if found]] |
| Newest recorded entry | The newest recorded entry in the audit trail if found |
| # of record in audit trail | The number of audit trail records |
Storage Checks
In the storage checks tab you can inspect the storage used by all components of PMA.core. Those are:
| Storage | Description |
|---|---|
| Tile cache size | The size of the folder that is used as tile cache |
| Azure/Amazon S3 cache size | The size of the folder that is used as cache for cloud operations |
| IIS folder size | The size of the folder in which PMA.core is installed |
| SQL server database size | The size of PMA.core's database. This includes the users, forms, form data as well as the audit trail |
