Distributing apps to multiple Qlik Cloud tenants using custom properties

Prerequisites

• A license that includes multi-cloud. Either of the following:
  • The same signed license key for Qlik Sense Enterprise on Windows and Qlik Sense Enterprise SaaS.
  • Different license keys, where the cloud attributes are enabled and on-prem is activated through a signed license.
• Two Qlik Cloud tenants with support for managed spaces (not Trials, Standard, or Business editions).

Set up deployments

For each Qlik Cloud tenant you will:

• Create a deployment in Qlik Sense Enterprise on Windows.

• Create an identity provider configuration in Qlik Cloud.

• Test the connection between Qlik Sense Enterprise on Windows and Qlik Cloud

The deployments will be called Region1 and Region2.

Create a deployment

Do the following:

1. In the Qlik Management Console (QMC), open Cloud distribution and select Deployment setup.

2. Click Set up new.

3. For Deployment name, enter Region1 for the first deployment and Region2 for the second. These names will be used as values in the custom property.

   

4. For API endpoint, enter the tenant URL.

5. For Audience, enter qlik.api.

6. Select Use local bearer token.

   Information noteUsing a local bearer token simplifies setup. If you're not using this, input the Client ID, Client Secret, and Token endpoint from your identity provider.
7. Click Apply.

8. Copy and save the local bearer token. This token will be needed for the identity provider configuration in Qlik Cloud.

Repeat these steps for the second deployment.

Create an identity provider configuration

Do the following:

1. Log in to your first Qlik Cloud tenant and open the Management Console .

2. Go to Identity provider.

3. Click Create new.

4. For Type, select Multi-cloud.

   

5. Optionally, enter a description.

6. Paste the local bearer token from the deployment setup into the Local bearer token field.

7. Click Create.

Repeat these steps for the second Qlik Cloud tenant.

Test the connection

1. In the QMC, open Cloud distribution and select Deployment setup.

2. For each of the two deployments, Region1 and Region2, click Test connection.

Create a custom property

You will use custom properties in the distribution policy to specify the target for app distribution. Define custom properties with deployment names as values.

Do the following:

1. In the QMC, open the Custom properties section.

2. Click Create new.

3. Set the name to deployments.

4. Under Resource types, select Apps.

5. Under Values, click Create new.

6. Type Region1 as a value.

7. Add the value Region2 in the same way.

8. Click Apply.

Now you have two custom property values that you can use in the distribution policy.

Create a distribution policy

Create a distribution policy for distributing apps to the two cloud deployments using the custom property.

Do the following:

1. In the QMC, open the Cloud distribution section and select Distribution policies.

2. Click Create new.

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

   

4. Name the policy Distribute to cloud deployments.

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

6. In the rule editor:

   • Keep the values subject and name.

   • On the second row, select #App in the first drop-down list and add @deploymentsin the last field.

   • The Conditions box in the Advanced section should contain the following string: ((subject.name=resource.@deployments)).

   • This could be read as: "If the deployment name equals the custom property value applied to the app, the app will be distributed to that deployment."

7. Click Validate rule. The rule syntax is checked and a confirmation is displayed.

8. Click Apply to save the settings.

With the configuration in this example, you can distribute apps to either Region1, Region2, or both, based on the tags used when publishing. For more information on publishing apps with tags, see Publishing apps to cloud hubs with tags.