Print widget in Portal for ArcGIS takes long time in ArcGIS enterprise

460
1
Jump to solution
05-30-2023 04:26 AM
Labels (2)
GISFunctionalGroup
New Contributor II

Hi everyone,

we are getting delayed responses from Print widget when printing the map in Web mapping application (we've downloaded the app & hosted in the IIS in windows server).

we've tried following tests to imporve the performance but no use.

  • all internal layers have  31370 Coordinates systems  & basemap in the 3857
  • whitelisted the ArcGIS external URLs (provided by ESRI)
  • removed the network firewalls & tested
  • excluded the ArcGIS Server folders form the Antivirus scanning 
  • datastores are registered
  • Printing with MAP_ONLY layout goes fast (<10 seconds)
    This includes the base map and our layers. This allows us to exclude the loading of the external datasource as potential problem
  • Printing in A4 Portrait goes slow
    The main difference between both seems to be the legend.
  • When we deactivate the legend in the printing (A4 portrait, but also other formats), we get the result in less than 10 seconds. When we activate the legend, we have the result after 40 seconds or more.

We are using ArcGIS enterprise 11.0 with SQL Server DB. We have downloaded the web map application and hosted in the IIS webserver.

If the above info is sufficient to help us , Kindly provide any workaround /solution to improve the performance of the Print widget.

 

Regards

GIS Functional Group

0 Kudos
1 Solution

Accepted Solutions
GISFunctionalGroup
New Contributor II

Hi Team,

After bundle of R&D, Tests we have found the a workaround for the performance of the Print widget in the Portal for ArcGIS. We are utilizing the some custom Layout templates as well in the print widget.

Before applying the following changes to the map & Layer the time taken for the a print is around ~1Min to 1.5Min

We've done the following changes to the web mapping application which we deployed in the IIS.

  1. We have used the own Basemap instead of ESRI Provided OSM basemap (Which will consume via Arcgis CDN). We have downloaded the OSM vector tiles from ArcGIS Pro Download map tool & shared as a Vector tile services to the Portal.
  2. We consumed above vector tile service as a basemap in the Webmap. 
  3. Our Operational Layers are (most of them are polygons which has custom symbology). Among the custom symbology, we decreased the thickness of the polygons such as cartographic, marker, and hash etc.
  4. Republish the Layer & overwrite with existing layer in the Webmap.

After applying the above changes to the map & Layer the time taken for the a print is around ~10 Sec to 45Sec.

we are glad the above solution helped us to improvement performance Hope it will help to improve your situation too.

Regards

GIS Functional Group 

 

 

View solution in original post

0 Kudos
1 Reply
GISFunctionalGroup
New Contributor II

Hi Team,

After bundle of R&D, Tests we have found the a workaround for the performance of the Print widget in the Portal for ArcGIS. We are utilizing the some custom Layout templates as well in the print widget.

Before applying the following changes to the map & Layer the time taken for the a print is around ~1Min to 1.5Min

We've done the following changes to the web mapping application which we deployed in the IIS.

  1. We have used the own Basemap instead of ESRI Provided OSM basemap (Which will consume via Arcgis CDN). We have downloaded the OSM vector tiles from ArcGIS Pro Download map tool & shared as a Vector tile services to the Portal.
  2. We consumed above vector tile service as a basemap in the Webmap. 
  3. Our Operational Layers are (most of them are polygons which has custom symbology). Among the custom symbology, we decreased the thickness of the polygons such as cartographic, marker, and hash etc.
  4. Republish the Layer & overwrite with existing layer in the Webmap.

After applying the above changes to the map & Layer the time taken for the a print is around ~10 Sec to 45Sec.

we are glad the above solution helped us to improvement performance Hope it will help to improve your situation too.

Regards

GIS Functional Group 

 

 

0 Kudos