Two-way sync
Changes in IBM AS/400 or InterSystems IRIS instantly reflect in both systems. No stale data, no manual imports.
Keep IBM AS/400 and InterSystems IRIS in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.
Two databases that must agree is one of the oldest problems in engineering: different engines for different workloads, separate services with overlapping reference data, a migration in flight, or regional instances that share a subset of records. Hand-rolled replication across systems means change capture, conflict handling, and type mapping, all built and maintained by your team.
Stacksync syncs tables or collections between IBM AS/400 and InterSystems IRIS continuously and bi-directionally, translating types between the two engines and resolving conflicts by rules you configure. Rows written on either side appear on the other within seconds.
Mirror selected tables to another region or environment continuously, filtered to just the rows that should travel.
Keep the same dataset live in both IBM AS/400 and InterSystems IRIS, so each workload runs on the engine that suits it.
When one database is replacing the other, sync both directions during the transition and switch traffic when ready, without a freeze window.
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.
| IBM AS/400 objects | InterSystems IRIS objects | |
|---|---|---|
| Physical files (tables) The Db2 for i tables mapped directly to sync targets. | Tables Relational projections of stored data are the primary read/write surface for SQL-based syncs. | |
| Logical files (views) Indexed or filtered views over physical files, usable as read sources. | Views SQL views expose curated slices of data for outbound replication. | |
| Members Sub-partitions of files in legacy applications, flattened or selected during syncs. | Schemas Schema organization scopes which tables a sync connection can see. | |
| Rows / records The unit of read and write, accessed via SQL or record-level access. | Persistent Classes Object-model classes project to tables, so class data is reachable through SQL. | |
| Journals and journal receivers The change log that enables log-based CDC on journaled files. | Globals The underlying multidimensional storage; typically accessed indirectly via SQL or objects in syncs. | |
| Data queues Program-to-program messaging objects sometimes used to hand events off to integrations. | Namespaces Namespaces partition databases and determine the connection context for integrations. |
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every IBM AS/400–InterSystems IRIS connection.
Changes in IBM AS/400 or InterSystems IRIS instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever IBM AS/400 or InterSystems IRIS data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
Handle millions of events per minute without losing a single IBM AS/400 or InterSystems IRIS record.
Track your IBM AS/400 ⇄ InterSystems IRIS sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between IBM AS/400 and InterSystems IRIS.
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.
Authenticate IBM AS/400 and InterSystems IRIS with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
Pick the IBM AS/400 and InterSystems IRIS 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.
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
Yes. Stacksync provides a managed, real-time two-way integration between IBM AS/400 and InterSystems IRIS: authenticate both systems, choose the objects to sync (such as IBM AS/400's Physical files (tables) and Logical files (views)), map fields visually, and changes propagate both ways in milliseconds — no code required.
Common patterns for IBM AS/400 and InterSystems IRIS: Regional or environment copies; Cross-engine sync; Migration with zero-downtime cutover. Mirror selected tables to another region or environment continuously, filtered to just the rows that should travel.
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). InterSystems IRIS: SQL over JDBC/ODBC, plus object and REST access layers. Authentication: Database credentials. Stacksync manages authentication, retries, and rate limits on both sides.
IBM AS/400: Character data is stored in EBCDIC with CCSID-based conversion, so syncs must handle encoding translation to Unicode. InterSystems IRIS: InterSystems positions IRIS as the successor to Caché, and it is widely deployed under healthcare and financial applications. Stacksync's field mapping accounts for these differences between IBM AS/400 and InterSystems IRIS without custom code.
Stacksync is SOC 2 Type II and ISO 27001 certified with HIPAA BAA support. Data is encrypted in transit, and a zero-persistent-storage architecture means IBM AS/400 and InterSystems IRIS records are not retained after a sync operation.
Stacksync pricing is usage-based and starts at $1,000/month, including the managed IBM AS/400 and InterSystems IRIS connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom IBM AS/400–InterSystems IRIS integration in-house.
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.
Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.
Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.
Securely connects to your systems with:
Every pair below is a real-time, two-way sync. Search all 386 integrations available for IBM AS/400 and InterSystems IRIS.