Real-time
Two-way sync
Changes in Exasol or IBM AS/400 instantly reflect in both systems. No stale data, no manual imports.
Data warehouse ⇄ Database
Exasol to IBM AS/400 integration — real-time, two-way sync
Keep Exasol and IBM AS/400 in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.
- SOC 2 and 6 other compliance frameworks
- POC with real engineers in minutes
Adopted by fast-scaling companies moving mission-critical data in real time
Case study
Migrated from MuleSoft
Case study
Migrated from Celigo
Migrated from Heroku Connect
Migrated from Matillion
Case study
Migrated from Fivetran
Case study
Migrated from Celigo
Why teams connect Exasol and IBM AS/400
Connect IBM AS/400 and Exasol with one live, two-way sync: operational rows flow into the warehouse, and computed results flow back where systems can read them fast.
Operational databases and analytical warehouses want the same data at different moments. Analysts want IBM AS/400's rows in Exasol, current and joinable, without a change-data-capture pipeline to maintain. Engineers want the outputs of warehouse work, such as aggregates, features, and segments, available in IBM AS/400 where the services that read from it get them at normal query latency.
Stacksync covers both directions with one connection. Tables or collections in IBM AS/400 sync into Exasol in real time, and result tables in Exasol sync back into IBM AS/400, with schema and type mapping between the two systems handled for you.
Common use cases
- 01 Sync computed metrics or customer segments from Exasol back into a CRM for sales and marketing use (reverse ETL).
- 02 Consolidate data from multiple operational databases into Exasol as the central analytics layer.
- 03 Keep customer and item files aligned with an ecommerce platform or modern ERP during phased modernization.
- 04 Feed shipment and invoice data from the AS/400 into logistics and finance tools in near real time.
Common sync patterns
Operational data in the warehouse, minus the pipeline
Rows from IBM AS/400 land in Exasol as they change, replacing hand-built CDC and batch extract jobs.
Serve warehouse results at database speed
Aggregates or model outputs computed in Exasol sync into IBM AS/400, where whatever reads from that database gets them without querying the warehouse.
Fresh analytics without loading windows
Because changes stream continuously, analysts query current data instead of waiting for last night's load.
What you can sync between Exasol and IBM AS/400
Representative objects on each side — any object or custom field can map to any target. Schemas are auto-detected; types are converted between the two systems.
| Exasol objects | IBM AS/400 objects | How this pairing syncs | |
|---|---|---|---|
| Views Read-only query surfaces often used as curated sources for reverse ETL. | Data queues Program-to-program messaging objects sometimes used to hand events off to integrations. | Views is specific to Exasol and Data queues to IBM AS/400 — each maps to any object or custom field on the other side. | |
| Virtual schemas Federated views over external sources; useful for deciding what needs physical replication. | Libraries The schema-equivalent containers that scope which files a sync reads. | Virtual schemas is specific to Exasol and Libraries to IBM AS/400 — each maps to any object or custom field on the other side. | |
| UDF scripts In-database functions that can transform synced data after load. | Physical files (tables) The Db2 for i tables mapped directly to sync targets. | UDF scripts is specific to Exasol and Physical files (tables) to IBM AS/400 — each maps to any object or custom field on the other side. | |
| Users and roles Grant read/write access for the dedicated integration account. | Logical files (views) Indexed or filtered views over physical files, usable as read sources. | Users and roles is specific to Exasol and Logical files (views) to IBM AS/400 — each maps to any object or custom field on the other side. | |
| Schemas Namespaces that group the tables a sync reads from or writes into. | Members Sub-partitions of files in legacy applications, flattened or selected during syncs. | Schemas is specific to Exasol and Members to IBM AS/400 — each maps to any object or custom field on the other side. | |
| Tables Primary sync target; columnar relational tables written with standard SQL. | Rows / records The unit of read and write, accessed via SQL or record-level access. | Tables is specific to Exasol and Rows / records to IBM AS/400 — each maps to any object or custom field on the other side. |
How changes propagate between Exasol and IBM AS/400
Each direction of the sync is driven by what the source system can signal and what the destination accepts — detection, delivery, and expected latency below.
Exasol IBM AS/400 Interval-based propagation
DetectionStacksync polls Exasol for changes on an incremental schedule, reading only records changed since the previous pass. Polling with timestamp or key columns.
DeliveryEach detected change is applied to IBM AS/400 as a row-level write, with types converted between the two schemas.
IBM AS/400 Exasol Sub-second propagation
DetectionChanges in IBM AS/400 are captured at the source via change data capture — no polling loop against its API. Journal-based CDC by reading journal receivers on journaled files.
DeliveryEach detected change is applied to Exasol as a row-level write, with types converted between the two schemas.
Rate-limit considerations
- Exasol: No API quota; concurrency is bounded by cluster resources and session limits.
- IBM AS/400: Bounded by system resources and subsystem configuration rather than an API quota.
What ships with Exasol ⇄ IBM AS/400
Connect Exasol and IBM AS/400 for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Exasol–IBM AS/400 connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Exasol or IBM AS/400 data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
At scale
Event queues
Handle millions of events per minute without losing a single Exasol or IBM AS/400 record.
Observability
Monitoring
Track your Exasol ⇄ IBM AS/400 sync health, view errors, and replay failed events in one click.
Trading partners
EDI
Transform legacy EDI complexity into simple database interactions between Exasol and IBM AS/400.
How the Exasol and IBM AS/400 connectors work
Exasol
- Integration surface
- SQL over JDBC/ODBC drivers and a WebSocket-based client protocol
- Authentication
- Database credentials (username and password)
- Change detection
- Polling with timestamp or key columns; Exasol does not expose a transaction-log change feed to clients
- Capabilities
- read · write
- Rate limits
- No API quota; concurrency is bounded by cluster resources and session limits
IBM AS/400
- Integration surface
- SQL over JDBC/ODBC to Db2 for i (for example the JTOpen/jt400 driver), alongside native record-level access
- Authentication
- IBM i user profile credentials (database credentials)
- Change detection
- Journal-based CDC by reading journal receivers on journaled files; polling as a fallback
- Capabilities
- read · write · CDC
- Rate limits
- Bounded by system resources and subsystem configuration rather than an API quota.
How it works
How to connect Exasol to IBM AS/400 — three steps, no code
Configure and sync within minutes, no code. Whether you sync 50k or 100M+ records, Stacksync handles the queues, infra, and plumbing. Integrations are non-invasive and need zero setup on your systems.
- 01
Connect your apps
Authenticate Exasol and IBM AS/400 with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
Exasol
connected
IBM AS/400
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Exasol and IBM AS/400 objects to sync — Stacksync auto-detects both schemas, including custom fields where the platform exposes them. Sync to existing tables, or let Stacksync create new ones with ideal data types.
objects · Exasol ⇄ IBM AS/400Customers 12,480Sales Orders 8,213Invoices 5,902Items 1,344 - 03
Map fields
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
Exasol IBM AS/400Company company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Exasol and IBM AS/400 integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Exasol and IBM AS/400: authenticate both systems, choose the objects to sync (such as Exasol's Views and Virtual schemas), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
On the Exasol side: Virtual schemas, UDF scripts, Users and roles, Schemas, plus custom fields where Exasol exposes them. On the IBM AS/400 side: Libraries, Physical files (tables), Logical files (views), Members. Stacksync auto-detects both schemas and converts types between the two systems.
-
Yes. Each object mapping can be bidirectional or restricted to a single direction (both systems accept writes). Read-only mirrors, one-way pushes, and full two-way sync can be mixed in the same integration.
-
Common patterns for Exasol and IBM AS/400: Operational data in the warehouse, minus the pipeline; Serve warehouse results at database speed; Fresh analytics without loading windows. Rows from IBM AS/400 land in Exasol as they change, replacing hand-built CDC and batch extract jobs.
-
Exasol: SQL over JDBC/ODBC drivers and a WebSocket-based client protocol. Authentication: Database credentials (username and password). IBM AS/400: SQL over JDBC/ODBC to Db2 for i (for example the JTOpen/jt400 driver), alongside native record-level access. Authentication: IBM i user profile credentials (database credentials). Stacksync manages authentication, retries, and rate limits on both sides.
-
Exasol: Exasol is an in-memory, columnar MPP database that creates and maintains indexes automatically based on query patterns, rather than requiring manual index design. IBM AS/400: The integrated database is Db2 for i; tables are physical files organized into libraries, with logical files acting as views. Stacksync's field mapping accounts for these differences between Exasol and IBM AS/400 without custom code.
SECURITY
Security teams trust Stacksync
As a data company, we understand the importance of keeping your data secure. Stacksync is built with security best practices to keep your data safe at every layer, and is DPF-certified for US, EU, UK and CH data transfers.
SOC 2 Type II
ISO 27001
HIPAA BAA
GDPR
CCPA
DPF US-EU-UK-CH
→ SECURITY WITH BENEFITS
SSO & SCIM
Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.
Alerts
Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.
Secure connection options
Securely connects to your systems with:
Related integrations
Every pair below is a real-time, two-way sync. Search all 361 integrations available for Exasol and IBM AS/400.
Popular · 2 of 361
No integrations match .
