QlikView Server Reference Manual PDF

Server/Publisher
Version 11.0 SR1 for Microsoft Windows

Second Edition, Lund, Sweden, February 2012
Authored by QlikTech International AB

Copyright1994-2012QlikTechInternationalAB,Sweden.
Underinternationalcopyrightlaws,neitherthedocumentationnorthesoftwaremaybecopied,photocopied,
reproduced,translatedorreducedtoanyelectronicmediumormachine-readableform,inwholeorinpart,
withoutthepriorwrittenpermissionofQlikTechInternationalAB,exceptinthemannerdescribedinthe
softwareagreement.
QlikTechandQlikViewareregisteredtrademarksofQlikTechInternationalAB.
ActiveDirectory,Excel,InternetExplorer,Microsoft,.NET,SharePoint,SQLServer,Visual
Studio,Windows,Windows7,Windows2000,WindowsNT,WindowsServer,WindowsVista,
andWindowsXParetrademarksofMicrosoftCorporationintheUnitedStates,othercountries,orboth.
CASiteMinderisaregisteredtrademarkofComputerAssociates.
FirefoxandMozillaareregisteredtrademarksoftheMozillaFoundation.
IBMisatrademarkofInternationalBusinessMachinesCorporation,registeredinmanyjurisdictions
worldwide.
IntelandCoreDuoaretrademarksofIntelCorporationintheU.S.and/orothercountries.
NetWeaverandSAParetrademarksorregisteredtrademarksofSAPAGinGermanyandinseveralother
countries.
NovellisaregisteredtrademarkofNovell,Inc.,intheUnitedStatesandothercountries.
OracleisaregisteredtrademarkofOracleand/oritsaffiliates.
Salesforce.comisatrademarkorregisteredtrademarkofSalesforce.com,Inc.
WikipediaisaregisteredtrademarkoftheWikimediaFoundation.
Othertrademarksarethepropertyoftheirrespectiveownersandareherebyacknowledged.
2 QlikView Server/Publisher
Contents
Contents
Part 1 Introduction 7
1 Overview 9
1.1QlikView 9
1.2QlikTechSupportServices 9
1.3Conventions 9
1.4AboutthisDocument 10
2 Whats New in QlikView 11 Server? 11
3 System Requirements 15
3.1QlikViewServer 15
3.2QlikViewPublisher 16
Part 2 Installation 17
4 Upgrading QlikView 19
4.1UpgradeConsiderations 19
4.2UpgradeProcedure 19
4.3Multi-machinePreparation 20
5 Installing QlikView Server 23
5.1InstallationProfiles 23
5.2LoggingtheInstallation 24
5.3CompletingtheInstallation 24
6 Building a Farm 27
6.1Planning 27
6.2Root/FirstInstall 28
6.3AddingServicesonOtherMachines 28
6.4Clustering 28
Part 3 Architecture 31
7 Roles 33
7.1QlikViewwithPublisher 33
7.2QlikViewwithoutPublisher 34
7.4WebServer 36
7.5DirectoryServiceConnector 37
7.6ManagementService 38
7.7DistributionService 39
7.8ReloadEngine 39
8 Logging 41
8.1LoggingfromQlikViewServer 41
8.2SessionLog 41
8.3PerformanceLog 42
8.4EventLog 44
8.5End-userAuditLog 45
8.6ManagerAuditLog 45
9 Documents, Data, and Tasks 47
9.1UserDocuments 47
QlikView Server/Publisher 3
Contents
9.2SourceData 48
9.3SourceDocuments 48
9.4Tasks 48
10 Service by Service 51
10.2QlikViewDistributionService 54
10.3QlikViewPublisherRepository 56
10.4ConfigurationFiles 57
10.5WebServer 59
10.6DirectoryServiceConnector 62
10.7QlikViewManagementService 63
Part 4 Security 65
11 Security Overview 67
12 Protection of the Platform 69
12.1Functionality 69
12.2SpecialAccounts 69
12.3Communication 69
13 Authentication 71
13.1AuthenticationwhenUsingQlikViewServerinaWindowsUserEnvironment 71
13.2AuthenticationwithaQlikViewServerUsinganExistingSingleSign-onSoftwarePackage 72
13.3AuthenticationUsingneitherIWAnorSingleSign-onSoftware 73
13.4QlikViewServerAuthenticationUsingCustomUsers 74
14 Authorization 77
14.1DocumentLevelAuthorization 77
14.2DataLevelAuthorization 77
Part 5 Licensing 79
15 Client Access Licenses 81
15.1CALTypes 81
15.2Identification 82
15.3DocumentCALRestrictions 82
15.4CombiningDifferentCALs 82
15.5LicenseLease 83
15.6ClusterLicensing 83
15.7ColdStandbyServers 83
16 Editions of QlikView Server 85
16.1Editions 85
16.2FeaturesandLimitations 87
Part 6 Appendix 89
17 Silent Installation 91
17.1Settings 92
17.2Dialogs 92
17.3AdditionalDialogs 96
17.4MST 97
17.5AdditionalInformation 97
18 OEM 99
18.1General 99
Contents
18.2DetailedFunctionDescription 99
19 DSP Interface 101
19.1DirectoryServiceProvider 101
20 SNMP 103
20.1MIBFile 104
21 Deploying MSI Packages with Group Policies 107
21.1General 107
21.2DeployingtheMSIPackage 107
21.3Step-by-stepGuide 108
22 QlikView Server Extensions 113
22.1AddingExtensionstoQlikViewServer 113
23 Configuring Microsoft IIS for Custom Users 115
24 Triggering EDX Enabled Tasks 119
Contents
Part 1 Introduction
Part1Introduction
1 Overview
1 Overview
ThisdocumentdescribesQlikViewServerandcontainsinformationoninstallation,architecture,security,
andlicensing.Thedocumentalsoincludesanumberofappendixesthatprovideadditionalin-depth
information.
1.1 QlikView
QlikView Server
QlikViewServerisaplatformforhostingandsharingQlikViewinformationoveranintranetortheInternet.
QlikViewServerconnectsusers,clienttypes,documents,andobjectswithinasecureenvironment.
QlikView Publisher
QlikViewPublishermanagescontent,access,anddistribution.Byreducingdata,eachusercanbepresented
withtailoredinformation.TheQlikViewPublisherserviceanduserinterfacearefullyintegratedinto
QlikViewServerandQlikViewManagementConsole(QMC).
1.2 QlikTech Support Services

ContactQlikTechifproductsupport,additionaltraining,orconsultationconcerningapplication
developmentisneeded.ConsulttheQlikTechhomepageforcurrentinformationonhowtogetintouchwith
thesupportservices:
http://www.qlikview.com
QlikTechInternationalheadquarters:
QlikTech International
150 N. Radnor Chester Road
Suite E220
Radnor, PA 19087
USA
Phone: +1 (888)-828-9768
Fax: 610-975-5987
Forotherlocations,visittheQlikTechhomepage(seeabove).
1.3 Conventions
Style Coding
Menucommandsanddialogoptionsarewrittenin bold.Filenames,paths,andsamplecodearewrittenin
Courier.
1 Overview
Environment Variables
Thepathsdescribedinthisdocumentuseenvironmentvariables.Thevariablesandtheequivalentpathsin
WindowsVista,Windows7,andWindowsXParepresentedbelow.
Environment Windows Vista/
Windows XP
Variable Windows 7
%ProgramData% C:\ProgramData C:\Documents and Settings\All
Users\Application Data
%ProgramFiles% C:\Program Files C:\Program Files
%UserProfile% C:\Users\[username] C:\Documents and Settings\[username]
1.4 About this Document

ThisdocumentdescribesQlikViewServerandQlikViewPublisherversion11.0.Thecontentsofthe
softwareaswellasthedocumentmaychangewithoutpriornotice.
2 Whats New in QlikView 11 Server?

ThischapterdescribesthefunctionalitythathasbeenaddedorimprovedinQlikView11Server.
Context Sensitive Help

ContextsensitivehelphasbeenaddedinQlikViewManagementConsole(QMC).
LDAPs
ConfigurableLDAPDSPforLDAPs(LDAPviaSSL)supporthasbeenadded.
Audit Logging by Document

Insomecases,itisrequiredtogenerateauserauditlog,sothateveryqueryisregisteredanditispossibleto
seewhodidwhatretroactively.
QlikView10Servercandothis;however,theswitchisfortheentireservereitheralldocumentsare
loggedornodocumentislogged.Inaddition,ifthereisalargenumberofselectionsinalistbox,notevery
selectionislogged.
InQlikView11Server,thisloggingcanbedoneperindividualdocument.Inaddition,loggingofevery
selectioncanbeenabled.
Enable/Disable Document Download, Exporting, and Printing

per Document and User
Inmanysituations,thesystemmanagerwantstopreventanyharddatacomingoutofQlikViewServer.In
thesesituations,downloadsofthe .qvwfile,printing,andexportingarenotallowed;onlytheinteractive
sessionwithQlikViewServerispermitted.
InQlikView10Server,thisfunctionalityisavailableatthedocumentlevelonlyfordownloading.
InQlikView11Server,thishasbeenimprovedsothatthefunctionalityisavailableonaperuserlevelas
wellasthecapabilitytoenableanddisableexportingandprintingonaperdocumentanduserlevel.
Supporting Task for .qvd Creation

Thecreationof .qvdfilescanbeaddedasaSupportingTask.
Note!Thisis notareplacementforcreating .qvdfilesusinga .qvw.SeetheQMConlinehelpformore
information.
Distribution to Email within a .qvw Document

A .qvwfilecanbedistributedtoemailrecipientsdefinedinafieldinthedocument.
Alert Email to Document Administrators

Alertemailscanbesenttodocumentadministrators.
License Tracking
TheuseoflicenseshasbeenaddedtotheQlikViewEventServerlogs.Thefollowingeventsarenowlogged
(whenusinglowverbositylogging):
l PGO,Recreating[filename]frombackup
l PGO,Recreatingcorruptfile[filename]
l PGO,Creatingfile[filename]
l License,Licenseleasedtouser[username]onmachine[machinename]
l CALusage,UsingCALoftype[CALtype]foruser[username]onmachine[machinename].
Sessionsonthiscaltype:X
l CALusage,ReleasingsessionCALforuser[username]onmachine[machinename]
l CALusage,UsageCALsessionforuser[username]onmachine[machinename]stopped
l CALusage,NamedUserCALsessionforuser[username]onmachine[machinename]stopped
l CALusage,DocumentCALsessionforuser[username]onmachine[machinename]stopped
l CALallocation,Unused(Document)NamedUserCAL[username]deletedok
l CALallocation,(Document)NamedUserCAL(notusedfor24hours)[username]deletedok
l CALallocation,Unused(Document)NamedUserCAL[username]markedfordeletionok
l CALallocation,(Document)NamedUserCAL[username]addedok
l CALallocation,NamedUserCAL(notusedfor24hours)[username]deletedok
l CALdeallocation,(Document)NamedUserCAL[username]nolongermarkedfordeletionok
l CALdeallocation,(Document)NamedUserCAL[username]notmarkedfordeletiondenied
l CALdeallocation,(Document)NamedUserCAL[username]notfounddenied
Distribution and Reload Performance

Theperformanceofreloadanddistributionhasbeenimproved.
Reloads
PriortoQlikView11Server,areloadisperformedinthefollowingwaywithPublisher:
1. Theentiredocument(.qvw)isloadedtomemoryfromdisk.
2. Areloadiscompleted.
InQlikView11Server,areloadisperformedinthefollowingway:
1. Thedocument(.qvw)withoutthedataisloadedtomemoryfromdisk.
2. Areloadiscompleted.
Theperformanceenhancementisthereductionintimetoloadthedocumenttomemoryfromdisk,since
thereisnodata.QlikView11Publishercanopensourcedocumentswithoutdatapriortoexecutingareload
task.Thereisnoneedtoloadthedocumentdatatomemoryandthenperformareloadofthedocument.
Loop and Reduce

PriortoQlikView11Server,aloopandreduceisperformedinthefollowingwaywithPublisher:
1. Theentiredocumentisloadedtomemoryfromdisk.
2. Thedocumentisreducedandsavedtodisk.
3. GotoStep1untiltheLoopiscompleted.
InQlikView11Server,aloopandreduceisperformedinthefollowingway:
1. Theentiredocumentisloadedtomemory.
2. Thedocumentisreducedwhilebeingduplicatedinmemory.
3. Thedocumentisreducedandsavedtodisk.
4. GotoStep2untiltheLoopiscompleted.
Theperformanceenhancementisthenumberoftimesthedocumentisloadedfromdiskforeachloop.
However,thememoryfootprintisincreased(basedonthelargestsliceduringtheloopandreduce)forthe
document.
QlikView Management Console User Interface

TheQMCuserinterfacehasbeenimproved:
l Userinterfaceinconsistencieshavebeencleanedup.
l TheperformanceofrefreshingtablesallovertheQMChasbeenimproved.
l TheStatuspageisdrawnandupdatedfaster.
l Allofataskchaincanbeexpandedbyright-clicking.
l Ausercanberemovedfromalldistributionswheretheuserisexplicitlytargeted.
l SearchandfiltershavebeenaddedtoSourceDocuments,UserDocuments,andTasks.
l AlertswithinQMChavebeenaddedforservicestatus.
l Clusteringandusertypeshavebeenmademoreconsistentamongtheservices.
Reduction with Lock Fields

InpreviousversionsofQlikView,areductionwasaffectedbylockfields(byineffectreduceonthelocked
values).InQlikView11Server,thereductionignoresanylockedfields.
Improved Logging
ChangestothesettingsinQlikViewServerandQlikViewWebServerarestoredintheauditlog.
ThelogginganderrorhandlinghavebeenimprovedforQlikViewDistributionService.
QMC and QMEC are Merged into QMC

QMChasbeenremovedandQlikViewEnterpriseManagementConsole(QEMC)hasbeenrenamedto
QMC.
AccessPoint Remake
AccessPointhasbeengivenanewlookandfeel:
l Newsearchcapabilitieshavebeenadded.
l Thedocumentattributeshavebeenleveragedtoimprovethecategorizationofdocuments.
l Documentdescriptionscanbeadded.
l GlobalmessagescanbeshownontheAccessPointbyaddingmessagesinQMC.
EDX Enhancements
StartinganEDXreturnsasessionIDtoallowinterrogationofthestatusofthesessionratherthanonthe
task.Whenthesessionisdone,thestatuscontainsalistofallthetasks(andsessionIDs)thathavebeen
triggered,allowingforcontinuoustrackingofthestatus.ThisfunctionalityisavailablethroughtheAPI.
Load Balancing Improvements

Anewalgorithm,CPUwithRAMOverload,forloadbalancingwhenusingaQlikViewWebServerhas
beenaddedforimprovedmanagementofaclusterofwebservers.Inessence,thewebservercannowroute
trafficbasedonRAMandCPUuse.
Retries
Ifataskthatcontainsaloopfails,itrestartsfromthepointoffailure,ratherthanfromthebeginningofthe
loop.
MSI Installation of QlikView Server

TheusabilityoftheMSIhasbeenimproved.
QlikView Settings Service

WhenMicrosoftIISisusedaswebserver,anewsupportservice,QlikViewSettingsService,allowsIISto
bemanagedviathesameport(4750)thatisusedtomanageQlikViewWebServer.
3 System Requirements
TosuccessfullyinstallandrunQlikViewServer/Publisher,therequirementslistedinthischaptermustbe
fulfilledbythetargetsystem.
3.1 QlikView Server

QlikView
32-bit (x86) 64-bit (x64)
Server
Platform WindowsXPProfessionalSP3* WindowsXPProfessionalx64SP2*
WindowsVista* WindowsVistax64*
Windows7* Windows7*
WindowsServer2003 WindowsServer2003x64Edition
WindowsServer2008 WindowsServer2008x64Edition
WindowsServer2008R2
Processor IntelCoreDuocompatibleorhigher Multi-corex64compatibleprocessors.

recommended.
Memory 1GBminimum.Dependingondata 4GBminimum.Dependingondata

volumesmoremayberequired.** volumesmoremayberequired.**
Diskspace 450MBtotalrequiredtoinstall. 450MBtotalrequiredtoinstall.
Security MicrosoftActiveDirectory MicrosoftActiveDirectory

NTLM NTLM
Third-partysecurity*** Third-partysecurity***
Webserver QlikViewWebServer(QVWS) QlikViewWebServer(QVWS)

MicrosoftIIS6and7 MicrosoftIIS6and7
Management MicrosoftInternetExplorer7,8,and9 MicrosoftInternetExplorer7,8,and9

console MozillaFirefox6 MozillaFirefox6
.NET 4.0 4.0

framework
Internet IPv4 IPv4

Protocol IPv6 IPv6
version
*Recommendedfordevelopmentandtestingpurposesonly.
**QlikViewisanin-memoryanalysistechnology;memoryrequirementsforQlikViewproductsaredirectly
relatedtothequantityofdatabeinganalyzed.
***Third-partysecurityrequiresQlikViewEnterpriseEditionServer(see Editions of QlikView Server (page
85)).
3.2 QlikView Publisher

QlikView
32-bit (x86) 64-bit (x64)
Publisher
Repository NativeXMLSQLServer2005or NativeXMLSQLServer2005or2008
database 2008
Part 2 Installation
Part2Installation
4 Upgrading QlikView
4.1 Upgrade Considerations
Migrating from 32-bit (x86) to 64-bit (x64) Version
Whenmigratingfrom32-bit(x86)to64-bit(x64)orfrom64-bit(x64)to32-bit(x86),therunningversion
mustbemanuallyremovedpriortoinstallingthenewversion.
Upgrading from Version 8 to 11

UpgradingfromQlikViewServerversion8toversion11requiresupgradingtoversion9priortoupgrading
toversion11.
Note!QlikViewServer cannotbeupgradeddirectlyfromversion8toversion11.
Upgrading from Version 9 or 10 to 11

