Establish Connectivity to QlikView
This article describes the process of creating plug-in Data Source to connect to QlikView. This Data Source will allow data from existing QlikView objects to be used in building elements using Metric Insights tools.
Your Metric Insights instance must be configured to support QlikView. This requires you to Configure a Remote Data Processor on your QlikView server or another Windows machine that has network access to your QlikView server. You will also need to install JRE (Java Runtime Engine) and .NET on the machine that runs the Remote Data Processor.
With the release of Version 6.2.1, .conf files are no longer required for advanced configuration in Metric Insights. It is recommended to use the Plugin Config page to adjust parameters and their values. See this article for more details.
1. Create New Data Source
Access Admin > Collection & Storage > Data Sources
- [+New Data Source]
- Сhoose "QlikView" from the Other drop-down
- [Next step]
2. Provide Required QlikView Parameters
- Input a descriptive phrase in Data Source Name
- Enter Server address
- If Remote Data Processor runs on the QlikView server, then enter 'localhost'.
- If it runs on a different machine, enter the QlikView server name (e.g. server=qlikview.metricinsights.com).
- Leave blank if pulling .qvw documents via the file system
- Specify the URL to use for creating UI links back to your QlikView server
- Provide Username and Plugin Password.
- Note that your Username must be in the same format that your QlikView server uses for Authentication. For example, if Active Directory then you typically include the Domain like: <Domain>\<Username> (e.g., corp\edun)
3. Configure Optional QlikView Parameters
You can edit any values in the Plugin Connection Profile Parameters grid by clicking the gear icon in the corresponding row:
|1||Category Filter||Specify the names of QlikView categories (comma-separated) to pull data from these categories only (e.g., Financial, Social). Wild card (*) is allowed. (e.g., Fin*, S*).|
|2||Objects in Containers||Specify the types of QlikView objects to pull data from Containers (e.g., graph, table, text)|
|3||Objects in Sheets||Specify the types of QlikView objects to pull data from Sheets (e.g., graph, table, text)|
|4||Object types to collect||Specify the types of QlikView objects to be collected (APPLICATION, SHEET, OBJECT)|
|5||Path to Server Folder||Specify the path to the server folder to pull .qvw documents from. Leave blank if pulling data from a QlikView server.
|6||QVW File Filter List||Used to narrow the list of QlikView documents (comma-separated) before loading of QVW files. Wild card (*) is allowed. (e.g., Social Media*, demo*)|
|7||URI Scheme||Enter URI Scheme to access the QlikView Server (either http or https)|
4. Advanced Configuration
Generate Object List defaults to "automatically" and requires you to to choose Object List Refresh Trigger from the drop-down below.
- "manually": Reports may be added one-by-one or via CSV file
- Select a New Remote Processor. See more on Configuring Remote Data Collector/Processor
Click [Test connection] in the upper right corner of the screen
When setting up connectivity to QlikView you can use the Test Connection button to verify that your Plug-in parameters are correct.
The following is a list of errors with possible actions
1. Error: There is currently NO data collector configured to service this remote data fetch request.
Action: Add a remote data collector in the Remote Collector section.
2. Error: Fail to get ticket from 'server'
Action: Add the user to the QlikView Administrators group on the QlikView server machine. This is required by QlikView in order to use the QlikView server Ticket API. More information about the QlikView server Ticket API can be found here. Note: you can work around this by configuring Metric Insights to access the .QVW files via the file system instead of via the QlikView server Ticket API. See the section on setting the server parameter. Also note that one of the requirements for QlikView is that QlikView authorization uses DMS and not NTFS: "QlikView needs to be running in DMS mode for security"
3. Error: The underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure channel.
Action: For https (ssl) connection to your QlikView server, make sure that the 'server' parameter contains the correct host name that matches the server certificate of QlikView. One way to test is to point your web browser to the 'server' parameter and verify that you do not see an error that indicates that the Server's certificate does not match the URL. This error could result from using IP address instead of host name, or vice versa.
4. Error: The remote server returned an error: (401) Unauthorized.
Action: Verify username and password are correct.
In addition, if SSL connection to QlikView server, then make sure plugin parameter 'URI Scheme' is 'https'.
Also, if you installed the remote data collector on the QlikView server, then make sure that the 'server' parameter is 'localhost' and not the name of the server (such as 'qlik.metricinsights.com)
5. Error: The remote name could not be resolved: 'server'
Action: Make sure you have network connectivity from the machine that runs the Metric Insights data collector and your QlikView server.
5.1. Set User Credentials when Pulling .QVW File Data via File System
When pulling QVW data from the file system instead of going through QlikView server, you will need to pay attention to what User is configured to run the Windows Service for the QlikView plugin.
This is not common.
NOTE: If you specified the 'server' parameter with the QlikView server name, then you can skip this step.
If you left the 'server' parameter blank, so that you will pull .QVW document data via the file system, then you will want to complete this step.
User credentials are specified in the the Remote Data Collector. This user is utilized for accessing the .QVW documents on the file system.
On the machine where the Remote Data Collector is installed, open the 'Metric Insights Daemon' Windows Service
1. Set the User in Log On menu. The default user is the local system account. You can enter a different user here. You will then need to restart the Windows Service for it to take effect.