Please note
This document is intended for on-premises customers who set up their infrastructure locally.
Different guidelines apply to cloud installations. Contact our sales team for more information.
Infrastructure, servers, and installation
The 4ALLPORTAL is a client-server-based web application.
The servers on which 4ALLPORTAL runs provide graphical user interfaces and send data to users and other servers.
Infrastructure
A 4ALLPORTAL requires the following infrastructure:
a separate database
a separate mail server
The system resources required depend on the expected data volume and the number of parallel users (recommended resources).
The additional software tools required for format conversion are installed automatically.
Server & Installation
A 4ALLPORTAL version 4 or higher must be run on a Linux server that supports Docker. The choice of Linux distribution depends on whether it can run Docker.
The 4ALLPORTAL is configured and run in a Docker container. No additional installation of other packages is required on the host.
The Docker host can be deployed either on virtual machines or on physical servers.
Additional requirements
For installation and updates, 4ALLPORTAL requires server access via the Internet to the 4ALLPORTAL repository server. The required URL is:
Both the repository and registry are required for installation.
A productive 4ALLPORTAL requires SSL encryption (HTTPS).
The system does not support domain names that contain an underscore ("_").
Further information
Technical documentation: Setting up a 4ALLPORTAL
Database
Supported databases
A 4ALLPORTAL requires its own database. The following databases are supported for Core Engine Version 4 or higher:
MySQL 8.0.31 or higher
Microsoft SQL Server (MS SQL) 2014, 2016, 2017, and 2019
MariaDB 10.6 or higher (10.11 recommended)
Required permissions for Microsoft SQL Server
The 4ALLPORTAL database user requires permission to create and modify databases (role: dbcreator).
In addition, the database must contain the "Fulltext Search" extension.
Integrated security with MS SQL
Please note: "Integrated security" is not possible when using MS SQL under Docker.
Database performance
SSD:
We recommend installing the database on separate SSD storage or on its own server instance (at least 300 MB/s for reading/writing). This ensures optimal system performance.
Optimization:
Use tools such as MySQL Tuner to optimize your database.
For large systems with many user-defined configurations, you can analyze performance issues with tools such as Use The Index, Luke.
A large "innodb_buffer_pool_size" (e.g., more than 8 GB) requires a lot of memory, but often increases performance.
Fast hardware:
Depending on the number of assets and index files used, more CPU and RAM are required to process queries quickly.
Mail server
The 4ALLPORTAL requires access to an SMTP server. This is used for email notifications to users, for example for assigned tasks or available download packages.
The mail server is also required for internal user administration.
When creating new users, passwords can only be assigned by the users themselves, not by the administrator. To do this, they receive a welcome email with a link that allows them to set their personal password.
This applies unless an authentication provider such as LDAP or SAML is used.
If you want 4ALLPORTAL GmbH to set up your 4ALLPORTAL system, please provide the necessary information about your mail server in advance.
Mail server configuration
Before you start 4ALLPORTAL, the mail server access data must be entered in the configuration file (e.g., docker-compose.yml) in the environment section.
The following information is required for the configuration file:
Mail host
Mail port
Security type (e.g., SSL encryption)
Mail server username and password
Email sender address
Email sender name (e.g., "4ALLPORTAL")
Configuration without authorization is also possible.
After installation, you can find the mail server configuration in the Admin Snap-in under General System Configurations > System Settings > General Settings.
Changes to the mail server
If you make changes to the mail server, for example, use new access data or set up a new server, you must also adjust your configuration file (e.g., docker-compose.yml) accordingly.
Otherwise, email notifications from 4ALLPORTAL may not be sent properly.
Further information
Technical documentation: Default Docker Image & environment
File system
The file system must be mounted in a directory on the operating system.
The way in which the storage is connected has a significant impact on the import speed for new and modified assets.
Direct connections are preferable to network storage systems.
/cefs performance
All asset derivatives are stored in the "/tmp" directory in the file system under /4allportal/data/cefs after they are created.
They are made available for the front end from the cefs folder.
Please note: The faster the /cefs and /tmp directories are, the faster the conversions, downloads, and jobs will run.
Inode support
You can use inodes to support moving files within the mount. Inodes are unique identifiers for the files in your file system that are independent of file content, file name, and file path.
Please note: Your storage system must support inodes if anything other than 4ALLPORTAL is making changes to the file system. Adding new files does not require inode support.
Recommended resources
The resources required for your 4ALLPORTAL depend on the expected data volume and the number of parallel users.
In general, the following applies:
CPU requirements usually increase with the number of parallel users.
For RAM, the following rule of thumb applies: Multiply your RAM by a factor of 1.3 to calculate the resources required for your "/tmp" directory (further information).
Additional CPU and RAM resources are advantageous for many users or complex queries.
Compare your individual requirements with one of the four recommended resource packages: Small, Medium, Large, or X-Large.
Please note
The suggested resources apply to 4ALLPORTAL only. If you are using a shared system for database hosting, plan for these additional requirements separately.
The following requirements apply exclusively to on-premise installations. For cloud installations, contact the 4ALLPORTAL sales team to obtain the relevant information.
If your parameters do not match any of the scenarios, please contact us for individual advice.
"Small" Resource Package
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 |
Recommended resources
| minimum | recommended |
CPU cores / threads | 2 | 4 |
RAM (per server, GB) | 6 | 12 |
combined servers | 1 | 1 |
Storage connection:
direct: SAS, iSCSI, Fibre channel
network share: NFS, SMB
Please note
If you are converting a large number of very large assets, you may need more resources.
"Medium" Resource Package
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 |
Recommended resources
| minimum | recommended |
CPU cores / threads | 8 | 16 |
RAM (per server, GB) | 6 | 12 |
combined servers | 1 | 1 |
Storage connection:
direct: SAS, iSCSI, Fibre channel
network share: NFS, SMB
"Large" Resource Package
Requirements
| from | to |
managed assets | 500,000 | 2,000,000 |
changed / new assets per day | 100 | 4,200 |
parallel users | 10 | 30 |
asset size in file system (TB) | 2 | 15 |
Recommended resources
| minimum | recommended |
CPU cores / threads | 8 | 16 |
RAM (per server, GB) | 16 | 32 |
combined servers | 2 | 5 |
Storage connection:
direct: SAS, iSCSI, Fibre channel
network share: SMB
Please note
We recommend a clustered system.
"X-Large" Resource Package
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 |
Recommended resources
| minimum | recommended |
CPU cores / threads | 8 | 32 |
RAM (per server, GB) | 16 | 32 |
combined servers | 3 | 8 |
Storage connection:
direct: SAS, iSCSI, Fibre channel
network share: SMB
Please note
We recommend a clustered system.
Operating system and browser
Operating system and CPU
4ALLPORTAL currently only supports Linux configurations with the following specifications:
a 64-bit x86-64 or ARM CPU
Kernel version 3.10 or higher
support for KVM virtualization
in general: Support for Docker
Desktop App
The Desktop App enables native file access and offers features such as drag & drop to the desktop for improved usability.
If you are working with the 4App Desktop App, you need one of the following operating systems:
Windows x86 or x64 (all versions supported by Microsoft)
Mac x64 or Apple Silicon (all versions supported by Apple)
/tmp Performance
All asset derivatives are generated in the "/tmp" directory. It must therefore be sufficiently powerful and larger than 5 GB (minimum).
With 5 GB, a maximum of 5 GB can be processed and made available in parallel.
As a rule of thumb, multiply your RAM by a factor of 1.3 to calculate the resources required for your "/tmp" directory.
After creation, asset derivatives are stored in the "/cefs" directory of the file system and made available to the frontend.
Supported browsers
The following browsers are supported for accessing the 4ALLPORTAL:
Google Chrome
Mozilla Firefox (including ESR)
Safari
Microsoft Edge (Chromium-based)
Opera
Vivaldi
Please note
The current or previous version is approved in each case.
Keep your browser up to date to ensure that all functions are performed reliably.
💡 Frequently asked questions
Which Linux distribution is recommended?
Any distribution that can reliably run Docker is supported.
Can I install 4ALLPORTAL without Internet access?
No, installation and updates require access to the 4ALLPORTAL repository server at https://repository.4allportal.net.
Does 4ALLPORTAL support Windows server systems?
No, version 4 or higher runs exclusively on Linux systems.
What is the minimum size for the "/tmp" directory?
At least 5 GB. Ideally, it should be 1.3 times the amount of RAM.
Which browsers are supported?
Chrome, Firefox, Safari, Edge (Chromium-based), Opera, and Vivaldi – in their current or previous versions.