Accesspoint

[#1]

Hi,

Is it possible to make like this in accesspoint

1. When user logins the Accesspoint user should see the dashboards it means the QVW files should open automatically . It should not show the QVW files and user should not choose it.

2. Is it possible to refersh the QVW files while opening.

3. If the both are possible then can it be done through QlikView Webserver or we should use IIS server

i have posted the similar Query earlier. But i am looking for this answer

[deepakk]

hi,

1. You can directly provide the application url to user whom you want the dashboard to be opened.

2. Refresh of data from Webserver is not possible. but i think you can reload applictaion through IIS using batch file. (by Creating ASP page and firing the batch file from it.).

I hope others too, might add their valuable inputs on the same.

[johanfo2]

I have just tried to start the "qv.exe /rp qvFile.qvw",  directly,through VBA and through bat files from a web service process. The web applications runs on an administrator account (intranet), so there should be no problemwith access rights.  I use .Net 4.0 and use the Process.Start()  function there.

What happens is that the "qv.exe" file turns up in the task manager, but nothing happes, it just sits there.  When I as a user, with the same access rights, start the bat file manually, it immediately starts to refresh the file.

My thoughts:

* It could be something related to environment variables

* It could be something to do with lack of graphical environment when the process starts through IIS

* Environment variables?

* Qlikview is programmed to prevent IIS triggered refreshes?

Your suggestions are greatly appreciated.

JF

[deepakk]

hi,

Are you running the batch file from the same system in both the cases.?

If not , try giving the netwrok path inside the batch file and try to run in  manually from other system.

[johanfo2]

I'm running the batch from exactly the same system!

[johanfo2]

I miraculously managed to solve it!

By adding the username and password options in .Nets' Process.Start(), the program ran smoothly.  Since the program ran under the correct username also without this parameter, I suspect this might have something to with some environment variables that are not set correctly when the webserver spawns executes the Start() function.

SecureString s = new SecureString();

                foreach (char c in "mypassw")

                    s.AppendChar(c);

                Process.Start(QlikViewExeFilePath, @"/rp ""C:\QlikView\AccessPoint\QVFile.qvw""", "myusername", s,"Domain");