Generate ODBC connection string by using the Scramble Connect User Credentials option in
Edit Script -> Settings Tab(In the bottom of the script window) -> Select Scramble Connect User Credentials
Now generate the ODBC or OLE DB connection string and copy this to the text file.
Hope this helps you.
Batch file is not executed by QLIKVIEW rt? So if we scramble as you have suggested it will take those credentials only and will fail to login.
If user id is ABC, Password is 123 and after scramblling userID will be xbshy and password will be 12hTGs.
So when we execute the batch file in the prompt for UserID and Password it will take
userID as xbshy
password as 12hTGs which will actually fail.
Any comments from your side please let me know
PLease correct me if I am wrong:
What you have said is:
Run the batch file and using the bacth file we need to trigger one QLikview document where the script(text file) is written to get the done file from ETL server is placed (Script which is maintained in the text file is now should be included in Qlikview document using include)??
In this case how QLikview can get the file from ETL server and place in required location??
Because it is not Qlikview scripting.
It will just open ETL server, get the done file and paste in QV server and delete from ETL server
open <SERVER NAME>
user <usER NAME> <PASSWORD>
lcd <LOCATION OF QLIKVIEW SERVER WHERE IT SHOULD PASTE THE DONE FILE>
cd <LOCATION OF ETL SERVER WHERE THE DONE FILE IS LOCATED>
get <DONE FILE NAME>
delete <DONE FILE NAME>
Oh, these are commands for some sort of ftp client program?
QlikView may offer methods to generate an ad-hoc command file where you replace $() placeholders with the actual username and password. Those can be lifted from a secure file (possibly encrypted). But that is too cumbersome, I think.
How about using QlikView itself to transfer the data from the ETL server. LOADs can be programmed to get their source data from an ftp-server, and support for username and password is included as well. That would mean that the transfer can be scheduled under task control, and that usernames and passwords are only residing inside a QVW (with its own security features).
See Script editor->Data tab->Data From Files. Enable the FTP checkbox, and click the Table Files button.
Dunno if you can drop the source file from inside QlikView though. But that could be handled by a batch job on the ETL-server.
That depends on the contents of this Done file.
A LOAD and STORE is the simplest way to transfer the contents and at the same time take advantage of the connection features of QlikView. And optionally do some preprocessing where needed.
However, you didn't supply any information yet on what data you want to transfer. So this is really guesswork at the moment.