Qlik Sense Communication Overview WebSocket protocol: Qlik Sense Enterprise is an in-memory, Visual Analytics platform which WebSocket is a protocol providing full-duplex communication channels over a single TCP enables users to create self-service visualizations from multiple data connection sources in a simple and governable way. Analytics can be administered, authored, and consumed via a web browser. All communication between HTTP/HTTPS: Qlik Sense services and clients is based on web protocols, and specific (HyperText Transport Protocol Secure) The protocol used to access a . When networking considerations are required for a Qlik Sense Enterprise :// is used as the prefix of a Web deployment. address rather than the common http://, the session is managed by a security protocol, Networking Requirements which is typically SSL, and the transmission Qlik Sense has the following networking requirements: is encrypted to and from the Web server.

TLS / SSL: WebSocket protocol (client to server) - Once the HTTPS (Transport Layer Security) and its communication has been initiated by the client, a WebSocket upgrade predecessor, Secure Sockets Layer (SSL), request is performed and maintained for the duration of the session. both of which are frequently referred to as Networking solutions such as load balancers, reverse proxies, and EMM "SSL", are cryptographic protocols that solutions between the client and Qlik Sense server software must provide communications security over a support and be configured for WebSocket traffic. .

Transport Layer Security (TLS) – Service and client to server Load Balancer: communication should use TLS. Client to server communication is a device that acts as a reverse proxy and distributes network or application traffic secured using certificates which Qlik Sense provides self-signed, out of across a number of servers. Load balancers the box. Additionally, customers have the option to procure a certificate are used to increase capacity (concurrent from a trusted root authority, if desired. users) and reliability of applications

Ports – The default ports used for client to server communication need EMM: to be open through any firewalls, reverse proxies, and load balancing (Enterprise Mobility Management) is the set of people, processes and technology focused devices to each Qlik Sense Proxy Service (QPS) in the site. on managing mobile devices, wireless networks, and other mobile computing 443 HTTPS/WebSocket Open User web traffic when using services in a business context. inbound HTTPS. Related Documents:

4244 HTTPS Open Authentication port when using http://www.qlik.com/us/resource- inbound Windows authentication over library/... HTTPS. Qlik Sense Architecture Overview 80 HTTP/WebSocket Open User web traffic when using HTTP Qlik Sense Scalability Technical inbound (optional) brief Qlik Sense Security Overview 4248 HTTP Open Authentication port when using inbound Windows authentication over HTTP (optional) https://help.qlik.com/... Qlik Sense Ports

Load Balancer Best Practice When utilizing a network load balancer, it must support and persistent/sticky sessions for users. It must load balance ports 443, 4244 and (if utilized) ports 80 and 4248 in a persistency group.