Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 
Not applicable

Qlikview 11 SR1 Server- how to make the QlikView - AccessPoint page available over the internet and create a web site of it

Hi there,

I think this is a vey common question but since i have no experience with such issues, any help would be great!

So, my company has just purchased a Qlikview 11 SR1 Server licence. We will install it on a Server machine running Windows Server 2008 R2.

My question in a nutshell.

What should be the steps that we must perform to make the QlikView - AccessPoint page available over the internet, making it a web site of some sort and apply an ssl certificate on it (so that the final web site address wil look like e.g https://qlik.companydomainname.com)?

Should we install SQL Server on the machine as well?

Thank you al in advance for your answers.

1 Solution

Accepted Solutions
Bill_Britt
Former Employee
Former Employee

A FQDN is assigned an IP address so when you type https://qlik.companydomainname.com  a DNS server knows what IP that name belows to. This is your outside address and is what you would NAT in the Firewall to the internal server address.  Are you wanting to setup SSL on  IIS or QVWS?

Bill - Principal Technical Support Engineer at Qlik
To help users find verified answers, please don't forget to use the "Accept as Solution" button on any posts that helped you resolve your problem or question.

View solution in original post

4 Replies
Bill_Britt
Former Employee
Former Employee

QV comes with an AccessPoint so it is ready to go. All you have to do is NAT you external address in you Firewall to point to the server hosting QlikView. As far as installing SQL on the server this is not recommended..

Bill

Bill - Principal Technical Support Engineer at Qlik
To help users find verified answers, please don't forget to use the "Accept as Solution" button on any posts that helped you resolve your problem or question.
Not applicable
Author

Thnks for your reply Bill.

Let's say that the Internal Server IP is 192.168.1.1 and the external is 100.100.100.100.

The Qlikview Access Point ip that i hit from my pc is http://192.168.1.1/qlikview/index.htm.

Correct me if i am wrong but the way i understand your answer is that if i NAT the external address in the Firewall ( e.g port 8080) to point to the server hosting QlikView i will be able to access Qlikview Access Point using the ip

http://100.100.100.100:8080/qlikview/index.htm.

This is not exactly what i want. The ideal would be to just click on something like

https://qlik.companydomainname.com  as i mentioned earlier, where qlikview will be the sub domain under the companydomainname that already exists.

Also where in Qlikview do i assign the SSL Certificates?

Thnks again.


Bill_Britt
Former Employee
Former Employee

A FQDN is assigned an IP address so when you type https://qlik.companydomainname.com  a DNS server knows what IP that name belows to. This is your outside address and is what you would NAT in the Firewall to the internal server address.  Are you wanting to setup SSL on  IIS or QVWS?

Bill - Principal Technical Support Engineer at Qlik
To help users find verified answers, please don't forget to use the "Accept as Solution" button on any posts that helped you resolve your problem or question.
parkera
Partner Ambassador
Partner Ambassador

Hello,  We created http://demo.differentia.co  as a sub-domain of our main site http://www.differentia.co and created a 302 redirect from our hosting provider and created an A record to point to the target router (fixed IP or alias does not matter). (All standard stuff). All other A records were deleted. 

Router and firewall need to be redirected to your server running QlikView Access point.

SSL can easily be setup and the question of whether to run SQl Server on the same server as QlikView all depends on performance/cost. As QlikView scales the service components of QlikView server can also be located on separate machines.

Naturally an external facing Access Point requires the correct combination of server/user licenses to be compliant with EULA.