Legacy permit tables to GIS
Permits in an older Oracle-based system are read nightly and added to an ArcGIS layer, with no change to the old application.
Oracle Database sits behind many city permitting, utility billing, ERP and lab systems, often on servers inside the city network. Integrations have traditionally meant custom scripts, database links or nightly exports.
SentraBridge reads Oracle tables and views (12c and later, including 19c and 23ai, now 26ai) and writes with insert, update or upsert, including SDO_GEOMETRY points for GIS. Flows can start when rows change using a changed-at column. The relay reaches internal servers without inbound firewall rules.
| resource | read | write | changes only | fields |
|---|---|---|---|---|
| Tables | read a table or a read-only query | insert, update, upsert | yes (changed-time column) | Any table you grant |
Permits in an older Oracle-based system are read nightly and added to an ArcGIS layer, with no change to the old application.
Account and payment views are copied to PostgreSQL so analysts don't query the production billing database.
Work orders created in an Oracle-backed system start a flow that updates the resident's Sentra 311 request.
A view is exported as a dated CSV to SFTP for a vendor that needs a daily file.
Systems cities commonly connect with Oracle Database, each with its own connector page.
Yes. The relay runs on your network next to the database and only calls out to SentraBridge over HTTPS. You list which hosts it may reach.
Oracle Database 12c and later, including 19c and 23ai (now Oracle AI Database 26ai). Connect with the service name, not the SID.
Yes, with a changed-at column. SentraBridge reads rows changed since the last good run.
We'll set up a workspace with your systems in a sandbox and build your first flow with you.