requires the tool to be installed to access its SDK.
requires Internet access to https://repo.maven.apache.org/maven2/ and/or other tool sites to download drivers into <TDC_HOME>/data/download/MIMB/. For more information on how to retrieve third-party drivers when the TDC server cannot access the Internet, see this article.
|Tool Web Site||http://www.qlik.com/us/products/qlik-sense|
|Supported Methodology||[Business Intelligence] Multi-Model, BI Report (Relational Source, Expression Parsing, Report Structure) via WebSocket API on QVF or QVD File|
|Remote Repository Browsing for Model Selection|
Import tool: QlikTech QlikSense 3.2 (http://www.qlik.com/us/products/qlik-sense)
Import interface: [Business Intelligence] Multi-Model, BI Report (Relational Source, Expression Parsing, Report Structure) via WebSocket API on QVF or QVD File from QlikSense Server
Import bridge: 'QlikSenseServer' 10.1.0
This bridge requires internet access to https://repo.maven.apache.org/maven2/ (and exceptionally a few other tool sites)
in order to download the necessary third party software libraries into $HOME/data/download/MIMB/
(such directory can be copied from another MIMB server with internet access).
By running this bridge, you hereby acknowledge responsibility for the license terms and any potential security vulnerabilities from these downloaded third party software libraries.
This bridge imports reporting metadata (QVF applications) from the Qlik Sense server using the Qlik Engine API (JSON over WebSocket).
FREQUENTLY ASKED QUESTIONS
Q: When do I need to generate execution log files?
A: Reports use data load scripts. The execution log files contain information that help the bridge understand the scripts' expressions. Whenever the script contains variables, loops, or dynamic script statements, execution log files may be useful.
Q: How do I provide information to help the support team reproduce an issue?
A: Provide an archive of the files involved (QVF, QVD, execution logs, external scripts).
|Engine API URL||URL of the Qlik Engine API.
To use the Qlik Engine API, you need to open a WebSocket to the engine using one of the following URIs:
wss://server.domain.com:4747/app/ or wss://server.domain.com[/virtual proxy]/app/
|User||To authenticate with Qlik Sense server you have to specify user name.
You can see user name on page Users of Qlik Management Console (https://server.domain.com/qmc).
|User directory||To authenticate with Qlik Sense server you have to specify user directory.
You can see user directory on page Users of Qlik Management Console (https://server.domain.com/qmc).
|Certificate||Path to the client certificate file (e.g. client.pfx). The client certificate is required for authenticating with the Qlik Sense server.
You can export it using the Qlik Management Console (https://server.domain.com/qmc)
To export the certificate please follow these steps:
1. Select Certificates on the QMC start page or from the menu.
The Export page for Certificates is displayed.
2. In the Machine name box, type the full computer name of the computer that you are creating the certificates for: MYMACHINE.mydomain.com or the IP address.
3. Using a password is optional.
4. Export file format for certificates has to be 'Windows format'.
5. Click Export certificates in the action bar.
The export of certificates is initiated and Exporting certificates is displayed.
When the export is finished, the dialog Certificates exported is displayed.
Certificates will be exported to this disk location displays the target directory where
one folder for each computer is added. In every folder the following certificates are created:
client.pfx, root.cer, server.pfx. If the export fails, the dialog displays Certificates export could not complete.
|Certificate Password||Password for client certificate.||PASSWORD|
|Applications||Specify applications ids you want ot import.
Left empty if you want to import all applications
|Log Folder||Path to Qlik Sense script log folder.
The script log files contain information that help the bridge understand the script expressions.
Whenever the script contains variables, loops, or dynamic script statements, execution log files may be useful.
This folder is located on Qlik Sense Server in Archive logs folder
and specified during installation of Qlik Sense Enterprise and has to be network folder.
For example \\server\share\ArchivedLogs\computerName\Script.
If you believe the script execution logs are not required, you may specify 'RequireLog=no' in the Miscellaneous parameter.
|Incremental import||Specifies whether to import only the changes made in the source or to re-import everything (as specified in other parameters).
True - import only the changes made in the source.
False - import everything (as specified in other parameters).
An internal cache is maintained for each metadata source, which contains previously imported models. If this is the first import or if the internal cache has been deleted or corrupted, the bridge will behave as if this parameter is set to 'False'.
|Miscellaneous||Specify the following miscellaneous options using a comma separated string:
- ODBC connection database type
- Replace DIRECTORY statement
- Require script log
ODBC connection database type
When Qlik Sense connects to a database using ODBC the database type is unknown. It is necessary to understand lineage through database specific SQL syntax.
Specify default database type using DatabaseType string (e.g. 'DatabaseType=Oracle'). When the Qlik Sense application connects to different database types, you may specify each type using the associated connection name (e.g. for 'ODBC CONNECT TO ConnectionName' use 'DatabaseType:ConnectionName=Oracle'). It is possible to mix the default database type with connection database types (e.g. 'DatabaseType=Oracle, DatabaseType:ConnectionName= TERADATA').
Here is a list of major supported database type:
A Qlik Sense DIRECTORY statement is used to set the Directory path for subsequent LOAD statements. When this directory is inaccessible use a DIRECTORY statement to redirect it to another directory.
To do so, copy the DIRECTORY statement from a script log file, add '=' and specify the path to another directory.
In this case, folder 'c:\folder' is redirected to 'd:\folder2' folder.
When the path after the DIRECTORY statement is empty, all DIRECTORY statements are redirected to the specified directory.
The script execution logs are employed to understand what tables applications use and to determine the lineage to their sources (e.g. QVD or database). When the log is not available an error message is logged. If the script execution log is not required, one may specify 'RequireLog=no'.
Note: when a log file is missing, its original script is used. In this case, some or all metadata details could be lost as scripts are dynamic because of loops, subroutines, variable definitions.
For example, the following will set the default database type to Oracle, asks to not require logs and redirects all DIRECTORY statements:
'DatabaseType=Oracle, RequireLog=no, DIRECTORY =[d:\folder2]'
Qlik Sense's Include, Store, Load statements operate with file path. When the original file path is not accessible by the bridge it logs errors, like:
'Unable to open Include file: '\\inaccessible\scripts\include.txt''
'Could not process the dependency because the source document '\\inaccessible\QVDs\file.qvd' is not accessible'
You can resolve the errors by copying inaccessible files to accessible paths.
For example, when necessary files are located in \\inaccessible\folder you can copy them to c:\accessible\folder and instruct the bridge to read them from the new location with:
The FILEPATH option allows you to replace a portion of the original file path with a new one.
You can specify multiple FILEPATH options, like:
FILEPATH [\\inaccessible]=[c:\accessible], FILEPATH [\\inaccessible2]=[c:\accessible2]
The bridge applies multiple FILEPATH options in order provided.
WRONG - FILEPATH [\\a]=[c:\a], FILEPATH [\\aa]=[c:\aa]
RIGHT - FILEPATH [\\aa]=[c:\aa], FILEPATH [\\a]=[c:\a]
Be sure not to specify the FILEPATH be outside of the Directory path where you have the Qlik Sense documents you would like to import.
Mapping information is not available