System requirements
This section describes the hardware and software requirements of Docuflair when you plan to run it on physical hardware.
Hardware requirements
Section titled “Hardware requirements”Docuflair server
Section titled “Docuflair server”| Component | Requirement | Notes |
|---|---|---|
| Processor | One of the following 64-bit processor types: | |
| an Intel processor supporting the Intel 64 architecture, or | ||
| an AMD processor supporting the AMD64 platform. | Intel Itanium IA64 processors are not supported. | |
| Up to 2 supported processor sockets are recommended on physical machines. | ||
| Memory | At least 8 GB (up to 256 GB) | The memory needed depends on the Docuflair licence enabled |
| and on the document throughput for scanning and printing | ||
| Page file size | The minimum page file value: 25% of the installed memory. | |
| Disk space | At least 30 GB free on the drive you install Docuflair on. | At least 2 GB free is required on the system drive. |
| Screen resolution | 1024 × 768 pixels (XGA) or higher | Full HD recommended |
| File system | NTFS | Required for the system partition and for the drive Docuflair is installed on |
Docuflair Embedded App
Section titled “Docuflair Embedded App”The following hardware platforms are supported:
- Epson Open Platform (EOP)
- Kyocera Hybrid Platform for Advanced Solutions (HyPAS)
- Kodak Alaris Scan Station EX 750 Plus
- Canon Scan Front 400
- Sharp (OSA)
- Xerox Extensible Interface Platform (EIP)
Software requirements
Section titled “Software requirements”| Component | Requirement |
|---|---|
| Docuflair (all editions) | Windows Server 2016, 2019 or 2022 |
| Standard or Datacenter, or | |
| a 64-bit edition of Windows 10 or Windows 11 | |
| (for test installations) | |
| Runtime | .NET Runtime 4.8 or later |
| Production use (all editions) | Microsoft SQL Server 2014 or later |
| Internet Information Server 7.0 or later |
Virtualisation
Section titled “Virtualisation”Running Docuflair in production on hardware virtualisation software is supported only when all of the following conditions are met.
The hardware virtualisation software runs on one of the following:
- Any version of Windows Server with Hyper-V technology, or Microsoft Hyper-V Server
- Any third-party hypervisor tested under the Windows Server Virtualization Program.
For Docuflair deployments the following applies:
- All Docuflair server roles are supported on a virtual machine.
- You can combine virtual machines running Docuflair with host-based failover clustering and migration technologies, provided the virtual machines are configured so that no state data is saved to or restored from disk when they are moved or taken offline. Any failover activity at hypervisor level must result in a cold start when the virtual machine is activated on the target node. All planned migration operations must either result in a shutdown and a cold start, or be carried out as an online migration using a technology such as Hyper-V (live migration). Virtual machine migration is the hypervisor vendor’s responsibility, so make sure your hypervisor vendor has tested and supports the migration of Docuflair virtual machines. Docuflair supports live migration of these virtual machines with Hyper-V.
- Only management software may be deployed on the physical host machine (antivirus software, backup software or virtual machine management software, for example). Do not install further server-based applications on the host machine (such as Exchange, SQL Server, Active Directory or SAP). Reserve the host machine for running the virtual guest machines.
- Some hypervisors offer functions for creating snapshots of virtual machines. Snapshots capture the state of a virtual machine while it is running and allow it to be rolled back to that state later. Snapshots are not application-consistent, however. Using them can have unintended and unexpected consequences for a server application that manages state data — as Docuflair does. Creating snapshots of a Docuflair virtual guest machine is therefore not supported.
- Many hardware virtualisation products let you determine how many virtual processors are assigned to each virtual guest machine. The guest machines’ virtual processors share a fixed number of physical processors in the physical system. Docuflair supports a ratio of virtual to physical processor cores of at most 2:1; a ratio of 1:1 is recommended. A dual-processor system with quad-core processors, for example, contains a total of 8 physical processor cores in the host system. In a system with that configuration you should assign no more than 16 virtual processors in total across all virtual guest machines.
- When calculating the total number of virtual processors required for the host machine, take the I/O and operating system requirements into account as well. In most cases the host operating system of a system hosting Docuflair virtual machines needs two virtual processors. Use that value as the basis for the host operating system’s virtual processor requirement when calculating the overall ratio of physical cores to virtual processors. If the host operating system’s performance monitoring shows processor utilisation equivalent to more than two processors, reduce the number of virtual processors assigned to the virtual guest machines accordingly. Also make sure that the overall ratio of virtual processors to physical cores is no greater than 2:1.
- In some circumstances, virtual guest machines cannot communicate directly with Fibre Channel or SCSI host bus adapters (HBAs) installed in the host machine. In that case, configure the adapters in the host machine’s operating system and present the logical unit numbers (LUNs) to the virtual guest machines as virtual disks or pass-through disks.