Skip to main content
Announcements
Qlik Connect 2024! Seize endless possibilities! LEARN MORE

Elevating an existing Qlik Sense rim node to a Failover Candidate

No ratings
cancel
Showing results for 
Search instead for 
Did you mean: 
Benoit_C
Support
Support

Elevating an existing Qlik Sense rim node to a Failover Candidate

Last Update:

Oct 10, 2022 8:54:18 AM

Updated By:

Benoit_C

Created date:

Oct 10, 2022 7:09:11 AM

For information about Qlik Sense failover candidates, see Qlik Sense Failover Central node: Requirements and Considerations.

Out of the box, you need to toggle the option to enable a rim node as a failover node during first time setup. In this article, we will outline how to accomplish elevating an existing node to being a failover candidate primarily using the QRS APIs.

 

Steps:

 

  1. Perform a GET /qrs/ServerNodeConfiguration/full API call

  2. Copy the JSON response

  3. Edit the JSON to include only the node that you want to elevate
            Remember to remove the []'s which bracket the JSON response

  4. Change the failoverCandidate to be true and slightly modify the modifiedDate

  5. Perform a PUT /qrs/ServerNodeConfiguration/{GUID_of_note_to_elevate} with the edited JSON in the body

  6. Export full trusted root from existing Central candidate

  7. Stop services on the newly elevated rim

  8. Deleted the existing trusted root certificate on the newly elevated rim

  9. Import the copy of the certificate that was previously exported from an existing Central candidate

  10. Start all services on the rim

 

 

Environment

Qlik Sense Enterprise on Windows 

 

 

Related Content 

https://community.qlik.com/t5/Official-Support-Articles/Removing-a-Rim-Node-not-to-be-a-Failover-can... 

Labels (2)
Comments
TusharDev_Qlik
Creator II
Creator II

@Benoit_C 

we are trying to implement same steps to convert one of our existing RIM nodes to be a failover candidate through postman but getting below error.

403 No client certificate supplied.

The request was a legal request, but the server is refusing to respond to it. Unlike a 401 Unauthorized response, authenticating will make no difference.

We have tried importing QlikClient certificate to our local system where postman is installed.

but error persists. Kindly advise.

 

Sonja_Bauernfeind
Digital Support
Digital Support

Hello @TusharDev_Qlik 

Please post about your query in the Qlik Sense Management and Deployment forum. When doing so, include:

  • Version of Qlik Sense and current setup
  • Steps you have attempted and what you are looking to achieve
  • the error you are seeing and when
  • error log snippets if you can find them in the log files (verify not to submit sensitive information)

All the best,
Sonja 

Contributors
Version history
Last update:
‎2022-10-10 08:54 AM
Updated by: