Entendemos que al publicar una hosted feature layer siguiendo esta instrucción, Publicar hosted feature layers013 Portal for ArcGIS | Documentacif3n para ArcGIS Enterprise<\/A>, los datos se almacenan en "ArcGIS Data Store." <\/P><\/P>Pero en el caso de subir un FDGB, ¿los datos terminan en un RDBMS tras bambalinas o los datos se almacenan realmente en una carpeta accesible para los servicios del portal? <\/P><\/P>Si la respuesta es la primera, como sospechamos, ¿significa eso que ArcGIS Data Store incluye un motor RDBMS como Postgresql? No instalamos ningún RDBMS como parte de la instalación de enterprise, ni pudimos encontrar servicios RDBMS en la máquina host. Así que estamos desconcertados...<\/P><\/P>Gracias!<\/P><\/P>Bo <\/P><\/BODY><\/HTML>
<\/P>
Pero en el caso de subir un FDGB, ¿los datos terminan en un RDBMS tras bambalinas o los datos se almacenan realmente en una carpeta accesible para los servicios del portal? <\/P>
Si la respuesta es la primera, como sospechamos, ¿significa eso que ArcGIS Data Store incluye un motor RDBMS como Postgresql? No instalamos ningún RDBMS como parte de la instalación de enterprise, ni pudimos encontrar servicios RDBMS en la máquina host. Así que estamos desconcertados...<\/P>
Gracias!<\/P>
Bo <\/P><\/BODY><\/HTML>
You are correct, a Base ArcGIS Enterprise installation includes Portal, Hosted ArcGIS Server, Relational Data Store, and optionally Web Adaptor.
Relational Data Store does in-fact leverage PostgreSQL server under the hood, so to speak, but it runs under the Data Store Windows Service and you'll also see some PostgreSQL tasks running on the host machine in Task Manager. The software manages the PostgreSQL and does not require any intervention in most cases. In the case of your file geodatabase, the data is loaded to the Relational Data Store and served out by the hosting ArcGIS Server. The file geodatabase itself is also stored in the Portal Content Store as it is considered a separate item.
Each of the 3 Data Store types utilizes a different engine, each was chosen based on the kind of data.
Since you are one of the product leaders, if I may cross-post from Updating Hosted Layer from Enterprise GDB - Esri Community
Jacob - Does SDE sync to hosted feature layers out of the box now? In other words does it or can it push data? We have 10.9.1, that would be wonderful. But even if it's 11.3 or coming to 11.4 or 11.5 that would be great to hear.
In a perfect world, hosted feature layers would act just like a referenced service pointing to SDE. Is that how it works in Enteprise 11.x? I am guessing no? I see a script above, to copy data. What if the schema changes? Also I am wary of python bandaids on the Esri stack unless it's the only way. Basically, wouldn't it be great if the hosted feature layer was an exact twin of the SDE layer? And the second data changes on SDE, it would push. Or perhaps push on a specified syncing schedule. Same thing with schema, if it changes, sync it, done. I am guessing... no. I'm not sure I see the point of hosted feature layers in this case. Vector tiles are great but it's too much work to leverage. Frankly I wish Esri had implemented hosted feature layer functionality natively in SDE. My guess, it was too much work to support multiple RDBMSs (SQL Server, Oracle, others). Which is understandable. But, we need some way of relying on hosted feature layers mirroring SDE. Possible? Or, is it coming?
And sidenote, hopefully, one day vector tiles will support featureServer cabilities, ie Identify/Query. (basically both things put together in one endpoint, one service sublayer, not two different REST endpoints doubling the amount of layers in an app)
Thank you for input or guidance.
I think for now, I'm going to re-architect our current situation, where we have several databases and no versioning.. to Posting all DBs into the Default, and keep that Protected, at the top, so that I can point map viewers to this for read-only services. Because ..... FeatureServer services require ALL layers to be from one singular database connection. (I always wondered why that was the case, but at least as of 10.91 that seems to be required still). One reason is so labels for all layers can be aware of each other in terms of placement.
Los miembros registrados pueden publicar, seguir actualizaciones y más. ¿Nuevo aquí? Regístrate gratis.
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.
