Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hi,
I am working in a project where we have a setup with Dev and QA in a single server and Pro in another server.
I just wanted to know if there should be a separate license to be used for Qlikview QA and PRODUCTION Server and also for publisher?
Very urgent!
Yes & Yes
This is a typical set-up for a small-to-meium sized environment without clustering. One platform is the Production platform with all QlikView services and a full license for both QlikView Server EE Edition and QlikView Publisher and a suitable number of CALs. The other is a QA+Development shared platform with again QlikView Server EE Edition and QlikView Publisher with all QlikView services and test licenses for both Server and Pulbisher. Test licenses don't need CALs, they re-use the server access licenses from the production machine (with separate management and tracking) but cannot lease Named CALs. Test licenses are half the price of their full license counterparts.
This basic architecture offers a number of variations (Connectors, Publisher on a separate machine, different AccessPoints etc.) on which you can decide later on.
Hi,
Maybe ltu can give you a clear idea on this ?
Yes & Yes
This is a typical set-up for a small-to-meium sized environment without clustering. One platform is the Production platform with all QlikView services and a full license for both QlikView Server EE Edition and QlikView Publisher and a suitable number of CALs. The other is a QA+Development shared platform with again QlikView Server EE Edition and QlikView Publisher with all QlikView services and test licenses for both Server and Pulbisher. Test licenses don't need CALs, they re-use the server access licenses from the production machine (with separate management and tracking) but cannot lease Named CALs. Test licenses are half the price of their full license counterparts.
This basic architecture offers a number of variations (Connectors, Publisher on a separate machine, different AccessPoints etc.) on which you can decide later on.