Hi D.Lender / All,
In Finesse 10.0 (UCCE), i have configured a Screenpop xml under 3rdpartygadget. But when rendering it shows HTTP error 404. When I checked the 3rdpartygadget/files, gadget xml is available on Finesse server.
URL Configured in cfadmin is as follows,
Below screen shows that screenpop gadget that has been hosted under 3rdpartygadget.
But still shows 404 rendering issue in Finesse10(UCCE).
Note: I have working knowledge on Finesse 9 and Finesse 10 (UCCX) prior to this Finesse(10) UCCE.
Let me know, if there are any configuration to make it works.
I have deleted my last 2 responses as they are not correct. You should not use the full path. Also note that even though your Finesse agent desktop is using https, gadgets that reside on the Finesse server use http since the gadget is on the same server as Finesse so there is no security issue.
Here is the recommendation for getting out of the problem:
1) Make sure the Gadget is deployed to both Finesse Servers (or at least the one that you are trying to access)
2) Revert the Desktop layout to load using relative path (/3rdpartygadgets/files/ScreenPop/ScreenPop.xml)
3) Try to load the Gadget XML into a browser directly by using the full URL (using your example): http://172.16.6.180:8080/3rdpartygadget/files/ScreenPop/ScreenPop.xml
…if the above works you will see the contents of the gadget in your browser. This proves it is deployed properly.
4) Restart “Cisco Tomcat” on the target server to clear the gadget cache.
That should clear things up.
We are facing the exact same symptoms, and chmod and using relative path/restart havent made a difference.
Accessing (or trying to access) the gadget XML file directly as below, also shows the 404 error:
This would indicate that tomcat is unable to serve/locate the content at the path - however gadget files are visible at the target location and have 644/777 permissions. Is there a need to "activate" the content deployed within the 3rdpartygadget folder?
This sounds like you followed Cisco's instructions and uploaded the .xml and .js files to Finesse Publisher but your Agent desktop is instead trying to parse them on a Subscriber. (even if the URL points to the publisher). Try turning off all subs before loading the report.
Or you can try uploading the gadgets to each of the Finesse servers manually (something that will have to be done anyhow)