ConsiderationsforupgradingfromQlikViewversion9or10toversion11:
l TheinstallationofQlikViewServerrequiresarebootofthemachineforproperoperation.
l QlikViewServerversion9handlesEDXtriggersviaHTTPPOSTcallsonly.InQlikViewServer
version10and11,EDXtriggersaretriggeredbytheQlikViewManagementService(QMS)API,
wheremoregranularfunctionalityisavailable.SeetheQMSAPIdocumentationintheManagement
ConsolesandtheQlikViewSDKforusageinstructions.
l QlikViewAccessPointisthedefaultstartpageforQlikViewServer.
l PreviousManagementConsolesforQlikViewServerandPublisherhavebeencompletelyreplacedby
QlikViewManagementConsole(QMC).TheQMCmustbestartedtoregisteralicenseforQlikView
Server,unlessavalidlicenseisalreadyavailableonthemachinerunningQlikViewServer.
l Anti-aliasingonfontsisnolongeravailable.
l QlikViewhasacommonfileformatforversions7,8,9,10,and11.
l Windows2000isnolongeranofficiallysupportedhostoperatingsystem.
l SeetheReleaseNotesformoreinformationonupgradingtoQlikView11.
4.2 Upgrade Procedure

ForasuccessfulupgradeofQlikViewServer,takethefollowingbasicpracticesintoaccount:
l BackupthecurrentQlikViewdatadirectory,whichincludesmostofthelogandsomeofthe
configurationfilesaswellasthedocumentfolders.Thefilesaretypicallylocatedinthefollowing
location:
Windows7,WindowsServer2008: %ProgramData%\QlikTech
WindowsXP,WindowsServer2003: C:\Documents and Settings\All
Users\Application Data\QlikTech
l PerformtheupgradeduringascheduleddowntimeQlikViewServermustbestoppedforthe
upgradetobesuccessful.
l LicensinginformationandsettingsaresavedbydefaultwhenQlikViewServerisremoved.Theyare
appliedtoanysubsequentinstallationofQlikViewServeronthesystem.
Note!TheinstallationdoesnotsupportupgradefrombetaorreleasecandidateversionsofQlikView11
Server.
ToinstallQlikViewServer,proceedasfollows:
1. VerifythatbackupmediaexistsforthecurrentreleaseofQlikViewServerandbackupallcurrent
filesassociatedwithQlikViewServer(HTMLpages,QlikViewdocuments,licensingfile,QlikView
Server .sharedfiles,andsoon).
2. WhenrunningQlikViewServerversion8,usethe UserstabinQMCtodetermineifthereareany
activeuserslinkedtoQlikViewServer.Itmaybeagoodideatosendoutabroadcastmessageto
notifytheusersthattheservicewillbestopped.
3. UninstallQlikViewServerfrom Start Menu>Control Panel.
4. InstallQlikView11Server.
Note!WhenupgradingfromapreviousversionandusingMicrosoftIIS,thevirtualfoldersinIISmustbe
updated(seethetablebelow).
Microsoft IIS
Update Required
Virtual Folder
QVAJAXZfc Updateto %ProgramFiles%\QlikView\Server\QlikViewClients\
QlikViewAjax.
QvPlugin Updateto %ProgramFiles%\QlikView\Server\QlikViewClients\

QlikViewPlugin.
QvClients Updateto %ProgramFiles%\QlikView\Server\QlikViewClients.
QvAnalyzer Removed
QvJava Removed
QvPrint Removed
4.3 Multi-machine Preparation

Whenupgradinganinstallationthatisspreadovermultiplemachines,extraplanningisrequired,since
versionscannotbemixedarbitrarily.
Simple Upgrade
Thisprocedurerequiresnospecialplanningandinvolvesthesmallestrisk,butcausesthesystemtobedown
forsometime.
Proceedasfollowstoperformastraight-forwardupgrade:
1. Performabackupasdescribedin Upgrade Procedure (page 19).
2. Stopallservicesrunningonallmachines.
3. Upgradetheservicesoneachmachine(inanyorder).
4. Startallservicesonallmachines.
Maximize Uptime
Thisprocedurerequiresmoreplanning,butthesystemuptime(fromanenduserpointofview)ismaximized.
Proceedasfollowstoperformtheupgrade:
1. Performabackupasdescribedin Upgrade Procedure (page 19).
2. StopQMS(whichmeansQMCbecomesunavailable).
3. Upgradeinthefollowingorder(lettheinstallerrestarttheservices):
a)Webservers
b)DirectoryServiceConnector(DSC)
c)QlikViewServer(QVS)
d)QlikViewDistributionService(QDS)
e)QMS
4. StartQMS(whichmeansQMCbecomesavailableagain).
Migration to a New Machine

Analternativewayistobuildthenewenvironmentonnewservers.
Note!WhenupgradingfromapreviousversionandusingMicrosoftIIS,thevirtualfoldersinIISmustbe
updated(see Upgrade Procedure (page 19)).
Proceedasfollowstoperformamigrationtoanewmachine:
1. Onthenewmachine,installarunning,licensedversionofQlikView11Server.
2. StopallQlikViewservicesontheoldmachine.
3. Removeorrenamethe %ProgramData%\QlikTech\ManagementService\QVPRfolder.
4. Removeorrenamethe %ProgramData%\QlikTech\ManagementService\qvpr_
<NewMachineName>.inifile.
5. Copythe QVPRfolderandthe .inifileasisfromtheoldmachinetothenewone(thatis,keep
thefoldername):
Version9: %ProgramData%\QlikTech\Publisher\CommandCenter
Version10: %ProgramData%\QlikTech\ManagementService
6. Renamethe .inifile(thatis,change qvpr_<OldMachineName>.inito qvpr_
<NewMachineName>.ini).
7. Changeallreferencesto <OldMachineName>to <NewMachineName>intheQVPR .xmlfiles.
8. StarttheQlikViewservicesonthenewmachine.
9. InQMC,changethesourcefolderpathtothecorrectfolder(orthetaskscannotbeedited).
10. Shutdowntheoldmachine.
5 Installing QlikView Server

IfMicrosoftIISistobeusedaswebserver,itmustbeinstalledpriortoQlikViewServer.
Note!IftherequiredMicrosoft.NET4.0Frameworkisnotinstalledonthetargetsystem,itisdownloaded
fromtheInternetandincludedaspartoftheQlikViewServerinstallationprocess.
ItisrecommendednottomovefolderlocationsaftertheQlikViewServerinstallationiscomplete,since
manysettingsdependontheinitialfilelocations.IfthelocationofQlikViewServerhastobechangedafter
theinstallation,proceedasfollows:
1. Run QlikViewServer_x86Setup.exeor QlikViewServer_x64Setup.exe.Click Nextin
theWelcomedialog.
2. Selecttheregionforthelocationoftheserver.Click Nexttocontinue.
3. Readthelicenseagreement,select I accept the terms in the license agreement,andclick Nextto
continue.
4. EntertheuserinformationforQlikViewServer.Click Nexttocontinue.
5. Allfilesareinstalledinthespecifiedfolder.Tochangetherootfolderfortheinstalledfiles,click
Changetospecifythepreferredlocation.Finally,click Nexttocontinue.
6. Selectthefeaturestorun.Toselectindividualfeatures,click Configure.Finally,click Nextto
continue.
7. SettheaccountthattheQlikViewServerandPublisherservicesaretorununder.Click Nextto
continue.
Note!IfusingalocaladministratoraccountonWindowsXPProfessionalx64SP2thatisnotpartofa
domain,theinstallationprogramcannotresolvetheaccount.Thismeansthattheaccountfortheservicesin
Computer Managerhastobesetmanually.
8. Click Installtostarttheinstallation.
9. Click Finishwhentheinstallationiscomplete.
10. LogofffromWindowsandthenlogonagain,sothatgroupmembershipsaddedduringthe
installationareupdated.
Note!ItmaybesufficienttologofffromWindowsandthenlogonagain.However,itisrecommendedto
restartthemachinetoenabletheQlikViewServerfunctionality.
5.1 Installation Profiles

Theprofilesavailableduringinstallationarelistedbelow.
Profile Description
Fullinstallation,single UsedtorunallcomponentsonasinglemachinewithQlikViewWebServer
machinewithQlikView aswebserver.
WebServer InstallsQlikViewServer(andexamples),QlikViewDistributionService,
DirectoryServiceConnector,QlikViewWebServer,andQlikView
ManagementService.
Fullinstallation,single UsedtorunallcomponentsonasinglemachinewithMicrosoftIISasweb
machinewithMicrosoft server.
IIS InstallsQlikViewServer(andexamples),QlikViewDistributionService,
DirectoryServiceConnector,QlikViewManagementService,andQlikView
SettingsService.
Note!ThisprofileisonlyavailablewhenMicrosoftIISisinstalledonthemachine.
Profile Description
QlikViewServer InstallsQlikViewServer,DirectoryServiceConnector,andtheQlikView
Serverexampledocuments.
Reload/Distribution InstallstheReloadEngineandtheQlikViewDistributionService.
Engine
ManagementConsole InstallstheQlikViewManagementServicetogetherwiththeQlikView
ManagementConsole(QMC).
WebServer InstallstheQlikViewWebServer.
5.2 Logging the Installation

Thesetupprocedureisloggedwhen Setup.exeisexecuted.Thelogfiles, QlikViewServerx86.wil
forthex86versionand QlikViewServerx64.wilforthex64version,arestoredinthe Tempfolderof
theuser(forexample, %UserProfile%\AppData\Local\Temp).Eachtimeaninstallationisexecuted,
anewfileisgenerated,over-writingthepreviouslogfile.
Obtaining the MSI package

IftheMSIpackageisneededfortheinstallation,proceedasfollowstoextractitfromthe .exefile:
1. Starttheinstallationfromthe .exefileandwaituntilthefirstdialogopens.
2. LocatetheMSIfile(oftenstoredwitharandomname,forexample, ed34g.msi)inthe Tempfolder
in %UserProfile%\AppData\Local(C:\Documents and Settings\username\Local
Settingsonpre-WindowsVistasystems).
3. Copythe .msifiletoanotherlocation.
4. Exitthe .exeinstallation.
5. InstallQlikViewServerusingthe .msifile.See Silent Installation (page 91)forinformationon
howtoperformasilentinstallation.Foradditionalinformation,see Deploying MSI Packages with
Group Policies (page 107).
5.3 Completing the Installation

AftersuccessfullyinstallingQlikViewServer,alicensemustberegisteredinQlikViewManagement
Console(QMC)toactivatetheinstalledsoftware.
Note!IfaccessisdeniedwhenstartingQMC,logofffromWindowsandthenlogonagain,sothatgroup
membershipsaddedduringtheinstallationareupdated.
Note!Runningreal-timeanti-virusprotectionontheserverdegradestheperformanceofQlikViewServer.It
isrecommendedthattheuserdocuments,sourcedocuments,logdirectories,and .pgofilesareexcluded
fromtheanti-virusscanning.
Running Microsoft IIS

IfMicrosoftIISisusedaswebserverinaWindowsServer2003(orlater)environment,enableASP.NETto
ensureproperoperationoftheQlikViewServersamplepagesandtheextendedfunctions(forexample,
QlikViewServertunnel).
Note!TooptimizetheperformancewhenrunningMicrosoftIISandAJAX,turnoncompressionintheweb
server.
ForinformationonhowtoconfigureIIS6,see
http://technet.microsoft.com/en-us/library/cc730629%28WS.10%29.aspx.
ForinformationonhowtoconfigureIIS7,see
http://technet.microsoft.com/en-us/library/cc782942%28WS.10%29.aspx.
Licensing
ThelicensingisusedtoauthenticateQlikViewServerandallowittorunonaspecificmachine.
Goto System>LicensesinQMC,selectaQlikViewServerorPublisher,andfillinthe Serial numberand
Controlfieldsonthe QlikView Server Licenseor QlikView Publisher Licensetab(dependingonwhether
QlikViewServerorPublisherwaschosen).
QlikView Server/Publisher License tab in QMC

TheLicenseEnablerFile(LEF), lef.txt,forQlikViewServerisautomaticallysavedin
%ProgramData%\QlikTech(C:\Documents and Settings\All Users\Application
Data\QlikTechonpre-WindowsVistasystems).
The PubLef.txtfileforQlikViewPublisherissavedin
%ProgramData%\QlikTech\ManagementService\Publisher LEF(C:\Documents and
Settings\All Users\Application Data\QlikTech\ManagementService\Publisher
LEFonpre-WindowsVistasystems).
Click Update License from Servertodownloadanew lef.txtfilefromtheQlikViewLEFserver.Thisis
primarilyusedwhenupdatingthenumberofClientAccessLicenses(CALs).
IftheLEFinformationcannotbeaccessedthroughtheInternet,itcanbeobtainedfromthelocalvendor.In
thatcase,copytheentire lef.txtfiletothelocationmentionedabove,orpastetheLEFdatausingthe
correspondingfieldontheQlikViewServer/PublisherLicensetabinQMC.Contactthelocalvendorfor
specificinstructions.
6 Building a Farm
6 Building a Farm
Serverfarmscanbeusedtoprovideadditionalperformance,redundancy,andsecurityinplaceofasingle
serversolution.
6.1 Planning
Beforestartingtheactualinstallation,planningisneeded.Thefollowingitemshavetobeconsidered:
l Trustmechanism
l Webserver(QlikViewWebServerorMicrosoftIIS)
l Redundancylevel
l Accounttoruntheservicesunder
l QVPRformat(XMLorSQL)
l Userdirectory
l Userauthentication
l Firewalls
Trust Mechanism
TrustmechanismsareprovidedwithWindowsgroupsorcertificates.
Windowsgroupscaneasilybedeployed,ifallservicesresideinasingleActiveDirectory(AD).Ifencrypted
communicationisneeded,itcanbeaddedmanually.
Certificatesprovidefortrustmechanismsincross-domainenvironmentsandcanalsoprovideSSLencryption.
Web Server
QlikViewWebServerisintendedforusewhenthewebserverisnotneededforotherpurposes.Itis
lightweightandeasytomanage,butatthesametimelimitedtosupportthetasksneededbyaQlikView
installation.
AMicrosoftIIS-hostedwebserverisrecommended,if:
l Moreflexibilityormoreadvancedtuningisrequired
l ThewebserveristobeusedforothertasksthanQlikView
l Anauthorizationschemenotavailableout-of-the-boxisrequired
Redundancy Level
Theredundancylevelismainlyaquestionofclusteringand/orhavingmultiplemachinesrunningthesame
service.AllservicesexceptQlikViewManagementService(QMS)canbeinstalledonmultiplemachines.In
addition,QlikViewServer(QVS),QlikViewDistributionService(QDS),andDirectoryServiceConnector
(DSC)canbeclustered.
Account to Run the Services Under

AdedicatedaccountshouldbecreatedtomanagetheQlikViewservices.Theaccountshouldbeassigned
duringtheinstallation,withproperprivileges,see Security Overview (page 67).Itisrecommendedthatthe
sameaccountisusedforallservices.
QVPR Format
ThechoiceofQVPRformatisbasedonreasonsoutsidetheQlikViewproduct(forexample,backupand
availability).TheinstallationalwaysstartsinXMLmode.
6 Building a Farm
User Directory
QlikViewdefaultstoWindowsusers(thatis,NTFSmode).Ifnon-Windowsusersaretobegivenaccess
(otherthananonymously),QlikViewServermustruninDocumentMetadataService(DMS)mode.
DMSmodemayalsobepreferableforotherreasons,see Document Level Authorization (page 77).
User Authentication
QlikViewsupportsmultipleauthenticationschemes.AdditionalschemesmayrequireASPXdevelopment
andthepossibleuseofMicrosoftIISforwebservices.
Forinformationontheavailableauthenticationschemes,see Authentication (page 71).
Firewalls
Makesurethattheservicesareabletocommunicate(forexample,byopeningtheappropriateportsinthe
firewalls).Forinformationontheports,see Service by Service (page 51).
6.2 Root/First Install

Beforestarting,makesurethattheappropriateserviceaccount(oraccounts)issetupandavailableonthe
machineswheretheservicesaretobeinstalled.
Inallinstallations,theremustexistexactlyoneQMS,whichmustbeinstalledfirst.NotethattheQMSmust
beabletocommunicatewithallthesubsequentlyinstalledservices.
Ifmoreservicesaretorunonthesameserver,theycanbeinstalledatthesametime.
6.3 Adding Services on Other Machines

Thenextstepistoinstalltheotherservicesontheotherservers.Ifmoreservicesaretorunonthesame
server,theycanbeinstalledatthesametime.Theorderinwhichtheservicesareaddedisnotimportant.
Whentheserviceshavebeeninstalled,itistimetoreturntoQlikViewManagementConsole(QMC)and
configuretheservices.ThisisdoneontheSystemtab.Thefirststepistoaddtheservices.Makesuretonote
thedifferencesbetweenbuildingoutaclusterandcreatingabrandnewcluster.
6.4 Clustering
Note!Do notmixarchitecturesthatis,32-bit(x86)and64-bit(x64)withinacluster.
QlikView Server
FortheQlikViewServerclustertoworkproperly,itisimportanttoset System>Setup>QVS
resource>Folders>Root Foldertoacommonsharedfolder.Inaddition, Alternate Temporary Files Folder
Pathmustbesettoacommonsharedfolder(separatefromtherootfolder).
Ifextensionsareused,itsimplifiesmanagementif Alternate Extension Pathissettoacommonshared
folder.
Itisalsocommonpracticetoset System>Setup>QVS resource>Logging>Log Foldertoacommonplace,
butthisisnotstrictlynecessary.
Note!Therootfoldermust notbeusedforanythingelsethanclusterfiles(thatis, .pgofiles)anduser
documents.
6 Building a Farm
QlikView Distribution Service

ForaclusterofQDSs, System>Setup>General>Application Data Foldermustbesettoacommonshared
folder.Inaddition, Source Foldersmustbecommonsharedfolders.
Directory Service Connector

AclusterofDSCsdoesnotneedanyspecificsettings.Thedifferencebetweenclusteredandnon-clustered
DSCsiswhetherthesettingsaresharedornot.
QlikView Web Server

Multiplewebserverscanbesetup,buttheyarealwaysconfiguredindependently(thatis,theyarenever
clustered).Notethatitisuncommon,butfromatechnicalperspectivepossible,tohavesomewebservers
runningQlikViewWebServer(QVWS)andsomeMicrosoftIIS.
Tunneling Using Microsoft IIS

