Product knowledge
Docs
Enterprise Gateway
Understand what your organization operates, where Gateway state lives and how to prepare a production deployment.
On this page
Deployment choices
Run the Gateway on infrastructure controlled by your organization or approved partner. Windows Full Setup provisions the current service and its local runtime dependencies. The ZIP supports administrator-managed deployments; its setup scripts, prerequisites and service management differ from Windows Setup.
Qlik Cloud does not require a Qlik Sense installation on the Gateway computer. A QSEoW connection needs approved access to the site, its certificate-backed APIs and the browser sign-in route. Keep these network and identity requirements separate from the AI client connection.
Persistent state and secrets
The Gateway retains configuration, user and connection state, encrypted credentials, repository content and operational records. Features such as InsightOps, reporting and writeback can retain additional content. Treat the database, repository and encryption key as one recovery responsibility.
Fresh Windows Setup provisions a private PostgreSQL core store. Existing installations can retain older layouts until a supported migration is completed. A package replacement or container restart is not a database migration.
The Gateway routes requested Qlik results to the configured client. Your AI provider and client settings determine what happens to that content after delivery. Review the entire data path before allowing sensitive data.
Operational responsibilities
Assign an owner for service availability, TLS certificates, licence activation, user access, backups and updates. Use a maintenance window for changes that interrupt connections or background work.
- Keep the canonical hostname, DNS, certificate names and client trust aligned.
- Maintain database-aware backups and separately protect repository files, configuration and encryption material.
- Monitor the service and the workflows people depend on, including scheduled notifications, reporting and writeback.
- Review local Seats and Qlik permissions when people join, change responsibilities or leave.
- Retain version, source, setup logs and workflow evidence when investigating a failure.
Enable features deliberately
Analytics, app development, migrations, InsightOps, writeback, reporting and SSE each have their own connection and permission requirements. Configure and test the workflows your team needs rather than enabling a feature solely because it appears in the product description.
For a partner-operated installation, document hosting, administration, incident response and handover responsibilities. Partner NFR access is for the partner’s own non-production use; customer delivery requires the customer’s paid licences and aligned Qlik rights.
Previous
Install and configure
Next