Deploy Qlik Sense Enterprise On Kubernetes
Deploy Qlik Sense Enterprise onKubernetesQlik Sense February 2021Copyright 1993-2022 QlikTech International AB. All rights reserved.HELP.QLIK.COM
2022 QlikTech International AB. All rights reserved. All company and/or product names may be tradenames, trademarks and/or registered trademarks of the respective owners with which they are associated.
Contents1 Planning your Qlik Sense Enterprise deployment51.1 Qlik product licenses5Product activationUnified licenseQlik Sense EnterpriseQlik NPrintingQlik Sense licensesLicense Enabler FileAccess assignment1.2 Before you install Qlik Sense Enterprise on Kubernetes55667101114System requirements for Qlik Sense EnterpriseSupported browsersMulti-cloud services1.3 Qlik Sense Enterprise on Kubernetes deployments14232527CSRF security for Qlik Sense Enterprise on Kubernetes2 Preparing for Qlik Sense Enterprise on Kubernetes28292.1 Preparing your local tools3 Installing Qlik Sense Enterprise on Kubernetes29313.1 Providing configuration settings313.2 Installing Qlik Sense313.3 Accessing the deployment33Creating an alias to the IP addressLogging in and applying the license3.4 Using Minikube333333Preparing MinikubeAdditional configuration when using MinikubeAccessing the installation on Minikube3.5 Installing Qlik Sense Enterprise on Kubernetes to a Red Hat OpenShift platform34343435Using MiniShift4 Setting up Qlik Sense Enterprise on Kubernetes after installation35374.1 Distributing apps to Qlik Sense Enterprise on Kubernetes374.2 Setting up identity providers37IdP requirementsSetting up ADFSSetting up Auth0Setting up Okta4.3 Configuring certificates in your Qlik Sense Enterprise on Kubernetes deployment3839434751Verifying the certificate with your browserUsing self-signed certificates and certificates not issued by public CA4.4 Configuring MongoDB in Qlik Sense Enterprise on Kubernetes535354Configuring the MongoDB connection54Connecting to MongoDB with SSL554.5 Configuring a proxy for Qlik License Service communication in Qlik Sense Enterprise onKubernetesDeploy Qlik Sense Enterprise on Kubernetes - Qlik Sense, February 2021563
Contents4.6 Optional configurations when installing Qlik Sense Enterprise on KubernetesUsing Google Web Risk to validate generic links5 Upgrading Qlik Sense Enterprise on KubernetesDeploy Qlik Sense Enterprise on Kubernetes - Qlik Sense, February 20215757584
1 Planning your Qlik Sense Enterprise deployment1Planning your Qlik Sense EnterprisedeploymentTo successfully plan and prepare for your Qlik Sense deployment, do the following:Introducing Qlik Sense EnterpriseGet a brief introduction to Qlik Sense Enterprise.Qlik Sense Enterprise deployment examplesSee examples of different ways to deploy Qlik Sense Enterprise.System requirements for Qlik Sense EnterpriseReview the Qlik Sense Enterprise system requirements.Qlik product licensesUnderstand how Qlik Sense uses license keys and LEF for site licensing.Understand how Qlik Sense uses tokens for user access allocation (token-basedlicensing).Ensure that you have your Qlik Sense license key available.1.1Qlik product licensesHere is a summary of the license options that are available for the different Qlik Sense relatedproducts. Licensing allows you to manage the usage of the Qlik Sense software in yourorganization.For detailed information on Qlik Sense licensing options, see Qlik's legal terms, product terms, and LicensingService Reference Guide: Qlik Legal Terms Qlik Product Terms Qlik Licensing Service Reference GuideProduct activationAll Qlik products are entitled and enforced by a License Enabler File (LEF). The LEF is the artifact that isdownloaded during the production activation. A Qlik product is licensed and activated using either a serial andcontrol number, or a signed license key. The use of a signed license key is required for Qlik Sense EnterpriseSaaS and Qlik Sense Enterprise on Kubernetes deployments, and for the use of capacity based licenses.With a signed license key, you need internet access (direct or through a proxy) to access the cloud-basedlicense backend, for user assignments, analytic time consumption, and product activations.Unified licenseAs of the April 2019 releases of Qlik Sense and QlikView, Qlik Sense customers can use a unified license inmultiple deployments. A unified license shares the same signed key between:Deploy Qlik Sense Enterprise on Kubernetes - Qlik Sense, February 20215
1 Planning your Qlik Sense Enterprise deploymentlmultiple Qlik Sense Enterprise deploymentslmultiple QlikView Server deploymentslQlikView Server and Qlik Sense Enterprise deploymentsApplying the same signed key to multiple deployments lets you share the same users and access types.Users can access all connected deployments using the same Professional or Analyzer access allocation.Qlik Sense EnterpriseQlik Sense Enterprise is the server version of Qlik Sense that you can deploy on a single node, or on multiplenodes. Qlik Sense Enterprise deployments are licensed and activated using a serial and control number, or asigned license key. Your Qlik Sense Enterprise license is based either on access types, or on tokens.Access typesAccess types licenses are the Professional and Analyzer Users licenses (user-based) and Analyzer Capacitylicenses (capacity-based). You can combine these for a subscription based license if you use the signedlicense key when your deployment is activated. You can combine only user-based licenses if you are using aperpetual license.After changing to a license with a signed key, you cannot return to using the old LEF basedlicense model.TokenYou use tokens to allocate access passes to users so that they can access Qlik Sense. The LEF determinesthe number of tokens that you can allocate to different access passes. A user without an access pass cannotaccess apps.With a Qlik Sense Token license you use tokens to allocate access passes to users. You can allocate useraccess and login access.The token license is available only to customers with existing Qlik Sense Token licenses.Core-based siteQlik Sense Enterprise core-based sites are licensed based on the number of CPU cores on which thesoftware will operate. A Core means a single processing unit within a processor or CPU, whether physical orvirtual, including a vCPU or virtual core, which is capable of executing a single software thread at a time.Qlik NPrintingYou can install and configure Qlik NPrinting to connect to QlikView documents or Qlik Sense apps. Thelicensing requirements and procedures are different depending on if you connect Qlik NPrinting to QlikViewor Qlik Sense.Deploy Qlik Sense Enterprise on Kubernetes - Qlik Sense, February 20216
1 Planning your Qlik Sense Enterprise deploymentQlik NPrinting versions 16.0.0.0 and later are licensed by a LEF. If you are using an earlier version of QlikNPrinting, we suggest that you upgrade to Qlik NPrinting versions 16.0.0.0 or later.A Qlik Sense token is not required for the Qlik NPrinting service account. However, becauseyou often perform troubleshooting within the Qlik NPrinting service account, it is helpful toassign a token to the Qlik NPrinting service account so that it has access to the Qlik Sensehub.Qlik Sense licensesQlik Sense Enterprise is the server version of Qlik Sense that you can deploy on a single node,or on multiple nodes. Qlik Sense Enterprise licenses are based either on access types, or ontokens.For detailed information on Qlik Sense licensing options, see Qlik's legal terms, product terms, and LicensingService Reference Guide: Qlik Legal Terms Qlik Product Terms Qlik Licensing Service Reference GuideIf you want to set up Qlik Sense Enterprise SaaS or Qlik Sense Enterprise on Kubernetes,please contact your Qlik representative or Qlik Support to obtain a valid license for the setup.Unified licenseAs of the April 2019 releases of Qlik Sense and QlikView, Qlik Sense customers can use a unified license inmultiple deployments. A unified license shares the same signed key between:lmultiple Qlik Sense Enterprise deploymentslmultiple QlikView Server deploymentslQlikView Server and Qlik Sense Enterprise deploymentsApplying the same signed key to multiple deployments lets you share the same users and access types.Users can access all connected deployments using the same Professional or Analyzer access allocation.Qlik Sense EnterpriseA Qlik Sense Enterprise deployment can be licensed using two different models: the serial and controlnumber and the signed license key. The License Enabler File (LEF) defines the terms of your license and theaccess types that you can allocate to users. Your Qlik Sense Enterprise license is based either on accesstypes, or on tokens. A core-based license is also available. The use of a signed license key is required for QlikSense Enterprise SaaS and Qlik Sense Enterprise on Kubernetes deployments, and for the use of capacitybased licenses.With a signed license key, you need internet access (direct or through a proxy) to access the cloud-basedlicense backend, for user assignments, analytic time consumption, and product activations.Deploy Qlik Sense Enterprise on Kubernetes - Qlik Sense, February 20217
1 Planning your Qlik Sense Enterprise deploymentUser-based and capacity-based licensesA user-based license grants a predefined number of access allocations that can be assigned to unique andidentified users. In Qlik Sense Enterprise, user-based licenses are either Professional and Analyzer Userslicenses, or User access passes allocated with a Token license.A capacity-based license grants a predefined number of time allocations for accessing Qlik Sense Enterprisethat can be used by identified or anonymous users. In Qlik Sense, capacity-based licenses are either basedon Analyzer Capacity access, or Login access pass allocated with a Token license.Access typesAccess types licenses are the Professional and Analyzer Users licenses (user-based) and Analyzer Capacitylicenses (capacity-based). You can combine these for a subscription based license if you use the signedlicense key when your deployment is activated. You can combine only user-based licenses if you are using aperpetual license.After changing to a license with a signed key, you cannot return to using the old serial andcontrol number license model.Professional and Analyzer Users licenseA Professional and Analyzer Users license is composed of Professional and Analyzer access types.llProfessional access (user-based) is allocated to an identified user to allow the user to access streamsand apps within a Qlik Sense site. The professional access is intended for users who need access toall features in a Qlik Sense installation. A user with professional access can create, edit, and publishsheets or apps, and make full use of the available features, including administration of a Qlik Sensesite.Analyzer access is allocated to an identified user to allow the user to access streams and apps in thehub. The analyzer access is intended for users who consume sheets and apps created by others. Auser with analyzer access cannot create, edit, or publish sheets or apps, but can create and publishstories, bookmarks and snapshots based on data in apps. The user can also print objects, and exportdata from an object to Excel.Analyzer Capacity licenseAn Analyzer Capacity license is composed of Analyzer Capacity access type.lAnalyzer capacity is a consumption-based license type, which is similar to analyzer access regardingavailable features. Users can access streams and apps in the hub and consume sheets and appscreated by others. Analyzer capacity access allows users to create and publish stories, bookmarks,and snapshots based on data in apps. Creating, editing, or publishing sheets or apps is not possible.With an analyzer capacity license, you subscribe to analyzer time, a defined amount of minutes permonth (calendar date). These minutes are shared between users and can be consumed by anyonewho is part of the user group, including anonymous users. Consumption is measured in units of 6minutes. For each new 6-minute period, a unit is consumed.Deploy Qlik Sense Enterprise on Kubernetes - Qlik Sense, February 20218
1 Planning your Qlik Sense Enterprise deploymentDynamic access assignmentDynamic access assignment is available for Qlik Sense Enterprise on Kubernetes and Qlik Sense EnterpriseSaaS deployments and is managed in the Management Console.Choose between four options:llllDynamic assignment enabled for both professional and analyzer access:Professional access is assigned, if available, otherwise analyzer access. If neither of those areavailable, analyzer capacity is assigned, if available.Dynamic assignment enabled only for professional access:Professional access is assigned, if available, otherwise analyzer capacity is assigned, if available.Dynamic assignment enabled only for analyzer access:Analyzer access is assigned, if available, otherwise analyzer capacity is assigned, if available.Dynamic assignment disabled for both professional and analyzer access:Analyzer capacity access is assigned, if available.You can upgrade from analyzer access to professional access, but not downgrade from professional toanalyzer.If you change to a new license key, all your assignments are removed, because they are associated with thelicense, not the tenant. However, if you start using the old license key again, the assignments will be present.TokenYou use tokens to allocate access passes to users so that they can access Qlik Sense. The License EnablerFile (LEF) determines the number of tokens that you can allocate to different access passes. A user withoutan access pass cannot access apps.The token license is available only to customers with existing Qlik Sense Token licenses.There are two types of access passes that can be allocated using tokens:llUser access pass (user-based) is assigned to unique and identified users allowing them unlimitedaccess to apps, streams, and other resources.Login access pass (capacity-based) allocates a block of passes to a group for infrequent or anonymousaccess. Allows full access for a limited period.When you allocate tokens, the number of available tokens is reduced. Each access type costs a certainnumber of tokens, and if the token balance is zero or insufficient, you cannot allocate more to the accesstypes. You can free up tokens and choose to use the tokens differently. The number of tokens for the QlikSense site can be increased or decreased by activating a new license.Core-based siteQlik Sense Enterprise core-based sites are licensed based on the number of CPU cores on which thesoftware will operate. The license is administered using a License Enabler File (LEF), which limits themaximum number of cores on which the Qlik associative engine and its components may operate. A Coremeans a single processing unit within a processor or CPU, whether physical or virtual, including a vCPU orvirtual core, which is capable of executing a single software thread at a time.Deploy Qlik Sense Enterprise on Kubernetes - Qlik Sense, February 20219
1 Planning your Qlik Sense Enterprise deploymentLicense Enabler FileIn Qlik Sense there are two alternative license models: the serial and control number and thesigned license key. The License Enabler File (LEF) defines the terms of your license and theaccess types that you can allocate to users.When licensing Qlik Sense using a serial and control number, the LEF can be downloaded when the serialnumber and the control number have been entered in the Qlik Management Console (QMC). The LEF canalso be pasted directly into the QMC, if, for example, no network connection is available. There are twolicense types that can be activated using a serial and control number: Professional and Analyzer Userslicenses, and Qlik Token licenses.When licensing Qlik Sense using a signed key, the LEF file is stored in the License Backend.If you want to set up Qlik Sense Enterprise SaaS or Qlik Sense Enterprise on Kubernetes,please contact your Qlik representative or Qlik Support to obtain a valid license for the setup.Professional and Analyzer Users licenseProfessional and Analyzer Users licenses grant a predefined number Professional and Analyzer (user-based)access type allocations. The LEF file determines the allocation of the access types.Analyzer Capacity licenses (capacity based) can only be licensed using a signed key. Whencombining professional, analyzer, and analyzer capacity access types in the same Qlik SenseEnterprise installation, you must license it using a signed key.Token licenseYou use tokens to allocate access passes to users so that they can access Qlik Sense. The License EnablerFile (LEF) determines the number of tokens that you can allocate, and holds the number of tokens availablefor the central node in a site. This means that a Qlik Sense site needs at least one (1) LEF. A user without anaccess pass cannot access apps.The token license is available only to customers with existing Qlik Sense Token licenses.You cannot use QlikView CAL-based licenses with Qlik Sense as the tokens are notcompatible with the Client Access Licenses (CALs) used in QlikView.Increase in tokensWhen the number of tokens in the LEF increases (for example, when buying additional tokens), the newtokens are added to the pool of unallocated tokens that can be used to allocate access passes that allowusers to access Qlik Sense.Deploy Qlik Sense Enterprise on Kubernetes - Qlik Sense, February 202110
1 Planning your Qlik Sense Enterprise deploymentDecrease in tokensWhen the number of tokens in the LEF decreases, the following happens:1. Unallocated tokens are removed.2. If step 1 is not enough to meet the decreased number of tokens in the LEF, any tokens that are freedup by removal of access passes cannot be used for new allocations until the number of allocatedtokens is below the new number set in the LEF.Access assignmentQlik Sense Enterprise licenses are based either on access types, or on tokens. Depending onyour license, you can allocate either access types or access passes to users, to allow them toaccess Qlik Sense.llAccess types licenses are the Professional and Analyzer Users licenses (user-based) and AnalyzerCapacity licenses (capacity-based).With a Professional and Analyzer Users license you can allocate professional access and analyzeraccess.With an Analyzer Capacity license you can allocate analyzer capacity access, where consumption istime based (analyzer time).With a Qlik Sense Token license you use tokens to allocate access passes to users. You can allocateuser access and login access.Access typesProfessional and Analyzer Users licenses and Analyzer Capacity licenses grant a predefined number ofaccess allocations. The License Enabler File (LEF) defines the terms of your license and the access typesthat you can allocate to users. You can combine these for a subscription based license if you use the signedlicense key when your deployment is activated. You can combine only user-based licenses if you are using aperpetual license. You must use a license with a signed key if you are licensing analyzer capacity access.Professional accessProfessional access is allocated to an identified user to allow the user to access streams and apps within aQlik Sense site. The professional access is intended for users who need access to all features in a Qlik Senseinstallation. A user with professional access can create, edit, and publish sheets or apps, and make full use ofthe available features, including administration of a Qlik Sense site.For Qlik Sense installations licensed with a serial and control number, if you remove professional accessallocation from a user, the access type is put in quarantine, if it has been used within the last seven days. If ithas not been used within the last seven days, the professional access is released immediately. You canreinstate quarantined professional access, to the same user, within seven days.Quarantine is not enforced on Qlik Sense installations that are licensed with a signed license key.Deploy Qlik Sense Enterprise on Kubernetes - Qlik Sense, February 202111
1 Planning your Qlik Sense Enterprise deploymentThe maximum number of parallel user connections for a single user of this type of access pass is five (5).Ifyou use a license with a signed license key, accessing the QMC also counts and adds to the maximumnumber of parallel sessions, which is five. To avoid unnecessary session consumption, the root admin shouldnot be allocated any type of access.When a user with the maximum number of parallel user connections ends a connection (for example, bylogging out) five minutes must pass before the user can use the access pass to add another connection (forexample, by logging in).Analyzer accessAnalyzer access is allocated to an identified user to allow the user to access streams and apps in the hub.The analyzer access is intended for users who consume sheets and apps created by others. A user withanalyzer access cannot create, edit, or publish sheets or apps, but can create and publish stories, bookmarksand snapshots based on data in apps. The user can also create bookmarks, print objects, stories, and sheets,and export data from an object to Excel.For Qlik Sense installations licensed with a serial and control number, if you remove analyzer accessallocation from a user, the access type is put in quarantine, if it has been used within the last seven days. If ithas not been used within the last seven days, the analyzer access is released immediately. You can reinstatequarantined analyzer access, to the same user, within seven days.Quarantine is not enforced on Qlik Sense installations that are licensed with a signed license key.The maximum number of parallel user connections for a single user of this type of access pass is five(5).When a user with the maximum number of parallel user connections ends a connection (for example, bylogging out) five minutes must pass before the user can use the access pass to add another connection (forexample, by logging in).Analyzer capacity accessAnalyzer capacity is a consumption-based license type, which is similar to analyzer access regardingavailable features. Users can access streams and apps in the hub and consume sheets and apps created byothers. Analyzer capacity access allows users to create and publish stories, bookmarks, and snapshots basedon data in apps. Creating, editing, or publishing sheets or apps is not possible.With an analyzer capacity license, you subscribe to analyzer time, a defined amount of minutes per month(calendar date). These minutes are shared between users and can be consumed by anyone who is part of theuser group, including anonymous users. Consumption is measured in units of 6 minutes. For each new 6minute period, a unit is consumed.Access passesWith a Qlik Sense Token license you use tokens to allocate access passes to users. The License Enabler File(LEF) determines the number of tokens that you can allocate to different access passes. A user without anaccess pass cannot access apps.User access passThis type of access pass allows a unique and identified user to access the hub.Deploy Qlik Sense Enterprise on Kubernetes - Qlik Sense, February 202112
1 Planning your Qlik Sense Enterprise deploymentThe access pass is valid within an entire Qlik Sense site. For example, if a user first connects to a node in theUSA and then, at a later stage, connects to a node in the UK, the user consumes the same access pass, ifthe two nodes are connected to the same central node.The maximum number of parallel user connections for a single user of this type of access pass is five(5).When a user with the maximum number of parallel user connections ends a connection (for example, bylogging out) five minutes must pass before the user can use the access pass to add another connection (forexample, by logging in).One (1) token corresponds to one (1) access pass. The access passes are allocated using the QlikManagement Console (QMC).You can have both a user access pass and the possibility to consume login access passes. Ifyou have five active sessions, opening an additional session will consume from your loginaccess passes.Removing user access pass allocationWhen a user access pass is removed, it enters a quarantine for seven (7) days, counting from the last timethat the access pass was used. For example, if the access pass is used on January 10, the tokens used toallocate the access pass are not available for new allocations until January 18. During the quarantine period,the original allocation of the access pass can be reinstated, which means that the quarantine period ends andthe user can start using the access pass again.Login access passThis type of access pass allows an identified or anonymous user to access the hub for a maximum of 60continuous minutes per 28-day period. If the user exceeds the 60 minutes time limitation, the user connectiondoes not time out. Instead, another login access pass is used. If no more login access passes are available,the user connection is discontinued.llIf an identified user is disconnected, the user can re-connect and continue to use the same accesspass, if re-connecting within the 60 minutes.If an anonymous user is disconnected, the user gets a new access pass when re-connecting.The login access pass tracks the number of logins and runs over 28 days. For example, if 1000 logins areassigned to Group A, the users in Group A can use 1000 logins over 28 days. If 100 logins are consumed onDay 1, the 100 logins are available again on Day 29.The maximum number of parallel user connections for a single user of this type of access pass is five (5).Note that this only applies to identified users. An anonymous user can only have one (1) user connection.When a user with the maximum number of parallel user connections ends a connection (for example, bylogging out) five minutes must pass before the user can use the access pass to add another connection (forexample, by logging in). However, a user can have more connections than allowed by a single access pass byconsuming additional access passes.One (1) token corresponds to ten (10) access passes. The access passes are allocated using login accessgroups in the QMC.Deploy Qlik Sense Enterprise on Kubernetes - Qlik Sense, February 202113
1 Planning your Qlik Sense Enterprise deploymentApp reloads will extend the session and consume access passes also when the app is notactively used. If a browser page is open with an app, app reloads will result in additional accesspass consumption.Removing login access pass allocationWhen a login access group is removed, the tokens used to allocate the access pass become available inaccordance to the following procedure:1. For every ten (10) unused login access passes, one (1) token is freed up.2. For every ten (10) login access passes that leave the used state after the period specified in the Loginaccess pass (page 13) section above has passed, one (1) token is freed up.See also:1.2Before you install Qlik Sense Enterprise onKubernetesTo successfully plan and prepare for your Qlik Sense Enterprise on Kubernetes deployment, do the following:System requirementsCheck that your environment fulfills the system requirements.Supported browsersCheck that your browsers are supported.Multi-cloud servicesUnderstand the Qlik Sense services.System requirements for Qlik Sense EnterpriseThis section lists the requirements that must be fulfilled by the target system in order to successfully installand run Qlik Sense.Deploy Qlik Sense Enterprise on Kubernetes - Qlik Sense, February 202114
1 Planning your Qlik Sense Enterprise deploymentQlik Sense Enterprise on WindowsQlik Sense Enterprise on Windows requirementsItemRequirementslMicrosoft Windows Server 2012 R2lMicrosoft Windows Server 2016lMicrosoft Windows Server 2019For development and testing purposes only:PlatformslMicrosoft Windows 10 (64-bit version only)These operating systems are supported by Qlik Sense. Third-partysoftware may require service packs to be installed.Multi-core x64 compatible processorsProcessors(CPUs)Advanced Vector Extensions (AVX) supportWe recommend that you use at least 4 cores per node in a Qlik Analytics Platformdeployment.8 GB minimum (depending on data volumes, more may be required)MemoryQlik Sense is an in-memory analysis technology. The memory requirements for the QlikSense products are directly related to the amount of data being analyzed.Disk space5.0 GB total required to installDisk shareSMB & NFSllStorageA network file share is required for the storage to be accessible by all servers inthe site. In case of a single-server deployment, local disk storage may besufficient.Sufficient storage is required for the volume of apps and content used in thedeployment.Qlik periodically runs network file share performance tests on Qlik Senseusing WinShare, and FreeNAS with SMB 3.0. For more information onnetwork file share solutions, contact your Qlik representative.SecuritylMicrosoft Active DirectorylMicrosoft Windows Integrated AuthenticationlThird-party securityDeploy Qlik Sense Enterprise on Kubernetes - Qlik Sense, February 202115
1 Planning your Qlik Sense Enterprise deploymentItemRequirementsWebSocketsWeb browsers and infrastructure components (such as proxies and routers) must supportWebSockets.NET4.8 or higherframework4.0 or higherWhen installing or upgrading Qlik Sense Enterprise Client-Managed,several unsigned PowerShell scripts are executed. If your company has apolicy only allowing the execution of signed scripts, you will have tobypass this policy during installation or upgrade. See SetExecutionPolicy for more information on the PowerShell execution policy.PowerShellPostgreSQL 9.6.x (included in the installer), 11.x (not included in the installer), 12.x (notincluded in the installer, must not be used with Centralized logging )RepositoryPostgreSQL is included in the Qlik Sense setup
Review the Qlik Sense Enterprise system requirements. Qlik product licenses Understand how Qlik Sense uses license keys and LEF for site licensing. Understand how Qlik Sense uses tokens for user access allocation (token-based licensing). Ensure that you have your Qlik Sense license key available.
User and access types for Qlik Sense SaaS and QSE Client-Managed editions are listed below. Qlik Sense Tokens remain available only to customers with existing Qlik Sense Token licenses. A Qlik Sense site refers to a deployment, which is centrally managed with a single license key or SaaS tenant and may cover multiple servers or nodes ("Site").
Upgrading to Qlik Sense June 2017 or later after uninstalling Qlik Sense 3.1 SR2 or later107 Upgrading to Qlik Sense June 2017 or later from Qlik Sense versions earlier than 3.1 SR2108 5.2 Upgrading and migrating from synchronized to shared persistence 111
Sense and QlikView applications (apps) in a customer's Qlik Sense Enterprise SaaS tenant. This means users have a single location to open and consume their Qlik apps. In addition to hosting Qlik apps, Qlik Sense Enterprise SaaS provides the ability to add links to other types of reports and assets such as documentation, providing a single .
Qlik for supply chain: forecasting and planning 6 Qlik for supply chain: sourcing and supplier performance 8 Qlik for supply chain: production insights 10 Qlik for supply chain: warehousing and distribution 12 Qlik for supply chain: transportation, storage and logistics 14 Qlik for supply chain: fleet management 16
Architecture Qlik NPrinting is a server based component that can be added to an existing QlikView and/or Qlik Sense environment. Qlik NPrinting is not a stand alone solution, it can only be used in conjunction with QlikView or Qlik Sense. The Qlik NPrinting server is responsible for sourcing data securely
Qlik Sense Architecture Overview 2 PL AT FORM Qlik Sense is the Qlik next-generation platform for modern, self-service oriented analytics. It supports the full spectrum of discovery use cases from visualization to reporting, all within a governed multi-cloud architecture. With Qlik Sense, your organization gets scalability,
Discuss concepts of data visualization and how they are implemented in Qlik Sense. Identify best practices for Qlik Sense visualization design. Share insights with Qlik Sense guided storytelling. Explain how Qlik Sense's responsive design enables developing multi-screen design. Prepare the apps and share them with others.
3/15/2021 6105636 lopez richard 3/15/2021 5944787 padilla elizabeth 3/15/2021 6122354 rodriguez alfredo 3/16/2021 6074310 aldan francisco 3/16/2021 6060380 bradley vincent 3/16/2021 6133841 camacho victor 3/16/2021 6100845 cardenas cesar 3/16/2021 6133891 castaneda jesse .
