Selection guide
Selecting a Touch Panel That Can Run Ignition and MySQL
Short answer
Only a panel PC running Windows or Linux can host the Ignition gateway and MySQL; an HTML5 web HMI is a locked browser that displays native HTML5 views and nothing more. Put the gateway and database on a separate computer and make the panel a swappable client — the memory math below shows why the all-in-one panel rarely fits both.
On this page
Only one class of touch panel can run Ignition and MySQL: a panel PC with a general-purpose operating system — Windows or Linux — that accepts installed software. An HTML5 web HMI cannot. It boots a locked browser on vendor firmware, so there is nowhere to install the Ignition gateway, no place for a MySQL server, and no Java runtime for the legacy client. Its entire Ignition role is displaying views the gateway serves as native HTML5. That leaves two working designs — an all-in-one panel PC hosting gateway, database, and client, or a split layout with the gateway and MySQL on a computer in the cabinet and the touch panel as a swappable client — and the memory arithmetic below decides between them.
What the Gateway and MySQL Actually Need #
The Ignition gateway is a Java service and MySQL is a database server. Both are installed applications: they want an installer or package mechanism, a persistent file system, background services that start at boot, and network ports they own. Inductive Automation's supported-platform list is built around exactly that class of machine, and desktop editions qualify — a server-class OS is not a requirement.
A web HMI panel has none of it. It runs an embedded browser on firmware the vendor updates, configured through the vendor's own tools, and it renders content served from somewhere else. Point that browser at the gateway address and you reach the gateway's web page and a login; from there the panel stops, because the client download it is offered is an installer it has no way to execute. For a closer look at what code actually executes on a browser-class panel, read where JavaScript and WebAssembly actually run on an HMI.
The Datasheet Check #
Read the operating-system line on the datasheet, not the product category, and sort every candidate into one of three rows.
| What the datasheet says | What the hardware is | Verdict for Ignition |
|---|---|---|
| Windows or Linux, user-installable software, mass storage | Panel PC | Can host the gateway, MySQL, and the client; proceed to sizing |
| HTML5, web panel, browser-based, firmware updates only | Thin browser client | Hosts nothing; display-only role at best |
| Proprietary HMI runtime, configured only by vendor software | Closed HMI terminal | Ignition is not an option on this hardware |
A panel marketed for HTML5 applications belongs in the second row whatever its screen size or processor, because the limit is the software model, not the horsepower. Only the first row proceeds to the rest of this article.
What a Browser-Only Panel Can Still Display #
One branch keeps a web panel in play: views the gateway itself serves as native HTML5. The Perspective module delivers exactly that — views that are fully HTML5 and CSS3 compliant, compatible with Chrome, Firefox, Safari, and Microsoft Edge, requiring no Java installation and no plug-ins.
Test before committing. Identify the browser engine and its version from the panel's documentation, then load your heaviest screen — trends, popups, your largest tag count — and watch render time and touch response on the actual unit. If the engine stumbles, or your project is the legacy Java client, return to the first row of the table and buy a panel PC. Applet mode is not a route on current hardware.
The Memory Arithmetic That Rules Out Most All-in-One Panels #
Inductive Automation's server sizing guidance sets the gateway's max heap at 66% of a machine's max memory on Windows and 85% on Linux. Those fractions exist because the gateway is designed to dominate the memory of whatever it runs on. Put MySQL on the same box and you are fighting that design.
Worked example — an 8 GB panel PC offered as the all-in-one host:
- Linux: 0.85 × 8 GB = 6.8 GB of heap for the gateway, leaving 8 − 6.8 = 1.2 GB for the OS, MySQL, and the client session.
- Windows: 0.66 × 8 GB = 5.28 GB of heap, leaving 8 − 5.28 = 2.72 GB for Windows, MySQL, and the client.
A historian writing continuously to MySQL does not live in 1.2 GB of headroom, and 2.72 GB on Windows is thin before Windows itself and the client are counted. Decision: an 8 GB panel is a client, not a server. For the general case, take the gateway and MySQL figures from the vendors' published system requirements, add the OS and the client, and if that sum pushes against the RAM where the heap fraction no longer fits, the database moves off the panel. The same addition applies to CPU and storage when the two share hardware.
Split or All-in-One: Commit to the Split #
| Layout | What runs where | What a failure costs |
|---|---|---|
| All-in-one | Gateway, MySQL, and client on one panel PC | A cracked touchscreen or dead panel takes the gateway, historian, and alarm history down with it |
| Split | Gateway and MySQL on a headless computer in the cabinet; the panel runs the client | Swap the panel without touching data; logging continues with the panel off; several panels share one gateway |
Choose the split. The parts operators touch take the abuse — gloved hands, cleaning chemicals, impact — and the server belongs in a cabinet. The all-in-one layout is defensible only on a small standalone machine where losing local history on a panel failure is acceptable.
If the enclosure forces one physical unit, bolt a fanless box PC behind a commercial touchscreen: one mounted assembly, two replaceable parts, and replacing the display leaves the gateway and database running. The same server-side thinking shapes choosing a web-based HMI and SCADA architecture at line level, and it explains how multiple HMI projects run on one server host as the panel count grows. For the operator side, pick from industrial panel PCs rated for the mounting location, and let the server be a separate computer.
Commissioning the Split System #
- Install the gateway and MySQL on the cabinet computer. Create the database and its user, then add the connection under the gateway's database connection settings.
- Configure the PLC device connections on the gateway and confirm tag quality reads good in the gateway itself before any panel is involved.
- Give the server a static IP on the control network and open the gateway's web and client ports through any firewall between server and panels. Keep the gateway on the control-network segment — its web interface is an exposed service and does not belong bridged onto the office LAN.
- On each panel PC, install the client the gateway's web page offers, point it at the server address, and set it to run an HMI application touch-only in forced full screen at OS login.
- Disable OS sleep, session-locking screen savers, and automatic update reboots during production hours.
Then prove the separation from the operator position:
- Watch live values change on the panel as the PLC values change. A good tag in the gateway under a static screen points at the binding, not the driver.
- Write a setpoint from the panel and read it back in the PLC.
- Note the time, power the panel off for several minutes while the process runs, power it back up, and confirm the client reconnects on its own.
- Query the MySQL history tables on the server for continuous rows spanning the outage window. Gaps mean logging depended on the panel, and the architecture is not split.
Questions asked
Can Ignition run in applet mode on an HMI panel's built-in browser?
No. Mainstream browsers removed the Java plug-in, and the embedded browsers built into HMI panels never shipped it, so the legacy Java client cannot load there. The supported client is the one you download from the gateway's web page and install on a panel running Windows or Linux.
Does Ignition require a server-class operating system?
No. The vendor's download page lists Windows 10/11, Windows Server 2016 through 2025, macOS 13 and later, and popular Linux distributions tested with Ubuntu 20.04, Ubuntu 22.04, and RHEL 8. A desktop OS on an industrial panel PC is therefore a supported platform; server editions matter for IT policy, not for the gateway itself.
Can the gateway be installed on a headless Linux server with no desktop?
Yes. The documented path is to download the installer to the server, mark it executable, create a dedicated Ignition user to own the service, and answer the configuration prompts the installer raises. No desktop environment is needed, because the gateway is administered through its own web interface from any client machine.
Can one gateway serve several touch panels?
Yes. The gateway hosts the project and each panel opens it as a client session, so you are adding sessions, not servers. Size the cabinet computer for the combined load of every panel plus the database, and read the license terms for connection counts before planning a large fleet of panels on one gateway.
Do the panels need Java or plug-ins installed to show the HTML5 views?
No. Perspective serves views that are fully HTML5 and CSS3 compliant and need no Java installation or plug-ins in Chrome, Firefox, Safari, or Microsoft Edge. The only Java on the client side belongs to the legacy client, which installs on the panel's own operating system rather than in the browser.