Editing a node

Do the following:

1. Open the QMC: https://<QPS server name>/qmc

2. Select Nodes on the QMC start page or from the Start drop-down menu to display the overview.

3. Select the node that you want to edit.

4. Click Edit in the action bar.

5. Edit the properties.

   Identification

   All fields are mandatory and must not be empty.

   Identification property descriptions

   Property	Description
   Name	The node name.
   Host 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. Information noteWe 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 allow list. Information noteThere is support for using an IPv6 address as host name.

   Node purpose

   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 who access and consume published apps, but not create new ones. The Create new app button is hidden, and the Work section is not shown by default. However, users can still access and edit their own unpublished or duplicated apps, depending on their license and security rules.

   • Development: this server is intended to allow users to create apps but not serve the normal user traffic for users consuming published apps. Create and edit capabilities are enabled.
   • 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.
   Node configuration

   Information noteThis section is only available when you have a Shared Persistence installation.

   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.

   Information noteIt 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.

   Node roles

   These are the roles that by default are assigned to the failover node.

   Node roles

   Role	Description
   Scheduler master	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.

   Services activation

   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.

   Service descriptions

   Property	Description
   Repository	The Qlik Sense Repository Service (QRS) is always included.
   Engine	The Qlik Sense Engine Service (QES).
   Printing	The Qlik Sense Printing Service (QPR).
   Proxy	The Qlik Sense Proxy Service (QPS).
   Scheduler	The Qlik Sense Scheduler Service (QSS).

   Scheduler priorities

   Choose whether the node should be available for reloads and preloads. These settings are only available when Scheduler is enabled under Services activation.

   Scheduler priorities

   Property	Description
   Scheduler to do reloads	The node can do reloads. Enabled by default.
   Scheduler to do preloads	The node can do preloads. Disabled by default.

   Tags

   Tags properties

   Property	Description
   Tags	Tip noteIf no tags are available, this property group is empty. Connected tags are displayed under the text box.

   Custom properties

   Information noteIf 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.

6. Click Apply in the action bar.

Successfully updated is displayed at the bottom of the page.