Skip to main content
Woohoo! Qlik Community has won “Best in Class Community” in the 2024 Khoros Kudos awards!
Announcements
Nov. 20th, Qlik Insider - Lakehouses: Driving the Future of Data & AI - PICK A SESSION

How to move the QlikView Distribution Service (QDS) Notification files

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

How to move the QlikView Distribution Service (QDS) Notification files

Last Update:

Jul 7, 2021 4:02:27 PM

Updated By:

Juli_K

Created date:

May 28, 2018 2:48:17 AM

The QlikView Distribution Service (QDS) notification files can be moved. This is especially necessary when dealing with a high load system. This will move the Task Execution notifications, the load balancing file, and the task execution history notification files.

Moves the following files: 

masterconfigurationnotification.xml
mastertaskexecutionhistorynotification.xml
mastertasknotification.xml
mastertriggernotification.xml
taskexecutionhistorynotification.xml
tasknotification.xml
triggernotification.xml
loadbalancer.xml
nodeinformation.xml


The setting needs to be applied to all notes in a QDS cluster.

Environment:

 
 
The Notification Folder path will have to be accessible by all of the QDS nodes in the cluster so the universal naming convention (UNC) path should be used (e.g. \\servername\filepath)
  1. Stop the QlikView Distribution Service
  2. Modify the file QVDistributionService.exe.config found in C:\Program Files\QlikView\Distribution Service
  3. Include:
      <!-- Alternate Path for Notification System -->
       <add key="NotificationFolder" value="Your folder Path"/>​
     
  4. Start the QlikView Distribution Service and verify that files are being updated.

Please make note:  

It is advised to COPY the notification.xml files from the original location to the new location.   

If you do not copy the original  xml to the new location, the QMC (Qlik Management Console) task history is gone from each task until each reload task gets triggered again.   The task history eventually reappears,  but in large systems, that could take some time depending on the task schedule.

The reason this happens is the taskexecutionhistorynotification.xml file  contains entries for all ID's from the TaskExecutionHistory folder.   If you do not copy the original taskexecutionhistorynotification.xml,  the process of "moving" the notification folder starts with a new xml file and the Distribution Service needs to run through each of the tasks to build the set of ID's again.

Per QLIK R&D, best practice is to copy all of the Notification system.xml files to the new location prior to restarting the QDS services.

Labels (1)
Comments
fmarvnnt
Partner - Creator III
Partner - Creator III

Sorry Sonja,

      Not clear where exacly has to be inserted the string in the config file.

 

 

Thank You in advance,

 

FMa

Sonja_Bauernfeind
Digital Support
Digital Support

Do you mean here?

 

<add key="NotificationFolder" value="Your folder Path"/>

You'd replace "Your folder path" with, for example \\server\folder or c:\folder\folder.

 

Version history
Last update:
‎2021-07-07 04:02 PM
Updated by: