<?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 Qlikview server installation in QlikView</title>
    <link>https://community.qlik.com/t5/QlikView/Qlikview-server-installation/m-p/269713#M1280079</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Yes, absolutely. It is a preferred configuration in many larger environments with high load on reloads.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;When installing, for example, you can go at it in a number of different ways. The preferred way is probably to install only the services you need on each machine. One example is to install everything except distribution service on server1 and only distribution service on server2. Then you can instruct QEMC on server1 to configure the distribution service on server2 from server1. You can then have data reload on server2 and get them published to the QVS service on server1.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Talk to your closest qliktech contact on how to get enterprise architecture advice and papers. &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 07 Jun 2011 19:55:22 GMT</pubDate>
    <dc:creator>StefanBackstrand</dc:creator>
    <dc:date>2011-06-07T19:55:22Z</dc:date>
    <item>
      <title>Qlikview server installation</title>
      <link>https://community.qlik.com/t5/QlikView/Qlikview-server-installation/m-p/269712#M1280077</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Is it possible to Install the server and publisher in two different machines. &lt;/P&gt;&lt;P&gt;I am looking at Qlikview 10. &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/Qlikview-server-installation/m-p/269712#M1280077</guid>
      <dc:creator />
      <dc:date>2026-01-26T18:19:17Z</dc:date>
    </item>
    <item>
      <title>Qlikview server installation</title>
      <link>https://community.qlik.com/t5/QlikView/Qlikview-server-installation/m-p/269713#M1280079</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Yes, absolutely. It is a preferred configuration in many larger environments with high load on reloads.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;When installing, for example, you can go at it in a number of different ways. The preferred way is probably to install only the services you need on each machine. One example is to install everything except distribution service on server1 and only distribution service on server2. Then you can instruct QEMC on server1 to configure the distribution service on server2 from server1. You can then have data reload on server2 and get them published to the QVS service on server1.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Talk to your closest qliktech contact on how to get enterprise architecture advice and papers. &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 07 Jun 2011 19:55:22 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Qlikview-server-installation/m-p/269713#M1280079</guid>
      <dc:creator>StefanBackstrand</dc:creator>
      <dc:date>2011-06-07T19:55:22Z</dc:date>
    </item>
    <item>
      <title>Qlikview server installation</title>
      <link>https://community.qlik.com/t5/QlikView/Qlikview-server-installation/m-p/269714#M1280082</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Stefan, can you do that without a publisher license? Because there wouldn't be a distribution service to configure at the QEMC.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Would you still be able to configure a distributed environment though changing config files?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 08 Jun 2011 03:08:28 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Qlikview-server-installation/m-p/269714#M1280082</guid>
      <dc:creator>danielrozental</dc:creator>
      <dc:date>2011-06-08T03:08:28Z</dc:date>
    </item>
    <item>
      <title>Qlikview server installation</title>
      <link>https://community.qlik.com/t5/QlikView/Qlikview-server-installation/m-p/269715#M1280085</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;No. To use distribution service with that kind of functionality you need to have a Publisher license active.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 08 Jun 2011 05:37:36 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Qlikview-server-installation/m-p/269715#M1280085</guid>
      <dc:creator>StefanBackstrand</dc:creator>
      <dc:date>2011-06-08T05:37:36Z</dc:date>
    </item>
    <item>
      <title>Qlikview server installation</title>
      <link>https://community.qlik.com/t5/QlikView/Qlikview-server-installation/m-p/269716#M1280086</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt; Daniel,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;While using publisher license is the optimal solution, you could achieve the same results by having a single directory for both source and user documents, that was centrally located.&amp;nbsp; This would allow you to serve documents from one server, while the other performs reloads and serves documents in a load balance /DR/QA role.&amp;nbsp; This option would require 2 server licenses, so I'm not sure if you would save on licensing costs.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Cheers,&lt;/P&gt;&lt;P&gt;B&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 09 Jun 2011 12:21:04 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Qlikview-server-installation/m-p/269716#M1280086</guid>
      <dc:creator>bnichol</dc:creator>
      <dc:date>2011-06-09T12:21:04Z</dc:date>
    </item>
  </channel>
</rss>

