Product knowledge

Docs

Docs
Gateway setup
View Markdown

Install and configure

Install the Gateway on Windows, open Experience Hub, then activate your licence and connect Qlik.

On this page

Choose the right download

Sign in to the Raptor Portal and open Dashboard > Raptor MCP License. Download Full Setup for a new Windows installation. Use Updater for an existing installation whose prerequisites and database configuration are already supported. The Gateway ZIP is the manual package for administrators managing their own deployment.

Install the Gateway on a machine your organization or partner operates. It needs network access to the Qlik environments it will serve. A Qlik Cloud installation can run on a Windows workstation or server; it does not require Qlik Sense to be installed on that machine.

Before you run Windows Setup

Run Full Setup as an administrator on 64-bit Windows. The fresh-install check requires at least 6 GB of free space on the selected drive. Allow additional space for your repository, database, logs and retained backups.

Choose the DNS hostname people will use to reach the Gateway, and arrange for it to resolve to this computer. Enter a hostname without a scheme, port or path. The Windows computer name is the initial suggestion. Fresh Setup uses HTTPS on port 7443, loopback HTTP on 7331 and a private PostgreSQL listener on 5433; these ports must be available.

  • Have the Windows service account and its password ready. Setup accepts DOMAIN\user, .\user or user@domain and verifies the account before installation.
  • Choose a separate PostgreSQL administrator password and retain it in your approved secret store.
  • Choose an empty installation folder on a fixed local drive. The default is C:\RaptorMCP\enterprise-gateway. Linked folders and junctions are rejected.
  • Under Storage locations, keep the suggested repository folder or choose a suitable Windows folder or SMB share. The selected service account must have the required folder and share access.
  • Full Setup includes its verified runtime dependencies. If an organization policy blocks installation or execution, resolve that policy with your administrator before continuing.

Install on Windows

The current Windows installation separates machine setup from Gateway activation and Qlik configuration. You do not enter a Qlik API key or Gateway licence in the fresh-install form.

  1. Open the downloaded Full Setup executable as an administrator and wait for Checking this computer to finish.
  2. Review Gateway hostname, Windows service account, Account password, Postgres administrator password and Install folder. Confirm the PostgreSQL password and review Storage locations.
  3. Read and accept the Raptor terms, then choose Install Raptor.
  4. Keep Setup open while it installs files, configures PostgreSQL, starts the services and checks the installed version, HTTPS and Hub entry page.
  5. When Setup reports Raptor is installed, choose Open Experience Hub. Follow the Hub instructions to sign in, activate the Gateway and configure Qlik.

HTTPS and persistent storage

Fresh Setup creates managed TLS and trusts its Gateway root certificate on the installation computer. Other computers still need to trust that root through your approved certificate-distribution process, or you can import a suitable certificate through Gateway administration. Its names must cover the canonical hostname and any additional browser addresses you configure.

A fresh Windows installation stores PostgreSQL, configuration and TLS material beneath the selected installation root; the repository defaults to its data\repository folder. Older installations can retain a different layout. Record the actual paths and preserve the Gateway encryption key when planning backup or migration.

Manual Linux, macOS and Docker deployments

The Gateway ZIP is an administrator-managed deployment. Its setup scripts and configuration examples are separate from the Windows Full Setup workflow. Prepare the runtime, service identity, persistent storage, HTTPS, licence and Qlik connection settings for the selected platform.

For Docker, use the supplied hardened Compose policy or a reviewed equivalent with an immutable image digest. Keep state persistent and QSEoW certificate mounts read-only. Existing Linux gateways moving from JSON or SQLite core state to PostgreSQL require an offline migration with a stopped snapshot, isolated rehearsal and verified cutover. Replacing an image does not perform that migration.

Previous

Before you register

Next

Enterprise Gateway