GeoEvent process Oracle/SQL connector

Question

Hi

My requirement is to display Oracle/SQL Server  Lat/Long real time data on map. The displayed data need to be stored in destination table (Feature Layer) as historical/Temporal. So that user can see,at what time what incident happen.

Is there any connector for this or any helpful document/tutorial available.

Please pass the required information.

Thanks,

Arun

RJSunderman · Answer

You do have a few options available, however, without relying on an ODBC / JDBC connector:

Here's another trick that a customer described to me. If you know an RDBMS wizard, ask them to help you create a spatial view of your data. ArcGIS can use a spatial view in the same way as it uses a feature class, so you can publish a spatial view as an ArcGIS feature service.

This can provide you a great deal of flexibility. You have complete control over your spatial view, such as joins you want to perform with other tables in your database or limiting the data exposed through the spatial view to the "most recent five minutes". The feature service will appear to be automatically updating to display the most recent data - but the back end database is doing all the work. And you now have the ability to query the feature service using endpoints exposed through the ArcGIS REST Services Directory.

I'm not an RDBMS wizard and thought this approach was absolutely brilliant.

- RJ

VinceAngelo · Answer

Feature services generally require a rowid column (32-bit integer, NOT NULL, with unique values) in addition to a geometry column.  If the views contain only string columns, they cannot be Feature Service ready.  You should probably ask a new question in an appropriate location (Managing Data, Geodatabase, ArcGIS Server), because branching this now would be too confusing.

- V

BrunoMendes · Answer

Sunderman,

We have two RDMS which we would like to integrate GeoEvent with.

I've done step 1 successfully with our view on SQL Server.

When I tried the same thing with an Oracle view, the tool says the feature service cannot be published due to one or more tables that are not supported.

In both cases our views have only textual data.