A QlikView Server cluster consists of multiple servers hosting the various services, with one QlikView Server service running on each node.
For example:
QVS1 (Server1)
- QlikView Management Service
- QlikView Server Service
- QlikView Distribution Service
QVS2 (Server2)
- QlikView Server Service
- QlikView Distribution Service
With no QlikView Publisher license, QlikView Server will use the QlikView Distribution Service as its "built-in" Reload Engine when performing reloads of files with .qvw extensions.
In the example above, is it possible to select which QlikView Distribution Service should be used within the cluster, without applying a QlikView Publisher license?
The answer is No.
With no QlikView Publisher license, it is not possible to select which Reload Engine should be used within the cluster environment. It will always make the Distribution service hosted on the Primary node of the cluster the Reload Engine, typically the same node hosting the QlikView Management Console.
In order to load balance or select the Reload Engine location within the cluster, a QlikView Publisher license is required, or you may switch the Primary and Secondary QlikView Servers in the QlikView Server resource in the Management Console if you do need to have the other box performing the application reloads.