properties.json file of arcgis portal shared content directory

[BanchanaPandey]

Does anyone know how is the properties.json file generated that lives in the shared content folder for ArcGISPortal?

The exact file location is in ....\arcgisportal\content\items on your shared content directory, whatever that you may have defined during your arcgis portal installation. Could be in your server machine or could be in a shared network drive as well.

In that properties.json file, under helperServices section, there is a printTask url and that is pointing to a url which we did not update anywhere. how is this file getting that url there?

If we look at the portal sharing, we see a different print task url that we identify.

any ideas? any seasoned experts of arcgis enterprise care to share and help me understand better please?

[A_Wyn_Jones]

Hi @BanchanaPandey 

You've discovered the Portal for ArcGIS default print task URL in your properties file which is used by Portal in a unfederated state - it is recommended by the Portal security scan to disable this once the Portal has been federated with a ArcGIS Server:

https://enterprise.arcgis.com/en/portal/latest/administer/windows/scan-your-portal-for-security-best...

You can disable the default print service in Portal admin > System > Properties - here's the syntax: 

https://developers.arcgis.com/rest/enterprise-administration/portal/system-properties/#:~:text=domai...

In your second screenshot, you can see that the Portal has configured itself with the ArcGIS Server default print task - this is done during federation.

[BanchanaPandey]

Thanks for that information  @A_Wyn_Jones 

We recently had an issue, where upon start of portal service, one of the machines is adding an extra comma after the print service (mentioned in this post https://community.esri.com/t5/arcgis-enterprise-portal-questions/arcgis-enterprise-dev-and-test-envi...  and Esri Case #03654828) which causes the postgres to not start at all.  We do have primary and standby portal machine and looks like primary has the issue, and we have to wait until the portal service in the standby machine also gets started, which then overwrites the properties file and self heals or removes that extra comman after the print task url. 

But if we were to start just primary, it will never start up. We have updated the properties.json file in both local version on the server machine and also in the shared content to remove that extra comman, but it keeps adding back. Is there a way to get rid of that extra comma somehow?

Thanks

Banchana