QV 11 Distributed Installation

[#1]

Hi...

We are upgrading from QV 10 to QV 11 SR4, but we needed to change the QV topology -- instead of having *all* services into one single machine we would like to have the QVS on our DMZ and the rest of the services in another server in the internal network.

After a couple of days of frustrated attempts, I decided to search for some orientation.

Current scenario:

QLIKVIEW-APP

• installed on our production LAN
• the initial setup contains:
  • QV Directory Service Connector
  • QV Management Service
  • Distribution Service
  • MS IIS Support

QLIKVIEW-WEB

• installed on our DMZ
• the initial setup contains:
  • QV Directory Service Connector
  • QV Server
  • MS IIS Support

I am able to setup the DS license; however, i noticed that it automatic expects a QVS on the current machine, even when I selected not to install one.

Looking at some documentation, I tried to define the second server on the QMC as qvp://QLIKVIEW-WEB:4747/; I see a network packet going from QLIKVIEW-APP to QLIKVIEW-WEB, but after a (long) while, it reports an error (see screenshots in attach)

Is there a way to distribute the services in this way? What are we doing wrong?

BTW, currently all firewall restrictions are removed between these 2 machines.

Any help would be greatly appreciated.

Thanks in advance,

José Nobre

[prabhu0505]

jose,

I would like to highlight couple of pointers for you.

1. All the services across the boxes should run with same service account.

2. In Domain Controller you cannot install qvs which is stopped from v9.

[Bill_Britt]

Hi,

I would agree with Saravana, check to make sure that all services are running under the same account. I have done this type of installation more than one without issues. Also, in writing the Server Certification material you will find a setup like this on the test.

Bill

[Anonymous]

Jose

Also have a look at extranet server.

This is a special qlikview version to run in DMZ zone

[jerrysvensson]

My client have  a similar setup like yours.

We used Certifcates instead Windows authentication and it works fine.

It was a little bit tricky though to get it setup correctly. Make sure you follow the manual exactly.

[#6]

Hi all,

thanks for your replies; sorry the late reaction, but were 2 hectic weeks, where QV was not the only project.

About the service account, we do need to use 2 service accounts, as per company's security policy. However, after a bit of a fight, we were able to set it up...

Not an easy task, but once you are there, all become obvious

Just for future reference, we need to go through the custom install, and select service by service. Also, the use of 2 service accounts, one for the internal network and another for the DMZ is achievable, but there are a couple of tricks to know... And finally, the order by which the licenses are applied is very important!

Once again, thanks for your replies...

Best regards,

José

[#7]

I would say the way to go with DMZ is to use certificate.