05-14-2018 08:46 PM - edited 05-14-2018 10:18 PM
Our client environment has Geospatial Portal and GTech Networks service which allows users to create WMS and WFS from GTech features.
The client has a couple of GTech Networks WFS and WMS services. These services are displayed fine in a geospatial portal instance.
However, when we do a print on a map that has a wms feature's instances, the output print doesn't have this feature instances, it only has the base layer Open Street Map.
We use PhantomJS as the engine and confirm the issue with both local printer and external printer. I also enable PhantomJS logger, but I could not find anything suspious from its log location C:\Window\temp\PhantomJS. From Fiddler, I see that the Snapshot.WebClient.ashx submits the workspace that contains the WMS. From IIS log file, I notice that after clicking the print button from the dialog, there is no entry of get map request to the wms from SnapshorRedirect.WebClient.ashx (referer) with PhantomJS as the agent which we should see if the printing process working correctly.
I am kind of running out of ideas on how to investigate why the wms doesn't get picked up by the portal printing. Appreciate for all suggestions and insights on the problem.
I include the log file from portal in case it helps.
I also not quite sure how the map image is generated, I look into the dll Intergraph.WebSolutions.Core.WebClient.Printing and couldn't not find that part responsible for this. Would somebody explain a bit? Thank you.
Solved! Go to Solution.
05-18-2018 01:32 AM
The "NetWorks Portal" is a customised version of the Geospatial Portal product created by the Hexagon Safety & Infrastructure division. Have you contacted them as well about this issue as they developed the NetWorks WMS service?
Have you enabled any authentication/login mechanism against the NetWorks WMS service that could stop the Geospatial Portal print service from gaining access to the WMS during printing?
05-20-2018 04:38 PM
Some update on the issue. We tested with a third party wms and it worked fine with the printing. We also found out that if we add the working wms into the current workspace, it stopped working. We create a new workspace and it starts working again. So, the workspace somehow causes the issue but I am sure how. But, it is good that now we have the printing working.