Databases (JDBC)

Some data only exists inside a database: an on-premise ERP’s SQL Server, an Oracle instance behind a VPN, a PostgreSQL read replica with no API in front of it. Database sources are served by RWS Connect: we build a managed pipeline that extracts from your database and exposes it through the RWS Connect API, a simple REST API that your integrations extract from like any other modern API.

​

Supported databases

Any JDBC-compatible database. Common examples:

• SQL Server
• Oracle
• PostgreSQL
• MySQL / MariaDB
• IBM DB2
• Firebird
• Sybase

If your database speaks JDBC, RWS Connect can extract from it.

​

When to use

• The system holds its data in a database but exposes no API
• You have (or can create) a read-only user or a read replica
• The database sits on-premise or behind a VPN
• The data you need is the result of a SQL query across several tables

​

How it works

1. RWS Connect connects to your database over JDBC, through a VPN when needed
2. The pipeline runs the agreed queries on the agreed schedule and writes the results to structured tables
3. Your integration extracts the tables through the RWS Connect API, like any other REST source

Everything the platform offers for API extractions works unchanged: pagination, dynamic parameters, business rules and scheduling.

​

What you provide

​

Requesting the connector

Email connect@rwsintegration.com with the items above to open a ticket.

​

How your data appears

• One table per source table or query, named as agreed in the ticket
• Columns in snake_case
• When the pipeline joins several source tables into one dataset, each column is prefixed with the table it came from, and every record is delivered as a single flat JSON object (see Column prefixes)
• Every run adds a snapshot stamped with the extraction date, so history is preserved
• Standard columns on every table: extracted_at, extraction_date, extract_start_date_parameter, extract_end_date_parameter

​

Next steps