Two-way sync
Changes in IBM AS/400 or Xactly instantly reflect in both systems. No stale data, no manual imports.
Keep IBM AS/400 and Xactly in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.
Product and engineering teams constantly need CRM data, and the CRM API is a poor way to get it: rate limits, pagination, custom objects, and integration code that breaks when an admin renames a field. What they actually want is the data in IBM AS/400, where it can be queried and joined like everything else.
Stacksync mirrors Positions & Titles, Quotas / Targets, Payment Summary (Payable), Products & Customers from Xactly into Data queues, Libraries, Physical files (tables), Logical files (views) in IBM AS/400 with real-time, bi-directional sync. Read CRM records with plain queries; write updates from your application and they appear in Xactly with validation intact. Go-to-market teams keep working in the CRM, engineers keep working in the database, and neither has to think about the other.
Signup, usage, or lifecycle changes written to IBM AS/400 sync onto the matching records in Xactly, giving go-to-market teams live product context.
Back-office apps read and write the synced tables; Stacksync handles the Xactly API, limits, and retries.
Field and stage updates in Xactly arrive as row changes in IBM AS/400, ready to drive jobs and notifications.
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 | Xactly objects | How this pairing syncs | |
|---|---|---|---|
| Physical files (tables) The Db2 for i tables mapped directly to sync targets. | Quotas / Targets Period quota and target values per position or plan; loaded from planning tools through Connect (write) and read for attainment reporting, so read and write. | Physical files (tables) is specific to IBM AS/400 and Quotas / Targets to Xactly — each maps to any object or custom field on the other side. | |
| Logical files (views) Indexed or filtered views over physical files, usable as read sources. | Payment Summary (Payable) Approved payable amounts per participant per period; read as the output that feeds payroll and accounts payable, so effectively read-only. | Logical files (views) is specific to IBM AS/400 and Payment Summary (Payable) to Xactly — each maps to any object or custom field on the other side. | |
| Members Sub-partitions of files in legacy applications, flattened or selected during syncs. | Products & Customers Product and customer/account master used in crediting rules and reporting; loaded and updated from CRM/ERP through Connect (write) and read for lookups, so read and write. | Members is specific to IBM AS/400 and Products & Customers to Xactly — each maps to any object or custom field on the other side. | |
| Rows / records The unit of read and write, accessed via SQL or record-level access. | Orders Sales order and transaction records loaded into Incent as the raw input for crediting and calculation; created and updated through Connect load and ETL steps (write) and read back for reconciliation, so read and write. | Rows / records is specific to IBM AS/400 and Orders to Xactly — each maps to any object or custom field on the other side. | |
| Journals and journal receivers The change log that enables log-based CDC on journaled files. | Credits Crediting records that tie an order to a participant and position; system-calculated credits are read, while manual and adjustment credits are loaded through Connect, so read and write. | Journals and journal receivers is specific to IBM AS/400 and Credits to Xactly — each maps to any object or custom field on the other side. | |
| Data queues Program-to-program messaging objects sometimes used to hand events off to integrations. | Transactions (Commission & Bonus) Calculated commission and bonus line items produced by Incent's calculation engine; read as the output of comp runs for reporting and downstream payout, so effectively read-only results. | Data queues is specific to IBM AS/400 and Transactions (Commission & Bonus) to Xactly — each maps to any object or custom field on the other side. |
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.
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 Xactly as a row-level write, with types converted between the two schemas.
DetectionStacksync polls Xactly for changes on an incremental schedule, reading only records changed since the previous pass. No CDC log for external tools to consume.
DeliveryEach detected change is applied to IBM AS/400 as a row-level write, with types converted between the two schemas.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every IBM AS/400–Xactly connection.
Changes in IBM AS/400 or Xactly instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever IBM AS/400 or Xactly 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 Xactly record.
Track your IBM AS/400 ⇄ Xactly sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between IBM AS/400 and Xactly.
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 Xactly 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 Xactly 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 Xactly: 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.
Yes — Stacksync ships production-grade connectors for both IBM AS/400 and Xactly. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
Change detection on IBM AS/400: Journal-based CDC by reading journal receivers on journaled files; polling as a fallback. On Xactly: No CDC log for external tools to consume. Incremental sync uses SQL predicates on modified/last-updated timestamp columns (for example WHERE modified_date > watermark) against Connect's queryable objects, or scheduled Connect ETL Pipelines that pull deltas since the last run. Xactly Connect has no outbound HTTP webhooks, so change detection is pull/ETL-based. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
On the Xactly side: Positions & Titles, Quotas / Targets, Payment Summary (Payable), Products & Customers, plus custom fields where Xactly exposes them. On the IBM AS/400 side: Data queues, Libraries, Physical files (tables), Logical files (views). 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 IBM AS/400 and Xactly: Product events onto CRM records; Internal tools without API code; Trigger workflows from CRM changes. Signup, usage, or lifecycle changes written to IBM AS/400 sync onto the matching records in Xactly, giving go-to-market teams live product context.
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 456 integrations available for IBM AS/400 and Xactly.