Deploying from development to UAT and on to production
There are a few things to remember to do as your nice new document goes through testing and on into production.
Explanation
Always use a consistent approach and document it so that everyone in the team works in the same way.
Background
One of the most common reasons for applications failing when deployed to UAT or production is the fact that file paths are hardcoded.
How to do it
Keep your application in self-contained folder structures and use relative references to files used within it.
Use the same network account to run QlikView services on all machines.
If there is a need to identify which server you are running on, use the ComputerName() function in your script. Alternatively, you could use $(Include=filename) or preferably $(Must_Include=filename) to set a variable.
If you use an include file, keep the name the same in all environments but change the contents as appropriate to the environment. So, for example, you may have an include...
