Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hello,
As per the title I'm looking to upgrade the QlikView AccessPoint and QMC to HTTPS.
I've gone ahead and followed this excellent guide on the Support Updates blog by @Sonja_Bauernfeind https://community.qlik.com/t5/Support-Updates-Blog/QlikView-AccessPoint-and-QMC-with-HTTPS-and-a-cus... and updated our Development Server with no issues.
The issue I have is that on our development server there is no QVD's published other than the stock default apps that come with a fresh install and it isn't licensed for QlikView Publisher like our Prod server.
I'm curious to know if I go ahead and make the changes as described in the blog will I encounter issues on production with published apps?
On Production we have QlikView Publisher running and querying if I need to make another other changes to config files to ensure there is no disruption.
I've also created a new CNAME for the server.
Running QlikView Server November 2017 SR2
Thanks
Hello!
Glad you found the guide useful 😄
As for your question: You'll be fine carrying them out on prod as well.
As I understand it, you're swapping the AccessPoint and QMC web interface over to use https. All that does is swap the client to server communication to those two sites over to https. You don't need to worry about what apps (.qvws) you are serving.
No changes between the services get carried out with the steps from this article.
You can swap the services to use a certificate as well, so that'd mean the Publisher talks to the QlikView Server with a certificate to authenticate rather than using the service user. But that's not what this article is about, so I assume that is not what you're trying to do.
Cheers,
Sonja
Cheers,
Sonja
Hello!
Glad you found the guide useful 😄
As for your question: You'll be fine carrying them out on prod as well.
As I understand it, you're swapping the AccessPoint and QMC web interface over to use https. All that does is swap the client to server communication to those two sites over to https. You don't need to worry about what apps (.qvws) you are serving.
No changes between the services get carried out with the steps from this article.
You can swap the services to use a certificate as well, so that'd mean the Publisher talks to the QlikView Server with a certificate to authenticate rather than using the service user. But that's not what this article is about, so I assume that is not what you're trying to do.
Cheers,
Sonja
Cheers,
Sonja
Hi @Sonja_Bauernfeind ,
That's exactly what I needed to know.
I think I was just looking for the reassurance to go ahead and do it 😄
Thanks for the excellent guide and for the answer.
Really appreciated and have a great weekend.
Regards,
Podge