STEP by STEP : QlikSense Installation 2025

 

QLIKSENSE INSTALLATION 2025

Pre-Installation Checklist

Before you begin, ensure the following:

• System Requirements: Verify that your server meets the minimum hardware and software requirements for Qlik Sense Enterprise. This includes supported versions of Windows Server, sufficient RAM, CPU, and disk space.

• Microsoft .NET Framework: Ensure that .NET Framework 4.8 or higher is installed. If not, the Qlik Sense installer will prompt you to install it.

• User Accounts: Create the necessary user accounts on the server to run Qlik Sense services.

• File Share: Set up a file share accessible to the central node and any rim nodes in a multi-node setup. This will store Qlik application data.

• Antivirus Software: Be aware that antivirus software can impact performance. Ensure it's configured to minimize interference with Qlik Sense operations.

---

📥 Downloading the Installer

1. Access Qlik Product Downloads: Navigate to the Qlik Product Downloads 

2. Select Qlik Sense Enterprise: Choose Qlik Sense Enterprise on Windows.

3. Download the Installer: Select the appropriate version (e.g., May 2025) and download the installer file.

---

🛠️ Installation Steps

1. Run the Installer: Right-click the downloaded installer file and select Run as administrator.

2. License Agreement: Read and accept the Qlik User License Agreement.

3. Cluster Setup: On the "Create or join a cluster" screen, select Create cluster

4. Host Name: Enter the fully qualified domain name (FQDN) of your server.

5. Repository Database:

   • Create a new database: Enter a password for the database user and superuser.

   • Connect to an existing database: Provide the database hostname and user credentials.

6. Qlik Services:

   • Enter the username and password for the Qlik services.

   • Configure additional settings like database connection pool size and listening ports.

7. Object Bundles: Choose whether to install additional object bundles like Dashboard and Visualization bundles.

8. Installation: Click Install to begin the installation process.

9. Completion: Once installation is complete, you will see a success message.

---

🔄 Post-Installation Configuration

1. Start Qlik Sense Services: Ensure all Qlik Sense services are running.

2. Access Qlik Management Console (QMC): Open a browser and navigate to https://<your-server-name>/qmc.

3. License Qlik Sense: In the QMC, enter your Qlik Sense license key.

4. Configure Data Connections: Set up necessary data connections for your applications.

5. Deploy Applications: Upload and configure your Qlik Sense applications.

---

🔐 Security Considerations

• Domain Controller: Avoid installing Qlik Sense on a domain controller. It's not supported and can impact performance and security. 

• Firewall and Ports: Ensure that the necessary ports are open and not blocked by firewalls. Refer to the Qlik Sense ports documentation for details.

STEP by STEP : QlikSense Migration 2024

Qlik Sense Migration: Server-to-Server Steps (Qliksense 2024)

✅ Pre-Migration Planning

1. Document Existing Environment

   • Qlik Sense version

   • License key

   • Data connections

   • User directory connectors (UDCs)

   • Security rules

   • Certificates (for HTTPS)

   • Scheduler tasks

   • Custom extensions or widgets

2. Verify Both Servers

   • Make sure the target server has the same OS and Qlik Sense version as the source.

   • If not, install the same version on the target first.

   • Ensure both servers are fully patched and meet Qlik’s system requirements.

3. Backup the Source Server

   • Certificates (via Qlik Sense QMC or MMC)

   • PostgreSQL repository database (QSR)

   • Application files from:

     • C:\ProgramData\Qlik\Sense\Apps

     • C:\ProgramData\Qlik\Sense\Repository\Content

   • Custom connectors/extensions if any

   • Qlik Sense configuration files from C:\ProgramData\Qlik\Sense\Repository\Exported Certificates

---

🧰 Migration Process

1. Install Qlik Sense on Target Server

• Do a fresh install of the same version of Qlik Sense on the new server.

• Choose "Central node" and "Use existing certificates" (optional if restoring from backup).

2. Stop Services on Both Servers

