It seems the CreateGISServerConnectionFile() function was not implemented in ArcGIS Pro. It would be nice to have this available. Here is evidence this is requested from other users.
This needs to be implemented, I should not have to click buttons in ArcPro to create a connection file.
We have a multi environment platform, and need the ability to deploy services to different environments in an automated manner.
This step is the only thing that we have to do manually... not scalable, repeatable, or efficient.
There is a workaround: https://community.esri.com/t5/arcgis-pro-questions/how-to-create-an-arcgis-server-connection-file/td...
import arcgisscripting arcgisscripting._createGISServerConnectionFile("ADMINISTER_GIS_SERVICES", "C:/admin", "new.ags", "https://maxscoolserver.org/raster", "ARCGIS_SERVER", True, "C:/admin", "sitemanager", "password123")
But ESRI should implement this within arcpy, so this idea is still valid.
Using an undocumented and unsupported function is generally a bad idea. There is a reason it is prefaced with an "_"
Add to the fact that it doesn't accept keyword arguments - only positional arguments - so you have to guess what those positions are and hope they haven't change...
Throw in that since it is proprietary closed source python, if it fails you have pretty much no way to troubleshoot it...
At best this is a "temporary hack" (over 2 years now?!?).
If this function is implemented for ArcGIS Pro, we would like it to include the option to save credentials to the Credential Manager (an option that is available when you manually add a server connection). This would allow us to easily set up access to standalone ArcGIS Servers for all users at our organization.
I would like to see this functionality ported to ArcGIS Pro.
We have an automated process to publish dozens of map services to a standalone ArcGIS Server deployment. We have to manually create an ags connection file for the many environments this routine publishes to. Would be great to have this function back in the ArcGIS Pro arcpy library. I second the ability to store credentials with the connection file.
I will explore the suggestion above using the private function but hesitant to use it in a production setting.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.