TunnelingisusedbyWindowsnativeclients(QlikViewDesktop,theOEMOCX,andtheInternetExplorer
plugin)andneededwhentheclientscannotcommunicatewithQlikViewServeronport4747(mostlikely
duetoafirewallblockingthetraffic):
l QVWS:Noextrasettingsarerequired.
l MicrosoftIIS:The QVSTunnel.dllfilemustbeaddedasanISAPIfilter.
ProceedasfollowstosetuptunnelingforMicrosoftIIS7:
1. OpentheInternetInformationServicesManager.
2. SelecttheIIStopnode.
3. OpentheISAPIandCGIRestrictionsdialog.
4. Select AddintheActionspaneandbrowsetothelocationof QVSTunnel.dll.
5. Provideadescriptionoftheinstanceandcheckthe Allow extension path to executebox.
6. OpenthesitethatistohosttheQlikViewServerandPublisherpagesandclick Scripts.
7. OpentheHandlerMappingsdialog.
8. LocateISAPIdllandselect Edit Features PermissionintheActionspane.
9. Click Executeinthedialogthatopens.
TesttheQlikViewServertunnelbyenteringthefollowingURLinaclientbrowserwindow:
http://<Servername>/scripts/qvstunnel.dll?test
Servernameisthewebserver.Ifthetunneliscorrectlysetup,thewebpagereturnsamessage(that
tunnelingisavailable)andtheQlikViewServerversionnumber.
Part 3 Architecture
Part3Architecture
7 Roles
7 Roles
TheoverallarchitectureofaQlikViewinstallationreflectstheseparationofroles.
7.1 QlikView with Publisher

ThefigurebelowshowsaQlikViewdeploymentwithPublishercontainingthelocationoftheQlikView
components.
QlikView deployment with Publisher containing the location of the QlikView components
Front End
Thefrontendiswhereendusersinteractwiththedocumentsanddatathattheyareauthorizedtoseevia
QlikViewServer.ThefrontendcontainstheQlikViewuserdocumentsthattypicallyhavebeencreatedvia
QlikViewPublisheratthebackend.Allcommunicationbetweentheclientandservertakesplacehereand
QlikViewServerisfullyresponsiblefortheclientauthorization.
Thefrontendreliesoninfrastructureresources(forexample,Windows-basedFileShareforclustering).
Note!QlikViewServercurrentlyonlyconformswithWindowsFileShareoraWindows-basedNAS.This
meansthatstoragemustbeowned,governed,andsharedbyaWindowsoperatingsysteminstance(typically
accessedusingapathlike \\<servername>\<share>).
Authenticationofendusersis(withexceptionofthebuilt-inCustomUsers)handledoutsideQlikView.
7 Roles
Back End
ThebackendiswheretheQlikViewsourcedocuments,createdusingQlikViewDeveloper,reside.These
sourcefilescontainscriptstoextractdatafromvariousdatasources(forexample,datawarehouses,Microsoft
Excelfiles,SAP,andSalesforce.com).Thisextractionsometimesinvolvesintermediatefiles(QVD
files).ThemainQlikViewcomponentthatperformstheloadinganddistributionatthebackendisthe
DistributionService.Withinthebackend,theWindowsfilesystemisalwaysinchargeofauthorization(that
is,QlikViewisnotresponsibleforanyaccessprivileges).
Thebackendusestheinfrastructureresourcesforclustering(forexample,Windows-basedFileShare)and
mayalsouseresourceslikeSMTPserversanddirectorycatalogs.
Note!QlikViewServercurrentlyonlyconformswithWindowsFileShareoraWindows-basedNAS.This
meansthatstoragemustbeowned,governed,andsharedbyaWindowsoperatingsysteminstance(typically
accessedusingapathlike \\<servername>\<share>).
Asdepictedhere,boththebackendandfrontendaresuitablefordevelopment,testing,anddeployment.
7.2 QlikView without Publisher

WithoutPublisher,theQlikViewarchitecturebecomesmorerestrictive.Alldistributionandreduction
facilitiesareremovedandreplacedbyareloaddirectlyontheuserdocuments.Withoutthedistribution
abilitiesofPublisher,developersneedtomanuallydeploythe .qvwfilebehindtheserver.
QlikView architecture without Publisher
7 Roles
7.3 QlikView Server

Thenumberofservers(clusteredornot)withinaninstallationisonlylimitedbythelicense.Itis,however,
notfeasibletorunmorethanoneQVSprocessperserver(physicalorvirtual).QVSisdesignedtomakethe
mostoftheresourcesavailabletoit.NotablytheQVSkeepsasmanycalculationresultsaspossiblecached
inmemorytokeeptheresponsetimestoaminimum.
QlikView Server Client Communication

TheQlikViewServerclientcommunicationarchitecturerequiresthreeprimaryprocesses,whichmustbe
abletocommunicatewitheachotherinaconsistentandsecuremanner.Thisinteractioncanpotentially
involvemultiplemachinesandmultiplenetworkconnections,aswellasothersubordinateprocesses.
QlikView Server client communication

Thethreeprimaryprocessesaredescribedbelow.
Process Description
QVS ProvidesQlikViewfunctionalitytotheclient.Themachinethathoststhisservicemustbe
runningaMicrosoftWindowsoperatingsystem.
Client Runsinawebbrowseroranapplicationshellthatprovidesacontainerfortheclientcode.The
clientcommunicateswithQVSeitherdirectlyorthroughthewebservertoprovidethe
QlikViewinterfaceandfunctionalitytotheenduser.
Web Runsanhttpserver,whichcanbeusedtoservehtmlwebpagestotheclient,assistswith
server authenticationoftheuser,andenablescommunicationbetweentheclientandQVS.
WiththeexceptionofCustomUsers,theauthenticationofclientusersisdoneoutsideQlikViewusing,for
example,Windowsauthentication.See QlikView Server Authentication Using Custom Users (page 74)for
informationonauthenticationofCustomUsers.
TheprotocolsdefinedforclientcommunicationwithQVSarelistedbelow.
7 Roles
Protocol Description
QlikViewProtocol Encrypted,binary,andTCP-based;communicatesdirectlywithQVSonport
(QVP) 4747.
QVPX XML-based;communicateswiththeQVSusinghttp/httpsthroughaweb
server.
Windowsclients(.exe/.ocx)communicatedirectlywithQVSusingQVPonport4747.Theseclientsdo
notrequireawebservertoestablishandmaintainaconnectionwithQVS.
TheAJAXclientandmobileclientsdonotcommunicatedirectlywithQVS.Theyestablishandmaintaina
connectionusingtheQVPXprotocolthroughawebserver,QlikViewWebServer(QVWS)orMicrosoftIIS.
Thisisnormallyaccomplishedusingport80(http).
ThedefaultinstallationsettingsforQVSuseQVWS,notIIS.QVWSsharesport80withIISonWindows
Vista,Windows2003Server,andWindows2008Server.OnWindowsXP,onlyoneofthetwowebservers
canuseport80.Ifbothareconfiguredtorun,theymustbeassigneddifferentports.
QlikView Server User Document

Forausertoopenadocument,itisrequiredthat:
l ThereisaClientAccessLicense(CAL)fortheuser
l Theuserhasaccesstothedocument
TheuserdocumentsarealwaysreadbyQVSandthustechnicallyonlyneedtobereadablebytheaccount
runningQVS.TheaccessrightsareeitherstoredintheACLlistofthedocument(whenQVSrunsinNTFS
mode)orinthe .METAfile(whenQVSrunsinDocumentMetadataServicethatis,DMSmode).These
settingsarepartofthedistributionfromthebackend.
Items(forexample,layout,reports,bookmarks,annotations,andinputfieldvalues)createdbyendusersare
storedin .Sharedfiles. .Sharedfilesarenotreplacedbythedistributionfromthebackend.
7.4 Web Server

QlikViewWebServer(QVWS)isincludedaspartoftheQlikViewServerinstallation.Thewebservercan
actasastandaloneservicetofulfilltheneedofmanyQlikViewServerinstallations.
Asanalternative,aMicrosoftIISsolutionthatprovidesmoreflexibility,additionalauthenticationschemes,
andwebservicesforapplicationsotherthanQlikViewServercanbedeployed.WhenIISisused,aspecial
service,QlikViewSettingsService,thathandlesmanagementcallsisinstalled.
OtherwebserverscanbeusedinaQVSenvironment,butatsomepointthetraffictargetingQVShastogo
througheitherQVWSorthededicatedASPXpagesonIIS.
TheQlikViewWebServercomponent(eitherQVWSorIIS-based)performsseveraltasks:
l HandlestheAccessPointbackend
l Transforms/routestrafficbetweenstatelesshttpandto/fromthesession-basedcommunicationwith
QVS
l HandlesloadbalancingofQVSclusters
l Servesstaticcontent(optional)
l HandlesauthenticationthroughWindowsorCustomUsers(optional)
l HandlesgroupresolutionthroughWindowsorDirectoryServiceConnector(DSC)(optional)
QlikView Server Tunnel

IftheQVScommunicationport(4747)isblockedinthenetworkfirewall,Windowsclientsattempttore-
routetheirconnectionthroughport80(http).ThisconnectionpathmustthenincludetheQVWS,orbe
installedonMicrosoftIIS,sothatQVStunnelcommunicationcanbeestablished.
7 Roles
7.5 Directory Service Connector

Thefigurebelowshowstheinformationflow.TheDirectoryServiceConnector(DSC)isresponsiblefor
retrievinguserinformationrelatedtoendusersfromavarietyofsources,including(butnotlimitedto)
ActiveDirectory,LDAP,ODBC,andCustomUsers.

ThewebserverusesDSCforgroupresolution,theDistributionServiceusesittolookupe-mailaddressesor
UIDsduringdistribution,andtheManagementServiceusesittohelptheadministratorfindusersand
groups.
7 Roles
7.6 Management Service

TheManagementServiceistheentrypointforallmanagement,boththroughQlikViewManagement
ConsoleandtheQlikViewAPIs.
Management Service
TheQlikViewManagementService(QMS)keepssettingsinadatabaseofitsown,theQVPR.TheQVPRis
bydefaultstoredasXMLfilesanalternativeisstoringthesettingsinanSQLdatabase.Aninstallation
canonlyhaveasingleinstanceofQMSactive.Active/passivefailovershouldbeusedforredundancy.Note
thatnootherserviceneedsQMStoberunning.
7 Roles
7.7 Distribution Service
Distribution Service
TheDistributionServiceworkswiththesourcedocumentstoproduce:
l Userdocuments
l .qvwfilesfordistributiontoafolderorviae-mail
l .pdfdocumentsfordistributiontoafolderorviae-mail
Thechainofeventsuptothefinaldistributioninvolvesoneormanyofthefollowingtasks:
1. Dataisloadedfromoneormoredatasources(includingQVD)intooneormore .qvwor .qvdfiles.
2. Adocumentisreducedintooneormoresmallerdocuments.
3. Attributesandusagerulesareadded(applicableonlywhendistributedtoaQVS).
TheDistributionServiceperformsthetasksaccordingtodefinedschedulesand/orasresponsestoevents.
7.8 Reload Engine

IntheabsenceofaPublisherlicense,theReloadEngineprovidesasubsetofthePublisherdistribution
services.TheReloadEngineonlyreloadsuserdocumentsandthesettingsaredefineddirectlyintheuser
documents.
8 Logging
8 Logging
AllalertsfromtheQlikViewservicesappearintheWindowseventlog.
8.1 Logging from QlikView Server

Detailedsessionlogsarefoundintheloggingdirectory,whichisspecifiedonthe System>Setup>Logging
tabinQlikViewManagementConsole(QMC).Thedefaultlocationis
%ProgramData%\QlikTech\QlikViewServer(C:\Documents and Settings\All
Users\Application Data\QlikTech\QlikViewServeronpre-WindowsVistasystems).
Logfilescanbesettosplit(thatis,createnew)daily,weekly,monthly,yearly,ornever.Performancelog
intervalscanbesetfromoneminuteandhigher.
Note!Settingtheintervaltobeverysmall,forexample,onlyoneminute,maynegativelyimpactthe
performance.
8.2 Session Log

Asessionisdefinedasasingleuserconnectedtoasingledocument.
Note!Thesessionlogisupdatedeachtimeasession ends.Thismeansnologentryiscreatedwhena
sessionstarts.
Thefilenameofthesessionlogis Sessions*.log,where *reflectstheservernameandthesplitinterval.
Eachentryofthesessionlogcontainsthefieldslistedbelow.
Field Description
ExeType TypeofQVSbuild.
Example:RLS32=32-bitreleasebuild
ExeVersion FullversionnumberofQVS.
Example:11.00.11076.0409.10
Timestamp Dateandtimewhenthelogentrywascreated.
Document QlikViewdocumentthatwasaccessed.
Document Filetimestampofthedocumentthatwasaccessed.
Timestamp
QlikViewUser QlikViewsectionaccessuserID(ifused).
ExitReason Reasonforsessiontermination:
l Socketclosed=Client-inducedtermination
l LRU=TerminatedasLeastRecentlyUsedinfavorofnewuser
l Shutdown=Server-inducedterminationforotherreasons
Note!Thisisnotacompletelist,astheexitvalueinsomecasescomesfromtheoperating
system.
SessionStart Timewhenthesessionwasstarted.
SessionDuration Durationofsessioninhours:minutes:seconds.
8 Logging
Field Description
CPUSpent(s) CPUsecondsspentbythesession.
BytesReceived Bytesreceivedbytheserverduringthesession.
BytesSent Bytessentbytheserverduringthesession.
Calls NumberofQlikViewcallsduringthesession(bidirectional).
Selections NumberofQlikViewselectionsmadeduringthesession.
AuthenticatedUser AuthenticatedWindowsNTuserID(ifany).
IdentifyingUser Clientuseridentification.
ClientMachine Clientmachineidentification.
Identification
SerialNumber SerialnumberoftheQlikViewclient(installedclientsonly,thatis,QlikView
DesktopandInternetExplorerplugin).
ClientType Clienttypeused:
l WindowsExe=QlikViewDesktopandInternetExplorerplugin
l Ajax=allclientsthatusetheQVPXprotocol
l Unknown
SecureProtocol Secureprotocolused:
l Onwhenencryptedcommunicationisused(typicallyWindowsclients).
l Offwhennon-encryptedcommunicationisused.
TunnelProtocol TunnelwhenQVStunnelcommunicationisused.
ServerPort Portusedbytheserver.
ClientAddress ClientIPnumber.
ClientPort Clientport.
CALType ClientAccessLicense(CAL)type:
l User=NamedUserCAL
l Session=SessionCAL
l Usage=UsageCAL
l Document=DocumentCAL
CALUsageCount NumberofUsageCALs.
8.3 Performance Log

Theperformancelogisupdatedattheintervalspecifiedonthe System>Setup>LoggingtabinQMC.The
defaultintervalisfiveminutes.Additionalentriesareaddedwhenevertheserverisstartedorstopped.The
filenameofthesessionlogis Performance*.log,where *reflectstheservernameandthesplitinterval.
8 Logging
Eachentryofthelogcontainsthefieldslistedbelow.
Field Description
ExeType TypeofQVSbuild.
Example:RLS32=32-bitreleasebuild
ExeVersion FullversionnumberofQVS.
Example:11.00.11076.0409.10
EntryType Entrytype:
l Serverstarting=Startup
l Normal=Normalintervallogentry
l Servershuttingdown=Shutdown
ActiveDocSessions Numberofdocumentsessions*thathasshownactivityduringtheinterval
andstillexistsattheendoftheinterval.
DocSessions Totalnumberofdocumentsessions*thatexistsattheendoftheinterval.
ActiveAnonymousDocSessions Numberofdocumentsessions*withanonymoususerthathasshown
activityduringtheintervalandstillexistsattheendoftheinterval.
AnonymousDocSessions Totalnumberofdocumentsessions*withanonymoususerthatexistsat
theendoftheinterval.
ActiveTunneledDocSessions Numberofdocumentsessions*withtunneledconnectionthathasshown
activityduringtheintervalandstillexistsattheendoftheinterval.
TunneledDocSessions Totalnumberofdocumentsessions*withtunneledconnectionthatexists
attheendoftheinterval.
DocSessionStarts Numberofdocumentsessions*thathasbeeninitiatedduringtheinterval.
ActiveDocs Numberofdocumentsloadedattheendoftheintervalinwhichtherehas
beenuseractivityduringtheinterval.
RefDocs Numberofdocumentsloadedattheendoftheintervalforwhichthereis
asessionattheendoftheinterval.
LoadedDocs Totalnumberofdocumentsloadedattheendoftheinterval.
DocLoads Numberofnewdocumentsloadedduringtheinterval.
DocLoadFails Numberofdocumentsthathasfailedtoloadduringtheinterval.
Calls TotalnumberofcallstoQVSduringtheinterval.
Selections Numberofselectioncallsduringtheinterval.
8 Logging
Field Description
ActiveIpAddrs NumberofdistinctIPaddressesthathasbeenactiveduringtheinterval
andstillexistsattheendoftheinterval.
Note!TunneledsessionsandmultipleusersoriginatingfromthesameIPcannotbe
distinguished.
IpAddrs TotalnumberofdistinctIPaddressesconnectedattheendoftheinterval.
Note!TunneledsessionsandmultipleusersoriginatingfromthesameIPcannotbe
distinguished.
ActiveUsers NumberofdistinctNTusersthathasbeenactiveduringtheintervaland
stillexistsattheendoftheinterval.
Note!Anonymoususerscannotbedistinguished.
Users TotalnumberofdistinctNTusersconnectedattheendoftheinterval.
Note!Anonymoususerscannotbedistinguished.
CPULoad AverageCPUloadfromQVSduringtheinterval.
VMAllocated(MB) SizeinMBofthevirtualmemoryallocatedbyQVSattheendofthe
interval**.
VMCommitted(MB) SizeinMBofthevirtualmemoryactuallyusedbyQVSattheendofthe
interval.ThisnumberispartofVMAllocated(MB)andshouldnotexceed
thesizeofthephysicalmemoryinordertoavoidunacceptableresponse
times.
VMFree(MB) SizeinMBoftheunallocatedvirtualmemoryavailabletoQVS**.
VMLargestFreeBlock(MB) SizeinMBofthelargestcontiguousblockofunallocatedvirtualmemory
availabletoQVS.ThisnumberispartofVMFree(MB).
UsageCalBalance -1.00=TherearenoUsageCALs.
*Oneuser+onedocument=Onedocumentsession.
**VMAllocated(MB)+VMFree(MB)=TotalmaximumvirtualmemoryspaceavailabletotheQVSprocess.
8.4 Event Log

