ArcGIS Server Feature Service Writer

FME Currently has a arcgis portal and arcgis online feature service writer. Are you suggesting that this feature service writer would publish data directly onto the arcgis server that is not federated with arcgis portal to host it? With feature services, I usually store the data in an SDE Database so this wouldn't help the use case since the data is being dynamically pulled at the database level.

Would be nice to support the API completely (add/update/delete features). Isn't this already built in partially as the ArcGIS Online updater a bit?

I think it would be great if FME could help those who are looking to batch process map service processes. This would be great for migrating to new environments. My idea is something along the lines of this:

1. Create a function reads your map document (MXD) and creates the draft service definition
2. AnalyzeForSD to analyze your draft service definition for errors that might prevent its publishing.
3. Run the Stage Service geoprocessing tool on your draft service definition. This converts your draft into a service definition (.sd) that is ready to publish to ArcGIS Server.
4. Run the Upload Service Definition geoprocessing tool to publish your service definition as a service.

This might be out of scope for FME and better served using python but I would much rather be using FME for this process

That's correct, so likely useful for smaller sites only and may have a limited lifespan.

Useful firstly where data needs to go up to the server, and not have a registered data source as Adriano mentions, and of course also where service MXDs or ArcGIS Pro projects are amended so the service definition has to change, or for sharing/security changes. Automating service publishing is always going to feel like a good idea! Overwriting would also be great.

I see it that it allows one to potentially smooth and integrate into one workspace what can be a time-consuming and overly manual process, for example in translating external data or data created by others internally into central geodatabases/SDE and then serving up, particularly where a data source cannot be registered and a WMS/WMTS service is not available to consume directly. Just throwing up some possibilities.

One possible limitation I see is that ESRI are promoting Data Store a lot, without this it really limits what you can publish to server/portal. I don't know all of the ins and outs but it's worth bearing in mind.

We have a use case for such Feature Service Writer directly out of FME Server: We have numerous external APIs which contribute feature attributes to a given spatial dataset. Our objective would be to connect the spatial dataset together with the APIs and output a Feature Service registered with Enterprise Portal and Federated Server without having to export the data periodically to a registered datasource (i.e. Db.)

Essentially we want FME Server to respond similarly to how Server Object Interceptors work for data enrichment, except as a backend REST call instead of an intermediary ArcServer call. As of the time of this writing SOIs cannot be used for such things as map service theming because the SOI operates too late in the delivery pipeline. Conversely, FME Server could integrate themeable attributes early in the pipeline.

Related idea: https://community.safe.com/s/bridea/a0rDm000000CbF2IAK/arcgis-portal-feature-service-writer-editing-options-and-specify-server-folder?t=1670966083807&orderby=Recent