Services and ports
The Qlik Alerting services run as Microsoft Windows services, which you can deploy on a single server. PoC and testing environments can however be installed on the same server as Qlik Sense.
Qlik Alerting services
The Qlik Alerting architecture runs as a number of individual services. All Qlik Alerting services are prefixed with Qlik Alerting in the windows installer to ensure they are ordered consistently in the windows services views.
| Service name | Description |
|---|---|
| Gateway | The Gateway service manages access and routes to all Qlik Alerting services. It ensures the simple management of any changes between front end and back end components. |
| Scheduler | The Scheduler service manages any event that is triggered based on a time-based schedule. It identifies the next time that any Qlik Sense reload task scan is due, the next time any alert record based on a schedule, or the next daily digest runtime. The Scheduler adds records to the database to act as a queue for future events. |
| Queuer | The Queuer service manages tasks that have been triggered but have not yet been picked up by the Worker for action. It is the backlog of work items to be processed. This service checks the database to add any scheduled events that are due but also receives queue requests from the Worker which will add additional work tasks to the queue during and on completion of other work tasks. |
| Worker |
The Worker service is the orchestrator of all the different tasks that are required to run the different processes in Qlik Alerting. It picks up the next task from the Queue and process it and therefore it orchestrates many different tasks. For example:
|
| Connector Hub | The Connector Hub service is a connector gateway that ensures that all core actions are consistent and resolves these requests to the relevant connector type. It also manages a queue in the database that ensures large spikes in requests are managed effectively. |
| Qlik Connector | The Qlik Connector service manages all access to Qlik Sense, including user session management and all other calls made to Qlik Sense to access metadata and application data. |
| Condition | The Condition service offers the validation engine where alert details and data from the scan are checked. |
| Notification Hub | The Notification Hub service manages actions when alert notifications are triggered. It manages requests to ensure that the relevant notification services receives information to send different types of notifications. . It also manages a queue in the database that ensures large spikes in requests are managed effectively. |
| Email Messenger | The Email Messenger manages email notifications sent through the identified mail server. It manages the authentication to the mail server, and the formatting of the mail information. |
| Mobile Messenger | The Mobile Messenger manages push notification to mobile devices so alert messages are sent directly to the notifications window on the mobile device. It also passes encrypted alert data to a real-time firebase database for the device to retrieve when the mobile app is opened, or when a message is received, and triggers the record to be grabbed. |
| Repository | The Repository service manages traffic from different services through to the dependent databases. This allows graceful management of the traffic to and from the database. |
Qlik Alerting default ports
The following tables are an overview of the ports used in a Qlik Alerting architecture.
| Service name | Default port setup |
|---|---|
|
Gateway |
Information noteAll traffic from external systems connects through this service.
4551 (HTTP) 4552 (HTTPS) |
| Scheduler | 4562 (HTTPS) |
| Queuer | 4561 (HTTPS) |
| Worker | 4563 (HTTPS) |
| Connector Hub | 4565 (HTTPS) |
| Qlik Connector | 4566 (HTTPS) |
| Condition | 4564 (HTTPS) |
| Notification Hub | 4567 (HTTPS) |
| Email Messenger | 4568 (HTTPS) |
| Mobile Messenger | 4569 (HTTPS) |
| Repository | 4560 (HTTPS) |
Other components default ports
| Service name | Default port setup |
|---|---|
| MongoDB | 27017 (TCP/IP) |
| Redis | 6379 (TCP/IP) |