Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Issue is two fold - 1)client cannot get IE plug in to work in a way to bypass access point when entering the document URL directly
2) client prefers ie plug in vs ajax because experiencing functional and graphical deficiencies using ajax
1 )Client cannot get IE Plug in to work in a way that the acces point can be bypassed. The users are on one domain and the
server is on another. Could this be creating issues with connecting directly using the URL vs needing to go through the access point?
2)Suggested using ajax but client noted 'Many rich media features such as click-and drag to select data on graphs, only works with the IE plug-in' .
I know ajax view is not quite as crisp but are there functions as the one mentioned above that cannot be perfromed using ajax?
Client did provided example where a graph displays using IE plug in but not using ajax. Is there a transparency setting in ajax that might be causing this to ocurr. I cannot seem to locate it if there is.
Thanks in advance.
Did you try using the qvp protocol (qvp://documentURL)?
No I have not.
If my document url is as below what would be the syntax?
Tried just replacing http with qvp and that was not it.
Thanks for your help.
Try this...
qvp://qv.mycompany.com/CSPoC/userid.qvw
I presume that CSPoC is the name of the mounted folder.
Good luck,
B
Another alternative is...
http://qv.mycompany.com/QvPlugin/opendoc.htm?document=CSPoC/userid.qvw
Thanks but we were unsuccessful with both.
With Ajax you do not seem to be required to be on the same network as the qv server to bypass the Accespoint landing page when entering the document URL directly.
Do you have to be on the same network when using the IE Plug?
You don't need to be on the same network for the IE Plug-in to work. I have several users at vendor sites that access the server remotely using the plug-in. They also use a custom html page in place of AccessPoint, with each link using the qvp protocol.
The problem I experienced was with the server name. Since the server name is only published internally using DNS, I needed to use the ip address in both the http address and the 'Link Machine Name' parameter in QEMC > Setup > QlikView Server > General tab.
B