Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hi all
Has anyone migrated the Publisher server into Qlikview server? Btw the server will be on AWS.
What are the pros and cons?
How is it done?
Is there any documentation which I can read thru?
Thanks & Regards
Melanie
You mean to turn off the publisher an using only the remaining distribution features from the server component? If yes then you will lose a lot of flexibility then you couldn't use different servers for reloads and responses to user-accesses and you could only use one trigger for each task and features like loop and reduce wouldn't be available anymore.
I'm not sure if there any documentation for this (rather not and a reinstall will be needed) and most often quite the opposite happens that when the qv environment is growing that the server-services will be divided and clusterred.
- Marcus
The idea of migrating the Publisher to the Qlikview Server would be due to wanting to share the CPU & RAM.
Job running now on the Publisher is scheduled early hours of the morning and finishes when working hours starts. Qlikview server will be used during working hours. However there is a possibility (& it might happen) at some point where re-running of a job and user access is concurrently done.
Why would the function of use one trigger for each task and features like loop and reduce wouldn't be available anymore when migrating?
Noted on the future clustering option if Publisher & Qlikview Server is merged.
- Melanie
Hi,
Note: The following will remove all current tasks and rebuild the QVPR database. Please make sure to backup all files mentioned before making any changes to the files/folders.
Note: If a previous backup was created of the QVPR database dated before applying the Publisher license, you may extract the zip file to the QVPR folder at this time. The backup is located in the %ProgramData%\QlikTech\ManagementService\QVPR\Backups. If there is no backup, tasks will need to be recreated manually.
Bill