is only supported on Microsoft Windows.
requires the tool to be installed to access its SDK.
|Tool Version||11.2 to 12.x|
|Tool Web Site||http://www.qlik.com/us/products/qlikview|
|Supported Methodology||[Business Intelligence] Multi-Model, BI Report (Relational Source, Expression Parsing, Report Structure) via COM API on QVW or QVD File|
|Remote Repository Browsing for Model Selection|
Import tool: QlikTech QlikView 11.2 to 12.x (http://www.qlik.com/us/products/qlikview)
Import interface: [Business Intelligence] Multi-Model, BI Report (Relational Source, Expression Parsing, Report Structure) via COM API on QVW or QVD File from QlikView
Import bridge: 'QlikViewFiles' 10.1.0
This bridge imports reporting metadata from QlikView documents.
The bridge requires the QlikView software and its COM/OLE API to be installed on the machine that is executing this bridge.
This bridge imports metadata from the following files:
- QVW documents
- QVD files
- execution log files associated to each QVW documents
- external script files referenced by QVW documents
Please ensure that the needed files above are available, and consult the Miscellaneous parameter documentation for additional information.
As connectivity to the API is through COM based automation, please be sure to close all QlikView instances and check the Task Manager to confirm there are no QlikView processes running, as these may interfere with the startup of a new process.
FREQUENTLY ASKED QUESTIONS
Q: What do I do if the bridge appears to stop processing for a long time with no log messages after 'Connected to QlikView version xx.xx.xxxxx.x'? A: Pop-up dialog issue: As connectivity to the API is through COM based automation, the import may be blocked because a dialog message may have been issued by QlikView and it is awaiting a response. In order to address this issue, you must look for windows in the background that would be the dialog requiring user attention. In some cases, e.g., if the bridge is executed as a service rather than directly as an application, in order to ensure that you see this message, you will need to re-run the bridge as a full application rather than a service.
Q: How to create the execution log files used by the bridge?
A: The execution log files are generated by QlikView when a QVW document script is executed. Enable generation of the log files in QlikView menu Settings / Document Properties / General / Generate Logfile. Then, execute the QVW document script.
Q: When do I need to generate execution log files?
A: The execution 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.
Q: How do I provide information to help the support team reproduce an issue?
A: Provide an archive of the files involved (QVW, QVD, execution logs, external scripts). If you wish to remove confidential data from these files, please request a script to do so.
|Directory||Directory path where to import QlikView documents from. Its subdirectories should contain all documents, log files and external script files involved in the QlikView project.
Ideally, the parameter should point to the production location of the project. When it is not possible to access the production location directly, you can copy the production directory to a different location and point the parameter to it. In this case, when the project uses QlikView DIRECTORY statements you need to redirect the statements to the new location. Consult the Miscellaneous parameter documentation for additional information.
|User ID||User ID specified in Section Access. This User ID has to have access to all documents in the Directory. Otherwise bridge will hang because of Qlikview pop-up window which will wait for correct User ID.||STRING|
|Password||Password specified in Section Access for the User ID.||PASSWORD|
|Miscellaneous||Specify the following miscellaneous options using a comma separated string:
- ODBC connection database type
- Replace DIRECTORY statement
- Require QVW execution log
ODBC connection database type
When QlikView 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 QlikView 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 QlikView 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 QVW file log, 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.
QVW execution log
The QVW script execution logs are employed to understand what tables QVW files 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 QVW 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]'
QlikView'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 QlikView documents you would like to import.
|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'.
|Meta Integration Repository (MIR)
(based on the OMG CWM standard)
|LastModificationTime||Last Modification Time|
|StoreContent||QVW, Connection, QVD|
|LastModificationTime||Last Modification Time|