Abbreviations, used in manual:
QG - Quality Gates
This guide explains how to add and connect a QlikView Data Source to Quilliup.
Prerequisites:
Local File Permissions:
Ensure that the Tomcat user running the application (for example, the user running the Windows service) has full access to the QVW files. This user must have the necessary permissions to open the files and read their metadata:
In the quilliup server folder, search for the QV.exe file (usually located under "C:\Program Files\QlikView") and run it with the quilliup user by holding the SHIFT key + right mouse click --> "Run as different user": 
Remote files (published) permissions:
Make sure that user that runs the application has full access to the published applications. The user must have permissions to the QlikView Access Point and read the published QVWs.
In the quilliup server, search for your web browser file location and open it with the quilliup user holding the SHIFT key + right mouse click --> "Run as different user" (for example, chrome file location): 
Log in to the access point web site and ensure that you can open the presented applications:
In quilliup UI:
In QG module, in the left side menu go to "Settings -> Data Sources -> QlikView":
A list of all existing Data Sources will appear on the main screen. You can either edit an existing Data Source or click the "Add Data Source" button to create a new one:
There are two options to connect QlikView to Quilliup:
1. Local
2. Remote
1. Local - fill the required fields:
Name - The name of the Data Source.
Location - A location previously created in the Administration module. This should be a valid path to the folder containing the QlikView files.
Path - (Optional) Use this field to specify subfolder(s) within the defined "Location" path, if applicable.
Filter - Select one of the two predefined file type options: *.qvd or *.qvw.
Filter by - This filter helps narrow down the list of files available within the connection.
Search subfolders - Enable this option if you want to include files located in subdirectories under the specified "Location" and "Path" (if provided).
Test Connection - Validates the connection and confirms it returns the correct number of files.
Assigned Projects - The Data Source must be linked to the relevant Project(s). Once assigned, it will appear in the list of Data Sources within the Project’s Data Sets.
2. Remote - fill the required fields:
Name - The name of the data source.
Host - The host address of the data source. If running locally on a desktop, you can use localhost.
Authorization:
SSO (NTFS, Header Authorization) – Uses Single Sign-On (SSO) to authenticate users via Windows (NTFS) or through an authorization header. This method is typically used in environments with Active Directory, allowing users to access QlikView resources without manually entering credentials.
Ticketing (DMS) – Uses QlikView's Dynamic Management System (DMS) authentication, where tickets are issued to authenticate users. This method requires explicit user credentials and is commonly used in non-Windows environments or when SSO is not configured.
If "Ticketing (DMS)" authorization is chosen, the following fields will be available:
Credential User - represents the application or service account that needs permission to request tickets or access resources in QlikView.
Credential Password - the password associated with the Credential User.
Username - specifies the actual end-user's username when tickets are issued on behalf of a specific user. In some configurations, Credential User could be an admin or service account, while Username represents the individual user gaining access through that account.
Root Folder/File:
1. Folder - a path to the folder where the files are located.
2. File - a path to *.txt file with listed files names.
One of the two options should be selected in the following cases:
1. The file folder located on the QlikView server is not accessible.
2. There is internal mapping for accessing the QlikView server, requiring file names to include the internal path.
Sample File - insert a QlikView file name\path to file. For example: "Deployed Docs\Bex.....Information.qvw".
Filter By - folder/file name template to filter by. Be careful not to include *.qvw in the file name, as this will prevent any tables from returning since their names do not contain *.qvw.
Search sub folders - if you need to search for files within the values defined in the fields "Location" and "Path" (if set).
Test Connection button - validates that the connection works properly and returns the correct number of files.
Assigned Projects - the Data Source must be assigned to relevant Project(s). When assigned, a Data Source will appear in the Data Sources list in the Project's Data Set(s).
Note: additional QlikView log file is usually created under "..\quilliup\webapps\ROOT\WEB-INF\lib\qvw\logs"
Comments
0 comments
Please sign in to leave a comment.