TheeventlogisupdatedeachtimealogentryismadeintheWindowseventlogbyQVS.Thestored
informationisamirroroftheinformationwrittentotheWindowseventlog.Thefilenameoftheeventlog
is Events*.log,where *reflectstheservernameandthesplitinterval.
8 Logging
Eachentryofthelogcontainsthefieldslistedbelow.
Field Description
SeverityID IDfortheseveritylevel:
1=Error
2=Warning
4=Informationornotice
EventID UniqueIDfortheeventtype.
Severity Eventseveritylevel:
l Error
l Information
l Warning
Message Eventdescription.
8.5 End-user Audit Log

Theend-userauditlogcontainsinformationonuserselections,includingclearselections,sheetactivation,
theapplicationofbookmarks,andreportaccess.Alogfilecalled AUDIT_<machinename>issavedto
%ProgramData%\QlikTech\QlikViewServer(C:\Documents and Settings\All
Users\Application Data\QlikTech\QlikViewServeronpre-WindowsVistasystems).
Note!TheloggingofuserselectionsinQVSisbasedonhowthecurrentselectionsobjectworksand
thereforelargerselectionsarenotloggedindetail.
Field Description
Server DateandtimewhenQVSwasstarted.
started
Document Pathandnameofthedocumentthatwasaccessed.
Type Typeofselectionmade(forexample,SelectionandBookmark).
User Username.
Message Informationonthetypeofselectionorapplicationofbookmarkthatwasmadeinthe
document.
Example:ApplyServer\BM15.
8.6 Manager Audit Log

Theauditloggingprovidesthepossibilitytotrackchangestotasksandsettingsinthesysteminordertosee
whomadethechangesandwhentheyweremade.
Theauditlogsarestoredin %ProgramData%\QlikTech\ManagementService\AuditLog.One
folderpertableiscreated.Eachfoldercontainsonefileperdaywiththechangesmadetothetasks.Thelogs
aretabseparatedfiles.
8 Logging
Theentriesfoundinthelogsarelistedbelow.
Entry Description
TransactionID TransactionID,whichisusefulforkeepingtrackofchangesmadesimultaneously.
ChangeType Typeofoperation, Update(neworchangedentries)or Delete(entrieshave

beendeleted).
ModifiedTime Timeanddate(inUTC)whenthechangesweremade.
ModifiedByUser Theuserthatmadethechangesintheuserinterface. Systemmeansthatthe

changewasinitiatedbythesystemandnotbyanyuser.
ID IDoftherow(thatwasupdatedordeleted)inthetablethatwaschanged.
Thefollowingexamplecomesfromthe AlertEmailtable.Theloghasbeenputinatableforbetter
overview.
TransactionID 455a241d-8428-4dc7-ba67-4ae7cb21cf3d
ChangeType Update
ModifiedTime 2010-02-0215:12:54
ModifiedByUser MyDomain\mjn
ID b3745325-cee7-4fe7-b681-9c9efe22fc5c
DistributionServiceID 8846d7dd-bb3f-4289-9c9b-b0ca71b7c3b2
EmailAddress mjn
Thefollowingexamplecomesfromthe QDSClustertable.Notethat TransactionIDisthesamefor

bothexamples.Thismeansthatthechangesweremadesimultaneously.
TransactionID 455a241d-8428-4dc7-ba67-4ae7cb21cf3d
ChangeType Update
ModifiedTime 2010-02-0215:12:54
ModifiedByUser MyDomain\mjn
ID a37f242c-6d80-42da-a10c-1742d2ec927f
DistributionServiceID 8846d7dd-bb3f-4289-9c9b-b0ca71b7c3b2
QDSWebAdress http://computer-mjn:4720/qtxs.asmx
CurrentWorkorderID 96bff2dc-f1ea-84d2-b6c4-ea58bf5c98e5
9 Documents, Data, and Tasks

9.1 User Documents
AuserdocumentisthedocumentthatanenduserseeswhenaccessingadocumentonQlikViewServer
(QVS).Tofullyidentifyauserdocument,boththeQVSserver/clusterandthepathrelativetotheserver
havetobeknown.Technically,auserdocumentconsistsofthreefiles:
1. .qvwfilethatcontainsthedataandlayout.
2. .METAfilethatcontains:
a. AccessPointattributes
b. Pre-loadoptions
c. Authorization(DocumentMetadataServicethatis,DMSmodeonly)
3. .Sharedfile(seebelow)
Note!IftheuserdocumentisdistributedbytheQlikViewDistributionService,boththe .qvwandthedata
inthe .METAfileareoverwritten.
TheaccesstouserdocumentsiscontrolledbyQlikViewServer.
Shared Files
TherearemultipleobjectsavailableforusercollaborationandsharingthroughQlikViewServer:
l Bookmarks
l Sheetobjects,includingcharts
l Reports
l Annotations
Eachoftheseobjectsmaybedefinedasauserobject,availabletoauthenticatedusers,regardlessofaccess
methodorlocation,orasharedobject,availabletoallusersofthedocumentthroughQVS.
TheobjectsareconfiguredandmanagedusingQlikViewManagementConsole(QMC).
OnceQVSisenabledforserverobjects,anyoftheQVSobjectsettingsarechecked,andthedocumentis
openedinQVS,aspecialdatabasefileiscreatedandmaintainedinthesamelocationastheQlikView
document.ThefilehasthesamenameastheQlikViewdocument,buta .Sharedfileextension.
Example:
l QlikViewdocument: Presidents.qvw
l QVSsharefile: Presidents.qvw.Shared
IfthenameoftheQlikViewdocumentischanged,the .Sharedfilehastobemanuallyrenamedtomatch
beforeopeningtherenamedQlikViewdocumentinQVS.Thispreservesthesharedobjectsattachedtothe
document.
WhenupdatingaServerobject,report,bookmark,orinputfielddata,thefileisexclusivelylocked.Making
aselectionorsimplyactivatingtheobjectdoesnotlockthefileandanynumberofserverscanreadthefile
atthesametime.Apartiallockisimplementedsothatdifferentsectionsofthefilemaybeupdated
simultaneouslybydifferentserversinacluster.
Thefileisreadoncewhentheserveropensthedocument,butitisnotreadagainunlesstherearechanges.
Allsessionssharethesameinternalcopyofthe .Sharedfile(thatis,openingasessiongenerallydoesnot
requirethefiletobereadfromdisk).
Theserverobjectscanbemanaged(forexample,changeofownershipordelete)onthe Documents>User
Documents>Server>Server ObjectstabinQMC.
9.2 Source Data

Sourcedataisanyexternaldatausedtopopulatethedatawithina .qvwfile.Thesourcedataisloadedto
the .qvwatreloadtime,whichcanbedone:
1. ThroughtheQlikViewDistributionService
2. ThroughtheReloadEngine
3. Manuallybythedeveloper
Accesstosourcedataisnotrequiredforenduserstousethe .qvwdocumentthroughQVSoncethe .qvw
fileispopulated.
9.3 Source Documents

SourcedocumentsareonlyapplicablewhenaPublisherlicenseisapplied.Mostsourcedocumentsoriginate
fromadeveloper,othersarecreatedbytheQlikViewDistributionServiceaspartofthedistributionprocess.
QlikViewDatafiles(QVD)canalsobecreatedaspartofthedistributionprocessasanintermediatestep.A
QVDfileisatableofdatastoredinformatthatisoptimizedforspeedwhenreadbyQlikView.
TheaccesstosourcedocumentsisgovernedbyNTFS.
9.4 Tasks
Taskscanbeusedtoperformawidevarietyofoperationsandbechainedtogetherinanyarbitrarypattern.
Thestartingpointwhendescribingtasksisthetransformationofasourcedocumentintoauserdocument.
Transforming Source Document into User Document

Thetransformationstartswithasourcedocumentandendsinoneormanyuserdocuments.
Source
Ataskisalwaystiedtoasourcedocument,sothesourceisgiven.
Layout
Thesourcedocumentcontainsthelayout,whichiscopiedunchangedallthewaytotheuserdocuments.
Theserversidelayoutisassociatedwiththeuserdocumentandisalsounchanged.
Reload
Thedatacanbe:
l Usedasstoredinthedocument(thatis,noreload)
l Partlyreloadedfromthesource(thatis,requirescriptpreparation)
l Fullyreloadedfromthesource,discardinganyolddata
l ReloadedinpartsbyuseofScriptParameters(whichrequirescriptpreparation)
Reduce
Thedocumentcanbereducedafterreload.Thereductioncaneitherreducetheinputintoasmallerdocument
(simplereduce)orsplititupintoseveralsmallerdocuments(loopandreduce).
Thereductionisbasedonaselection,eitherdonedirectlyinQMCorusingbookmarks.
Distribution
DistributionrequiresaQlikViewPublisherlicense.
Thedestinationisdefinedas:
l AlistofusersandafolderonaQlikViewServer
l Alistofusersandafolderinthefilesystem
l Alistofusers(assumingtheire-mailaddressesareknown)
Note!Loopanddistributemustbeused,ifdifferentcontentistobedistributedtodifferentusers.Ifnot,
thesamedocument(ordocuments)isdistributedtoall.
Information
Informationcanbeassociatedwiththedocumentaspartofthedistributiontoaserver.Theinformationis
notmovedwiththedocument,ifitisdistributedtoanotherlocation.TheinformationisusedinQlikView
AccessPoint.
Thefollowinginformationcanbeassociatedwiththedocument:
l Description
l Category
l Arbitrarynamevaluepairs
Server Settings
Thesettingsforthedocumentaredistributedtoaserver.Thesettingsarenotmovedwiththedocument,ifit
isdistributedtoanotherlocation.ThesettingsareenforcedbyQlikViewServer.
Authorizationenforcedbytheserver(equaltoallservers):
l Theusersauthorizedtocreateserverobjects
l Theusersauthorizedtodownloadthedocument
l TheusersauthorizedtoprintandexportthedocumenttoMicrosoftExcel
PreferencesappliedbyQlikViewAccessPoint(equaltoallservers):
l InternetExplorerpluginisrecommended
l Mobileclientisrecommended
l AJAXclientisrecommended
Performanceenforcedbytheserver(equaltoallservers):
l Auditlogging
l Maximumopensessions
l Documenttimeout
l Sessiontimeout
Availability(perserver):
l Never
l On-demand
l Pre-loaded
10 Service by Service
ThischapterdescribestheQlikViewServer/Publishercomponentsindetail.
10.1 QlikView Server

Overview
Executable %ProgramFiles%\QlikView\Server\QVS.exe
Data %ProgramData%\QlikTech\QlikViewServer
Listens to QVP:4747;QVP(tunneling):4774;Broadcast:14747;SNMP:161
Uses/Controls -
Used by QDS,QMS,QVWS,QlikViewDesktop/InternetExplorerplugin/OCX
Files
Settings and Configuration
File Description
Settings.ini StorestheQlikViewServer(QVS)settings.Manualchangesinthisfilerequirerestart
ofQVS.ThisfileisalwaysstoredintheDatafolder(see Overview (page 51)).
Cluster
QVSuses .pgofilestocoordinateacluster.ThefilesarestoredintheDatafolder(see Overview (page
51)).
File Description
BorrowedCalData.pgo KeepstrackofborrowedClientAccessLicenses(CALs).
CalData.pgo KeepstrackofCALs.
IniData.pgo Coordinatedversionof Settings.ini.
ServerCounters.pgo Keepstrackofstatistics.
TicketData.pgo Keepstrackoftickets.
Logs
Thelogsarekeptonepernodeinthecluster.ThelogfilesarestoredintheDatafolderbydefault(see
Overview (page 51)forthedefaultpath).
File Description
Events_<computer_name>.log Eventlog.
File Description
Performance_<computer_name>.log Performancelog.
Sessions_<computer_name>.log Sessionlog.
Special Folders
ThespecialfoldersarestoredintheDatafolder(see Overview (page 51)forthepath).
Folder Description
Extensions Note!TheExtensionsfolderhastobecreatedmanually.
Bydefault,QVSlooksforextensionsinthisfolder.Extensionobjectsarelocated
in Extensions\Objectsanddocumentextensionsarelocatedin
Extensions\Document.U seQlikViewManagementConsole(QMC)to
manageallextensionsinoneplaceincaseofacluster.
Temp Bydefault,QVSputstemporaryfilesinthisfolder(forexample,whenexporting
usingtheAJAXclient,atemporaryfileiscreatedinthefolder).
Load Sharing (Clustering)

Allclusteringrequiresacluster-enabledQlikViewServerlicense.QlikViewServersupportsloadsharingof
documentsacrossmultiplemachines.Thissharingincludestheabilitytoshareinrealtime,information
aboutserverobjects,automateddocumentloading,anduserlicenseCALs.Speciallicensingisavailableto
enablemultipleserverinstancessharethesamelicensenumber.
Load sharing using QlikView Web Server

TouseloadsharingbetweenmultipleQVSs,alldocumentandsupportfilesmustbesharedbetweenthe
servers.Inotherwords,allserversshouldpointtothesamephysicallocationforthefiles.QVScreatesand
maintainsadditionalfilestostoreloadsharingdata.ThesefileshaveaPersistentGroupObject(.pgo)file
typeextensionandarelocatedintheDatafolder(see Overview (page 51)).Thesefilesarelockedwhen
QVSisrunning.Thedifferent .pgofilescontaininformationonborrowedCALs,CALsinuse,server
settings,andticketdata.
OperatingsystemloadbalanceorfailoverconfigurationsareexternaltotheQVSloadsharingconfiguration,
andQVShasnocontroloverthosesystems.
ServerconfigurationsettingsaresharedbetweenallclusteredQVSsandcanbemaintainedthroughQMC
connectedtoanyoftheclusteredQVSs.PerformanceofaparticularQVSsystemcanbemonitoredthrough
QMCbyconnectingtothatsystem.Theloadbalancingsettings,thatis,whichQVStheclientshouldbe
directedto,arestoredinQlikViewWebServer(QVWS).
Document-relatedmetadataissharedvia .metafiles(oneperdocument).Thisdataisoftenreferredtoas
DocumentMetadataService(DMS)data.SinceDMSdataissharedamongtheQVSs,anyautomated
documentloadproceduresareperformedonallservers.DMSauthorizationisalsosharedamongallclustered
QVSs.
10.2 QlikView Distribution Service

Overview
Executable %ProgramFiles%\QlikView\Directory Service
Connector\QVDirectoryServiceConnector.exe
Data %ProgramData%\QlikTech\DistributionService
Listens to HTTP:4720;SNMP:4721
Uses/Controls DSC,QVS,QVB
Used by QMS
Note!Afterrestartingthemachine,theWindowseventlogmaycontainamessagethattheQlikView
DistributionService(QDS)failedtostartinatimelymanner,eventhoughitstartedsuccessfully.Thisis
becausetheQDSinitializationphaseislongerthantheWindowstimeoutperiod(30secondsbydefault).
Toavoidtheeventlogmessage,eitherchangetheWindowstimeoutperiodorconfigureQDStodependon
anotherlatestartingservicetomakeQDSstartupduringalessbusyperiod.
Files
TheQlikViewDistributionService(QDS)filescanbedividedintothreegroupsbasedonmainpurpose.All
filesarestoredintheQDSDatafolder(see Overview (page 54)).Inaclusteredsetup,allQDSsmustshare
thesameprogramfolder.Thisissolvedbythefile config_<computer_name>.xml,whichcontainsthe
programdatapathtouse.

ThefileslistedbelowarelocalcopiesoftheinformationstoredinQVPR.
File Description
Configuration.xml Configurationfilefortheservice.
Tasks\Task_ Theactualtasks.Notethatdeletedtasksarenotautomaticallyremoved(due
<GUID>.xml tosupportissueanalysis).
Triggers\Triggers_ Theactualtriggers.Notethatdeletedtriggersarenotautomaticallyremoved
<GUID>.xml (duetosupportissueanalysis).
Notification.xml Usedtosynchronize Configuration.xml, TaskDetails.xm,and

TriggerDetails.xmlwithQVPR.
TaskDetails.xml Alistoftheavailabletasksinthe Tasksfolder.Inaddition,usedto

synchronizethefilesinthatfolderwithQVPR.
TriggerDetails.xml Alistoftheavailabletriggersinthe Triggersfolder.Inaddition,usedto

synchronizethefilesinthatfolderwithQVPR.
Cluster
File Description
LoadBalancer.xml UsedtoselectwhichQDS(inacluster)todothejob.
Logs
File Description
TaskResults\TaskResult_ LatestresultofthetaskidentifiedbytheGUID.
<GUID>.xml
TaskLogIndex\TaskLogIndex_ Thisisjustforlookup(onefilepertask),pointingtotheactual
<GUID>.xml log.
EdxResults\EdxResult_ Untilthetaskiscompleted,thisfilecontainsthecurrentstatus
<GUID>.xml oftheEDXtask.Whentheexecutionisfinished,itcontainsthe
result(success/fail)andthetaskstartedasaresult(ifany).
<node-nr>\Log\<Date>.txt GeneralQDSeventanderrorlog.
<node-nr>\Log\Cluster_ Synchronizationlog.
<Date>.txt
<node-nr>\Log\LoadBalancer_ Loadbalancinglog.
<Date>.txt
<node-nr>\Log\Root_ QDSeventlog.
<Date>.txt
<node-nr>\Log\WebService_ QDSeventlog.
<Date>.txt
<node-nr>\Log\Workorder_ QDSeventlog.
<Date>.txt
<node-nr>\Log\<date>\<time> QDStaskeventlog.
- <task name>\Tasklog.txt
<node-nr>\Log\<date>\<time> Thedistributionrelatedtothetask(onlyexistsfordistribution
- <task tasks).
name>\DistributionReport.xml
QlikView Batch
Overview
Executable %ProgramFiles%\QlikView\Distribution Service\qvb.exe
Data -
Listens to COM
Uses/Controls -
Used by QDS
Files
File Description
Settings.ini Usedtostoresettings.
Logs
File Description
<document_name>.log Reloadlogthatisplacedtogetherwiththereloadeddocument.
10.3 QlikView Publisher Repository

