Skip to main content Skip to complementary content

Distributing apps to Qlik Cloud

When you publish apps to streams in Client-Managed Qlik Sense, you may also want to distribute the apps to your Qlik Cloud deployment. By making configurations in Client-Managed Qlik Sense and in your cloud tenant, you can automate the distribution to cloud so that apps are automatically distributed to your Qlik Cloud deployment when you publish them to a stream.

Information noteDistributing and publishing a Qlik Sense app from Client-Managed Qlik Sense to Qlik Cloud does not include the private community sheets. Only published community sheets are available.

Prerequisites

To distribute an app from Client-Managed Qlik Sense to qlik you need the following:

  • Qlik Cloud tenant.
  • A license that includes multi-cloud. Either of the following
    • The same signed license key for Qlik Sense Enterprise on Windows and Qlik Cloud.
    • Different signed license keys, where the Qlik Sense Enterprise on Windows license has the cloud attributes enabled.

Configurations

The following is a high-level description of the configuration steps.

  1. Set up a deployment in the Qlik Management Console (QMC) of your Qlik Sense Enterprise on Windows server.

  2. Create a multi-cloud identity provider configuration in the tenant.

  3. Create the distribution policy in the QMC.

Setting up a deployment

Do the following:

  1. From the QMC start page, open Cloud distribution.

  2. Click Deployments setup.

  3. Click Set up new in the bottom-left corner.

  4. Enter a deployment name.

    You will use this name in the distribution policy.

  5. Enter the API endpoint, that is, your tenant address.

    Example: https://my-tenant.eu.qlikcloud.com.

  6. For Audience, enter qlik.api.

  7. Select Use local bearer token.

    Information noteUsing a local bearer token simplifies setup. If you do not use it, you need to enter Client ID, Client secret, and Token endpoint instead.
  8. Click Copy to clipboard.

    You need the local bearer token in the identity provider configuration.

  9. Click Apply.
Information noteDeployment setup is also available in the QMC, under Cloud distribution.

Creating the identity provider configuration

Do the following:

  1. Open the Management Console in your Qlik Cloud tenant and select Identity provider in the menu to the left.

  2. Click Create new.

    The Create identity provider configuration window is opened.

  3. Under Type, select Multi-cloud.

  4. Optionally, enter a description.

  5. In the Local bearer token box, paste the token you copied in the deployment setup.

Creating the distribution policy

Distribution policies are used to determine whether a published app can be distributed to one or more of the deployments in Qlik Cloud. Only published apps can be distributed.

Do the following:

  1. In the QMC of Qlik Sense Enterprise on Windows, open Cloud distribution and select Distribution policies.

  2. Click Create new.

  3. In the Create rule from template list, select Distribution_App.

  4. Name the distribution policy.

  5. Under Basic, verify that the resource filter value is App_* and the action Distribute is selected.

  6. In the rule editor keep the values subject, name, =, and value. In the last field, you only need to add the name of the deployment you created earlier (in Setting up a deployment). Let us assume it is deployment.

    The Conditions box in the Advanced section should then have the following string: ((subject.name="deployment")).

  7. Click Validate rule.

    The rule syntax is checked, and, if valid, a confirmation is displayed.

  8. Click Apply to save the rule.

This is a simple example of app distribution where all apps that are published to a stream also are distributed to your Qlik Cloud tenant. By using custom properties you can make more granular rules for app distribution, see Distribution policies - example.

Visit the discussion forum at community.qlik.com

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – let us know how we can improve!