Book Image

QlikView Server and Publisher

By : Stephen Redmond
Book Image

QlikView Server and Publisher

By: Stephen Redmond

Overview of this book

Table of Contents (15 chapters)
QlikView Server and Publisher
Credits
About the Author
About the Reviewers
www.PacktPub.com
Preface
Index

Service Oriented Architecture


All of the QlikView services talk to each other using HTTP web service calls. This means that the services can be easily deployed on different servers—even in different domains and behind firewalls—as long as the services can make calls on the ports they use.

QlikView Server

The QVS is slightly different from the other servers, in that "direct" clients—QlikView Desktop, QlikView Plugin, and any OCX clients—will communicate with it via a proprietary, encrypted, binary messaging format, QVP, over port 4747. If a client can't connect directly with the server on port 4747, they have the option of "tunneling" via HTTP or HTTPS through the QVWS or IIS; the web server then talks to QVS over port 4774. The Ajax and mobile clients do not go directly to the QVS. They will communicate to the QVWS/IIS using the XML-based QVPX format.

The QlikView Server also has a settings port 4749, which is available when using certificates. QVS listens for SNMP queries on port 161.

QlikView Management service

This service is the main broker between the other services. It presents the QlikView Management Console (QMC) to administrators on port 4780. The URL is as follows:

http://servername:4780/QMC/SystemSetup.htm

This is the frontend that an administrator can use to set up and configure all of the QlikView services. The QMC requires NTLM authentication, and only members of the local QlikView Administrators Group can run the console.

QMS also has a backend service address on port 4799 that allows access to the API via the web service address http://servername:4799/QMS/Service.

The web services can be accessed by users who are members of the local QlikView Management API group.

If enabled, QMS listens for SNMP queries on port 4781.

QlikView Web Server/Settings service

The QVWS service will serve web pages over port 80 (HTTP) or 443 (HTTPS) or any other configurable port. When listening for requests from other services, such as QMS, it listens on port 4750. The service address is http://servername:4750/QVWS/Service.

If the QVWS is deployed in a different firewall segment to the QMS, you will need to ensure that port 4750 is open in both directions. Similarly, port 4747 needs to be open in both directions between the QVWS/IIS and QVS.

If enabled, QVWS listens for SNMP queries on port 4751.

Directory Service Connector

The DSC is the service that connects to user repositories such as Active Directory or LDAP. It communicates on port 4750. The service address is http://servername:4730/DSC/Service.

As with other services, if this is located on a different firewall segment, port 4730 will need to be open in both directions between the servers.

If enabled, the QDS listens for SNMP queries on port 4731.

QlikView Distribution Service

The QlikView Distribution Service is the service that enables the QlikView Publisher functionality. It listens on port 4720. The service address is http://servername:4720/QDS/Service.

This service is only available if there is a QlikView Publisher license installed. As with the other services, port 4720 will need to be open to enable communication across a firewall.

If enabled, QDS listens for SNMP queries on port 4721.