Overview
Executable -
Data %ProgramData%\QlikTech\ManagementService\QVPR
Listens to -
Uses/Controls -
Used by QMS
Files
Bydefault,QlikViewPublisherRepository(QVPR)isasetofXMLfiles.Thesefilesarebackedupas .zip
filesin %ProgramData%\QlikTech\ManagementService\QVPR\Backups.
Security Groups
WheninstallingQlikViewServer/Publisher,acoupleofsecuritygroupsarecreated.
TheQlikViewServer/Publisherservicesmustrununderanaccountthatismemberofthesecuritygroup
QlikViewAdministrators.UsersconnectingtoQMCmustbepartofthisgroup.Anyoneconnectingtoa
remoteservicemustalsobememberofQlikViewAdministrators.
TheusersconnectingthroughtheAPImustbemembersoftheQlikViewManagementAPIsecuritygroup.
Thegroupisnotcreatedduringtheinstallationandhastobeadded(andpopulated,forexample,withthe
membersoftheQlikViewAdministratorsgroup)manually.Amembershipinthisgroupisrequiredtoimport
tasksfromanotherQlikViewServer/Publisher.
TheQlikViewEDXsecuritygroupisnotcreatedduringtheinstallationandhastobeadded(and
populated)manuallyinorderforuserstorunEDXtasks.
Document Administrators
TodelegatetheresponsibilityofcreatingtaskstopeoplenotpartoftheQlikViewAdministratorsgroup,
userscanbeappointeddocumentadministrators.Thedocumentadministratorsareonlyallowedtoaccessthe
tabsinQMCthatarerelatedtoeitheruserdocumentsorsourcedocuments.
Note!TheuseofdocumentadministratorsrequiresaQlikViewPublisherlicense.
Formoreinformationonhowtoappointdocumentadministrators,seetheQMConlinehelp.
10.4 Configuration Files

Management Service QVManagementService.exe.config
Inadefaultinstallation,thisfileislocatedin %ProgramFiles%\QlikView\Management Service.
Thefilehasanumberofautomaticallygeneratedtagsthatshouldnotbemodified,butthesettingslisted
belowcanbemodified.
Setting Description
ApplicationDataFolder Folderwherethelogfolderandallotherfiles/foldersarecreated.The
defaultvalueis %ProgramData%\QlikTech\ManagementService.
ThisfolderiswheretheXMLversionofQVPRandtheLEFinformation
arestored.
UseHTTPS True=Communicationrunsoverhttps.Acertificateforthewebsiteis
neededtoenablethissetting.
Trace Usedfordebuglogging.
QMSBackendWebServicePort Portthatthebackendmanagementservicelistensto.Thedefaultvalueis
4799.
QMSFrontendWebServicePort Portthatthefrontendmanagementservicelistensto.Thedefaultvalueis
4780.
MaxLogRecords Maximumnumberoflogrecordsthatshouldberetrievedforatask.
EnableAuditLogging True=Tracka)changesontasksandsettingsmadeinthesystem,b)who
madethechanges,andc)whenthechangesweremade.
AuditLogFolder Pathtothefolderwheretheauditlogsaresaved.
AuditLogKeepMaxDays Maximumnumberofdayseachlogissaved.
Foradditionalinformation,see SNMP (page 103).
Distribution Service QVDistributionService.exe.config

Inadefaultinstallation,thisfileislocatedin %ProgramFiles%\QlikView\Distribution
Service.Theappsettingstagisthepartthatcanbemodified.Someofthesettingsintheconfiguration
filearedescribedbelow.
Setting Description
ApplicationDataFolder Folderwherethelogfolderandallotherfiles/foldersarecreated.
Thedefaultvalueis
%ProgramData%\QlikTech\DistributionService.This
folderiswheretheXMLversionofQVPRandtheLEFinformation
arestored.
WebservicePort PortthattheQlikViewDistributionServiceusestocommunicate
with.Thedefaultvalueis4720.
UseHTTPS True=Communicationrunsoverhttps.
DSCAddress PortthattheDirectoryServiceConnectorserviceusesto
communicatewith.Thedefaultvalueis4730.Ifthevalueis
modified,thetagDSCAddressinthe
QVDirectoryServiceConnector.exe.configfilehastobe
modifiedtoo.
DSCTimeoutSeconds TimeoutforcallstotheDirectoryServiceConnector.
DSCCacheSeconds HowlongtheservicecachestheresponsesfromtheDirectory
ServiceConnector.
QlikViewEngineQuarantineTimeInms HowoftenaQlikViewengineisallowedtostart(inmilliseconds).
OpenDocumentAttempts Howmanytriesthatcanbemadetoopenadocumentbeforeitis
loggedasanerrorduringdistribution.
DebugLog True=EnableloggingofmemoryusageandstacktraceonError
logging.
Trace True=Enabledebuglogging.
EnableBatchMode EnablethissettingtomakebatchcallstotheQlikViewDistribution
Service(see QlikView Distribution Service (page 54)formore
information).

QVDirectorServiceConnector.exe.config
Thisfileisbydefaultlocatedin %ProgramFiles%\QlikView\Directory Service
Connector\QVDirectoryServiceConnector.exe.config.Thesettingsmostcommonlymodified
arelistedbelow.
Setting Description
ApplicationDataFolder Folderwherethelogfolderandallotherfiles/foldersarecreated.Thedefault
valueis %ProgramData%\QlikTech\DirectoryServiceConnector
(C:\Documents and Settings\All Users\Application
Data\QlikTech\DirectoryServiceConnectoronpre-WindowsVista
systems).
WebservicePort PortthattheDirectoryServiceConnectorserviceusestocommunicatewith.The
defaultvalueis4730.Ifthevalueismodified,thetagDSCAddressinthe
QVDistributionService.exe.configfilehastobemodifiedtoo.
UseHTTPS True=CommunicationrunsoverSSLinsteadofhttp.Acertificatefortheweb
siteisneededtoenablethissetting.
PluginPath PathwheretheDirectoryServiceConnectorlooksforavailableDSPplugins.The
defaultvalueis %ProgramFiles%\QlikView\Directory Service
Connector\DSPlugins.
Trace True=Enabledebuglogging.
DisableCompress Enablethissettingtodisablecompressionofthehttpcommunication.
10.5 Web Server

Thewebservercanbethebuilt-inQlikViewWebServer(QVWS)orMicrosoftIIS.QVWSisinstalledasa
Windowsserviceduringadefault,completeinstallationofQlikViewServer.WhenIISisused,thesame
functionalityisprovidedbyasetofASPXpagesandaspecialsupportservice,QlikViewSettingsService
(QSS).QSSactsasthemanagementinterfaceforsettingsusedbytheASPXpages.
Overview
QlikView Web Server
Executable %ProgramFiles%\QlikView\Server\Web Server\QVWebServer.exe
Data %ProgramData%\QlikTech\WebServer
Listens to HTTP:80;HTTP:4750;SNMP:4751
Uses/Controls DSC
Used by Webbrowserclientsandmobileclients
QlikView Settings Service
Executable %ProgramFiles%\QlikView\Server\Web Server

Settings\QVWebServerSettingsService.exe
Data %ProgramData%\QlikTech\WebServer
Listens to HTTP:4750
Used by QMS
Files
File Description
Config.xml Configurationfilefortheservice.
Logs
File Description
Log\<date>.txt Eventanderrorlog.
Load Balancing
QVWShostswebpages,preparesthefilelistforAccessPoint,andmanagestheloadbalancingofQlikView
Servers(QVSs).
AccessPointisawebportalfordocumentshostedonQVWS.ThepagesforAccessPointarebydefault
locatedinthefolder %ProgramFiles%\QlikView\Web.QVWSalsoactsaswebserverforanyAJAX
pagesaccessedbytheendusers.
TheloadbalancingperformedbyQVWSisdifferentfromloadbalancingawebserver,sincetheadditional
workandresourceconsumptionisalmostsimilarforeachuser,soitdoesnotmatteronwhichservertheuser
endsup.
Theloadbalancingschemesarelistedbelow.
Scheme Description
Random Thedefaultloadbalancingscheme.Theuserissenttoarandomserver,nomatterifthe
documenttheuserislookingforisloadedornot.
Loaded IfonlyoneQVShastheparticulardocumentloaded,theuserissenttothatQVS.Ifmore
Document thanoneQVSornoneoftheQVSshasthedocumentloaded,theuserissenttotheQVS
withthelargestamountoffreeRAM.
CPUwith TheuserissenttotheleastbusyQVS.
RAM
Overload
ThesettingsforloadbalancingareconfiguredinQMC.
QlikView AccessPoint
QlikViewAccessPointisawebportalthatliststhedocumentseachuserhasaccessto.AccessPointonly
linkstoeachdocumentitdoesnothostthedocuments.ThehostingisdonebyQlikViewServer.
Thedocumentscanbedisplayedasthumbnailsorinadetailedlist.
Thumbnails view in AccessPoint
Detailed view in AccessPoint
ThesettingsavailableinAccessPointarelistedbelow.
Setting Description
Category Categorygroupingforthedocument.CategoriesaremanagedinQMCunder
Documents>User Documents>Document Information.
Setting Description
Attribute Attributegroupingforthedocument.AttributesaremanagedinQMCunder
Documents>User Documents>Document Information.
Viewas Documentdisplaytype, Detailedviewor Thumbnailsview.

IntheDetailedview,thedocumentscanbesortedbyName,Category,andLastUpdate.
Clicka view detailslinkintheThumbnailsvieworaplussign(+ )totheleftofadocumentnameinthe
Detailedviewtodisplayadditionalinformationonadocument(seebelow).
Field/Button Description
LastUpdate Whenthedocumentwaslastupdated.
Note!ThisisonlydisplayedintheThumbnailsview.
NextUpdate Whenthedocumentwillbeupdatednexttime.
Note!Thisisonlydisplayedifthedocumentispartofataskthathasa
schema.
FileSize Sizeofthedocument.
AvailableClients Clickaclienttoopenthedocumentwiththatclient.
Removelastdocumentstate Clickthisbuttontoremovethelastdocumentstate.
ClickastariconnexttoadocumentnameintheThumbnailsorDetailedviewtosetthepreferencesforthe
document.
Setting Description
Openwith Selectaclienttomakeitthedefaultclienttoopenthedocumentwith.
Addto Clickthislinktoaddthedocumenttothefavoritedocuments.Select Category>Favorites

favorites inAccessPointtodisplaythefavorites.
10.6 Directory Service Connector

ForinformationontheDirectoryServiceProvider(DSP)interface,see DSP Interface (page 101).
Overview
Executable %ProgramFiles%\QlikView\Directory Service
Connector\QVDirectoryServiceConnector.exe
Data %ProgramData%\QlikTech\DirectoryServiceConnector
Listens to HTTP:4730;SNMP:4731
Uses/Controls -
Used by QDS,QMS,QVWS
Files
ThesesettingsoriginatefromQVPR.
File Description
Resources/<id>.xml DSPconfigurations.
Logs
File Description
10.7 QlikView Management Service

Overview
Executable %ProgramFiles%\QlikView\Management
Service\QVManagementService.exe
Data %ProgramData%\QlikTech\ManagementService
Listens to HTTP:4780(Web);HTTP:4799(API);SNMP:4781
Uses/Controls DSC,QDS,QVS,QVWS
Used by Webbrowser/APIclient
Files
QlikViewManagementService(QMS)keepsaglobalviewofthesettingsinQVPR.
File Description
Logs
File Description
Part 4 Security
Part4Security
11 Security Overview
11 Security Overview
ThesecurityofQlikViewServer/Publisherconsistsofthefollowingparts:
l Protectionoftheplatform:Howtheplatformitselfisprotectedandhowitneedstocommunicateand
operate.
l Authentication:Whoistheuserandhowcantheuserproveit?QlikViewusesstandard
authenticationprotocols,suchasIntegratedWindowsAuthentication(IWA),HTTPheaders,and
ticketing,toauthenticateeveryuserrequestingaccesstodata.
l Documentlevelauthorization:Istheuserallowedtoaccessthedocumentornot?QlikViewuses
server-sidecapabilitiessuchasDocumentMetadataService(DMS)orWindowsNTFStodetermine
accessprivilegesatfilelevel.
l Datalevelauthorization:Istheuserallowedtoseeallofthedataorjustpartsofit?QlikView
implementsrowandfieldleveldatasecurity,usingacombinationofdocument-levelcapabilities
(SectionAccess)andserver-sidedatareductioncapabilities(QlikViewPublisher).
12 Protection of the Platform

12.1 Functionality
Thefunctionalityfordownloadingdocumentsand/orprintandexporttoMicrosoftExcelcanberestrictedat
theuserlevelforeachdocumentontheserver.
12.2 Special Accounts

Supervision Account
ThesupervisionaccountisanaccountthatisgrantedaccesstoalldocumentscreatedbytasksinQlikView
Publisher.
Anonymous User Account

WhenQVSisstartedforthefirsttimeonamachine,aWindowsaccountiscreatedforanonymoususers.The
accountnameis IQVS_name,where nameisthenameofthemachineinthelocalnetwork.
Ifthemachineinquestionisadomainserver,theanonymousaccountiscreatedasadomainaccount.Ifnot,
itiscreatedasalocalmachineaccount.
Eachfolderandfilethatistobeavailableforanonymousclientsmustbegivenreadprivilegesforthe
anonymousaccount.
Note!StartQVSandletitcreatetheanonymousaccountbeforeattemptingtograntanyprivileges.Donot
trytocreatetheanonymousaccountmanually.
QlikView Administrators
TheQlikViewAdministratorsgroupisusedforgrantingaccesstotheQlikViewManagementConsole
(QMC)aswellasauthorizationofcommunicationbetweenservices,ifWindowsAuthenticationisused.
12.3 Communication
Protection of AJAX Client
TheAJAXclientusesHTTPorHTTPSastheprotocolforcommunicationbetweentheclientbrowserand
theQlikViewWebServer(QVWS)orMicrosoftIIS.Thecommunicationbetweenthebrowserandtheweb
servercanbeprotectedusingSSL/TSLencryptionovertheHTTPprotocol(thatis,HTTPS).
ThecommunicationbetweenthewebserverandQVSusesQVPasdescribedbelow.
Protection of Plugin
TheQlikViewplugincancommunicatewithQVSintwoways.Ifthepluginhastheabilitytocommunicate
withQVSusingQVP(port4747),thesecuritydescribedin Server Communication (page 70)isapplied.
IfthecommunicationcannotuseQVPoriftheclientchoosesitintheplugin,thecommunicationis
tunneledusingHTTPtothewebserver.
IfHTTPSisenabledonthewebserver,thetunnelisencryptedusingSSL/TLS.
Server Communication
TheQVScommunicationusestheQVPprotocol,whichisencryptedbydefault.TheQVPprotocolcanbe
protectedusing1024-bitRSAforkeyexchangeand128-bitRC4fordataencryption,providedtheMicrosoft
EnhancedCryptographicProviderisinstalled.IftheMicrosoftBaseCryptographicProviderisused,the
protectionofthecommunicationis512-bitRSAforkeyexchangeand40-bitRC4fordataencryption.
Services Communication
TheservicesthatarepartoftheQlikViewplatform(thatis,QVS,DSC,QMC,QDS,andQVWS)all
communicateusingwebservices.ThewebservicesauthenticateusingIntegratedWindowsAuthentication
(IWA).
13 Authentication
13 Authentication
AlthoughQlikViewcanbeconfiguredtoallowanonymousaccess,themajorityofimplementationsrequire
userstobeauthenticated.Insuchenvironments,QlikViewalwaysrequiresthattheuserisauthenticated
whenestablishingasessionviaQlikViewServer(eitherthroughabrowserorwhendownloadingand
openingadocumentviatheQlikViewDesktopclient).
IntheQlikViewcontext,theauthenticationofauserisalmostalwaysdoneagainstanexternalentitythatis
thenusedtopasstheexternallyauthenticateduseridentitytoQlikViewServer.Insuchascenario,
QlikViewreliesontheauthenticationtobeperformedpriortoaccessingQlikView,andthatsometokenof
identityistransmittedto,andtrustedby,QlikView.
13.1 Authentication when Using QlikView Server in a

Windows User Environment
AuthenticationtoaQlikViewServerinanenvironmentbasedonWindowsusers(forexample,incorporating
ActiveDirectory)isstraightforward.Theprocessisasfollows:
1. TheusercredentialsarevalidatedwhentheuserlogsintotheWindowsoperatingsystemonthe
clientmachine.
2. LaterwhentheuserwantstoestablishasessionwithaQlikViewServer(QVS)(forexample,viaa
browseronthedesktop),QVScanusethebuilt-inIntegratedWindowsAuthentication(IWA).
3. Theidentityofthelogged-inuseriscommunicatedtoQlikViewServerusingeithertheKerberosor
theNTLMsecuritysolution.Thissolutionprovidessinglesign-oncapabilitiesrightoutofthebox.
Incasetheauthenticationexchangefailstoidentifytheuser,thebrowserpromptstheuserfora
Windowsuseraccountnameandpassword.
13 Authentication
Authentication when using QlikView Server in a Windows user environment

