You can create one or more nodes and use them in a multi-node site. Give each node a specific role within the deployment to support planning of resources. For example, specify if a node is to run scheduled reloads or serve content to users.
When you create a node its associated services are also created and they inherit the node name: repository, engine, printing, proxy, and scheduler.
Do the following:
Select Nodes on the QMC start page or from the StartS drop-down menu to display the overview.
Click P Create new in the action bar.
Fill out the properties.
All fields are mandatory and must not be empty.
The node name.
The host name. You cannot edit the host name after the creation of the node. The server address must either be in the fully qualified domain name format: node2.domain.com or the machine name format: node2.Note: We recommend that you use the fully qualified domain name (FQDN). If you only use the machine name as the host name, the FQDN must be added manually to the virtual proxy Host white list.Note: There is support for using an IPv6 address as host name.
Use the drop-down to select which environment the node is intended for: Production, Development, or Both.
This setting is defined in the QMC on each node that is added. Depending on what node purpose you choose, different properties are applied to the node. These properties can then be used by load balancing rules and security rules for controlling access.
The effects of choosing the different options are as follows:
- Production: this server is intended to support users to access apps but not create them. This means that when a user connects to this node, the Create new app button in the hub is not displayed to the user. To hide the Work section in the hub, you need to disable the security rule that grants the application owner access. This means that when a user connects to this node, the buttons in the hub to create apps and the Work section are not displayed to the user. You cannot edit an app on a production node.
- Development: this server is intended to allow users to create apps but not serve the normal user traffic for users consuming published apps. In this case, the create and edit capabilities are enabled, but the server will not be considered when load balancing user traffic. Published apps are never available on a development node.
Note: This section is only available when you have a Shared Persistence installation.
- Both: this setting allows both activities to occur on the node. This means that both normal user traffic is handled and users can create apps.
In a multi-node environment, you can select one or more nodes to be failover candidates. In a failover scenario, where the central node stops working, one failover candidate assumes the role of central node. This solution eliminates the risks associated with the central node as a single point of failure.
A requirement for a failover candidate is that the services Repository, Engine, Proxy, and Scheduler are active. A node that does not have all these services active cannot be a failover candidate.Note: It is only when creating a new node that you can make it a failover candidate. Once a node has been created you can neither make it a failover candidate nor clear any failover candidate selection.
These are the roles that by default are assigned to the failover node.
Responsible for the scheduled reload tasks and user synchronization tasks within a Qlik Sense site.
License maintainer Responsible for the maintenance of licenses and tokens within a Qlik Sense site. User synchronizer Responsible for the user synchronization within a Qlik Sense site. Node registrator Responsible for the registration and removal of nodes within a Qlik Sense site. App manager Responsible for the management of apps within a Qlik Sense site. Database cleaner Responsible for the cleaning of the database within a Qlik Sense site.
Select which services to include. If a service is not installed when trying to activate, the properties will be applied when the installation is complete.
The Qlik Sense Repository Service (QRS) is always included.
The Qlik Sense Engine Service (QES). Printing The Qlik Sense Printing Service (QPR).
The Qlik Sense Proxy Service (QPS).
The Qlik Sense Scheduler Service (QSS). Property Description TagsTip: If no tags are available, this property group is empty.
Connected tags are displayed under the text box.
Property Description Custom propertiesIf no custom properties are available, this property group is not displayed at all (or displayed but empty) and you must make a custom property available for this resource type before it will be displayed here.Click Apply to save your changes. If a mandatory field is empty, Apply is disabled.
Click Apply in the action bar to create and save the node.
Successfully added is displayed at the bottom of the page and a dialog with your authorization password appears.
If you typed the Host name incorrectly the message Node registration failed appears.Note: You cannot edit the host name after the node has been created. Create a new node and type the correct host name.
Copy the authorization password and follow the instruction in the dialog to authorize the certificate on the host name machine.
If successful, the Certificate setup dialog displays The service was successfully unlocked.
Restart the services that you installed on the new node.
You have now created a new node and authorized the certificate to make the node operational.
You can use load balancing to get a more even distribution of the work load between different nodes. On the central node, load balancing is automatically added to the virtual proxy, but on all other nodes you need to configure the virtual proxy with load balancing. If you create a new virtual proxy, you must configure it by adding load balancing and selecting which nodes that the virtual proxy can forward work to.