How to move Qlikview documents from dev to Testing and Prod environments
How do we move qlikview documents from dev environment to Testing and prod enviroments.
Is there any object migration tool to transport the objects ? or do we have to manually point all the underlying databases or change the connection strings in the script editor to point the tables to the respective database instances.
Was wondering if somebody can throw some light on it?
Try using something like this in your script. It allows you to easily switch between databases. You only need to change the variable. This can of course also be done when you have even more databases that you like to connect.
In our shop, most QlikView applications reading from databases are only loading QVDs, and most user applications read only from QVDs. There are exceptions, but that's the norm. For the QVD-loading applications, we use variables to control where we're pointing. However, since QlikView only reads instead of writes data, I typically leave these pointed at the production databases, even during development.
The user applications, as mentioned, usually read only from QVDs. So user applications don't need any variable changes on an install. We also use relative addressing, and the same folder structure in all three environments. So we don't need to change drives and directories either. We can therefore run the exact same script in production as we run in test. Nothing in the script needs to be changed when we install.
So an "install" here is really nothing more than copying the file to the production server.
Now, we actually use a script to do our install, which handles code versioning, checks a couple common places for the file so that you don't have to give it a full directory, can do optional reloads, detects if this is a first time install and gives an error message if you aren't one of the administrators, and I don't know what all. I don't know, because I don't care and don't have to care. I keep my own archives of previous versions. I wouldn't care if I had to type a directory, because I know where the file I want to install is. I almost never do a reload during the install, and instead reload in QlikView Server if necessary. I am an administrator, so it doesn't warn me about new installs, because I know I'm doing a new install. So from my perspective, I'd be just as happy doing a drag and drop from the test server to the production server. I'm probably missing something, but I really think it could be just that simple if you wanted it to be that simple.
That's right. i do the same too. it's really that simple, sometimes make me feel uncomfortable.
But, once i copied over to production, i'll run the distribution job again on publisher, just to make sure everything is ok. but i'm not sure if this is neccesary?
and when you said you use a script for your install and versioning, what does it mean? if it's some nice tool, could you share it with us?
nicksatch wrote: But, once i copied over to production, i'll run the distribution job again on publisher, just to make sure everything is ok. but i'm not sure if this is neccesary?
The distributed file is, I believe, a different file than the source file that you copied over (not certain though). So yes, I think you need to run the distribution job in Publisher. The annoyance is if your reload and distribution are in the same job (typical for version 9), in which case you end up running the reload as well, even if you don't need to. If that's a particular problem, you can always split the reload and distribution apart. I normally like to reload anyway, just to be safe, even if I'm fairly confident that I copied back all the right QVDs from production, pointed at the production databases, and so on. So I almost always run both the reload and distribution after copying the source file over.
nicksatch wrote: and when you said you use a script for your install and versioning, what does it mean? if it's some nice tool, could you share it with us?
Well, I didn't write it, and only looked at it for the first time yesterday. It looks like it's a .BAT file that executes an ANT procedure on some XML to do a bunch of things related to the install, and most of them are specific to our environment and procedures. I don't think it would be useful to anyone else, and I wouldn't be comfortable sharing someone else's code anyway.
