Skip to main content

Connecting QlikView Server to a Qlik Sense Enterprise SaaS or Qlik Sense Enterprise on Kubernetes deployment

ON THIS PAGE

Connecting QlikView Server to a Qlik Sense Enterprise SaaS or Qlik Sense Enterprise on Kubernetes deployment

Before you can publish QlikView documents or links, you must first connect your QlikView Server installation to a Qlik Sense Enterprise SaaS or Qlik Sense Enterprise on Kubernetes deployment.

Prerequisites

To publish QlikView documents or a links to a QlikView document, you must have:

  • A version of QlikView Server April 2020 or later.
  • A valid Publisher license.
  • A configured Qlik Sense Enterprise SaaS or Qlik Sense Enterprise on Kubernetes cloud installation.
Note: To access QlikView documents from a published link on the cloud hub, the user will need to be able to access the QlikView server the link was distributed from.

Connecting QlikView Server to a Qlik Sense Enterprise cloud deployment

Do the following:

  1. In the QlikView Management Console, go to the System tab, open the Setup section, then select the Cloud Deployments folder.
  2. Select the Plus icon Add button to create a new cloud deployment connection.
  3. In the Service URL field, enter the first part of the cloud tenant URL, for example <tenant_name>.<region>.qlikcloud.com/.
    Select Apply to create the connection. Under Cloud Deployments you will see connection you just created.
  4. Select the connection, then select the General tab.

    1. In the Deployment name field, enter a name for the cloud deployment.
    2. In the API endpoint field, enter the URL to the Qlik Sense Enterprise cloud deployment that you want to publish to.
    3. Select a web server from the Web Sever drop-down menu.
    4. Under Distribution Settings, you can disable the distribution of links, documents, or both.
  5. In the Issuer configuration section, click Generate configuration to generate the local bearer token.

    • To connect to a Qlik Sense Enterprise SaaS deployment, select Qlik Cloud Services format.
    • To connect to a Qlik Sense Enterprise on Kubernetes deployment, deselect the box Qlik Cloud Services format.
  6. Copy and save the local bearer token to a preferred location. You will need to add it to the Qlik Sense Enterprise cloud deployment to complete the connection with your QlikView Server deployment.
    Adding the bearer token to the Qlik Sense Enterprise cloud hub
  7. Select Apply to confirm the configuration.

Adding the bearer token to the Qlik Sense Enterprise cloud hub

To create a secure connection between your QlikView Server and your Qlik Sense Enterprise cloud hub, the QlikView Distribution Service (QDS) generates a bearer token that you add to your Qlik Sense Enterprise deployment. The bearer token has a signed key that is used in all API calls between the cloud hub and the QlikView Server.

For Qlik Sense Enterprise SaaS

To add your bearer token on Qlik Sense Enterprise SaaS:

  1. In the Management console, go to Identity provider, then Create new.

  2. From the drop-down menu, select Multi-cloud.

  3. Add a description for this identity provider.

  4. In the Local bearer token section, paste the bearer token that you generated in the QlikView Management Console.

  5. Click Create to complete the identity provider setup.

Note: If you are setting up your Qlik Sense Enterprise cloud hub tenant for the first time, see Setup with a local bearer token.

Once the connection between the QlikView Server and Qlik Sense cloud deployments is complete, you can create tasks to distribute QlikView documents or links to the connected cloud deployments.

Publish a QlikView document in a Qlik Sense cloud hub

Publish a link to a QlikView document in a Qlik Sense cloud hub

For Qlik Sense Enterprise on Kubernetes

To add your bearer token on Qlik Sense Enterprise on Kubernetes, you need to manually add it to your Kubernetes values.yaml file. Add the bearer token that you generated in the QlikView Management Console to the section under idpConfigs.

The identity providers section will look similar to the example below:

- identity-providers:
  secrets:
    idpConfigs:

    - issuerConfig:
        issuer: "<url>"
        primary: false
        realm: custom
        hostname: "<hostname>"
        staticKeys:
        - kid: "qlik-72e77ggc-ce68-4ab1-bafa-f1e85c75583b"
          pem: |
          -----BEGIN CERTIFICATE-----
          MIIDQzCCAiugAwIBAgIQAIJVY31Yy1hjZYKYKsiQoTANBgkqhkiG9w0BAQsFADAU
          MRIwEAYDVPPDDAlRVkNsb3VkQ0EwHhcNMTgxMjA3MDkyMzI0WhcNMjgxMjE0MDky
          MzI0WjAUMRIwEAYDVQQDDAlRVkNsb3VkQ0EwggEiMA0GCSqGSIb3DQEBAQUAA4IB
          DwAwggEKAoIBAQCFSTm5F+Vyj2GPOl7ATPUhd0+/QVPK9s2iw53K3ez6EHn1CXua
          Xqm5SmTT69WcdW8fpVHJQ5SgUfAMeHeFawT76TUYiOgdKJjepRwTc2hIvmtgrgGw
          ixqZAe14BEeDYTi88FlyezHr/WiX8InyaaIo7EgjMU638vFGlnJOCHasV9EQSEBO
          h2gOyxVsM/ZEjhvxU0AmKxJ5uiUabIXbWfQ38/DJPPRj8D6TgmVvNUknal0NVs8Y
          XVFgfcta3qwBqoWPXQpBs0r281u/Ui1hJOLHnZY0fQLbPKtI+eadMHlQYAy3P/Mq
          IthTByAI8Ku7fGKJu4RmccpFU8qMvLaQ8v0lAgMBAAGjgZAwgY0wHQYDVR0OBBYE
          FLMNjixLQfeTjetgYyi2pCKcQZl5MB8GA1UdIwQYMBaAFLMNjixLQfeTjetgYyi2
          pCKcQZl5MBcGCCsGAQUFBw0KBAsECVFWQ2xvdWRDQTAyBggrBgEFBQcNCwQmBCQ0
          ZWQzNmY3Mi01OWU0LTQzPPItYjI5MS1hZDgzMjZlMjYyNTYwDQYJKoZIhvcNAQEL
          BQADggEBACdi6C70jDO0PJYH/6NJ3AbuBOe60YHB9vm799L8POC5ID7DQ5AeMZr/
          y7lMp9V/BH6khPNU7FaNv/3iaqBJryvVbWjb5+VZJkRHjYv4igxjfb5QvyjZjvkr
          lsgtsaB4aQgsgrjUiMdhNKf8dyRQSUixUeAs75giko8O+Hz2woybjpDvc3uPPJgK
          1+dNaNKBXhs+FmSxdiI/OTCwPynm9pkRz4PvE9K3C1oBwjdW6hAJRG6/J5Hvzz+V
          6fPAmjJJu4Oq4RdSptOHhSwLMj/KgPTVaeVSP02YRSOLZbiSbxX0zVeKGd0e0S/2
          JGPzzCc5NHbj/h80f6PuZjAIR9/lPfU=
          -----END CERTIFICATE-----
Example of the Kubernetes values.yaml file with the QlikView Server bearer token added.

Once the connection between the QlikView Server and Qlik Sense cloud deployments is complete, you can create tasks to distribute QlikView documents or links to the connected cloud deployments.

Publish a QlikView document in a Qlik Sense cloud hub

Publish a link to a QlikView document in a Qlik Sense cloud hub