Replacing the 16 digits license key and control number.
JSON Web token.
Secure communication, https://
To apply a Signed License Key, a secure network connection is required to be established: A signed license key requires connectivity to license.qlikcloud.com. It can establish in any of the security scenarios below:
The Signed License Key will be delivered to you via email, in the same email that you normally receive the standard license key 16 digits and control number.
I. Please note that after changing to a license with a signed key, you cannot return to using the old LEF based license model. If you want to go back to the old LEF based license model a new installation will be required.
II. If the SLK is already in use in another Qlik Sense or QlikView environment including SaaS, and Analyzer allocations are in place for users that exist in the new environment, the users may be assigned a Professional license automatically regardless, leading to the user having both Professional and Analyzer allocations. This new Professional allocation will then synchronize to the pre-existing environments. If the user has no allocation in any existing environment(s), the user with an assign legacy Token will automatically be assigned a Professional license, which synchronizes to pre-existing environments.
1. Launch the QMC 2. Go to License Management
3. As a default, you will be prompted to apply the Signed License Key. Paste the code into the designated area.
4. Click on Apply
5. If the license is successfully applied in the QMC, the Hyperlink (Use serial number and control number) to go back to license through the old model will disappear and on the left hand side will only say Signed license key.
Note: System must have access to the external network to authenticate the license with the Qlik Sense License database.
A user opens the QlikView Desktop and attempts to lease a license from the QlikView Server. However, after successfully connecting and authenticating ...
A user opens the QlikView Desktop and attempts to lease a license from the QlikView Server. However, after successfully connecting and authenticating and even opening a QlikView document, the Desktop client remains unlicensed (Personal Edition).
Relevant log file:
The relevant log file to review on the QlikView server to verify if the user has arrived and has attempted to lease a license is the QlikView Server Event log. Note that it will only log the relevant lines when set to High logging level.
Notice License: License leased to user DOMAIN\ADMINISTRATOR Information CAL allocation: No CAL assigned to user "DOMAIN\QVSERVICE" - lease license denied.
The common reason for QlikView license lease failing:
License lease has not been properly enabled in QlikView Management Console.
License lease only allows a borrowed CAL to be used twice in a 24 hour / 7 day period, depending on the version.
This can cause problems if the user connects to many different servers in a Citrix "Farm" during this time. A single user can lease up to two licenses to two separate workstations within a 24 hour / 7 day period. An attempt to lease the third license in a 24 hour / 7 day period will be revoked if the same User ID is used. Additionally, the existing license lease of the third machine, should there be one previously existing, will be revoked in the case where the same User ID has leased a license from two other workstations in the previous 24 hour / 7 day period. The third machine will, however, be able to lease a license after 24 hours / 7 days have passed.
Quarantine Period For Named User And Document CALs In QlikView Has Changed:
The quarantine time for Named User and Document CALs will be set to 7 days by the following deliveries; QlikView 11.20 SR16 QlikView 12.00 SR6 QlikView 12.10 IR and later
Clients using multiple or roaming profiles.
The Lease info is stored locally in the profile, so if they no longer have access to it they will lose the lease. Look for root cause details in the LeasedLicense section of C:\Users\\AppData\Roaming\QlikTech\QlikView\Settings.ini. The LeasedLicenseCheck value shows more details on why the license lease has failed.
You can also open via QlikView Desktop Client > Help> Document Support Information and search for the parameters above, as below:
License Lease is not allowed if the QlikView Server license has a document restriction, meaning license only allows for a certain number of documents.
This is specified as a NUMBER_OF_DOCUMENTS tag in the license LEF file.
Deleting of the folder ConnectionsMRU und LeasedLicenseMRU in the Registry
Verify that the following registry key is present: Registry > HKEY_CURRENT_USER > Software > QlikTech > QlikView
(More common on a Windows Server) The user is logged into a temporary profile.
This will allow the license to lease initially, but the lease will be removed once the temporary profile is cleared out. You can check for this after the user logs in by going to C:\Users and looking for the login name. If it's not there, and there is a Temp folder, check there. One fix would be to disable temp profiles.
Port 4747 is not open on the computer attempting to lease the license from the QlikView Server and communication using QVP protocol isn't possible.
This typically the case when error "Connected to server OK, Negotiations Timed Out Switching to HTTP tunneling" is returned.
After applied unified license on Qlik Sense Enterprise and Qlik Sense SaaS, there are new users synchronized in Qlik Sense Enterprise. Those new user...
After applied unified license on Qlik Sense Enterprise and Qlik Sense SaaS, there are new users synchronized in Qlik Sense Enterprise. Those new users are having encrypted user name and "UNKNOWN" for the user directory. What are these users?
With unified license, all servers will synchronize the users from Qlik backend license server every 10 minutes. Once applied unified license on Qlik Sense Enterprise and SaaS, the new users created on either environment will be automatically synchronized to other servers. You can find more details about unified license from Qlik Licensing Service Reference Guide.
If the IDP on SaaS are different from the user directory on Qlik Sense Enterprise, the synchronized user from SaaS to Qlik Sense Enterprise will be having "UNKNOWN" directory for the new users. In this case, these new user can be removed. But the solution is to create an IDP on SaaS. This IDP will be appear as directory with correct user name for those synchronized users on Qlik Sense Enterprise.
Please note, if the same domain/user will consume one license. So if the same user has user account in multiple IDPs, then the user will consume multiple licenses.
Using a Signed License Key with its Signed License Definition in a long term offline environment past the 90 days provided by Delayed Sync requires (b...
Using a Signed License Key with its Signed License Definition in a long term offline environment past the 90 days provided by Delayed Sync requires (besides license modification) additional configuration steps!
No license has long term offline capability enabled by default.
Long term offline capability needs to be specifically approved by Qlik and the conditions of offline use agreed to by the customer. See Request license off-line approval - April 2020 and onwards. Once approval has been obtained through the CSO, the license will be modified with an additional attribute OFFLINE;YES;;
Additional configuration changes are necessary for long term offline mode to function
(Delayed Sync requires a Signed License Definition, but does not require additional configuration steps)
Configuration changes needed:
These changes will need to be done on all nodes running the Service Dispatcher. Not only the Central node.
Stop the ServiceDispatcher service
As Administrator, open the Service Dispatcher services.conffile located by default in C:\Program Files\Qlik\Sense\ServiceDispatcher
Locate [Licenses.parameters]and add the parameter -offline
Analyzer Capacity license was introduced in Qlik Sense February 2019, that allows having a pool of user consuming apps by a unit of time (a unit is 6...
Analyzer Capacity license was introduced in Qlik Sense February 2019, that allows having a pool of user consuming apps by a unit of time (a unit is 6 minutes) without the need of having a license assigned to a user (named user)
When a user from the pool, logs in the hub, he will consume 1 unit after 6 minutes another unit will start being consumed and so on. If the user stays in for 15 minutes, 3 units will be consumed (18 minutes) as a unit started is a unit consumed. No consumption is registered if the user is logged in but idle (not opening apps, sheets,...). If he is at the same time active on, for example, Qlik Sense Enterprise for Windows, that also generates consumption of units.
When all analyzer units have been consumed, no users from the pool can access Qlik Sense, until the monthly reset occurs. To avoid lockout, coverage can be added to the subscription. Coverage is a function that allows to buy minutes packages automatically when consumed, it can either be unlimited or with a defined ceiling. For more information on this see the license metrics for Qlik Sense
Important: An access to the Internet is required to use this type of license. You must have a license key (a new type of licence) to replace the serial number (old license), see article: Licencing Qlik Sense for Analyzer Capacity
If a customer is experiencing an issue with them no longer able to receive any type of Qlik Alerting e-mails (Broadcast, Data, or System) after the a...
If a customer is experiencing an issue with them no longer able to receive any type of Qlik Alerting e-mails (Broadcast, Data, or System) after the alerts are showing as triggered within the Qlik Alerting console.
Qlik Alerting (Any version)
C:\Program Files\Qlik Alerting\Worker\Daemonand investigate the log file qlikalertingworker.out.log and/or the C:\ProgramData\QlikAlerting\worker.log for the below errors:
Note: Qlik Alerting license expiration date is found in the QlikSense LEF file.
Qlik Alerting License has expired. Have the customer's Qlik Account manager reach out to customer to get an updated license.
An expired PRODUCTLEVEL tag in the LEF (License Enabler File), such as 2011-01-01, indicates the Maintenance agreement has expired and needs to be ren...
An expired PRODUCTLEVEL tag in the LEF (License Enabler File), such as 2011-01-01, indicates the Maintenance agreement has expired and needs to be renewed to continue support and be eligible for major release upgrades.
Please note that the expired license can be applied to a version of the product that was released before the expiry date.
The license cannot be applied to versions of the product released after the expiry date of the PRODUCTLEVEL.
Without a current/paid maintenance agreement, no further Technical Support can be provided
The license cannot be applied to versions of the product released after the expiry date
After purchasing Qlik Sense Business digitally with a specific amount of seats, those seats cannot be lowered after or during the trial period.
After purchasing Qlik Sense Business digitally with a specific amount of seats, those seats cannot be lowered after or during the trial period.
Roles were assigned to users.
You cannot reduce seats below the number of users that have been assigned a role in the product. The tenant admin must therefore remove users from the management console, wait 2 minutes, then try to reduce seats again.
Q: When getting permission for our Sharepoint tenant site - you mention you allready got it approved. Was this done inside of Sharepoint itself or your Office 365 Azure AD portal ?, it seems other connector seem to suggest needing to do this to approve and allow third party apps to send requests. Is this correct?
A: There is nothing to be done from the Azure portal. If it's the first time using the connector, it's mandatory to use the Azure tenant admin when authenticating. This will prompt and authorization approval for Qlik's sharepoint app (the reason why appears as a third party app it's because is not developed by microsoft).
Q: What is the purpose of the "Access Token"?
A: The access token will grant access to connector
Q: Is there a connector to Azure?
A: Yes, both in SaaS and on-premise (december 2020)
Q: When you say 'Azure Tenant,' is that the same as Auzre AD admin portal to approve the app?
Q: We are using a proxy to connect to outside enterprise connections (Sharepoint Online).But it's possible to activate proxy only for some connections types ?
Hello everyone and welcome to the March edition of Support Techspert Thursdays. I’m Troy Raney and I’ll be your host for today's session. Today's presentation is Best Practices for Using Qlik Web Connectors with Francisco Fernandez. Francisco, why don't you tell us a little bit about yourself?
Hello, my name is Francisco and I’m a Technical Support Engineer here at Qlik. I’ve been working at Qlik since 2019 and my main focus are Qlik Web Connectors and Qlik Sense integrations, such as APIs and mashups.
Okay, and what are we going to be going through today?
We are going to go through installation tips; how to use SharePoint Connector; difference between SaaS and on-premise connectors; and a little bit of troubleshooting.
Okay, and for those of us who are kind of new to Qlik Web Connectors, what are Qlik Web Connectors and how do they work?
The Qlik Web Connectors package is a lightweight web service that helps you fetch data from many web-based data sources, and also social media. It contains 42 different connectors with tons of functionalities. Also, it can be used in a separate server, so it's a completely isolated package that doesn't depend on Qlik Sense or QlikView; and that's the main reason it can be used with both.
So Qlik Web Connectors works with both Qlik Sense and QlikView?
Yes. Here in the example architecture. You can see that the Qlik Web Connectors is being run in a different server. That's why it doesn't have a dependency.
Okay, that's cool. Now why should someone start using these connectors? How are they useful?
So, first of all, because it's free of charge with a Qlik Sense license.
That’s always nice.
It's free. It's simple to install and configure. Auto-generate the scripts. It can be used as a Windows service or run as an application. As I previously mentioned, it can be used both with Qlik Sense and QlikView.
Okay, I think the initial question for a lot of people is: how to install it and how to get started?
Yep, you can download the Web Connector from our Support page. As a demo, I already downloaded the package. This is what you get from the download page. I already uncompressed it, so we are ready to go.
Okay, and what version of Web Connectors is this? Is this the latest version?
Yeah, this is the latest version. This is December 2020.
Francisco, what are we looking at here?
We are looking at the connector. It's basically a library of DLLs, as you can see here. Each DLL is a connector. And we also have some folders that contains the connector configuration. Scroll down. We can see the deploy.config file, which contains all the connector configuration. Scroll further, we can see here: application executable and the application service executable.
Yeah, you mentioned there's two different ways of running connectors: one as a service or as an executable application.
Yeah, if we want to use it as an application; we only need to double Qlik this window will pop up and we are ready to go. The connector is already working.
If we want to run it as a service, we have to go here to batch files. And we have two batch files here. The first one contains the installer service, and the second one contains the uninstall service.
Can I ask you, what are the advantages of running it as a service versus just clicking on the application?
Running the Web Connectors as a service is especially useful for server admins. It allows them to automate tasks, such as restart all the services at once using a script.
Okay, can you show us the details of running the service installer?
Yeah, if we open it using the Notepad++, we can see here that it contains a path. This path should be where our Web Connector is located. In our case, it is in the desktop. So, we should change the path here. Save it and install after that. And it will be available in the services tab. If we want to start using the connector, we have to check the configuration in the deploy.config file. Notepad++ and edit it. Here we have an XML configuration file which contains lots of tags, as you can see.
Yes, these are kind of difficult to read with the human eye sometimes if you're not used to editing XML files. What settings here are important that we should take a look at?
First of all, the port where we want to run the connector. This is by default: 5555. You can change it to whatever port you want to use. Secondly, one of the most important tags is: the Allow Remote Access, which basically allows access to the Web Connector from remote machines.
Okay, so if like I have Qlik Sense running on a totally different machine, this is the major setting that allows that connection?
Yeah. Otherwise, you will see an error message saying that you have to enable it.
We have to change it to True. After that, we should look at the File System Allow Path. This tag is quite important, especially for those connectors who download files, because the connector needs access to the file system. You can either allow full access to any path by using the wildcard (*) or you can specify which paths you want to use for the downloads. You have to use the semi-colon (;) to enumerate more than one path.
I see that's a little confusing having the examples right above the setting which is initially by default: blank.
Yeah, usually people tend to mistake this with actual configuration parameters, but the parameter starts after the arrow (->). This is basically not being used by the connector.
Lastly, we have Default Allow IP Addresses. This is also very important if you are using the Web Connector in a multi-node environment because it will allow all the nodes access to the Web Connector. You have two options: use any to allow all the nodes including the new ones if you want to add more nodes. Or you have the other option is to specify the IP Addresses of those nodes. Usually, I tend to prefer to use any. We have some other advanced features.
Yeah, so I see a lot of settings there about security and SSL. And if someone wanted to take advantage of all those security settings, would they go to the Help page to find all that information?
Yeah, they can find it in the Help page in the section called Advanced Qlik Web Connectors Configuration.
How do we access the console here? Could you show us that again?
Now, we are going to run the Web Connector as an application for demonstration purposes. The land page is this one. In case that you are running it as a service, it's the same page. This is the main page. Here you can find all the connectors available.
That's a long list. Would you mind walking us through the steps to set up a connection?
Yeah, we can start by using SharePoint which is here. First of all, what we have to do is authenticate to our SharePoint site using the Can Authenticate table and pressing Parameters.
We can see that we have here the base URL. In this case, we are using Qlik’s SharePoint site. In your case, you will have to use your company SharePoint site. We also have Prompt and Consent level. If you were already using the SharePoint connector, you will have to use None. But if this is the first time that you're using the connector, you should use Consent and using an Azure tenant admin, consent the application. Since we are already allowed access to the application, we are going to use None and continue with the authentication process, which generates this authentication code. Copy to clipboard. Go back to Authentication Code here and paste it and then save. We can run to see if we are authenticated. The Web Connector is allowed to retrieve data.
Okay so we've authenticated ourselves from the connector to our company SharePoint site?
Okay, what's next?
Now we can start by trying to retrieve a list. I already set up a list for the demonstration. It's in here.
Okay, so this is our SharePoint site, and you've got a list there I see?
Yeah. Here in the URL, we can see that we have all this. So, the first part is the site Sub Path.
So here is our site and site Sub Path. So, it usually is always Sites followed by the name of the group that we want to use. After that, we usually find what's the table that we need to use. In our case, since we want to retrieve a list as you can see, we should use the table ‘List.’ But if we want to retrieve document let's say, you we will have to go to the Documents as you can see here. I already put the Site and the Subsite path. And using list. We can run the table, and we can see all the lists that are available.
Okay so, this is a preview of everything it reads from that Subsite?
Yeah, it's reading metadata. So, it's not only reading our list, but everything that gets pulled by the connector.
We already know the name of the list that we want to retrieve. And this is the identifier that we have to use.
Okay, do you need to copy that?
Yeah, we are going to copy this. If you want to retrieve data from a list, it's very important to use one of these tables, because lists are not files; are actually metadata. If you want to use the Get File table, it will fail. So, for example, as you can see: everything is correctly set up and we are going to paste. Bear in mind that this might contain spaces, so you have to delete them, and run the table. And as you can see, we have a Not Found. This might be also a 403 - Not Authorized.
That didn't work because the command was Get File, but you actually pasted the ID of a List, so it doesn't match?
Instead, we are going to use the correct table, which is: List Items from ID. So, the Connector stores what was your last search, so basically that's why we didn't have to paste it again. If we run the table again, we can see that we are able to retrieve the list.
Okay, so it previews the actual list right there.
And if we go to the list, we can see that the information matches.
Okay, how do we get this data in Qlik Sense?
Here, we can see that we have all the instructions to create a connection in Qlik Sense.
Francisco, would you demonstrate for us creating this connection now that you've prepared everything in Web Connectors?
Just following the instructions, we have to copy the URL, and we have to create a web file connection in Qlik Sense. So, we go to the Data Load Editor. Create New Connection. Scroll down until we see Web File. And we have to paste the URL that we copied, and username.
Any name, right?
Any name and create the connection. Also, here in instructions it's mentioned that you have to create a variable with a connection string that you are using. I already done that before, so everything is correctly set up now.
And we only have to copy the script to the clipboard and paste it and make a reload. As you can see, the reload was successful and we are able to retrieve the list.
Francisco, that all seemed to go very smoothly. Just following the instructions, copying, and pasting from Qlik Connectors to Qlik Sense; what should you do when things go wrong?
I prepared an example actually.
We're going to do the same; but in this case, I purposely made an empty list with no data in it. As you can see here, we are going to make the same procedure as we did before.
We are going to look for Empty List. We are going to copy the ID and follow the same procedure as we did before. Delete this, paste. As we mentioned before, we have some spaces. We have to delete them and run the table. The connector is basically saying that there is no data to pull. So usually when this happens, we have to verify in SharePoint that there is actually data in what we are trying to retrieve. There is no data in here, so the connector cannot achieve anything.
How would it be different, Francisco if you're trying to load a file from SharePoint instead of a list?
So, we have here this folder that contains this file. We have to go to List Files. And since we already know the folder: Save Inputs and run the table. We can see here that we have our Excel file and we just need to copy the unique ID. Go back. We have two options: either the Get File or Download File.
We're going to use Get File. Paste the unique ID. Run the table. As you can see, we are able to generate a string.
In case that we want to use it in Qlik Sense, we just need a new connection using this URL.
Would that be a web file connection?
Yeah, it's a web file connection in this case.
What happens if admins encounter an error while trying to set up that connection?
One of the common problems that we are seeing from Support is that sometimes Qlik Sense is failing to reload the data with a 500 error.
In order to troubleshoot that problem, we usually go to the localhost. In this case, we already are here. Try to open the URL. So, as you can see, we are able to download the data. If we open this, we will see the Excel file and all the data that contains. So just copying this URL and going to the node that is failing, pasting in the browser should be the same result as the in the localhost.
That data file that you downloaded, is that the actual XLS file?
Yeah, it doesn't have an extension because it's ready to be used with Qlik Sense.
Okay, that's a great step to test the access to the data. What troubleshooting steps would you take if it doesn't have access?
What we need to do is: go to the home page. Go to Settings. Double check if the allowed IP addresses matches with the deploy.config file. In here, we have ‘Any,’ and also, we have ‘Any’ here. It's not likely that we are going to face this problem, but in case that you have ‘Any’ here and ‘localhost’ here, you will have to change it and then press Save. If you change any parameter here and press Save, there is no need to restart services.
Okay, but it's very important that the settings in the main page here need to match what's in the deploy.config file?
Yeah. Also, if you're using more than one administrator, all the administrators have to have the same allowed IP addresses.
Okay, so that's a very important setting there.
And where would you find the log files if you needed to investigate further?
Go into the home page. Here in the Log Files tab, you can see all the logs. If we open one, for example this one. We can see that it's an XML file. So, for example, when we tried to retrieve the Empty List, we receive ‘No Rows Return’ error message. We can look for the exact same error here in the logs. We can see the error message.
What’s the difference between Qlik Web Connectors for Qlik Sense on Windows versus Web Connectors for Qlik Sense Enterprise SaaS?
The Qlik Web Connectors is standalone. It’s a package that you have to install in the server. As a kindly reminder: always use the latest version. It contains 42 connectors. On the other hand, the Qlik Web Connectors for SaaS it's integrated in Qlik Sense. It's always using the latest version. It contains 33 connectors. It's still growing. Soon it will be available the SharePoint File Connector, so I’m sure that many customers will be happy knowing this.
Yeah definitely. So just to clarify, that whole installation process, configuration that we saw; that's not really necessary in SaaS because it's already built in?
Yeah. Qlik is taking care of that.
To review, what are some basic troubleshooting steps when things go wrong?
First of all, always double check in if you are using the latest version. Then you can check the logs for any error messages.
And lastly, you can check the API limitations of the connector. You can check that in the About button under the Useful Links page.
Okay, because basically the Web Connectors are using the APIs of each individual web source and like Google or Facebook their APIs; and they may change?
Yeah, that's correct.
Where are some resources where admins can find more information?
They can find more information in the help page, and also in the community articles that Support creates.
And again, where can we find the Web Connector download that we started with?
You can go to Qlik Support download site. Look for Qlik Connectors and under the Qlik Connector site, just go to the latest version available.
Okay, now it's time for Q and A. Please submit your questions through the Q&A panel on the left side of your on24 console. Francisco, which question would you like to address first?
So, first we have: do we need to upgrade to the latest version of Qlik Sense to use them?
No, but we strongly suggest to upgrade to the latest version of Qlik Web Connectors.
Moving on to the second one, are all the connectors free along with the Qlik Sense license? Some of the connectors on our site show as premium.
Ah yeah, if you are using a previous version, let say from March 2020 or maybe May 2019 it will appear that they are still premium, but if you upgrade to December 2020 you will see that all appear as free. Also, it’s not only Qlik Sense. If you have a QlikView license and you use the December 2020 version, you will see that the connectors are also free.
Uh, we’ve had trouble connecting to the SharePoint site. What administrative privileges need to be granted to what user?
Probably this question might be related to the when you first start using the SharePoint connector, you have to use an Azure tenant admin to authenticate to the connector; so an application will be created in the tenant site. This might solve the problem that you’re facing.
And we have another question. Does the account running Qlik Sense need to be an administrator on the SharePoint site?
Uh, no, there is no need.
Uh, are all the 42 connectors free to use including SharePoint 365 connector?
Well, I think I already answered this one, yeah. All of them are free to use.
I see some questions that we already answered regarding the license. If you are still seeing the connector is not free to use, you basically need to upgrade to the latest version of the connector.
Does the version of Sense or QlikView matter?
Uh, no. They are not related. As we mentioned during the presentation, the connector is a separate package. It is isolated.
For example, this one is a good one. In a multi-node setup, do I need to install of each node or only on the central node?
You can install the Web Connector only on one node. There is no need to install the Web Connector on each node. This is not like the ODBC package. And you can even install the Web Connector on a different server, as long as it has connectivity to the – to the Qlik Sense Server.
What is the difference between QS Standard and Legacy mode when obtaining the load script?
This is a change regarding to Qlik Sense actually. It’s not related to the Web Connector. The Legacy Mode has some differences when loading the connection strings. You can go to the QMC, after you go to Engines and you can enable or disable the Legacy mode.
We are using a Proxy to connect to object enterprise connections, uh like SharePoint, but it’s possible to activate the Proxy only for some connection types. Example: ActivateProxy for SharePoint online.
Unfortunately, this is a limitation that the connector has. You can only setup one proxy and you cannot select which connectors are using that proxy.
Uh, can Web Connectors be used with Qlik Sense Desktop?
Yeah, they can used in Qlik Sense Desktop. And you can also try them in your Desktop if you want to.
Uh, how can we fetch multiple files from a folder in a SharePoint site?
So unfortunately, this is a current limitation that the connector has. I strongly suggest creating a feature request in the community to raise awareness within the product management.
I saw there’s a couple questions asking about the difference between the REST connector and Web Connectors. You want to address that?
Yeah. Basically, the REST Connector has the same capabilities as the SharePoint connector for example when retrieving data. But the thing is that using the SharePoint Connector is much easier than using the REST connector because all the authentication part is handled by the – by the SharePoint Connector, so it is much easier to use.
A question just came in. Are Web Connectors free for QlikView users as well?
Yes, as long as you are using the latest version.
Is there a connector to Azure?
Yes, we have once connector to Azure Block Storage.
Okay Francisco, we’ve got time for one last question.
Those web connectors have limitation on large volume of data?
Not specifically, since each connector uses a different API. There might exist API limitations, but not the connector itself.
Well thank you very much Francisco.
You're welcome and thanks for everyone for listening. I hope this has helped many people and good luck with your web connections. Feel free to post any questions you might have in the Qlik community. I’m there quite often, and I have written several of the articles on Web Connectors.
Okay great! Thank you everyone! We hope you enjoyed this session. Thank you to Francisco for presenting. We appreciate getting experts like Francisco to share with us. Here is our legal disclaimer. Thank you once again and have a great rest of your day.
One environment's users are Inactive and Removed Externally in a second environment using Signed License Key (SLK).
When applying an SLK to a second ...
One environment's users are Inactive and Removed Externally in a second environment using Signed License Key (SLK).
When applying an SLK to a second Qlik Sense environment, the users stored in the first Qlik Sense environment repository are synchronized to the second Qlik Sense environment. These users may be marked inactive and removed externally.
If you remove a user from one deployment, it is not removing the user access but removing the user license assignment and it would effectively remove user's license assignment from all deployments activated using the same Signed License Key.
Qlik Sense Enterprise on Windows using Signed License Key (SLK).
This is working as designed. This is a synchronization for license assignments and not access rights, which is a security permission which the administrators can control at each deployment.
Contact the account management team to evaluate license use and to split/provide a new key for multiple environments.
Confirm (per LEF) that the license is displaying the correct amount for the specific attribute.
Confirm that the Signed License Key (SLK) is still applied correctly and no other interruptions are occurring.
Restart the services.
If it is not reflecting the correct amount in the QMC, the best practice is to delete some parts in the SLK, try to apply it (as a faulty SLK), then re-apply the correct SLK again. (Currently, it is not possible to manually "refresh" the SLK in any other way, as it should happen automatically).
Analyzer capacity is a consumption-based license type, which is similar to analyzer user access regarding available features. Note that Analyzer Capacity does not equal Analyzer User access. See the Qlik Sense Online Help for more details on the different license types available. Users can access streams and apps in the hub and consume sheets and apps created by others. Analyzer capacity access allows users to create and publish stories, bookmarks, and snapshots based on data in apps. Creating, editing, or publishing sheets or apps is not possible.
With an analyzer capacity license, you subscribe to analyzer time, a defined amount of minutes per month (calendar date). These minutes are shared between users and can be consumed by anyone who is part of the user group, including anonymous users. Consumption is measured in units of 6 minutes. For each new 6-minute period, a unit is consumed.
Create an Analyzer Capacity License Rule in Qlik Sense Client-Managed:
Open the Qlik Sense Management Console
Go to Licenses Management
Open Analyzer Capacity Rules in the right-hand menu (See fig 1)
Click Create new
Provide details for your rule. In our example, we are enabling users in the group capacity to receive Analyzer Capacity Licenses.
Name: Name of your rule Description: Description of your rule Actions: Allow access
When purchased, our Qlik products are delivered with a 16-digit license key (LEF) and/or the Signed License key (SLK). What key is applied may differ ...
When purchased, our Qlik products are delivered with a 16-digit license key (LEF) and/or the Signed License key (SLK). What key is applied may differ depending on your requirements or the version of the product.
Generally, you’ll have two activation options:
The Signed License key (SLK), available for Qlik Sense Enterprise, QlikView, and ABDI.
And a combination of the 16-digit key, a control number, and the License Enabler File (LEF)
Note: These license activation methods cannot be mixed. A license activated with an SLK cannot also be activated using the key + control number method.
Customers who have been using Qlik the longest are likely familiar with the LEF method already, while the SLK may not be as widely known yet, which is why we frequently get questions around it.
In this blog post, we will cover the differences between the two activation methods, as well as what benefits the Signed License key brings to the table. Details on how to activate them will follow in the second post to this short series.
What is a Signed License Key (SLK)?
The SLK is an encrypted JSON web token used to activate Qlik Sense Enterprise or ABDI. It contains product information, available access types for users, and any applicable product add-ons or limitations.
An SLK should not be used on Qlik Sense Enterprise on Windows with the token model.
You cannotchange from an SLK activated system to a LEF activated system.
The SLK requires online connectivity to our licensing server for both activation and continued operation.
Every license has a LEF. Each 16-digit license number that you get can be translated into a LEF, regardless of the method used to activate the license. The LEF itself contains all the instructions for the Qlik Product, such as license level, numbers of users, access types available for assignment, as well as all the limitations or add-on.
When applying your license using the license number and control number, the LEF will be downloaded to the product during activation. It will be updated with each refresh request.
The first line of the LEF is always your 16-digit license number and it ends with a checksum so that an unauthorized alteration of the content is impossible.
It requires a control number for activation
You can change from a LEF activated system to an SLK activated system (but not the other way around). Always use LEF activation if your license has tokens.
Your signed license key will be sent to you in the license delivery email.
If you did not receive your SLK via email, please contact Customer Support. Please make sure to provide the corresponding 16-digit license key and the Support team will be able to get the SLK for you.
There is no way to get the SLK from the Support Portal at this time.
Benefits of using an SLK
Using the Signed License Key makes more product and deployment options available to you.
Examples of these are:
Multi-site deployments, such as connecting a Qlik Sense Enterprise site with a QlikView Server deployment using Qlik Sense Enterprise license options. This is enabled by accepting a Dual-Use offer for each QlikView deployment that should be enabled for a Unified License scenario.
Multi-geo deployments, such as having Qlik Sense Enterprise sites in different locations using the same list of users.
Qlik Sense Enterprise for Kubernetes and Qlik Cloud Services. Either stand-alone or in a multi-cloud setup.
Consumption-based licenses, such as Qlik Sense Enterprise Analyzer Capacity. This additional user license is possible to use in a single or multi-cloud scenario.
All the above is enabled by the use of the Signed License Key. This is made possible by the local deployment syncing all entitlement data (assigned users access, etc.) with all available deployments sharing the same SLK. The synchronization is done using the Qlik Licensing Services and our license backend hosted in Qlik Cloud.
And this is it for an overview of our available license types and activation methods. We’ll follow this up with part two soon, detailing the move from a LEF activated license to an SLK. Until then, give this post a like if you found it helpful! And please let us know if you have any questions or feedback in the comments.
Qlik Sense Desktop can authenticate against Qlik Sense Enterprise Client-Managed, Qlik Sense Enterprise SaaS and Qlik Sense Business. This is how cus...
Qlik Sense Desktop can authenticate against Qlik Sense Enterprise Client-Managed, Qlik Sense Enterprise SaaS and Qlik Sense Business. This is how customers can continue to use Qlik Sense Desktop, and it provides a very economical option when paired with Qlik Sense Business.
The following requirements need to be met:
A functioning network connection to the Qlik Sense Enterprise Client-Managed Server or Enterprise SaaS/Business tenant.
Use of a Professional license. Analyzer licenses do not support Desktop Authentication For legacy token license: User and Login Passes allow Desktop Authentication
No TEST license. Test licenses disallow the use of authentication links
As a benefit of our Analytics Modernisation Program (AMP), a signed license key is issued as a unified license key. This enables the use of one licens...
As a benefit of our Analytics Modernisation Program (AMP), a signed license key is issued as a unified license key. This enables the use of one license across Qlik Sense Enterprise on Windows and QlikView, granted the license has the required QlikView infrastructure attributes (QV_NODES for QVS, QDS_NODES for Publisher).
This allows for analyzer capacity to be shared across all systems using the same license.
A QlikView server currently shows 18 minutes of consumption in the QlikView Management Console (Fig 1.)
This can be accessed through: System > Licenses > Professional and Analyzer access.
If a user accesses and consumes on a linked Qlik Sense Enterprise Server, the Qlik Sense Enterprise Management Console will show the up to date consumption. See Fig 2. Note the 24 minutes, an increase from the 18 we have seen in QlikView.
This can be accessed in the Qlik Sense Management Console > License Management > License usage summary
The usage on the server will be synchronized and shown on the other linked servers within approximately 10 minutes. See Fig 3 and note the 24 minutes, which matches the value in Qlik Sense.
For localconsumption data, each server will store its own consumption and user information.
For Qlik Sense Enterprise on Windows, the License Monitor app will show capacity consumption.
For the QlikView Server, the capacity consumption is shown and stored in the local session log file, with the CAL consumed being Analyzer Capacity, with a log entry like this:
RLS64 12.50.20200.0 20210412T132942.000+0200 20210412T133617.000+0200 C:/ProgramData/QlikTech/Documents/retail store performance.qvw 20190220T113522.000+0200 Socket closed by client 20210412T133601.000+0200 00:00:16 0.000000 10228 1303493 31 2 QTSEL\ghd 1718e2e6-5b1c-4b9e-87a9-d9200f55e37a Ajax QvWS 12.50.20200.0 browser.msie illa/5.0 (windows nt 10.0 On 4747 fe80::df3:cd38:b86f:50bd 58495Analyzer Capacity6 315dcfab-7448-4f4b-8209-ef34742b1abe
How we can best help you depends on the challenge you’re facing. This video will explain what is covered by Qlik Support, how the severity of a case is defined, and how that affects the service license agreement. At Qlik, we want to help you succeed. How we can best help you depends on the challenge you’re facing.
Qlik Support is an important part of Customer Success.
Our most successful customers are engaged along this entire journey with our customer onboarding, Education and Professional services.
To help clarify the difference between these offerings, Qlik support is here there to help when your Qlik product is not performing as expected; certainly with errors, task failures, or possible bug reports in a break – fix fashion. And we will work with you to investigate performance degradation or latency issues. Professional services are available in a more proactive way to offer best practices, upgrades and performance tuning to help you get the most from your Qlik implementation. Your environment and data is unique, and professional services can work with you to develop a strategy to be the most successful.
Before creating a case with Qlik Support, try to find a quick solution with the search tool on Qlik Community. It searches across our Knowledge base, Qlik Help, and Qlik YouTube channels, and more all from one place. If you can’t find the help you need in Qlik Community, you can raise a support case with us. To help us understand the severity of the issue, here is how case severity is defined: Severity one errors are when the software is inoperable, or your production environment is inaccessible, These will be worked 24 - 7 until service is restored. Severity 2 issues can be a significant performance impact, An issue that is preventing a future launch, Or an error that has a temporary work around, but requires significant manual intervention. Severity 3 issues are when data is delayed, Results are not matching expectations, Reporting defects, Misleading or incomplete documentation, Or general disruptions in production.
Having an appropriate Severity set on the case is important because it directly results in how quickly the case will receive a response and the frequency of communication during the investigation of the case. Especially with high severity cases, the severity is expected to change during the life of an investigation. The initial response time of a Severity once case is directly within 30 minutes of completing the registry of the case. After that, the support team member will follow up with you at-least every 4 hours or until access to the production environment has been restored and the severity of the case can be lowered. For severity 2 cases, a first response will be made within the first 60 minutes of case creation, during normal business hours, Monday through Friday. And follow-ups every 2 days after that. For severity 3 cases, the initial response will be received within 4 hours, and weekly communication until the issue is resolved.
For the best results with your support case, set the appropriate severity, Enter a meaningful and detailed description of the issue Preemptively provide all the necessary logs and technical details, and maintain effective activity on the case.
I hope this has helped clarify some details of the Qlik Support policy, and demonstrate how Qlik Support is here to partner with your success. Thanks for watching.