Skip to main content Skip to complementary content

Introduction

Qlik Enterprise Manager, also referred to as Enterprise Manager, provides a single point of control for designing, executing, and monitoring Qlik Replicate and Compose tasks throughout your organization. If your site has multiple Qlik servers with tens, if not hundreds of tasks, Enterprise Manager greatly eases the design, management, and monitoring of these tasks. Whether your site deploys a single Qlik server or multiple servers, Enterprise Manager is your single go-to interface to create data endpoints, design tasks, execute them, and monitor the replication process in near real-time. In addition, Enterprise Manager lets you view all tasks in a tabular format that offers advanced grouping and filtering capabilities.

The following figures show a high-level view of a possible Enterprise Manager installation environment and a more detailed architecture diagram.

Note that components labeled as "Qlik Server" can either be Qlik Replicate or Qlik Compose.

Example Enterprise Manager environment

Example Qlik Enterprise Manager environment mapping, with a central Qlik Enterprise Manager instance hosted on a Windows machine, with multiple client machines for remote access, multiple connected Qlik Replicate instances hosted on Linux servers, a Qlik Compose instance on a remote Windows server with a console for user access, and an optional PostgreSQL server for analytics purposes

Enterprise Manager architecture

Example Qlik Enterprise Manager architecture, with Enterprise Manager hosted on a Windows Machine. Data is sent from Replication and Compose Servers via port 3552, either directly to the Enterprise Manager instance or to an intermediate Qlik Console machine that then passes the data to Enterprise Manager via port 443. SQLite settings and data repositories in Enterprise Manager then feed the data into the Enterprise Manager core, which consists of a Replicate Server Manager/Handler, a Rest API, a Message Center, and a Storage Manager, which connect to Client Machine web browsers via port 443. It also contains an Analytics system that optionally connects to a PostgreSQL server via port 5432

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – let us know how we can improve!