Theauthenticationprocessdiffersbasedontheenvironment:
l LocalAreaNetwork(LAN):IWAismostcommonandmostsuitableforrecognizingWindowsusers
onaLAN.Theactofauthenticationisperformedwhenloggingintheworkstation,andthisidentity
isleveragedbyQlikView.
l Multi-domainenvironment:TheinternalcompanynetworkIWAshouldbeavoidedinarchitectures
wherethereisamulti-domainenvironmentwithnotrustrelationshipbetweenthedomainofthe
workstationandthedomainoftheserver,orwhenusedacrossareverseproxy.Insuchan
environment,configuretheQlikViewdeploymenttouseeitheranexistingexternalSSOserviceora
QlikViewcustomticketexchangetoexposeanauthenticatedidentitytoQlikView.
13.2 Authentication with a QlikView Server Using an
Existing Single Sign-on Software Package
InenvironmentswhereanSSOinfrastructurealreadyexists(forexample,CASiteMinder,IBMWebSeal,
orOracleOblix),QlikViewcanusetheHTTPheaderinjectionmethodofsinglesign-onprovidedbythe
13 Authentication
SSOinfrastructure.Thismeanssinglesign-onisprovidedrightoutofthebox.TheSSOinfrastructure
softwarepackagescanbeconfiguredasfollows:
l Repeatusergetaccess:Thesoftwarepackagescanbeconfiguredtoprotectaresource.Whenauser
requestsaccesstoQlikView,theSSOpackagegrantsaccess,iftheuserhaspreviouslysignedinto
theSSOauthenticationpage.
l Newuserlogin:IftheuserdoesnothaveanexistingsessionwiththeSSOpackage,theuseris
redirectedtotheSSOpackageloginpage.Afterloggingin,theuserisredirectedtotheoriginalURL
thattheuserrequested.
Inbothcases,iftheuserhasproperlyauthenticatedtotheSSOsoftware,theusernameisinjectedintoan
HTTPheaderandthevalueinthatheaderiswhattheQlikViewserveracceptsastheauthenticatedidentity
oftheuser.
Note!UnlessSSOsoftwareisinplace,theHTTPheadermethodofauthenticatingtoaQlikViewServer
mustnotbeused.HTTPheaderscaneasilybespoofed.AlloftheSSOsoftwarepackagesmentionedabove
provideprotectionagainstthistypeofspoofingattacks,ifthesoftwarepackageistheonlypathforusersto
accessthecontent.
QlikViewdoesnotrecommendorendorseanyspecifictoolorproductforprovidingidentityinHTTP
headers.Theapproachishighlysuitedtoextranetdeploymentswhereintheusersmaynotexistinthe
internalActiveDirectory.TheactofauthenticationisperformedbythereverseproxyorISAPIfilterthat
interceptstheattemptoftheendusertointeractwithQlikViewcontent.
13.3 Authentication Using neither IWA nor Single Sign-on

Software
QlikViewprovidesathirdmethodforsinglesign-on,CustomTicketExchange(CTE),whenneitherofthe
methodsdescribedaboveissuitable.
CTEreliesontheuserhavingauthenticatedpreviouslytoanothersystem:
1. Thethird-partysystemisgrantedtheprivilegeandresponsibilitytorequestanauthenticationtoken
(calledaticketinQlikView)fromQVSonbehalfoftheauthenticateduserofthethird-party
system.Itistheresponsibilityofthethird-partysystemtoonlyrequestticketsforusersthathave
beenproperlyauthenticated(forexample,QVShasnoknowledgeoftheauthenticationstatusofthe
user).
2. Thesystemthenpassestheauthenticationtokentotheuser,whousesitinarequesttoopena
sessionwithQVS.
3. QVSchecksthattheticketisvalidandthenopensasessionfortheauthenticateduser.
TicketedauthenticationismainlyapplicablewhenembeddingQlikViewcontentinthird-partyapplications
andportals,andisrarelyusedforprovidinggeneralaccesstoQlikView.Typicallyasmallamountofcustom
developmentisneededtoimplementtherequestandpassingoftheticketfortheCTEmethodtowork.
13 Authentication
Authentication using neither IWA nor single sign-on software
13.4 QlikView Server Authentication Using Custom Users

Thethreemethodsdescribedabovealluseasinglesign-onprinciple,wheretheuserIDandpasswordare
storedexternallytoQlikViewServerandanexternalentityisresponsiblefortheauthentication.Less
common,althoughpossible,istheabilitytostoretheusercredentialsintheQlikViewServerenvironment
usingtheCustomUsersfunctionalityinQlikViewPublisher.Inthiscase,usersandpasswordsaredefined
andstoredwithintheQlikViewenvironmentandthewebtieroftheQlikViewdeploymentisresponsible
forformsauthentication.Thissolutionissuitableforsmaller,standaloneQlikViewServerdeployments,and
mustnotbeusedinenvironmentswheretheuserdefinitionsaretobeavailabletomultiplesystems.Insuch
environments,itishighlyrecommendedtouseoneofthethreesinglesign-onsolutionsdescribedabove.
Eachcoexistentformofauthenticationmayrequireadistinctwebserverinstance.Severalwebserverscan
forwarduserrequeststothesameQVSinstance(s).
13 Authentication
QlikView Server authentication using Custom Users
14 Authorization
14 Authorization
Onceauserhasbeenauthenticated(thatis,thesystemknowswhotheuseris),thefirststepinassigningthe
securityprivilegeshasbeencompleted.Thesecondstepistounderstandtheauthorityoraccessrightsthat
theuserhastoapplications,data,orboth.ThisstepisreferredtoasAuthorization.Atafundamentallevel,
anadministratorpopulatesanAccessControlList(ACL)withalistofusersand/orgroupsandwhattheyare
tohaveaccessto.Whenthetimecomesforausertorequestaccess,thesystemlooksuptheauthenticated
identityoftheuserintheACLandverifiesiftheadministratorhasgrantedtheuserenoughprivilegestodo
so.
DirectaccesstoaQlikViewdocumentusingQlikViewDesktopisalwaysgovernedbytheWindowsNTFS
filesecurity.Accesstotheweb-basedQlikViewManagementConsole(QMC)isrestrictedtoWindowsusers
thataremembersofaparticularlocalWindowsgroup.
14.1 Document Level Authorization

Onceauserhasbeenauthenticated,QlikViewServertypicallyhandlesauthorizationonitsown.QlikView
ServerprovidesthechoicebetweenstoringtheACLinformationasWindowsNTFSprivileges(applicable
onlywhentheuserisauthenticatedusingaWindowsuseridentity)orbystoringtheACLinformationinthe
internalrepository,DocumentMetadataService(DMS),inQlikView.ThechoiceofNTFSorDMSaffects
theaccesstoalldocumentsinQlikViewServer.
NTFS vs. DMS

QlikViewServercanusetheNTFSprivilegesoftheWindowsfilesystemtostoreauthorizationinformation.
WheninNTFSauthorizationmode,QlikViewServercontrolsaccesstoagivenQlikViewdocumentby
determiningiftheauthenticateduserhasNTFSprivilegestotheunderlyingQlikViewdocumentfile(.qvw).
ThisisbasedontheoperatingsystemprivilegesandWindowsNTFSisusedfortheACL.Theprivilegesof
theauthenticateduserareconfiguredbyaserveradministratorusingstandardWindowsExplorer
functionalityviadirectorypropertiesoptions.
AsanalternativetoWindowsNTFS,QlikViewcanuseitsownACL,DMS.UnlikeNTFS,thisallowsnon-
Windowsusersandgroupstobeauthorizedtoaccessapplicationsanddata.DMSintegratesfullywiththe
existingDirectoryServiceProvider(forexample,ActiveDirectory,otherLDAP)whereGroupMembership
hasbeenrecordedthisisamechanismbywhichQlikViewServercanre-useexistingenterpriseaccounts
andgroupstructures.Thepermittedusersorgroupsarerecordedinametafilethatresidesnexttothe
QlikViewdocument,anditismanagedusingQMC.
NTFSisthedefaultdocumentauthorizationmodel,suitablewhenallusersandgroupsareidentifiedin
ActiveDirectoryorlocallyontheQlikViewServerhost.TheNTFSpermissionsmaybeinheritedfromthe
directorythattheQlikViewdocumentsarein,ormaybeassignedusingQlikViewPublisherdistribution
tasks.
DMSisrequiredwhentheauthenticateduseridentityisnotaWindowsuseraccount.TheDMSpermissions
areexplicitlyassignedusingQMC,ormaybeassignedusingQlikViewPublisherdistributiontasks.
14.2 Data Level Authorization

Datalevelauthorizationallowsaccesstobegrantedordeniedonadocumentlevelandeventospecificdata
inadocument.
14 Authorization
Therearetwotypesofdatalevelauthorizations:
l Dynamicdatareduction:Determinesiftheuserisallowedtoviewthedatawhentheusertriesto
accessit.
l Staticdatareduction:PerformedbyQlikViewPublisher,determinesiftheuserisallowedtoviewthe
datawhenitispreparedfortheuser.
Staticanddynamicreductionofdatacanbeusedonitsown,butcanalsobecombinedtodeliverdatalevel
authorization.
Dynamic Data Reduction

DynamicdatareductionisdoneinQlikViewusingtheconceptofSectionAccess,whichispartofthe
QlikViewdocument.
TheSectionAccessfunctionalityisdescribedintheQlikViewDesktoponlinehelp.
Static Data Reduction

Forlargerdeploymentsand/orthoseinneedofcentralizedcontrolofauthorizationcapabilities,QlikView
Server/Publisherareused.Departmentsorfunctionsoftenhaveamasterapplicationthatcontainsall
relevantdatacoveringallanalysisneeds,andthismasterdocumentneedstobeseparated(reduced)
accordingtotheneedsandaccessprivilegesoftheintendedaudience.QlikViewPublisherreloadsthe
QlikViewdocumentwithavailabledata,refreshestheSectionAccesstables,andsplitsthelargeQlikView
documentintosmallerdocumentsbasedonvaluesinaparticularfield.
Thisreductionanddistributionallowsforafilecontainingmanydatafieldstobebrokenupbythe
contentsofafieldanddistributedtoauthorizedusersorgroupsaccordingtotheiraccessprivileges.
Oneofthebenefitsofreducinganddistributingsourcefilesinthismanneristhatthedocumentsthatare
createdinthisprocesscontainnoexplicitreferencetothesourcedata(forexample,adatabaseconnection
string)intheirscriptenvironments.Therefore,ifauserinteractswiththedocumentviaQlikViewDesktop,
theusercannotseethelocationofthesourcedata.Allofthedatapertinenttotheuserneedsiscontainedin
thedocument.
AnadministratorcanuseQMCtocreatetasksonsource .qvwor .qvdfilestoaccomplishthis.Atabasic
level,thestepsareasfollows:
1. Onthesourcedocument(either .qvwor .qvd),applythedatareductioncriteria(forexample,
choosethefieldnameonwhichtoreducethedata).
2. Applythedistributioncriteriatothenewlycreated(reduced)files:
a.AssigntheauthorizationprivilegesusingeitherDMSorNTFSACLs.
b.Choosethetypeofdistribution(forexample, .qvwfilesor .pdfreport).
c.Choosethelocationforthenewlycreatedfiles.
3. Applythenotificationcriteriaforthecompletionofthetask(forexample,e-mailnotification)
Thenewlycreatedfilesonlycontainthedatathattheuserorgroupisauthorizedtosee,sincethedatahas
beenreducedfromthemasterdocumentinaccordancetothereductioncriteria.Thisiswhytheprocessis
termedStaticDataReduction.Hence,thereisnoriskofanunauthorizedpersonviewingdata,sinceonly
authorizeddataexistsineachfile.
Part 5 Licensing
Part5Licensing
15 Client Access Licenses

ToconnecttoaQlikViewServer(QVS),eachclientneedsaClientAccessLicense(CAL).TheCALsare
purchasedwithQlikViewServerandtiedtotheserverserialnumber.ACALisnevertransferredtoaclient,
butaclientusestheCALwhenconnectingtotheserveror,ifaclusterlicenseisused,aspecificQlikView
Servercluster.CALscannotbetransferredbetweendifferentQlikViewServerclusters.Ifauserisrequiredto
workwithdocumentsresidingindifferentclusters,aseparateCALisneededforeachoftheclusters.
Note!TheCALsrequiretheQlikViewServerswithinaclustertobewithinthesamegeographicaland
physicallocationandwithinthesamenetworksub-net/segment.
15.1 CAL Types

TheCALsdescribedbelowareusedtoprovideusersaccesstothevariousQlikViewServersidentifiedin
Editions of QlikView Server (page 85).
Note!CALsareusedforlicensingonlyandtheyhavenothingtodowithuserauthenticationfordata
accesspurposes.
CAL Type Description

Named ANamedUserCALisassignedtoauniqueandidentifieduser(see Identification (page
UserCAL 82)forinformationonhowusersareidentified)whomayaccessasmanyQlikView
(an documentsasmayresideontheserverorserverclustertowhichtheNamedUserCALis
identified assigned.ANamedUserCALmaybetransferredtoanotheruserpursuanttothesoftware
userona licensingagreement,inwhichcasethereisa24-hourquarantinebeforetheNamedUser
server) CALcanbetransferredtoanotheruser.Thereisnotimelimitforhowlongauserassigneda
NamedUserCALcanaccessaQlikViewdocument.
Document ADocumentCALisassignedtoauniqueandidentifieduser(see Identification (page 82)

CAL(an forinformationonhowusersareidentified)whomayaccessonlytheoneQlikView
identified documenttowhichtheDocumentCALisassigned.MultipleDocumentCALscanbe
user assignedtoaparticularuser.Forexample,ifauserconnectstotwoQlikViewdocuments,
withina theuserwillhavebeenassignedtwoDocumentCALs.ADocumentCALmaybe
given transferredtoanotheruserpursuanttothesoftwarelicensingagreement,inwhichcasethere
document) isa24-hourquarantinebeforetheDocumentCALcanbetransferredtoanotheruser.There
isnotimelimitforhowlongauserassignedaDocumentCALcanaccesstheQlikView
documenttowhichtheCALisassigned.
Session ASessionCALallowsanyuser,identifiedoranonymous/unidentified,ononeQlikView
CAL clienttoaccessasmanyQlikViewdocumentsasmayresideontheserverorserverclusterto
whichtheSessionCALisassignedforaminimumperiodof15minutes.ForSessionCALs,
theQlikViewclientreferstoeachuniqueinstanceoftheQlikViewclient(forexample,the
AJAXclient,QlikViewDesktop,ortheInternetExplorerplugin)ontheusersmachine.The
minimumsessiontimeforaSessionCALis15minutes,whichmeansthatsessionsthatend
inlessthan15minuteswillstillconsumethesessionuntilthe15minutemarkispassed;
thosewhichterminateafter15minuteswillconsumetheiractualsessionlength.Bydefault,
thereisnomaximumsessionlength,butthiscanbeconfigured.
CAL Type Description

Usage AUsageCALallowsanyuser,identifiedoranonymous/unidentified,toaccessonlyone
CAL QlikViewdocument,residingontheserverorserverclustertowhichtheUsageCALis
assigned,fromoneclient(forexample,theAJAXclient,QlikViewDesktop,ortheInternet
Explorerplugin)foratimeperiodof60minutesper28-dayperiod.Ifauserexceedsthe60
minutetimelimitation,theuserwillhaveconsumedtwoUsageCALswithoutanywarning
beinggiventotheuser.Every28days,theUsageCALisrefreshedandtheusermayonce
againviewanewQlikViewdocumentfor60minutes,usingthesameUsageCAL.Usage
CALsarecontinuouslyrecharged(atapacecorrespondingto1/28ofthe totalnumberof
UsageCALsassignedtotheQlikViewServerperday).
15.2 Identification
TouseaNamedUserCALoraDocumentCAL,theclientusermustbeidentifiedviaanauthenticateduser
name(WindowsActiveDirectoryorthroughaticketexchangebetweenthewebserverandQlikView
Server).AnIPaddressisnotavalidformofidentificationforaNamedUserCAL.Thetwomethodsof
identificationcannotbemixedonthesameinstanceofQlikViewServer.Notethattheusername
identificationrequiresWindowsauthenticationonAJAXclients,sincemachinenameidentificationcannot
beusedfortheseclients.
AnyCALusedbyanidentifiedusermaynotbetransferredtoanotheruser,unlessthetransferisduetoa
changeintheemploymentstatusorworkdutiesoftheprioruser,inwhichcasethereisa24-hourquarantine
beforetheCALbetransferredtoanotheruser.
15.3 Document CAL Restrictions

ThepurposeoftheDocumentCAListoprovideamechanismbywhichlicenseescanlicensetheuseofa
singledocument.Topreventthecombinationofmanydatamodelsinasingledocument,thereare
restrictionsinthedocumentsthatcanbeusedwiththeDocumentCAL.However,theNamedUserCAL,the
SessionCAL,andtheUsageCALcanbeusedtoopenanyfunctionalQlikViewdocument.TheDocument
CALcanonlybeusedwithdocumentsthathaveasinglecontiguousdatamodelanddonotcontainany
chasmtrapsbetweentables.
MostcommondatamodelsusedinQlikViewdocumentscanbeusedforDocumentCALs.Forinstance,
properstarschemasandsnowflakeschemastypicallyhavethefieldwiththehighestcardinalityinthefact
tableandthekeysindimensionaltableshavealowercardinality.Forsnowflakeschemas,thecardinality
decreasesfurtherwhenmovingawayfromthefacttable.Documentscontainingsuchmodelstypicallyfulfill
theabovedemandsandarewell-suitedforDocumentCALs.
Documentswithmultiplelogicalislandsarenormallynotallowed.Multiplelogicalislandsareonly
allowed,iftheadditionaltablesareunconnectedandcontainonlyfewrecordsorasinglecolumn.
Inaddition,thedocumentmaynotcontainanylooselycoupledtables.
Finally,thecardinality(thatis,thenumberofdistinctvalues)ofthekeyfieldsmustdecreasewhenmoving
awayfromthefacttable.
15.4 Combining Different CALs

AgiveninstanceofQlikViewServercancarryanycombinationoftheCALtypeslistedin CAL Types
(page 81).WhendifferentCALtypesarecombinedonthesameserver,theorderofpriorityintheCAL
assignmentisdoneasfollows:
1. IfthereisadedicatedNamedUserCALfortheconnectingclient,itisused.
2. IfthereisadedicatedDocumentCALfortheconnectingclient,itisused.
3. IfanewNamedUserCALcanbeassignedtotheconnectingclient,itisused.
4. IfanewDocumentCALcanbeassignedtotheconnectingclient,itisused.
5. IfthereisanavailableSessionCAL,itisused.
6. IfthereisanavailableUsageCAL,itisused.
7. Ifnoneoftheabove,accessisdenied.
15.5 License Lease

AQlikViewclientthatdoesnothavearegisteredlicenseisallowedtoconnecttoQlikViewServerand
borrowalicense,sothattheusercanworkofflineforaperiodof30days.TheQlikViewclientmustthen
makeanauthenticatedlogon(notanonymous)andobtainaNamedUserCAL.EachtimeQlikViewis
started,QlikViewtriestocontactQlikViewServerandrenewthelicenselease.Iftheclientcannotreachthe
serverafter30days,thelicenseleaseexpires.
AlicenseleasecanonlybeusedwithQlikViewDesktopandtheInternetExplorerplugin.Thismeansa
licenseleasecannotbeobtainedwhenusinganAJAXclient.
15.6 Cluster Licensing

