QlikView

QlikView is flexible business intelligence tool to connect to data and create reports. Create a QlikView catalog source to extract metadata from the QlikView source system.

Objects extracted

Metadata Command Center extracts the following objects from a QlikView source system:

•Application

•Button Field

•Column

•Condition

•Connection

•Connection Model

•Connection Schema

•Database Schema

•Document

•Expression

•Field

•File

•File Directory

•Folder

•Group

•Measure

•QVD

•QVD Model

•QVW

•QVW Model

•Source Column

•Source File

•Source Table

•System Field

•System Variable

•Table

•Text Field

•Variable

Prerequisites for configuring the QlikView catalog source

•Install the Secure Agent on a Windows machine to configure a QlikView catalog source. Ensure that you install the QlikView Desktop tool on the same machine where the Secure Agent is running.

•Before you run a QlikView catalog source job, close all QlikView instances and check the Task Manager on the Windows machine to confirm that there are no QlikView processes running. The QlikView catalog source job may get stuck if there are any QlikView processes running on the same machine where the Secure Agent is running.

•The user that starts the Secure Agent must have the licensed edition of QlikView Desktop. The catalog source job does not extract any metadata from the QlikView source system if you are using the QlikView Desktop Personal Edition. If you don't have a QlikView Desktop license, you must lease a license from QlikView Server to the Qlik Client. For information about leasing the QlikView Desktop License, see Knowledge Base article 000196172.

Connection properties

On the Registration page in Metadata Command Center, enter the path to the directory from which you want to import the QlikView documents. This directory should be present in the same machine where the Secure Agent is running.

Configuration parameters for metadata extraction

Expand the Catalog Source Configuration Options in the Metadata Extraction tab on the Configuration page. Configure the following additional parameters to extract metadata from a QlikView source system:

Property	Description
Miscellaneous Options	You can specify the following additional options to pass at runtime: -database.type ORACLE -log.notavailable -file.path [qlik server file path]=[agent file path] -m 4G -customXMILocation [path to xmi files] - -database.type. Specify the default database connection without any connection name. For example, enter -database.type ORACLE If specifying multiple database connections, enter each database type using the associated connection name. For example, enter -database.type MyConnectionName=ORACLE - -log.notavailable. Specify this option if you are extracting metadata from a source system that contains dynamic metadata such as subroutines, loops, and variable definitions. The Qlik log files are required because the dynamic metadata cannot be directly extracted from the Qlik scripts. In such cases, some critical metadata for lineage are missing. This option lets you extract metadata even if the log folder path is not available. - -file.path. Use this option to replace a portion of the original file path with a new one by specifying multiple file.path options. For example, enter -file.path [qlik server file path]=[agent file path] - -m. This option lets you specify the memory size required to run the metadata extraction job. For example, enter -m 4G - -customXMILocation. Specify this option if you want to load the XMI files that are generated when you run a metadata extraction job. Specify the location where the XMI files are stored. For example: -customXMILocation E:\Dev\apps\Metadata_Foundation_Agent\workspaces\QlikView

Property

Description

Miscellaneous Options

You can specify the following additional options to pass at runtime:

-database.type ORACLE -log.notavailable -file.path [qlik server file path]=[agent file path] -m 4G -customXMILocation [path to xmi files]

- -database.type. Specify the default database connection without any connection name. For example, enter -database.type ORACLE

If specifying multiple database connections, enter each database type using the associated connection name. For example, enter -database.type MyConnectionName=ORACLE

- -log.notavailable. Specify this option if you are extracting metadata from a source system that contains dynamic metadata such as subroutines, loops, and variable definitions. The Qlik log files are required because the dynamic metadata cannot be directly extracted from the Qlik scripts. In such cases, some critical metadata for lineage are missing.

This option lets you extract metadata even if the log folder path is not available.

- -file.path. Use this option to replace a portion of the original file path with a new one by specifying multiple file.path options. For example, enter -file.path [qlik server file path]=[agent file path]
- -m. This option lets you specify the memory size required to run the metadata extraction job. For example, enter -m 4G
- -customXMILocation. Specify this option if you want to load the XMI files that are generated when you run a metadata extraction job. Specify the location where the XMI files are stored. For example:

-customXMILocation E:\Dev\apps\Metadata_Foundation_Agent\workspaces\QlikView

Referenced source systems

If the source system references another source system, create a connection assignment in Metadata Command Center to view data lineage with endpoints. To create a connection assignment, create a connection based on the referenced source system, and then assign the connection to the catalog source.

Note: You can view the lineage with reference objects without creating a connection assignment. After connection assignment, you can view the actual objects.

You can assign the following source systems as endpoint catalog sources:

Source system	Object class type
Microsoft SQL Server	Database
Oracle	Database