Select to view content in your preferred language

Recommended .aprx location when publishing a feature service

1505
5
Jump to solution
02-01-2024 02:01 PM
Labels (2)
AndreaB_
Frequent Contributor

Hello all,

We are using ArcGIS Pro to publish feature services. The default .aprx save location is the user's C drive on their own computer. We typically don't ever use that - seems like a very bad idea. Usually we save aprxs in a mapped letter drive folder on our server that multiple people can access (network file share). For a short time we are going to have file share folders unavailable as we switch entire networks. What do you think about saving the .aprx on the C drive of the GIS Server in the new environment and publishing the feature services from there? Would that work? I can't think of why not, but wanted to ask all of you.

Data connections will be referenced to the SQL geodatabase so no problems accessing the data.

Thanks.

0 Kudos
2 Solutions

Accepted Solutions
ZachBodenner
MVP Regular Contributor

That doesn't sound like an issue to me. I've used local server publishing for things like aerial imagery, and if that works I can't imagine why a regular old feature service wouldn't. Smart to keep your .aprx's on a mapped drive, that's how we do it as well. I would imagine your server is backed up regularly, so even if something weird happens you should be protected.

Happy mapping,
- Zach

View solution in original post

RanaDas
Regular Contributor

Hi @AndreaB_ 

It is not required to publish/overwrite the service again. During a publishing activity the publishing tool creates a MAP file and Service definition file in the in the arcgisinput directory. The service will continue to work even if the location (where you save the project) of the .aprx is not connected, as it has nothing to do with the file.

You will face issues with the service if the published service has referenced data which is stored in the network drive. If you have such services, you shall have to repoint and register the path of the referenced data in a location that is accessible by ArcGIS Server and has sufficient privilege to the Server Service account.

You can verify the path in installation directory of your ArcGIS Server.

RanaDas_0-1706852514548.png

Hope this helps.

 

 

View solution in original post

5 Replies
ZachBodenner
MVP Regular Contributor

That doesn't sound like an issue to me. I've used local server publishing for things like aerial imagery, and if that works I can't imagine why a regular old feature service wouldn't. Smart to keep your .aprx's on a mapped drive, that's how we do it as well. I would imagine your server is backed up regularly, so even if something weird happens you should be protected.

Happy mapping,
- Zach
RanaDas
Regular Contributor

Hi @AndreaB_ 

It is not required to publish/overwrite the service again. During a publishing activity the publishing tool creates a MAP file and Service definition file in the in the arcgisinput directory. The service will continue to work even if the location (where you save the project) of the .aprx is not connected, as it has nothing to do with the file.

You will face issues with the service if the published service has referenced data which is stored in the network drive. If you have such services, you shall have to repoint and register the path of the referenced data in a location that is accessible by ArcGIS Server and has sufficient privilege to the Server Service account.

You can verify the path in installation directory of your ArcGIS Server.

RanaDas_0-1706852514548.png

Hope this helps.

 

 

AndreaB_
Frequent Contributor

Great! Good information from both of you. Thanks!

0 Kudos
ZachBodenner
MVP Regular Contributor

You bet! Remember you can accept more than one solution if you found @RanaDas 's additional info helpful!

Happy mapping,
- Zach
0 Kudos
AndreaB_
Frequent Contributor

ooh, did not know that. 😊

0 Kudos