Ignition Gateway Configuration and Administration
Key Takeaway
How to configure the Ignition gateway through its web-based administration console — networking, security, redundancy, Gateway Network, and performance tuning.
Quick Answer
The Ignition gateway is administered through a web-based console at
http://gateway-ip:8088. From this console, administrators
configure device connections, database links, security zones, project
resources, Gateway Network connections, redundancy settings, and system
performance parameters.
Gateway Web Interface
The gateway web interface is organized into several sections:
- Status — Overview dashboard showing gateway uptime, active connections, thread counts, memory usage, and licensed modules.
- Config — All configuration pages for OPC-UA, tags, databases, alarming, projects, networking, security, and scheduling.
- Redundancy — Master/backup gateway pairing and failover configuration.
- Gateway Network — Outgoing connections to remote Ignition gateways for multi-site data sharing.
Security Configuration
Ignition supports role-based access control through identity providers including internal user sources, Active Directory/LDAP, SAML 2.0, and OpenID Connect. Security zones restrict access to specific projects, tags, and gateway functions based on client IP ranges or authenticated roles. SSL/TLS configuration is managed through the gateway's built-in certificate management or external keystores.
Gateway Network
The Gateway Network enables communication between multiple Ignition gateways across a WAN. Common use cases include centralized alarm management, remote tag history access, and enterprise-wide reporting dashboards that aggregate data from field gateways. Connections are encrypted with TLS and support store-and-forward for intermittent links.
Performance Tuning
Key performance settings include:
- JVM Memory — Adjust the gateway's Java heap size
in
ignition.conf(default 256 MB initial, 2 GB maximum). Large systems may need 4-8 GB. - Scan Classes — Set polling rates appropriately. 1-second scans for critical analogs; 10-30 second for status points. Excessive 100ms scanning can overload both the gateway and field devices.
- Tag Provider Optimization — Use folder-level scan class overrides and leased tag execution to reduce unnecessary polling.
- Database Connection Pooling — Configure max connections and validation queries to prevent pool exhaustion under heavy historian load.
Frequently Asked Questions
The default HTTP port is 8088 and the default HTTPS port is 8043. The Gateway Network (GAN) uses port 8060 by default.
Yes. Ignition supports Active Directory and LDAP as identity providers for user authentication, as well as SAML 2.0 and OpenID Connect for single sign-on.
The Gateway Network enables multiple Ignition gateways to share data, alarms, and tag history across a WAN. It supports store-and-forward for intermittent connections and is encrypted with TLS.