AspecialtypeoflicenseisavailabletoallowmultipleQlikViewServerinstallationstosharethesame
licenseserialnumberandsupportsharedCALs.Theserversareautomaticallyconsideredasclustered.Note
thatthisconfigurationaffectsnetworkswhereunauthorizedlicensesharingbetweentestandproduction
environmentshasbeenconfigured.
Note!TheCALsrequiretheQlikViewServerswithinaclustertobewithinthesamegeographicaland
physicallocationandwithinthesamenetworksub-net/segment.
15.7 Cold Standby Servers

QlikViewServerlicensekeyscanbeinstalledonasmanyserversasrequiredprovidedthatonlythelicensed
numberofQlikViewServersarerunningatanygiventime.Thus,acoldstandbyenvironmentcanbe
installedandready-to-run,butcannotbelive(thatis,theWindowsservicescannotbestarted)andinuse
priortotheliveenvironmentbeingshutdown.
16 Editions of QlikView Server

QlikViewServercomesinanumberofeditionsdesignedfordifferentorganizationsandpurposes.
Upgradingisdonethroughthelicensekey.
16.1 Editions
ThevariouseditionsofQlikViewServerarelistedbelow.
Edition Description
QlikView QlikViewEEServerisdesignedtobeusedinlargeandcomplexdeploymentsand
Enterprise providesfeaturessuchasunlimiteddocuments,server-basedcollaboration,integrationwith
Edition third-partysecuritysystems,serverclustering,andclusterlicensing.Theminimum
(EE)Server configurationofaQlikViewEEServeristenNamedUserClientAccessLicenses(CALs).
QlikView QlikViewSBEServerisdesignedtobeusedinsmallerdeployments.Theminimum
Small configurationofaQlikViewSBEServerisfiveNamedUserCALs.
Business
Edition
(SBE)
Server
QlikView QlikViewIASisaQlikViewServerthatislicensedforanuncappednumberofusers,but
Information limitedtoasingleQlikViewdocument.QlikViewIASrunsinanonymousmodeandmust
Access bepublicallyaccessiblewithoutauthentication(onthepublicInternet),thatis,itmustnot
Server beplacedbehindafirewall.N oQlikViewclientcanaccessQlikViewIAStheuser
(IAS) interfacemustbebuiltbytheendusereithermanuallyorbyusingQlikViewWorkBench.
Note!ThereisnolicenseleasefromQlikViewIAS.
QlikView QESallowsenduserstodeployQlikViewsolutionstotheirextranet.QESisbasedon
Extranet QlikViewEEServer,butonlysupportsuptothreeQlikViewdocuments.Theservercanbe
Server deployedwithacombinationofSessionandUsageCALs.QESsupportsmobileclientsand
(QES) canbedeployedinclusteredenvironments.TheAJAXclientoracustomizedAJAXclient
canbeusedviaQlikViewWorkBench,whichisincludedinQES.
InadditiontotheeditionsofQlikViewServerdescribedabove,thereisalsoanumberofadditional,server-
relatedproducts,allofwhicharelistedbelow.
Product Description
QlikView QlikViewTestServerisalicensethatprovidesanenvironmentseparatefromproduction
TestServer tousefordatavalidation,applicationtesting,andpreparation/migrationofQlikView
documentstonewversionsand/orreleasesofQlikView.
QlikViewTestServercomesintwoeditions,QlikViewEETestServerandQlikViewSBE
TestServer,bothofwhichhavethesamefeaturesandlimitationsasthecorresponding
productionservers.Inaddition,thewatermarkTestissuperimposedonallchartsand
addedtoallobjectcaptions.
Note!ThereisnolicenseleasefromQlikViewTestServer.
Product Description
QlikView QlikViewPublisherisalicensethataddssignificantfunctionalitytothestandardreload
Publisher capabilityofQlikViewServer.QlikViewPublisherincludesfunctionalitytohandlefield
levelsecurityandaccesscontrolfromcentraladministrationsoftwarelikeWindowActive
DirectoryorNovellLDAP.QlikViewPublisherisalsoneededtosupportcomplex
distributionmodelsforQlikViewdocuments.Inaddition,eachlicenseofQlikView
Publisherallowsanadditionalnode/serverforreload,distribution,orsecuritymanagement
inamulti-node/serverdeployment.
WiththeadditionalcomponentQlikViewPublisherReportDistribution,anyQlikView
documentreportcanbedistributedasa .pdffiletoafolderorviaemailorSMTP.
QlikView QlikViewWorkBench(anadd-ontoQlikViewEEServer)isadevelopmenttoolfor
WorkBench creatingwebmash-upswithQlikView.Itfeaturesdraganddropeditingcapabilities
withintheMicrosoftVisualStudiodevelopmentenvironmentandallowsforcustom
webinterfacesandintegrationwiththird-partyservices.
Note!QlikViewWorkBenchisnotavailableforusewithQlikViewSBEServer.
QlikView QlikViewWebParts(anadd-ontoQlikViewEEServer)forMicrosoftSharePointallows
WebParts forrapiddeploymentofQlikViewobjectswithinMicrosoftSharePointportal
for environments.
Microsoft
Note!QlikViewWebPartsarenotavailableforusewithQlikViewSBEServer.
SharePoint
QlikView QlikViewLocalClientisaclientwithallfunctionalityusedtodevelopQlikView
LocalClient documents.QlikViewLocalClientisdeployed,iftheenduserdeployslocalclientsonly.
QlikView AnybodyregisteredonQlikView.comisallowedtodownloadQlikViewanddevelop
Personal QlikViewdocumentsforpersonaluse.TherearenorestrictionstoQlikViewPersonal
Edition EditionexceptthatitcannotopenQlikViewdocumentscreatedbyotherusersorperform
animportofanentirelayoutfromanXMLfile.
16.2 Features and Limitations

ThetablebelowliststhefeaturesandlimitationsofeacheditionofQlikViewServer(Yes=supported,No=
notsupported).
EE SBE IAS QES
Licensing
NamedUserCALs Yes Yes No No

(max
25)
SessionCALs Yes No Yes Yes

(unlimited)
UsageCALs Yes No No Yes
DocumentCALs Yes Yes No No

(max
100)
ExternalUsersAllowed? No No Yes Yes
Clients
AJAX(andmobiledevicesviaAJAX) Yes Yes Yes Yes

(WorkBench (WorkBench
included) included)
InternetExplorerPlugin Yes Yes No No
InstalledQlikViewClient Yes Yes No No
Scalability
Canbeclustered(additionalserverlicenserequired) Yes No Yes Yes
UnlimitedDocuments Yes Yes No No

(1only) (3
documents
only)
Integration
ThirdPartySecurityIntegration Yes No No Yes
DynamicDataUpdate Yes Yes Yes Yes
Features
LicenseLease(offlineaccess,NamedUserCALsrequired) Yes Yes No No
Annotations Yes Yes No Yes
Collaboration(sheets,sheetobjects,andinputfields) Yes Yes No No
SessionCollaboration Yes Yes No Yes
EE SBE IAS QES

QlikViewPublisherandPDFgeneration(additional Yes Yes No No
licenserequired)
QlikViewConnectorforusewithSAPNetWeaver Yes Yes Yes Yes

(additionallicenserequired)
TestServerOption Yes Yes Yes Yes
CanbeembeddedinMicrosoftSharePoint(QlikViewWeb Yes No Yes Yes

PartsforMicrosoftSharePoint)(additionallicenserequired)
Buildbespokemashups/AJAXapplications(QlikView Yes No Yes Yes

WorkBench)(additionallicenserequired) (included) (included)
Security
SectionAccess Yes Yes No Yes
DocumentMetadataService(DMS) Yes No No Yes
ActiveDirectory/NTFS Yes Yes No Yes
AnonymousUser Yes No Yes No

(with (mandatory)
Session
CALs)
Part 6 Appendix
Part6Appendix
17 Silent Installation
Whenrunningasilentinstallation,QlikViewisinstalledwithalimitedsetofornodialogsatall.This
meansallfeatures,properties,anduserselectionshavetobeknownwhencreatingthesilentinstallation
package.TherearealsosomestandardpropertiesinWindowsInstallerServicethatmayberequired.
Toprepareasilentinstallation,theMSIfilehastobeextractedfromtheQlikView Setup.exefile.
Asilentinstallationcanberunwithdifferentinterfacelevels:
/qn Completelysilent.
/qb Basicuserinterface.
Adda +signatendoftheinterfacelevelscommandtogetamodaldialogattheendoftheinstallation
sayingFinishedandifitwassuccessfulornot.
ThefollowingsilentinstallationcommandlinesarerecommendedforQlikView:
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"
Thecommandlineaboveinstallsallfeaturescompletelysilentlywithamodaldialogattheendofthe
installation.
Ifjustalimitedsetofthefeaturesaretobeinstalled,change alltothenameofthefeatureinstead.If
severalfeaturesaretobeinstalled,separatethemwithcommas.
Thefollowingfeaturescanbeinstalled:
l DirectoryServiceConnector
l ManagementService
l QVS
l QvsDocs
l WebServer
l DistributionService
l SupportTools
l QvsClientswiththesub-featuresPluginandAjaxZfc
l MsIISwiththesub-featuresQvTunnelandQlikViewSettingsService
Note!Forthesub-featurestobeincludedintheinstallation,theyhavetobeincludedinthelistoffeatures
tobeinstalled.
msiexec /i QlikViewServerx86.msi ADDLOCAL="all" DEFAULTWEBSITE="2" /qn+
Thiscommandlineinstallsallfeatures,includingthevirtualdirectoriestoanotherwebsitethanthedefault
one.ThisrequiresamachinewithMicrosoftInternetInformationServices(IIS)installedandmorethanone
websiteonit.Thesitenumberalsohastobeknown.Set DEFAULTWEBSITEtothesitenumberwherethe
virtualdirectoriesaretobeinstalled.Tofindthenumberofthewebsite,checkIIS.
Theinstallationprocedurecanbelogged,usingthefollowingcommand:
msiexec /i QlikViewServerx86.msi ADDLOCAL="all" DEFAULTWEBSITE="2"/L*v
log.txt /qn+
17.1 Settings
Thefollowingsettingsaregoodtoknowwhendesigningasilentinstallationpackage:
Prerequisites .NETFramework4.0
Default installation folder ProgramFilesFolder\QlikView

(INSTALLDIR)
Windows Installer Version 3.1Schema301
Default language English(UnitedStates)1033
Require Administrative Yes

Privileges
INSTALLEVEL 100,allfeaturesissetto101bydefault
Features See Silent Installation (page 91).Thereisahiddenfeaturecalled

Install.Donotremoveit.
IIS FourvirtualdirectoriesandanApplicationpoolareinstalled
Services Fiveservicesareinstalled
17.2 Dialogs
TheQlikViewinstallationhaseightdialogs,oneofwhichisaCustomSetupdialogandoneofwhichisa
Websitedialog.Alldialogssetimportantproperties.Tofindthevalueofaproperty,doatestinstallation
withverboselogging.Notethatthepropertyvaluesmaydifferdependingonthelanguageandoperating
systemused.
Region
Thisdialogisusedforspecifyingtheregion.
Property: REGION_LIST
Region dialog
License Agreement
Thisdialogdisplaysthelicenseagreementfortheselectedregion.
Radiobutton: AgreeToLicense = "Yes"
License dialog
Customer Information
Thisdialogisusedforenteringthecustomerinformation.
Properties: USERNAME, COMPANYNAME
Customer information dialog
Destination Folder
Thisdialogisusedtosetthedefaultfolderfortheinstallation.
Property: INSTALLDIR
Destination folder dialog
Profiles
Thisdialoghasseveralpropertiesconnectedtoit,sincetherearemultipleprofilestochoosefrom.
Select Full Installation, Single machine with QlikView Webservertoinstalleverything,including
QlikViewWebServer,neededtorunQlikViewonasinglemachine.TouseIISinstead,select Full
Installation, Single machine with IIS(thisoptionisonlyavailableifIISisinstalledonthetargetmachine).
Toperformacustominstallation,select Custom installation, select profilesandthenselecttheprofilesto
install.The WebserverprofileallowstheusertochoosebetweenQlikViewWebServerandIIS(ifIISis
installedonthetargetmachine).
Properties:
l PROPQVS:QlikViewServer
l PROPDS:Publisher
l PROPQMC:ManagementConsole
l PROPWEB, PROPIIS=1or2:Webserver
l PROPIIS(ifIISisinstalled)or PROPSTATE:SingleMachineInstall
Profiles dialog
Logon Information
Thisdialog,whichisoptionaltouse,isusedtospecifytheuserthatistoruntheservicesthatareinstalled.
Whenclicking Next,aCustomActionchecksthattheentereduserisvalid.TheCustomAction,whichis
implementedbyInstallShield,requiresthemachinetobepartofaDomaintoworkproperly.
Properties:
l LOCALSERVICE
l IS_NET_API_LOGON_USERNAME
l IS_NET_API_LOGON_PASSWORD
Logon information dialog
Ready to Install
Thisisthelastdialog.Click Installtostarttheinstallation.
Ready to install dialog
17.3 Additional Dialogs

Custom Setup
Thisdialogisdisplayedwhenclicking ConfigintheProfilesdialog,see Profiles (page 94).
Custom setup dialog
Website
ThisdialogisdisplayedwhenselectingIISaswebserverintheProfilesdialog,see Profiles (page 94).
Property: DEFAULTWEBSITE
Website dialog
17.4 MST
WhencreatinganMSTfile,theMSIfileiscustomizedwithoutanychangesbeingmadedirectlyintheMSI.
TheMSTfileworksasafilterontopoftheMSIandallowschangestobemadetotheinstallation.For
example,thedefaultinstallationfolderforQlikViewServeris %ProgramFiles%\QlikView,butifthat
ischangedto C:\QlikViewintheMSTfile,thedefaultfolderischanged.Thesamethingcanbedone
withthedialogs,whichmeanspropertiescanbepreset,sothattheinstallationcanberunwithalimitedset
ofdialogs.
TocreateanMSTfile,anMSIrepackagingstudio(forexample,InstallShieldAdminStudio)isneeded.
Note!QlikTechdoesnotsupplyanyMSTfilesanddoesnottakeanyresponsibilityforMSTfilescreated
bycustomersorpartners.
17.5 Additional Information

Foradditionalinformationonsilentinstallation,see Deploying MSI Packages with Group Policies (page
107).
18 OEM
18 OEM
18.1 General
TheOEMfeaturepreventsabuseofQlikViewServerssoldunderanOriginalEquipmentManufacturer
(OEM)licenseandprotectstherevenuestreamsofboththeOEMproductsandthefullQlikViewproduct.In
addition,thefeaturehelpsavoidchannelconflictsbetweenQlikViewOEMpartners,QlikViewreseller
partners,andQlikViewdirectaccountmanagers.
TheOEMfeatureincludesthefollowingrestrictions:
l AQlikViewServerdeliveredtoacustomerbyanOEMpartnercannotrunotherQlikView
applicationsthantheonesdeliveredbytheOEMpartner.
l AQlikViewapplicationdeliveredtoacustomerbyanOEMpartnercannotrunonanotherQlikView
ServerthantheonedeliveredbytheOEMpartner.
18.2 Detailed Function Description

ThefunctionsoftheOEMfeatureareasfollows:
AtagwithakeyisdefinedintheQlikViewServerLicenseEnablerFile(LEF)as OEM_PRODUCT_ID.This
LEFtagisissuedonceforeachOEMpartnerandtheirQlikViewDesktop,andQlikViewServerlicenses
withmatchingtagsaredeliveredforeachQlikViewServerdeploymentrequiringthisfeature.
TheUserPreferencesdialoginQlikViewDesktopallowsanOEMdevelopertoembedahashkeyinthe
.qvwfile.Thehashkey,whichisbasedonthe OEM_PRODUCT_IDkeypresentintheQlikViewDesktop
licenseoftheOEMpartner,isacapitalized40characterhexstringthatisstoredintheDocumentProperties
andDocumentmetadata.Inthedialog,thepartnercanlabelallkeysgeneratedforthe .qvwfiles.Thesame
keycanbeusedformultipledocumentsbelongingtothesamecustomer.
AQlikViewServerwiththe OEM_PRODUCT_IDtaginitsLEFonlypermitsthepublishingof .qvwfiles
withamatchingkeyonthatQlikViewServer.Astandard,non-OEMQlikViewServerbydefaultopensany
.qvwfile,withtheexceptionof .qvwfilescontainingaspecifickeythatsomeOEMpartnersareissued
withtopreventopeningwithanyotherQlikViewServerthantheonewithamatching OEM_PRODUCT_ID.
ThetablebelowprovidesafewexamplesoftheresultsoftheOEMfunctionality.
File
Normal.qvw OEM 1.qvw OEM 2.qvw
QlikView NormalQlikView Fileopened Filenot Filenot
Server Server opened opened
OEM1(Nolicense Filenot Fileopened Filenot

lease) opened opened
OEM2(Nolicense Filenot Filenot Fileopened

lease) opened opened
InQlikViewDesktop,a .qvwfilecontaininga PRODUCT_IDisopenedinusermode.
19 DSP Interface
19 DSP Interface
ThereasonfordevelopingaproprietaryDirectoryServiceProvider(DSP)istohaveQlikViewdistribute
documentstousersinadirectoryservicenotsupportedbydefault,andtoprovidegroupresolutiontothe
webserver.
19.1 DirectoryServiceProvider
DirectoryServiceProvideristheinterfaceoftheclassthatplugsintotheframework.Themembersofthe
interfacearelistedbelow.
Member Description
LogMessage LogMessageEvent { Directlyafterconstruction,thisfieldisinstantiatedwitha
set; get; } delegatethatprovidescrudeloggingfacilities.
string ProviderName { get; } Afree-form,preferablydescriptive,nameofthecomponentthat

issuitablefortheenduser.
string ProviderType { get; } Aninstallation-uniqueidentifierusedinternallybythe

