<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Node CAL limitations in a QVS cluster? in QlikView</title>
    <link>https://community.qlik.com/t5/QlikView/Node-CAL-limitations-in-a-QVS-cluster/m-p/693437#M1317675</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi All,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I was wondering if it might be possible to limit CALs depending on the server node in a QVS cluster. My case is that I would like to have a specific user group to use Session CALs and a other one to use only usage CALs.&amp;nbsp; Using a load balancer I am pretty sure I can drive the user to the ad hoc node but since pgo file are shared this feature "CAL limitations" will apply or not to both nodes separately or not?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;My opinion is that I should start with some Session and Usage CAL and ask for a remix clause after a few months of usage monitoring.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thx for your comments,&lt;/P&gt;&lt;P&gt;Michael&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 26 Jan 2026 18:19:17 GMT</pubDate>
    <dc:creator>agilos_mla</dc:creator>
    <dc:date>2026-01-26T18:19:17Z</dc:date>
    <item>
      <title>Node CAL limitations in a QVS cluster?</title>
      <link>https://community.qlik.com/t5/QlikView/Node-CAL-limitations-in-a-QVS-cluster/m-p/693437#M1317675</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi All,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I was wondering if it might be possible to limit CALs depending on the server node in a QVS cluster. My case is that I would like to have a specific user group to use Session CALs and a other one to use only usage CALs.&amp;nbsp; Using a load balancer I am pretty sure I can drive the user to the ad hoc node but since pgo file are shared this feature "CAL limitations" will apply or not to both nodes separately or not?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;My opinion is that I should start with some Session and Usage CAL and ask for a remix clause after a few months of usage monitoring.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thx for your comments,&lt;/P&gt;&lt;P&gt;Michael&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 26 Jan 2026 18:19:17 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Node-CAL-limitations-in-a-QVS-cluster/m-p/693437#M1317675</guid>
      <dc:creator>agilos_mla</dc:creator>
      <dc:date>2026-01-26T18:19:17Z</dc:date>
    </item>
    <item>
      <title>Re: Node CAL limitations in a QVS cluster?</title>
      <link>https://community.qlik.com/t5/QlikView/Node-CAL-limitations-in-a-QVS-cluster/m-p/693438#M1317678</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Michael,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The limitation tab will only limit the number of CAL's for both nodes, it won't work as or sort of CALs load balancer, and unfortunately, I do not think there is a way to load balance CALs or predetermining what CALs and numbers CALs can be use for each node within a cluster environment. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Maybe someone else has another type of solution, good luck!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Gio &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 15 Sep 2014 14:26:55 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Node-CAL-limitations-in-a-QVS-cluster/m-p/693438#M1317678</guid>
      <dc:creator>Giuseppe_Novello</dc:creator>
      <dc:date>2014-09-15T14:26:55Z</dc:date>
    </item>
  </channel>
</rss>

