Issue With IFrame Embedded ICN Daeja ViewONE Virtual Viewer
Hi, I am currently working on integrating ICN Daeja ViewONE Virtual Viewer using iFrame. To elaborate, from a Web application hosted on one server, there is an action to open the Document, which would launch Virtual Viewer residing on a different server, to open the document. This works perfectly fine when I use the Virtual Viewer URL format http://hostname:port/navigator/bookmark.jsp?docid=. However, when I try to use DNS (Domain Name Server) i.e. http:///navigator/bookmark.jsp?docid=, Virtual Viewer initialization fails and throws the below error - "Unable to start viewer. Unable to init UI."
Is there any constraint that while invoking Virtual Viewer, URL should be hostname:port, and not DNS?
Please let me know where I could find logs for this initialization failure so that I could analyze more on the problem.
Please note that :
IBM Daeja ViewONE Professional Viewer works fine when invoked using either hostname:port or DNS.
Under Application-level logging, I have already configured as Debug, but no sign for the above issue in either SystemOut.log or SystemErr.log
Please provide some pointers.
Thanks, Divya
Hi Divya,
I want to integrate ICN Viewer with custom application . I followed the link given below to do the task but I have certain confusion
1.Not clear what to do at ICN server side. 1. What need to do in Custom application ? What need to do with the XDomainViewerAPI.html and XDomainViewerWindow.html file? Please help me , how can I integrate Viewer with custom application . In current scenario both ICN and Custom application deployed on the same server.
If you will provide help , then really it would be great for me.
Regards, Ahmad
Hi Divya,
There is no constraint regarding DNS vs IP however unlike Daeja ViewONE Professional, Virtual runs only in the browser and therefore is limited by the same-origin policy of browser requests.
Unfortunately the issue is happening before the viewer has had a chance to set up its logging fully. However you should be able to see any issues in the Javascript console of the browser. The network tab of the developer tools may also show some useful information. You can normally find this by pressing F12 and then loading the page that contains the viewer.
The supported solution to this is to run the viewer on the same origin as the web page. That means if you're running on http://navigator/ then the page and all resources should come from that location.
Thanks, Mat.
Hi There,
Did this issue get resolved?