# System requirements
The 4ALLPORTAL is a client-server based software product. The server(s) which run the 4ALLPORTAL provide graphical user interfaces and send data to users and other servers.
The 4ALLPORTAL requires a separate database, a separate mail server, and a file system.
An installation is possible either on virtual machines or on physical servers. We advise an installation process of your database on a separate SSD-storage or a separate server-instance. This ensures an optimal performance of your system.
The hardware which runs the 4ALLPORTAL has to be sized depending on the following:
- number of managed assets (pictures, videos, documents, etc.)
- renewal rate of the assets per day
- growth rate of the assets per day
- parallel users
- size and type of the assets in the file system
For details and possible scenarios, check our hardware requirements.
# Access to the 4ALLPORTAL Repository server
Please allow the 4ALLPORTAL server access via internet to the 4ALLPORTAL Repository. The required URL is https://repository.4allportal.net.
If you use a proxy, please inform the 4ALLPORTAL support.
# Database
The 4ALLPORTAL requires a separate database. We currently support the following:
CoreEngine up to latest 3.x version
- MySQL 5.7.x, MySQL 8.0.31 or later (requires Core version 3.10.38)
- Microsoft SQL Server (MSSQL) 2014, 2016, 2017 and 2019 (restricted)
- MariaDB 10.4 or later (10.11 recommended)
We advise an installation of your database on a separate SSD-storage or a separate server-instance. This ensures a better performance of your system.
Required permissions for Microsoft SQL Server: The 4ALLPORTAL database user requires the permission to create and alter databases (role: dbcreator). Additionally, the database requires the extension Fulltext Search.
# Mail server
From version 3.2 upwards, the 4ALLPORTAL requires a separate mail server. It is necessary for a running 4ALLPORTAL to provide and configure it during installation.
Note: If your system is set up by 4ALLPORTAL GmbH, please pass the necessary information about your mail server to 4ALLPORTAL GmbH in advance.
# Technical background
The 4ALLPORTAL needs a separate mail server for the implementation of our current user management. When creating new users, passwords can only be assigned by users themselves, not by the administrator. Users receive a welcome e-mail with a link for the assignment of their personal password.
# Configuring the mail server
The configuration is usually done using the installation manager (e.g. Windows Server or CentOS Installation) before installing the 4ALLPORTAL.
# Required information
- host
- port
- security, e.g. SSL encryption
- user name and password (mail server)
- e-mail sender address
- e-mail sender name, e.g. "4ALLPORTAL"
After installation, you can view and adjust your configurations in the admin snap-in General system configuration/System settings/Mail server in the administration area of your 4ALLPORTAL.
Note for Docker systems: Before starting a Docker container, add the mail server to the configuration file docker-compose.yml in its "environment" section.
Mail server changes: If you want to make changes (e.g. mail server credentials) or use a new one, make sure to configure the changes in the 4ALLPORTAL immediately. Otherwise e-mail notifications from the 4ALLPORTAL may not be sent properly.
# File system
- the filesystem needs to be mounted into a directory on the operating system
- you can make use of inodes to support moving files within a 4ALLPORTAL mount
The way the storage is connected has a significant effect on the import speed for new and changed assets. Direct connections are preferable to mounted storage systems.
# Inode support
Your storage system has to support inodes to transfer data via a file system mount (for example Samba-Mounts). Inodes are unique identifiers for files of your file system, that are independent of file content, file name and file path.
# Hardware requirements
The following hardware advice is divided into four scenarios. If your parameters are not covered in one of the following scenarios, please contact us for individual advice.
# Scenario 1
# Your requirements:
| from | to | |
|---|---|---|
| managed assets | 1 | 100.000 |
| changed / new assets per day | 1 | 800 |
| parallel users | 1 | 10 |
| asset size in file system (GB) | 1 | 750 |
# Our recommendation:
| from | recommended | |
|---|---|---|
| CPU cores / threads | 8 | 12 |
| RAM (per server in GB) | 16 | 32 |
| combined servers | 1 | 1 |
| storage connection | direct: SAS, iSCSI, Fibre channel mount: NFS, SMB |
# Scenario 2
# Your requirements:
| from | to | |
|---|---|---|
| managed assets | 100.000 | 500.000 |
| changed / new assets per day | 50 | 1.200 |
| parallel users | 5 | 20 |
| asset size in file system (TB) | 1 | 5 |
# Our recommendation:
| from | recommended | |
|---|---|---|
| CPU cores / threads | 12 | 16 |
| RAM (per server in GB) | 32 | 64 |
| combined servers | 1 | 1 |
| storage connection | direct: SAS, iSCSI, Fibre channel mount: NFS, SMB |
# Scenario 3
# Your requirements:
| from | to | |
|---|---|---|
| managed assets | 500.000 | 2.000.000 |
| changed / new assets per day | 100 | 4.000 |
| parallel users | 10 | 30 |
| asset size in file system (TB) | 2 | 15 |
# Our recommendation:
| from | recommended | |
|---|---|---|
| CPU cores / threads | 12 | 16 |
| RAM (per server in GB) | 32 | 64 |
| combined servers | 2 | 5 |
| storage connection | direct: SAS, iSCSI, Fibre channel mount: SMB | |
| clustered system |
Note: We recommend running the database management system on a separate server and / or to store the database files on SSD for optimum speed.
# Scenario 4
# Your requirements:
| from | to | |
|---|---|---|
| managed assets | 2.000.000 | 10.000.000 |
| changed / new assets per day | 400 | 10.000 |
| parallel users | 20 | 100 |
| asset size in file system (TB) | 5 | 100 |
# Our recommendation:
| from | recommended | |
|---|---|---|
| CPU cores / threads | 12 | 16 |
| RAM (per server in GB) | 32 | 64 |
| combined servers | 3 | 8 |
| storage connection | direct: SAS, iSCSI, Fibre channel mount: SMB | |
| clustered system |
Note: We recommend running the database management system on a separate server and / or to store the database files on SSD for optimum speed.
# Operating Systems
We currently support the following operating systems:
- Linux System - CentOS 7, RedHat RHEL or Debian (the latest release)
- The CentOS project is end of life on 2024-06-30 and stops receiving feature update on 2020-12-31, therefore we discourage its usage
- Windows Server 2012 R2 (Powershell Version 5.1 or later required) (restricted)
- Windows Server 2016 (Powershell Version 5.1 or later required) (restricted)
- Windows Server 2019 (Powershell Version 5.1 or later required) (restricted)
# Supported web browsers
Please use one of the following supported web browsers:
- Google Chrome (latest or one previous version)
- Mozilla Firefox (latest or one previous version + ESR)
- Safari (latest or one previous version)
- Microsoft Edge (latest and last version 18 or one previous version)
- Edge Chromium
- Opera
- Vivaldi (latest or one previous version)
- No support for Internet Explorer (end of support was in January 2020)
Note: Please keep your browser up-to-date to make sure all features work successfully.
# Software requirements
- Currently the 4ALLPORTAL needs specific versions of various software:
- The dependencies are installed during installation.
- On Linux they have to be available using a package-manager.
- On Windows you need to be able to run PowerShell scripts.
- You will need admin/root privileges for installation.
- Our Desktop Client has a minimum MacOS X and Windows version.
- To run a 4ALLPORTAL on docker, you need a working docker installation.