SAP JDBC
JDBC integration connects SAP (via middleware) to relational databases, reading from and writing to database tables directly, useful for integrating legacy or non-SAP systems that expose only a database.
Use JDBC integration when a system exposes only its database (no API), typically legacy applications.
- Through a JDBC adapter (in PI/PO or CPI), SAP integration can query and update external databases with SQL, moving data between SAP…
- JDBC adapter in the middleware.
- SQL for read/write operations.
- Watch out: a direct database connection bypasses every application check the ERP would have run.
What JDBC integration does
Through a JDBC adapter (in PI/PO or CPI), SAP integration can query and update external databases with SQL, moving data between SAP and systems that have no proper API. It is a pragmatic way to integrate database-only applications, though it couples to their schema.
Key aspects
- JDBC adapter in the middleware.
- SQL for read/write operations.
- Polling for changed data.
- Schema coupling to the target database.
When to use it
Use JDBC integration when a system exposes only its database (no API), typically legacy applications. Prefer proper APIs where available; JDBC integration is a pragmatic fallback that requires care around the target’s schema and data integrity.
Common pitfalls
- Wrong tool for the integration style.
- Ignoring monitoring/error handling.
- Point-to-point instead of governed integration.