Before Installing QlikView Server
Before installing QlikView Server, you need to consider:
- If Microsoft IIS is to be used as web server, it must be installed prior to QlikView Server.
- It is not possible to install QlikView Server to a server that acts as a domain controller.
- Internet protocol IPv4 or IPv6 is required for installation of QlikView Server.
- When installing QlikView Server/Publisher, several security groups are created. Several other security groups must be created following the installation. These must be properly configured to ensure that the appropriate services can run, and to ensure that users can access the appropriate functionality. Before you begin the installation, see Security Groups in QlikView Publisher Repository.
- It is recommended not to move folder locations after the QlikView Server installation is complete, since many settings depend on the initial file locations. If the location of QlikView Server has to be changed after the installation, uninstall QlikView Server and then reinstall.
- Any previously defined tasks are deleted when the QlikView Publisher license is activated.
Setup Procedure
Run the QlikView Server installation executable:
Microsoft Windows x64 version: QlikViewServer_x64Setup.exe
If the User Account Control dialog is displayed, click Yes to allow the program to make changes on this computer.
Click Next in the Welcome dialog.
Select the region for the location of the server. Click Next to continue.
Read the license agreement, select I accept the terms in the license agreement, and click Next to continue.
Enter the customer information for QlikView Server. Click Next to continue.
All files are installed in the specified folder. To change the root folder for the installed files, click Change to specify the preferred location. Finally, click Next to continue.
Select the type of installation you want to perform:
Full installation, Single machine with QlikView Webserver: Used to run all components on a single machine with QlikView Web Server as web server.
Full installation, Single machine with Microsoft IIS: Used to run all components on a single machine with Microsoft IIS as web server. This option is only available if IIS is installed on the target machine.
Custom installation, select profiles: If this option is selected you select the profiles you want to be included in the installation from the Profiles section in the dialog:
QlikView Server: Installs QlikView Server, Directory Service Connector, and the QlikView Server example documents.
Reload/ Distribute Engine: Installs the Reload Engine and the QlikView Distribution Service.
Management Console: Installs the QlikView Management Service together with the QlikView Management Console (QMC).
Webserver: Installs the QlikView Web Server.
To make further configuration of features to be installed, click Config. When done, click Next.
To use pre-defined configuration of features, click Next.
Set the account that the QlikView Server and Publisher services are to run under. Click Next to continue.
Note:The account that is used to run the QlikView services must have local administrator privileges.
You can also select I want to specify the account to be used for the services later.
Select the IIS Website from the drop-down list and click Next.
Note:This step is only applicable if Full installation, Single machine with Microsoft IIS was selected in Step 8. If not, proceed directly to the next step.
Select the Service Authentication method:
Use digital certificates: Authenticate communication between QlikView servers using digital certificates and SSL. This alternative is recommended in environments where not all servers have access to a common Windows Active Directory or when the security provided by certificate authentication is required. Note that digital certificates are only supported by Windows Server 2008 R2 and later.
Use QlikView Administrators Group: Authenticate communication between QlikView services based on membership in the local Windows group QlikViewAdministrators. This alternative can be used in environments where all servers that are part of the QlikView installation can authenticate using a common Windows Active Directory.
Click Next to continue.
Click Install to start the installation.
Note:This may take several minutes to complete.
Click Finish when the installation is complete.
Log off from Windows® and then log on again, so that group memberships added during the installation are updated.
Note:It may be sufficient to log off from Windows and then log on again. However, it is recommended to restart the machine to enable the QlikView Server functionality.
Logging the Installation
The setup procedure is logged when running the QlikView Server installation executable. The log files are as follows:
Microsoft Windows x64 version: QlikViewServerx64.wil
The log files are stored in the Temp folder of the user (for example, %UserProfile%\AppData\Local\Temp). Each time an installation is executed, a new file is generated, over-writing the previous log file.
Obtaining the MSI package
If the MSI package is needed for the installation, proceed as follows to extract it from the .exe file:
Start the installation from the .exe file and wait until the first dialog opens.
Locate the MSI file (often stored with a random name, for example, ed34g.msi) in the Temp folder in %UserProfile%\AppData\Local.
Copy the .msi file to another location.
Exit the .exe installation.
Install QlikView Server using the .msi file.
Completing the Installation
After successfully installing QlikView Server, a license must be registered in QlikView Management Console (QMC) to activate the installed software.
Note:If access is denied when starting QMC, log off from Windows and then log on again, so that group memberships added during the installation are updated.
Note:Running real-time anti-virus protection on the server degrades the performance of QlikView Server. It is recommended that the user documents, source documents, log directories, and .pgo files are excluded from the anti-virus scanning.
Running Microsoft IIS
Handling Timeouts
Note:This is only needed when using very large QlikView documents that return timeouts.
Proceed as follows to handle timeouts:
Open the %ProgramFiles%\QlikView\Server\QlikViewClients\QlikViewAjax\web.config file in a text editor (for example, Notepad).
Search for the following text:
<httpRuntime requestValidationMode="2.0" />
Edit the text so that it becomes:
<httpRuntime requestValidationMode="2.0" executionTimeout="900"/>
Save the file.
Enabling ASP.NET
If Microsoft IIS is used as web server, enable ASP.NET to ensure proper operation of the QlikView Server sample pages and the extended functions (for example, QlikView Server tunnel).
Optimizing the Performance
To optimize the performance when running Microsoft IIS and AJAX, turn on compression in the web server.
For information on how to configure IIS http compression:
Licensing
The licensing is used to authenticate QlikView Server and allow it to run on a specific machine.
Proceed as follows to enter the license for QlikView Server:
Go to System>Licenses in the QMC.
Select a QlikView Server or Publisher.
Fill in the Serial number and Control fields on the QlikView Server License or QlikView Publisher License tab (depending on whether QlikView Server or Publisher was chosen).
Note:Any previously defined tasks are deleted when the QlikView Publisher license is activated.
QlikView Server/Publisher License tab in QMC
The license is checked every time a document is opened. If the time limit specified by the License Enabler File (LEF) is reached, the QVS automatically enters offline mode, which means that it is reachable from the QMC, but not operational.
The License Enabler File (LEF), lef.txt, for QlikView Server is automatically saved in %ProgramData%\QlikTech.
The PubLef.txt file for QlikView Publisher is saved in %ProgramData%\QlikTech\ManagementService\Publisher LEF.
Click Update License from Server to download a new lef.txt file from the QlikView LEF server. This is primarily used when updating the number of Client Access Licenses (CALs).
If the LEF information cannot be accessed through the Internet, it can be obtained from the local vendor. In that case, copy the entire lef.txt file to the location mentioned above, or paste the LEF data using the corresponding field on the QlikView Server/Publisher License tab in QMC. Contact the local vendor for specific instructions.
Silent Installation
When running a silent installation, QlikView is installed with a limited set of or no dialogs at all. This means all features, properties, and user selections have to be known when creating the silent installation package. There are also some standard properties in Windows Installer Service that may be required.
To prepare a silent installation, the MSI file has to be extracted from the QlikView Setup.exe file.
A silent installation can be run with different interface levels:
/qn Completely silent.
/qb Basic user interface.
Add a + sign at end of the interface levels command to get a modal dialog at the end of the installation saying “Finished” and if it was successful or not.
The following silent installation command lines are recommended for QlikView:
msiexec /i QlikViewServerx64.msi Addlocal="all" IS_NET_API_LOGON_USERNAME="Domain\username" IS_NET_API_LOGON_PASSWORD="password" /qn+
Alternatively:
QlikViewServer_x64Setup.exe /s /v"/qn+ Addlocal="all" IS_NET_API_LOGON_USERNAME="Domain\username" IS_NET_API_LOGON_PASSWORD="password""
The command line above installs all features completely silently with a modal dialog at the end of the installation.
If just a limited set of the features are to be installed, change all to the name of the feature instead. If several features are to be installed, separate them with commas.
The following features can be installed:
DirectoryServiceConnector
ManagementService
QVS
QvsDocs
WebServer
DistributionService
SupportTools
QvsClients with the sub-features Plugin and AjaxZfc
MsIIS with the sub-features QvTunnel and QlikView Settings Service
Note:For the sub-features to be included in the installation, they have to be included in the list of features to be installed.
msiexec /i QlikViewServerx64.msi ADDLOCAL="all" DEFAULTWEBSITE="2" /qn+
This command line installs all features, including the virtual directories to another website than the default one. This requires a machine with Microsoft Internet Information Services (IIS) installed and more than one website on it. The site number also has to be known. Set DEFAULTWEBSITE to the site number where the virtual directories are to be installed. To find the number of the website, check IIS.
The installation procedure can be logged, using the following command:
msiexec /i QlikViewServerx64.msi ADDLOCAL="all" DEFAULTWEBSITE="2"/L*v log.txt /qn+
Settings
The following settings are good to know when designing a silent installation package:
Prerequisites
.NET Framework 4.7.2 or higher
Note:For .NET Framework 4.7.2 to work, Windows 10 must be updated to the Anniversary update Build 1607 or later.
Default installation folder (INSTALLDIR) ProgramFilesFolder\QlikView
Windows Installer Version 3.1 Schema 301
Default language English (United States) 1033
Require Administrative Privileges Yes
INSTALLEVEL 100, all features is set to 101 by default
Features
Silent Installation
There is a hidden feature called “Install”. Do not remove it.
IIS Four virtual directories and an Application pool are installed
Services Five services are installed
Dialogs
The QlikView installation has a number of dialogs, one of which is a Custom Setup dialog and one of which is a Website dialog. All dialogs set important properties. To find the value of a property, do a test installation with verbose logging. Note that the property values may differ depending on the language and operating system used.
Region
This dialog is used for specifying the region.
Property: REGION_LIST
Region dialog
License Agreement
This dialog displays the license agreement for the selected region.
Radio button: AgreeToLicense = "Yes"
License dialog
Customer Information
This dialog is used for entering the customer information.
Properties:
USERNAME
COMPANYNAME
Customer information dialog
Destination Folder
This dialog is used to set the default folder for the installation.
Destination folder dialog
Profiles
This dialog has several properties connected to it, since there are multiple profiles to choose from.
Select Full Installation, Single machine with QlikView Webserver to install everything, including QlikView Web Server, needed to run QlikView on a single machine. To use IIS instead, select Full Installation, Single machine with IIS (this option is only available if IIS is installed on the target machine).
To perform a custom installation, select Custom installation, select profiles and then select the profiles to install. The Webserver profile allows the user to choose between QlikView Web Server and IIS (if IIS is installed on the target machine).
Properties:
PROPQVS: QlikView Server
PROPDS: Publisher
PROPQMC: Management Console
PROPWEB, PROPIIS = 1 or 2: Webserver
PROPIIS (if IIS is installed) or PROPSTATE: Single Machine Install
Profiles dialog
Logon Information
This dialog, which is optional to use, is used to specify the user that is to run the services that are installed. When clicking Next, a Custom Action checks that the entered user is valid. The Custom Action, which is implemented by InstallShield, requires the machine to be part of a Domain to work properly.
Properties:
LOCALSERVICE
IS_NET_API_LOGON_USERNAME
IS_NET_API_LOGON_PASSWORD
Logon information dialog
Service Authentication
This dialog is used to select the type of service authentication. QlikView Administrators Group is selected by default.
Property: PROPCERT (1 = Digital certificates, 2 = QlikView Administrators Group)
Service authentication dialog
Ready to Install
This is the last dialog. Click Install to start the installation.
Ready to install dialog
Additional Dialogs
Custom Setup
This dialog is displayed when clicking Config in the Profiles dialog.
Custom setup dialog
Website
This dialog is displayed when selecting IIS as web server in the Profiles dialog.
Property: DEFAULTWEBSITE
Website dialog
MST
When creating an MST file, the MSI file is customized without any changes being made directly in the MSI. The MST file works as a filter on top of the MSI and allows changes to be made to the installation. For example, the default installation folder for QlikView Server is %ProgramFiles%\QlikView, but if that is changed to C:\QlikView in the MST file, the default folder is changed. The same thing can be done with the dialogs, which means properties can be preset, so that the installation can be run with a limited set of dialogs.
To create an MST file, an MSI repackaging studio (for example, InstallShield AdminStudio) is needed.
Note:Qlik does not supply any MST files and does not take any responsibility for MST files created by customers or partners.
Source:
https://help.qlik.com/en-US/qlikview/April2020/Subsystems/Server/Content/QV_Server/QlikView-Server/QVSRM_Installation.htm
https://help.qlik.com/en-US/qlikview/April2020/Subsystems/Server/Content/QV_Server/QlikView-Server/QVSRM_InstallationSilent.htm
Posts