• Stop all Qlik Sense services:

  QlikSenseRepositoryService
  QlikSenseEngineService
  QlikSenseSchedulerService
  QlikSenseProxyService
  QlikSenseServiceDispatcher
  QlikSensePrintingService
  

3. Copy the PostgreSQL Repository Database

• Backup using Qlik-provided tool or standard pgAdmin method:

  C:\Program Files\Qlik\Sense\Repository\PostgreSQL\<version>\bin\pg_dump.exe -U postgres -Fc QSR > QSR.backup
  

• Move the .backup file to the target server and restore it:

  pg_restore.exe -U postgres -d QSR -v QSR.backup
  

4. Transfer Certificates

• Export the certificates from the old server using QMC or MMC.

• Copy them to the same location on the new server:
  C:\ProgramData\Qlik\Sense\Repository\Exported Certificates\

5. Restore Application and Content Folders

• Copy contents of these folders to the same locations on the target server:

  • C:\ProgramData\Qlik\Sense\Apps

  • C:\ProgramData\Qlik\Sense\Repository\Content

  • Any custom folders used for extensions, connectors, etc.

6. Adjust Configuration Files

• Update hostnames and paths in:

  • Repository.exe.config

  • Scheduler.exe.config

  • Any custom configuration scripts

---

🔐 Post-Migration Tasks

1. Start Qlik Sense Services

   • Start all services in proper order or reboot the server.

2. Verify Services

   • Open the Qlik Management Console (QMC).

   • Check if all services are running, users are visible, and apps are accessible.

3. Reapply License

   • In QMC, re-enter the license if needed (particularly if MAC address has changed).

4. Reconfigure Data Connections (if needed)

   • Update paths if folder structures have changed.

5. Test Everything

   • Open apps via the Hub.

   • Validate reload tasks.

   • Test user access and security rules.

   • Run a few sample reloads and data connection tests.

6. DNS or Hostname Redirection

   • Update DNS to point to the new server IP (optional).

   • Or reassign the old hostname/IP to the new server.

Nprinting- (ver -16) Server Certificate Update Process

Certificate Update Process for QLIK Nprinting

Import the certificate to QV Nprinting Server

1. Copy the certificate to the Server that will host QlikView Nprinting Server(.pfx format)

2. Launch an elevated Microsoft Management Console (MMC)

3. Add the certificates snap-in > Local Computer Account

4. Expand Certificates > Personal > Certificates

5. Right Click > All Tasks > import

6. Click Next

7. Browse to the certificate then click next

8. Type the password that was created when the certificate was created and click next

9. Import the certificate in the personal store and click next

10.  Review the information and click Finish

Pre-requisite steps

Generate the Thumbprint

1. From the MMC console double click on the certificate in the Personal store > select the details Tab and scroll down to thumbprint

2. Copy the thumbprint into Notepad > Find/Replace <space> replace with <no spaces>

a.    Example 21 7b 64 d2 3a… should become 217b64d23a

3. Download Guidgen.exe from Microsoft to generate a unique GUID

a.    http://www.microsoft.com/en-au/download/details.aspx?id=17252

4. Execute Guidgen.exe

a.    Create a registry format GUID

b.    Copy the GUID to Notepad

 

Bind http to SSL using netsh

1. Stop Nprinting Services

2.Launch command prompt

    Enter the following:-

3. netsh http delete sslcert ipport= 0.0.0.0:9000
4. netsh http delete sslcert ipport= 0.0.0.0:9001

5. 

netsh http add sslcert ipport=0.0.0.0:9000 certhash=0000000000003ed9cd0c315bbb6dc1c08da5e6 appid={00112233-4455-6677-8899-AABBCCDDEEFF}

netsh http add sslcert ipport=0.0.0.0:9001 certhash=0000000000003ed9cd0c315bbb6dc1c08da5e6 appid={00112233-4455-6677-8899-AABBCCDDEEFF}

