Discussion Board for collaboration on QlikView Management.
Hello Everyone,
We all know that Qlik introduced Subscription based license, Many Clients may already been using it and many are in process of Migrating to the new License Model. With this Qlik gives package for bunch of Qlik products and for Some Clients who have not used QlikView Publisher earlier , that would be available for use when they get into subscription license. So Upon Applying SLK it would Activate Publisher
In this post, I would like to explain the steps I followed to Resolve below problems I faced.
Problem:
You are Activating Publisher in Qlik Deployment.
I came across the unique problem for a customer : when we apply the Signed License Key to Existing Qlik Deployment, which was single node with Default Qlik Reload Engine - After Applying the SLK Qlik Tasks would be cleared out.
Alternatively the Problem could be when User have Qlik Installation with Reload Engine and then after purchasing new license /Publisher license they want to migrate all their tasks from Reload Engine to New Publisher Server.
Resolution:
If you have lesser number of tasks (20-30) and without complex dependency/Schedules/Triggers you may create all tasks manually and avoid below hassle.
First of all, Take all the necessary backups for Existing Qlik Installation before proceeding with following steps.
Also it is advised to execute these steps in TEST environment before performing them into your production environment. You may need to adapt to these steps according to your environment configuration.
For Convenience Below steps are tested with Singe Node QlikView Installation only.
Now Restore Tasks from the Backup
From here You may see that Tasks are Visible Back Again.
Verify under Documents folder Go to Source Documents Tab check the Folders, and Tasks is associated with Appropriate QVW file.
If you are migrating tasks to another publisher - Update the new publisher server under Systems > Distribution Service.
And Restarts QDS on new Publisher server and Disable QDS on Existing server. You may loose task history along the way.
Another Scenario: Tasks are created with QVW in subfolders.
Important Note:
Publisher Service Does not traverse through all the sub folders, so you may need to map multiple folders in QMC.
When you add folders under Distribution service they are generated with new ID , and That Folder ID is very crucial to map the tasks
So, If you have Complex Sub Folders Structure You would need to have additional changes after above steps because tasks would be visible but as orphan. It is good if you have simplified Folder Structure :
Source Documents - Folder which contains your QVW files and Reload Tasks are associated with it
User Documents - Folder which contains your QVW files consumed by users through Access point or other means
Also Look at this article and Video help for Migrating reloads Tasks from One to Another Publisher node.
Hope these helps everyone!!
Thank you
Ravi
QlikView #Publisher
Thanks @RaviGinqo for sharing.
I would also share the following article for reference for our Community users.
QlikView: Task list empty after applying Unified S... - Qlik Community - 1886428
Cheers,
Albert
Thanks @RaviGinqo for sharing.
I would also share the following article for reference for our Community users.
QlikView: Task list empty after applying Unified S... - Qlik Community - 1886428
Cheers,
Albert