System Requirements¶

System Types¶

Component	Small Deployment	Medium Deployment	Large Deployment	Enterprise
Messages per day	< 5000	< 250K	< 5M	> 5M

Hardware Requirements¶

Component	Small Deployment	Medium Deployment	Large Deployment	Enterprise
Dedicated Server	Not required	Recommended	Recommended	Required
Processors¹	2–4 cores	4–6 cores	6–12 cores	12+ cores
System RAM	2–4 GB	4–8 GB	8–16 GB	16+ GB
QIE RAM²	2 GB	2–4 GB	4–8 GB	8+ GB
Available Hard Disk Space³	20–50 GB	50–100 GB	100–500 GB	500+ GB
Virtualization⁴	Supported	Supported	Supported	Supported

¹ QIE is a multi-threaded enterprise application and can take full advantage of all available CPU cores. A 64-bit JVM is recommended and requires a minimum of 2 cores.
² 32-bit JVM is limited to 1.2 GB of RAM.
³ Hard disk requirements vary depending on message volume and retention policy; recommendation based on 14-day retention.
⁴ QIE has been tested in virtualized and workstation environments on both Windows and Linux guest systems.

Sizing for large messages

There is no hard limit on the size of a message QIE can process, but each message is loaded entirely into the JVM heap. A receiver holds the incoming file in memory, queues it, and the processor then makes another copy, so at least two full copies of the message exist at once. Allow headroom on top of that: as a rule of thumb, allocate at least four times the file size in heap (about 4 GB to process a 1 GB file, ~40 GB for a 9 GB file). For files too large to hold in memory, enable the Large File Handling Options on the File, FTP/SFTP, and Network Share receivers, which stream the file to disk and pass the channel a reference to it instead of loading it into the heap.

Software Requirements¶

Component	Small	Medium	Large	Enterprise
Database Management System (see Supported Databases)	MariaDB v10–11 MySQL v8.x MSSQL 2016–2022	MariaDB v10–11 MySQL v8.x MSSQL 2016–2022	MariaDB v10–11 MySQL v8.x MSSQL 2016–2022	MariaDB v10–11 MySQL v8.x MSSQL 2016–2022

All deployments:

Operating System: All Windows platforms currently supported by Microsoft / Ubuntu 9.04 or newer / Unix. QIE supports both 32-bit and 64-bit operating systems.
Java: 64-bit Java Runtime Environment (JRE) version 17+. See Supported Java Versions for the supported distributions.
Client Browser: Used to access the QIE console. See Supported Browsers for the minimum versions.

Outbound Network Access¶

QIE performs a nightly license check-in with the Qvera license servers and also downloads QIE product updates from them. The QIE server (through any HTTP proxy in use) must be able to make outbound HTTPS requests to:

qvera.com
qiecheckin.com

Both are required. A firewall, proxy, or intrusion-detection appliance that blocks connections to either host, or that strips or blocks intermediate chunk downloads inside a session, can cause check-ins and auto-updates to fail.

If check-ins fail for consecutive days, QIE takes graduated action:

Consecutive failed days	Behavior
2	An admin alert appears warning that check-ins are failing.
8	All running channels are stopped each morning at 7 a.m. local time. Channels can be manually restarted, but stop again the next morning until check-in succeeds.
22	All channels are permanently stopped. No channels are allowed to start until a successful check-in takes place.

Add firewall or proxy allow-list entries for the two domains above before installing QIE in an environment with restricted egress.