a.    ipport parameter specifies the IP address and port (ensure the ipport = 0.0.0.0 (do not replace with the actual IP Address)

b.    certhash parameter specifies the thumbprint of the certificate (previously copied to notepad).

c.    appid parameter is the GUID (previously copied to notepad)

6. Start Nprinting Services.

How to clear the cache used by QlikView Server

How to clear the cache used by QlikView Server

Description
The cache is handled automatically by QlikView Server and should not be cleared manually. However in some situations there might be a reason to clear the cache on a regular basis, typically once a day.


Resolution
The first and obvious way to clear the cache is to restart the QlikView Server service. This can be donemanually or through a scheduled stop & start of the service using the command netstop & netstart.

net stop QlikViewServer
net start QlikViewServer

Another option is to add the following entry in the [Settings 7] entry in the settings.ini file for QlikView Server,located in %ProgramData%\QlikTech\QlikView Server:
[Settings 7]
ClearCacheTimesPerDay=1

The value set is the number of times per day the cache will be cleared, syncronized at midnight. A value of 1will clear the cache once per day at midnight.

Attention: Clearing the cache may lead to increased response times from the user's perspective. Use withcaution!

Qlikview Server Clustering

Qlikview Server Clustering

Prerequisites:

Following requirements have to be met before starting the QlikView Server cluster configuration:

• A QlikView Server license allowing QlikView Server clustering.  That means that the QlikView Server LEF must consist of an entry “NUMBER_OF_CLUSTER_NODES;X;;” where X is 2 or higher
• AccessPoint (based on IIS or QlikView Web Server), Management Service, Qlikview Distribution Service, Directory Service Connector are already installed on QlikView system in the network
• A domain user to run the QlikView services on every machine is available.
• A Windows Network-Share
• All QlikView Server cluster nodes need read /write access to the following data centrally stored:
• Server status files aka .pgo
• QlikView Documents aka QVWs
• QlikView Server Logs aka audit, session, performance, event logs

Step-by-Step Installation

1. Prepare the shared device:

Create folders for the files accessed by every QlikView Server cluster node.:

• QvRoot for the .pgo-Files
• QvMount for a Mounted Folder
• QvLogs for the Logfiles
• QvExtensions for the extensions
• QvTemp for the temp files

2. Prepare the cluster nodes:

On each planned QlikView Server cluster node perform the following configuration

•   Login as Administrator
•   Turn Off Windows Firewall 

 

•   Deactivate Internet Explorer Enhanced Security Configuration for Administrators

• Add Domain User the QlikView services should use to Local Administrators Group
• Start QlikView Server setup and install feature “QlikView Server” only

NOTE: Do not install any other services such as QlikView Management Service on multiple nodes in the cluster!

• During the setup check that you will specify the QlikView service account later 

• Do not restart the system immediately after install is completed, but
    o   Add QlikView service user to “QlikView Administrator Group”
    o   Change Logon setting of the QlikView Server Service to the QlikView Service user
• Restart the system

3. Configure QlikView Server-Cluster in QlikView Enterprise Management Console

• Open QlikView Enterprise Management Console and register QlikView Server licence with activated cluster nodes

• Add first QlikView Server cluster node below QlikView Servers

• Switch Root,Mount,Logs,Extensions and Temp Folders to Shared Device folder paths using UNC-syntax (i.e \\Fileshare\QvRoot)

• Press Apply and let QlikView Enterprise Management Console initiate restart of QlikView Server service
• Add each additional QlikView Server cluster node and activate them by entering control number of the registered QlikView Server license

• Press Apply and let QlikView Enterprise Management Console initiate restart of QlikView Server service on all nodes
• Verify all QlikView Server nodes are running

• Configure Load Balancing feature (Functionality see QlikView Server Reference Manual)

How to Change the Qlik Sense Service Account - Considerations when changing the Sense Service account

Work to Prepare for the activity:-

• Record the Share Path:
  • Navigate in the QMC > Service Cluster and record the Root Folder

Changing Qlik Sense dependencies

• Stop all Qlik Sense services
• Ensure permissions on the Program Files path (this should be provided by Local Administrator rights):
  • Navigate to the installation path (default: C:\Program Files\Qlik)
  • Select the Sense folder > Right Click > Properties > Security > Edit > Add
    • Lookup the new service account
    • Ensure that the account has Full control over this folder
• Ensure permissions on the %ProgramData% path (this should be provided by Local Administrator rights):
  • Navigate to the installation path (default: C:\ProgramData\Qlik)
  • Select the Sense folder > Right Click > Properties > Security > Edit > Add
    • Lookup the new service account
    • Ensure that the account has Full control over this folder
• Ensure access to the certificates used by Qlik Sense
  • Start > MMC > File > Add/Remove Snap-In > Certificates > Computer Account > Finish
    • Go into Certificates (Local Computer) > Personal > Certificates
    • For the Qlik CA server certificate
      • Select > Right Click > All Tasks > Manage Private Keys > Ensure that the new service account has control
    • If using a third party certificate, do the same
• Ensure access to the Service Cluster path used by Qlik Sense
  • Start > Computer Management > Shared Folders > Shares > Select the Share path
  • Right click on the Share Path > Properties > Share Permissions > Add the new service account to have full control
  • Open Windows File Explorer and navigate to the folder (e.g. C:\Share) > Right click on the folder > Security > Edit > Add the new service account to have full control
• Start the Qlik Sense Repository Database
• Ensure that the AppImport folder used by Qlik Sense for staging app imports will be accessible by the new service account:
  • Open a connection to the QSR database:
    • Open a Command Prompt
    • C:\"Program Files"\Qlik\Sense\Repository\PostgreSQL\9.6\bin\psql.exe -h localhost -p 4432 -U postgres -d QSR -e
      • Note: If Qlik Sense is installed in another location, then the above path will need to be adjusted
      • Note: If using Qlik Sense 3.x Shared Persistence, then the above path may need to be adjusted to the 9.3 directory rather than the 9.6 directory
  • Type in \x to enable extended mode on the terminal
  • For builds X-Y: SELECT "AppImportFolder" FROM "RepositoryServiceSettings";
  • For builds X-Y: SELECT "Temporaryfilepath" FROM "ServerNodeConfigurations";
  • If this path points to a user's profile or other path which the new service account does not have access to, then run this style of command:
    • UPDATE "public"."RepositoryServiceSettings" SET "AppImportFolder"='C:\foo' WHERE "AppImportFolder"='C:\Users\....';
    • UPDATE "public"."ServerNodeConfigurations" SET "Temporaryfilepath"='C:\foo' WHERE "AppImportFolder"='C:\Users\....';
    • Note: Ideal location is a path like C:\ProgramData\Qlik\Sense\Apps which is not tied to an individual user's account
• Ensure membership in the Local Groups that Qlik Sense requires:
  • Start > Computer Management
  • Navigate to Local Users and Groups > Local Groups
  • Add the new service account as a member of:
    • Administrators (if using this configuration option)
    • Performance Monitor Users
    • Qlik Sense Service Users
• Now for all Qlik service (except the Qlik Sense Repository Database Service) swap the account over by using the windows services control panel
• Start the remaining Qlik Sense Services
• Access the QMC to validate functionality, preferably as a previously configured RootAdmin
• Access the Data Connections section of the QMC
• Toggle the User ID field and change the data connections used by the License and Operations Monitor apps to use the new user ID and password:

• Execute the License Monitor reload task
• Add the RootAdmin role to the new service account
  • QMC > Users
  • Filter on the new UserID > Edit
  • Add RootAdmin role
• Inspect the configured User Directory Connectors and change the User ID and password combination if previously configured

External Dependencies:

• Go into the QMC > Data Connections section
• Inspect all Folder data connections and determine all network shares that the service account needs access to. Either change them yourself or alert the necessary teams to provide both Share and NT level access to these shares.
• Inspect all Data Connections and ensure that none use the old Service account and password
  • Follow up with necessary teams to provision access to data sources which used the old credentials.