OAC Connectivity: Remote Data Gateway & Cloud Data Sources

Explain how OAC connects securely to on-premise data sources via the Remote Data Connector/Gateway, alongside native cloud data source connectivity.

A cloud-hosted analytics service still frequently needs to query data that lives behind an on-premise firewall — a company's core transactional database isn't simply moved to the cloud just because the BI tool is — and OAC solves this with the Remote Data Gateway (formerly called the Remote Data Connector), a topic interviewers use to test whether a candidate understands real hybrid-cloud deployment constraints, not just cloud-native connectivity.

It's like a hotel room's safe that only opens from the inside — the on-premise gateway reaches out to check in with the cloud service itself, rather than the cloud service trying to reach in through a door the customer's IT security team would never agree to unlock from the outside.

Key Concepts

The Remote Data Gateway is a lightweight agent installed inside the customer's own network, alongside or near the on-premise data source, that establishes an outbound-only connection to OAC in the cloud — critically, this means the customer's firewall doesn't need to open any inbound port to the internet, since the gateway initiates the connection outward and OAC routes query requests through that established tunnel. This is a common interview detail because it directly answers the security objection every enterprise network team raises first: "you want us to expose our database to the internet? No." The gateway is registered in OAC, and once configured, on-premise sources appear as connectable data sources just like any native cloud source, from the end user's perspective.

inside the customer's own networkoutbound-only connection

For purely cloud-native sources, OAC provides direct connectors to Oracle Autonomous Database, Object Storage, Fusion Applications (SaaS), and various third-party cloud databases/warehouses and applications, typically authenticated via stored credentials or OAuth, without needing any gateway at all since these sources are already internet-reachable (through appropriate network/security configuration).

A senior-level distinction to raise: the choice between live/direct query connections versus extracting data into an OAC dataset (a cached snapshot) is a performance and freshness trade-off similar to OBIEE's caching discussion — live connections always reflect current on-premise data but are bounded by gateway/network latency and the source database's own load, while dataset extracts are fast to visualize against but require a refresh schedule to stay current.

live/direct query connectionsextracting data into an OAC dataset