frameworkandrelatedcomponents.Theidentifiersusedbythe
suppliedprovidersare AD, NT, Local,and Custom.
void SetupPath (string _path, Createsanodethatrepresentsthecorrespondingdirectory

string _username, string _ servicenodeonthespecifiedpath.Uponfailure,anexceptionis
password); thrown.
IList<string>GetKnownRootPaths Thereturnedlistshouldcontainoneormoreviablepathsfor
(); themethodslistedhere.
void ClearCache (); Clearsthecache(ifany).
string DomainName { get; } Adomainnameassociatedwiththepaththatissetup.Itis

usedasaqualifiertoseparatenodesfromdifferentproviders(for
example,theshippedActiveDirectoryprovideruses
NetBIOSNameasdomainname).
IDictionary<string, string> Thedictionaryofsupportedsettingshasthenameofthesetting

GetSettings (); as keyandthenameofthetypeas value.
void SetSetting (string _name, Theparsingresponsibilityisobviouslyputontheprovider.

string _value);
IList<IDSObject> Search Searchesfornodeswithattributesmatchinganyofthepatterns

(string [] _pattern, provided.Theattributesarespecifiedwiththe typeparameter,
eSearchType _type, string _ whichcanbeoneormorevaluesfromtheenumeration.If type
otherattribute); isother,thelastparameterspecifiesthenameoftheattribute.
Thesearchtypelegacyidisusedforbackwardscompatibility.
Searchshouldsupportpatternscontainingthewildcardsign
*,whichmatcheszeroormorecharactersofanykind.

19 DSP Interface
Member Description
void Dispose (); Calledwheneveraproviderobjectisreleased.
IDSObject Asimpleinterfaceforanytypeofnodewithinthedirectory
service.
string ID { get; } NodeID,uniquewithintheinstantiatedpathandconsistent

overallexecutions.
string DisplayName { get; } Commonnameofthenodeinthedirectoryservice.
string AccountName { get; } Accountnameassociatedwiththenode(ifpresent).
eDSObjectType ObjectType { Basictypeoftheobject.

get; }
IList<IContainer> MemberOf (); Alistofallgroupsthatthenodeismemberof.
string GetCustomProperty Anyotherpropertynotnativelysupportedbytheinterface.If

(string _name); notpresent,nullisreturned.
string Email { get; } Theprimarye-mailaddressassociatedwiththenode(ifany).

20 SNMP
20 SNMP
QlikViewprovidesSNMPagentsforallservices.However,thesettingisoffbydefault,sincethe
implementationisinitsinitialstagesandsubjecttochange.Atthetimeofwriting,readingoperationsfrom
theagentsareenabled.Thefollowingmessagesaresupported:
l GetRequest
l GetResponse
l GetNextRequest
AllservicesanswerthestandardSNMPqueries(seebelow).
Identifier Query Description
1.3.6.1.2.1.1.1 sysDescr Descriptionofservice/product.
Example:
sysDescr.0:Qlikview Publisher
Commandcenterservice version 8.50.600
1.3.6.1.2.1.1.2 sysObjectID Unittype.

Example:
sysObjectID.0:iso.org.dod.internet.private.
enterprises.qliktech
.products.publisher.Distributionservice
1.3.6.1.2.1.1.3 sysUpTime Systemuptime.

Example:
sysUpTime.0:0 hours, 12 minutes, 15 seconds
1.3.6.1.2.1.1.4 sysContact Canbesetintheconfigurationfile.

Example:
sysContact.0:Unspecified System contact
1.3.6.1.2.1.1.5 sysName Canbesetintheconfigurationfile.

Example:
sysName.0:Unspecified name
1.3.6.1.2.1.1.6 sysLocation Canbesetintheconfigurationfile.

Example:
sysLocation.0:Unspecified location
1.3.6.1.2.1.1.7 sysService Constant,72meansapplicationserver.

Example:
sysServices.0:72
TheQlikViewDistributionServicecanansweradditionalqueries.Thesearespecifiedinthe MIB File (page

104).
Eachservicehasaconfigurationfile,whichisstoredinthesubfolderfortheserviceintheinstallation
folder.Forexample,theconfigurationfilefortheQlikViewDistributionServiceis
QlikViewdistributionService.exe.config.

20 SNMP
TheSNMPsettingscanbeadjustedinthe SNMP SETTINGSpartoftheconfigurationfile.SNMPhastobe

enabledforallservices(thedefaultisoff).
Setting Description
EnableSNMP EnablestheSNMPlistener.Thedefaultvalueis false.
SNMPPort SetstheporttousefortheparticularPublisherservice.Seethedefaultsettingsfor
eachservicebelow.
SNMPsysContact Contactinformationforthepersonresponsibleforthemanagednode.Thedefault
valueis Unspecified System contact.
SNMPsysName Anadministrativelyassignednameforthemanagednode.Byconvention,thisisthe
fullyqualifieddomainnameofthenode.Ifthenameisunknown,thevalueisazero-
lengthstring.Ifleftempty,itdefaultstothecurrentmachinename.Thedefaultvalue
is Unspecified name.
SNMPsysLocation Physicallocationofthenode(forexample,telephonecloset,thirdfloor).The
defaultvalueis Unspecified location.
DebugSNMP EnablestheextendeddebuglogfortheSNMPlistener.Thedefaultvalueis false.
Thedefaultportsettingsfortheservicesarelistedbelow.
Service Default Port Setting
ManagementService 4781
DirectoryServiceConnector 4731
DistributionService 4721(defaultSNMPport)
QlikViewServer 4748
Allportscanbeconfigured.Iftheservicesareinstalledondifferentmachines,theycanallrunonthesame
port.TheportschangeastheimplementationmovesawayfromtheexperimentalSNMPrangeandintothe
rangeallottedbyQlikTech.
20.1 MIB File

AMIBfileisincludedintheQlikViewdelivery,sothatallSNMPmanagerscaninterprettheadditional
responsesfromtheQlikViewDistributionService.Note,however,thattheMIBfileissubjecttochange.
Thefileisinstalledin \QlikView\Support Tools.Thesupporttoolsrequireacustomizedinstallation.
TheQlikViewDistributionServicecananswerthequerieslistedbelow,inadditiontotheonespreviously
mentioned.
Identifier Query
1.3.6.1.4.1.30764.1.2.2.1 QDSTaskExecuteStatusTable
1.3.6.1.4.1.30764.1.2.2.1.1 QDSTaskExecuteStatusEntry
1.3.6.1.4.1.30764.1.2.2.1.1.1 QDSTaskID(taskIDnumber)
1.3.6.1.4.1.30764.1.2.2.1.1.2 QDSTaskName(taskname)

20 SNMP
Identifier Query
1.3.6.1.4.1.30764.1.2.2.1.1.3 QDSTaskExecuteStatus(taskstatus):
l Waiting
l Running
l Aborting
l Failed
l Warning
1.3.6.1.4.1.30764.1.2.2.1.1.4 QDSTaskNextExecutionAt(whenthetaskwillbeexecutednext)
1.3.6.1.4.1.30764.1.2.2.1.1.5 QDSTaskLastExecutedAt(whenthetaskwasexecutedlast)
1.3.6.1.4.1.30764.1.2.2.1.1.6 QDSTaskCurrentWork(whatthetaskiscurrentlydoing)
1.3.6.1.4.1.30764.1.2.2.1.1.7
ForadditionalinformationonSNMP,see:
l RFCforSNMP: http://www.ietf.org/rfc/rfc1157.txt
l Wikipedia: http://en.wikipedia.org/wiki/Simple_Network_Management_Protocol

21 Deploying MSI Packages with Group Policies
21 Deploying MSI Packages with Group

Policies
Note!ThischapterismainlyintendedfortheInternetExplorerplugin.
21.1 General
Acommonproblemtodayishowtodeployapplicationsinanetworkenvironmentwheretheusershave
limitedrights,andhowtodeployapplicationsforaspecificgroupofusers.Thissectionbrieflydescribes
howtodeployMicrosoftWindowsInstaller(.msi)packageswithgrouppoliciesinanActiveDirectory
environment.
Note!DeploymentofsoftwarewithgrouppoliciesisonlysupportedbyworkstationsrunningWindowsXP
Professional,WindowsVista,orWindows2003or2008Server.
TheQlikView .msipackagesrequireversion2.0orhigheroftheWindowsInstallerservicetobeinstalled
onthedestinationworkstations.
21.2 Deploying the MSI Package

Whenthe .msifilehasbeenobtained,itmustbeplacedinasharedfolderonthenetwork.Makesurethat
allusersand/ormachinesthataretoinstalltheapplicationhavereadaccesstothefolder.Whenthepackage
hasbeenmadeavailabletotheusersand/ormachines,theGrouppolicyobjectthatwilladvertisethe
installationpackagecanbecreated.
Thepackagecanbeadvertisedtoeachuseroreachmachine.Usethe User Configuration>Software Settings
containertoadvertisethepackageperuser,andthe Computer Configuration>Software Settingscontainer
toadvertisepermachine.BothcontainersarelocatedintheGroupPolicyObjecteditor.
Ifthepackageisadvertisedperuser,itcanbeeitherassignedorpublished.Apackagethatisadvertisedper
machinecanonlybepublished.
Topublishapackageperusermeansthatitislisted(thatis,advertised)intheAddprogramsfromyour
networklistintheAdd/Removeprogramsdialog.
Add/Remove programs dialog

Eachusermustclickthe Addbuttontocompletetheinstallation.
Topublishapackagepermachinemeansthatthepackageisinstalledandaccessibletoallusersonthat
machinethenexttimethemachineisrebooted.

Anadvertisedpackagethatisassignedisalsolistedinthe Add programs from your networklistandcan

beaddedfromthere.Thisoptionalsooffersafewmorewaystoactivatetheinstallationpackage:
l Shortcuts(iftheinstallationpackageaddsany)onthedesktopand/orStartMenu:Theshortcutsare
addedandtheinstallationpackagecanbeexecutedbyclickingtheappropriateshortcut.
l Fileassociation:Theinstallationprogramisexecutedwhentheusertriestoopenafilethatis
associatedwiththeadvertisedapplication.
Thereareafewmorewaystoexecutetheinstallationwhenitisadvertisedasassigned,buttheyarenot
applicabletoanyQlikViewinstallationsandthereforebeyondthescopeofthisdocument.
Note!TheInternetExplorerplugininstallationpackagedoesnotaddanyshortcutsorfileassociations.Itis
thereforenotrecommendedtoadvertiseQlikViewinstallationpackageswiththeassignoption.
Advertising
Toadvertisemeansthattheadministratorgivestheinstallationpackagepermissiontoexecuteonanaccount
withlockeddownpermissions.
Whenthepackageisadvertised,therearesocalledentrypointsloadedontothedestinationsystem.Entry
pointsaretypicallyshortcuts,fileassociations,listingintheAdd/RemoveProgramsdialog,andsoon.
21.3 Step-by-step Guide

Thissectionprovidesastep-by-stepguideforcreatingagrouppolicyforadvertisingoftheQlikView
InternetExplorerplugin .msipackageonanumberofmachinesintheActiveDirectory.
Proceedasfollowstocreateagrouppolicy:
1. Browsetothefoldercontainingthe .msipackage.Sharethefolderwiththenetworkuserswith
permissiontoinstallthepackage.
Sharing the folder

2. Open Active Directory Users and Computersandhighlightthe Organizational Unit (OU)where

thepackageistobedeployed.
Highlighting the Organizational Unit where to deploy the package

3. Right-clickandselect Properties.
Selecting Properties

4. Gotothe Group Policytab,click New,andgivethegrouppolicyobjectanappropriatename.
Providing a name
5. Highlightthenewgrouppolicyobjectandclick Edit.
Highlighting the new group policy object

6. Expand Computer Configuration>Software Settingsor User Configuration>Software Settings,

dependingonhowthepackageistobedeployed.Inthiscase, Computer Configuration>Software
Settingsisselected.
Selecting Software Settings

7. Right-click Software installationandselect New>Package...Apop-upwindow,askingwhereto
locatetheinstallationpackage,isdisplayed.
Creating a new package

8. Browsetotheinstallationpackage(inthiscase, QvPluginSetup.msi),selectit,andclick Open.
Opening the installation package

9. Selectthedeploymentmethod Assignedandclick OK.Sincetheinstallationistobeappliedtothe
Computer Configuration,onlythe Assigneddeploymentmethodcanbeused.
Selecting deployment method

10. Thedeploymentruleisnowreadyforuse.AllmachinesintheOUgetthisdeployment
automatically.Whatactuallyhappensisthatwhenamachineisrebooted,theinstallationprogramis
executed,sothatanyuserthatlogsontoamachineinthatOUcanruntheinstalledprogram.The
rulecanbeappliedtomanydifferentOUs.
Deployment rule is ready for use

22 QlikView Server Extensions
22 QlikView Server Extensions

22.1 Adding Extensions to QlikView Server
TorunQlikViewExtensionsonaQlikViewServer,thecontentsofthe Extensionsfolderhavetobe
copiedfrom %UserProfile%\AppData\Local\QlikTech\QlikView\Extensions\Objectsto
the %ProgramData%\QlikTech\QlikViewServer\Extensions\Objectsfolderontheserver.
Ifthepathtotheextensionsischanged(forexample,toacommonplaceforallserversinacluster),that
pathmustbeusedinstead.Notethatthepathsetcorrespondsto
%UserProfile%\AppData\Local\QlikTech\QlikView\Extensions(thatis,itdoesnotinclude
\Objects).

23 Configuring Microsoft IIS for Custom Users
23 Configuring Microsoft IIS for Custom

Users
WhenusingMicrosoftIISaswebserverforCustomUsers,configurationisneeded.
ProceedasfollowstoconfigureIISforCustomUsers:
1. InQlikViewManagementConsole,changetheparametersonthe System>Setup>Authenticationtab
inaccordancetothefollowing:
Authentication Always
Type CustomUser
Parameters CUSTOM\
Login Address Alternateloginpage(webform)
Authentication tab

2. Selectthe QlikViewvirtualfolderandthen Authentication.
Selecting Authentication
3. Disable Windows Authenticationandenable Anonymous Authentication.
Enabling Anonymous Authentication for the QlikView virtual folder

4. Selectthe QvAjaxZfcfolderandthen Authentication.

5. Disable Windows Authenticationandenable Anonymous Authentication.
Enabling Anonymous Authentication for the QvAjaxZfc folder

6. Right-click QvAjaxZfcandselect Switch to Content View.
Selecting Switch to Content View

7. TheconfigurationofIISfortheCustomUseriscomplete.

24 Triggering EDX Enabled Tasks

Tostarttasksthathaveanexternaleventastrigger,theQlikViewManagementServiceAPI(QMSAPI)must
beused.TheusermakingtherequestcallsmustbeamemberoftheQlikViewAdministratorslocalgroupor
theQlikViewEDXlocalgroup.TheQlikViewAdministratorsgroupissetupduringtheinstallationof
QlikViewServer,buttheQlikViewEDXgroupmustbecreatedmanuallyin Computer Management.
MembersoftheQlikViewEDXgrouponlyhavetherighttotriggerEDX-enabledtasks.
Themethodtousehasthefollowingsignature:
Parameter Purpose
guid IDoftheQlikViewDistributionService(QDS)wherethetaskisdefined.
taskNameOrId TasknameorIDofthetaskinstringformat.
password Password(ifrequiredbythetask).
variableName Variablename(ifrequiredbythetask).
variableValues Listofvaluesforthevariable.
Thereturnedresultcontainsinformationonwhetherthetaskwassuccessfullystartedornot.

Theexamplebelowshowshowtotriggerataskandwaituntilithasfinishedoruntilacertainamountof
timehaspassed.
TheexamplecomesfromtheQMSAPIdocumentation,whichisinstalledaspartoftheQlikView
ManagementConsole(QMC).Itcontainsdetailedinformationontheavailablemethodsandhowtoget
startedwiththeQMSAPI.

QlikView Server Reference Manual PDF

Enviado por

Dados do documento

Título original

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

QlikView Server Reference Manual PDF

Enviado por

Direitos autorais:

Formatos disponíveis

Server/Publisher

Version 11.0 SR1 for Microsoft Windows

1.2 QlikTech Support Services

%ProgramFiles% C:\Program Files C:\Program Files

%UserProfile% C:\Users\[username] C:\Documents and Settings\[username]

1.4 About this Document

2 Whats New in QlikView 11 Server?

Context Sensitive Help

Audit Logging by Document

Enable/Disable Document Download, Exporting, and Printing

Supporting Task for .qvd Creation

Distribution to Email within a .qvw Document

Alert Email to Document Administrators

Distribution and Reload Performance

Loop and Reduce

QlikView Management Console User Interface

Reduction with Lock Fields

QMC and QMEC are Merged into QMC

Load Balancing Improvements

MSI Installation of QlikView Server

QlikView Settings Service

3.1 QlikView Server

Processor IntelCoreDuocompatibleorhigher Multi-corex64compatibleprocessors.

Memory 1GBminimum.Dependingondata 4GBminimum.Dependingondata

Diskspace 450MBtotalrequiredtoinstall. 450MBtotalrequiredtoinstall.

Security MicrosoftActiveDirectory MicrosoftActiveDirectory

Webserver QlikViewWebServer(QVWS) QlikViewWebServer(QVWS)

Management MicrosoftInternetExplorer7,8,and9 MicrosoftInternetExplorer7,8,and9

.NET 4.0 4.0

Internet IPv4 IPv4

3.2 QlikView Publisher

Upgrading from Version 8 to 11

Upgrading from Version 9 or 10 to 11

4.2 Upgrade Procedure

QvPlugin Updateto %ProgramFiles%\QlikView\Server\QlikViewClients\

QvClients Updateto %ProgramFiles%\QlikView\Server\QlikViewClients.

4.3 Multi-machine Preparation

Migration to a New Machine

5 Installing QlikView Server

5.1 Installation Profiles

5.2 Logging the Installation

Obtaining the MSI package

5.3 Completing the Installation

Running Microsoft IIS

QlikView Server/Publisher License tab in QMC

Account to Run the Services Under

6.2 Root/First Install

6.3 Adding Services on Other Machines

QlikView Distribution Service

Directory Service Connector

QlikView Web Server

Tunneling Using Microsoft IIS

7.1 QlikView with Publisher

7.2 QlikView without Publisher

QlikView architecture without Publisher

7.3 QlikView Server

QlikView Server Client Communication

QlikView Server client communication

QlikView Server User Document

7.4 Web Server

QlikView Server Tunnel

7.5 Directory Service Connector

Directory Service Connector