Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hi,
I am new to Qlikview. In development server, we have .qvw documents (Source Documents) and published to AccessPoint to test them. Then how to move/deploy them to QA/Production server? For .qvw file itself, I think I can copy to QA/Produ Source Documents folder, then publish it. However, how about the connection string? How to reset connection to QA path/Production path?
Also, for every developer using local client license, after development, administrator needs to move .qvw file from development folder to development server - Source Documents folder, correct?
Please advise or recommend any documents for reference.
Thanks in advance.
Hi,
You can use dos command net to server, and the copy the qvw file from local to the server folder that what you want.
Hi,
For us we have same folder structure for all three environments Development,QA & Production.
(1) We use relative paths in our scripting so that when we move them they will work fine and no code changes required.
(2) We will use include script with connection string.Before moving to QA/Prod we can change the connection string accordingly.So that you don't need to go to individual applications and change.
We can also implement code to pick up right connection string depending on environment./server name
(3) Once the above changes are done our admin will move all QVD generator QVW files and User facing QVW to corresponding folders in QA and create tasks in QEMC.
(4) Admin has to created a ODBC from server to QA database if it first time and use that connection string
Hi Chiranjeevi,
This is a very good answer. I have seen this at all major sites.
Bill
Thanks everybody. Your answers are really helpful. I am so glad to know you guys here.
Hi Cheeramjivi,
Can you please tell me how testing licences work
I mean if I have access of test licence then how can i test any qlikview document.
Moreover shall we deploy QV application in accesspoint by only using test environment.
Please suggest.
Thanks
Hi,
A test license will match you production license. You will not be able to lease a license from it and some of your graphs will have the word "TEST" across it. You will be able to test any QVW just like it would be in production.
Bill
Hi, Wei
About the DTAP process, have you taken a look at the Deployment Framework?.
Lots of usual problems like script modification, string connection modification between environments, etc have been addressed in its structure:
The full adoption of the Framework may be a project in itself but I'm sure that you will find interesting the ideas gathered in it.
Hope it helps.
Best regards.
Hi Bill,
Please correct if I am wrong.
You mean test licences are only for testing purpose of QVW files.
If I have 1 test licences in allocated then I can test any number of document(Just like named user cal I can access any number of doc in testing environment).
Thanks
Have a look at QVScriptor it can deploy your applications to your DEV, QA, PROD targets.
You can rollback in case of problems and also define target values and connections strings specifics to each target
Regards