QlikView uses ports to communicate between web browsers (users) and servers, and between different services in single or multi-node deployments.
The following table provides an overview of the ports used in a QlikView deployment.
| - | Component | Inbound | Outbound |
|---|---|---|---|
|
|
QlikView Server (QVS) |
4747 (QVP: QlikView Protocol) 4774 (QVP Tunnelling) 14747 (Cluster users SOAP API) 4749 (SSL) |
14747 (Cluster broadcast) |
|
|
QlikView Web Server (QVWS) |
80 (HTTP) 443 (HTTPS) 4750 (SOAP API) 14750 (Certificate) |
4730 (DSC SOAP API) 4735 (DSC custom users SOAP API) 4747 (QVS QVP) 4774 (QVS QVP tunnelling) |
|
|
QlikView Distribution Service (QDS) |
4720 (SOAP API) 14720 (Certificate) |
4730 (DSC SOAP API) 4747 (QVS QVP) |
|
|
QlikView Directory Service Connector (DSC) |
4730 (SOAP API) 14730 (Certificate) 4735 (Custom users SOAP API) |
- |
|
|
QlikView Management Service (QMS) |
4780 (HTTP) 4799 (SOAP API) |
4747 (QVS QVP) 4750 (QVWS SOAP API) 14750 (QVWS Certificate) 4720 (QDS SOAP API) 14720 (QDS Certificate) 4730 (DSC SOAP API) 14730 (DSC Certificate) 4735 (DSC custom users) 4799 (Remote QMS SOAP API) |
|
Qlik License Service | 9200 | 443 (HTTPS) |
The following example shows the ports used to connect the different QlikView services. In a QlikView deployment, all these services can be installed on the same server (single-node deployment). Alternatively, you can decide to set up a multi-node deployment, and install different services on different servers. For further information about QlikView architecture and deployments, see Architecture and Deployment pages.
The following diagram shows the ports used for connecting the different services in a QlikView Server deployment (QV: QlikView).
