Also interested in this packaging method. We are having trouble with connectivity from some networks to a QV server running in Azure installed as VM role. The white paper only mentions this in passing without any instructions.
I've no further information. I would like to prepare myself for this because there are more and more customers who wants to work with Qlikview in a (their) cloud environment. There's few information due to the license policy i guess--> OEM context.
I found a document explaining how to do it, but not in details. At least gives you an idea of what has to be done.
Check page 20 in the whitepaper attached.
"A web role is intended to host a web based application within IIS (Internet Information Services) on a Windows Server. To deploy to a web role a customer builds an Azure package containing the application, uploads it to Azure and then decides how much resource to give to that package. The amount of resources and number of instances can be flexed as needed and there are several features to support this.
While QlikView is accessed by users as a web application the back end is based on several Windows services and these are installed via an installer. To package QlikView into a web role the package must run the installer silently and then use the management API to license and configure the server. While this takes some knowledge of the Azure platform API it is possible to deploy QlikView in this way.
This style of deployment is well suited to deploying a configurable and packaged QlikView environment and so may appeal best to QlikView partners wanting to offer a similar offering to their customers. Once packaged a fully functional QlikView Server can be made available within 10 minutes and the same package could be used to deploy multiple servers with different configurations."