Discussion Board for collaboration on Qlik NPrinting.
Hi All,
QlikView server migration will require change of "Address" & "ClusterID" of NPrinting cluster connection. We have >50 clusters connection setup in NPriting. Below is sample of Address & ClusterID used in cluster connection
http://<QMS server name>:4799/QMS/Service
QVWS@<QVWS server name>
Would like to check is there is any method to mass update Address & ClusterID in cluster connection instead of update 1 by 1. Meanwhile, I would like to understand what is the best practice to use generic "Address" & "ClusterID" in cluster connection to prevent mass update when there is server migration.
Thanks,
Boon Haw
Hi,
you must provide required entities.
I would use API to read all connections and then update all of them:
https://help.qlik.com/en-US/nprinting/May2021/APIs/NP+API/index.html?page=82#Connections
Since we are Qlik developers I would use Qlik script and Qlik rest connector to write it. API was recently updated with the ability to create and update connections so my NPrinting.qvs does not contain ready to use script but you can easily use it to write your own script:
https://nprintingadventures.com/2019/04/08/nprinting-api-qlik-rest-subroutines/
another option (!!! but not officially supported!!!) would be to run update on NPrinting repository database using tools like pgAdmin. It is much easier to do, but at the same time it is not officially supported and therefore I do not recommend it. Before using this method I would definitelly take a backup of NPrinting repository!
cheers
Lech
Hi,
you must provide required entities.
I would use API to read all connections and then update all of them:
https://help.qlik.com/en-US/nprinting/May2021/APIs/NP+API/index.html?page=82#Connections
Since we are Qlik developers I would use Qlik script and Qlik rest connector to write it. API was recently updated with the ability to create and update connections so my NPrinting.qvs does not contain ready to use script but you can easily use it to write your own script:
https://nprintingadventures.com/2019/04/08/nprinting-api-qlik-rest-subroutines/
another option (!!! but not officially supported!!!) would be to run update on NPrinting repository database using tools like pgAdmin. It is much easier to do, but at the same time it is not officially supported and therefore I do not recommend it. Before using this method I would definitelly take a backup of NPrinting repository!
cheers
Lech