infoConnect for Kafka 
Composed of three connectors with source and sink capabilities, Infoview’s infoConnect can be used with Kafka open-source and Confluent enterprise to exchange events between IBM i and Kafka
Data Replication
Real-time bi-directional integrations
- Enable event-based use cases with homegrown or commercial IBM i applications
- Exclusively for IBM i (AS/400, iSeries) based systems
- Does not require IBM i expertise to leverage
- Supports data replication functionality with DB2
Complementing Professional Services Assistance
Architectural advisory
Middleware platform implementation
Platform and Application Support
System integration
Custom connector development
infoConnect product implementation
Source and Sink Operations
Works with RPG and COBOL Languages
- Data queue source: Read data queue data and publish to a Kafka topic
- Data queue sink: Polls data from Kafka topic and publishes to IBM i data queue
- Program call sink: Writes to IBM i data queue, calls IBM i programs, and maps program call parameters
infoConnect for Kafka: IBM i (AS400) Connector Suite for Real-Time Event Streaming
Confluent-Certified Source and Sink Connectors – Built Exclusively for IBM i (AS400)
infoConnect for Kafka is a suite of three Confluent-certified connectors with source and sink capabilities, designed exclusively for IBM i and AS400 systems. It runs as a plug-in within the Kafka Connect runtime, on-premise, cloud, or Confluent Hub, with no performance impact on the IBM i itself and no IBM i development expertise required to operate. Both Apache Kafka open-source and Confluent Enterprise stacks are supported out of the box.
Real-Time IBM i Event Streaming, DB2 Data Replication, and Program Calls via Kafka
The connector suite covers three core IBM i operations through Kafka. The data queue source connector reads IBM i data queue messages and publishes them to Kafka topics. The data queue sink connector polls Kafka topics and writes back to IBM i data queues. The program call sink connector goes further, writing to data queues, calling IBM i programs directly, and mapping program call parameters. When paired with infoCDC, DB2 table change events are delivered to Kafka topics in near real time with no custom IBM i or Kafka development.
Why infoConnect for Kafka Outperforms JDBC Connectors and Generic IBM i Alternatives
Unlike JDBC connectors, infoConnect for Kafka enables true bi-directional integration between IBM i and Kafka in real time with no time lag, no additional application servers, and no code generation. The connector resides entirely within the Kafka or Confluent platform, leaving zero footprint on the IBM i system. Organizations can start with a 30-day free trial, run a consultant-scoped POC, or engage Infoview’s team for full Rapid Start implementation. Pricing is based on physical IBM i server count only, with no restrictions on transaction volumes or endpoints.
Feature Comparisons at a Glance
| InfoConnect by Infoview Systems | Other market solutions |
|---|---|
| Supports API enablement as well as data replication and green screen automation functionality when paired with infoCDC and/or infoRPA | Offers just API enablement capabilities |
| Supported by a global team of IBM i, middleware (MuleSoft, Confluent/Kafka, AWS) and integration professionals | Supported by a team of primarily IBM i professionals who may not have cross-platform experience in middleware platforms |
| Connector resides within Kafka / Confluent platform with no performance degradation on the IBM i system directly | May reside on the IBM i and cause system impact |
| Requires no additional infrastructure to leverage | May require additional infrastructure to implement |
| Connector operations do not require a background in RPG or IBM i based development | Often requires at least some background in IBM i development to use and implement |
| Supports Confluent Enterprise and Kafka open-source | May not support middleware functionality right “out of the box” and could require custom development or multiple third-party products |
| Minimal implementation timelines – little to no training required for end customer teams who will own product operations | Can take longer to implement and often requires specialized training for owners of product operations |
| Priced quite fairly for mid-market to enterprise firms with no restrictions on transaction amounts or endpoints | Often priced for enterprise sized firms or based on transaction amounts |
Flexible Proof of Concept Models
Infoview Ownership and Implementation
Our Team would implement the desired use cases including full alignment with your team’s Kafka/Confluent and IBM i development guidelines, best practices, integration architecture review, adoption for IBM i integration, IBM i development and configuration, as well as go-live support
The end result would entail working integrations deployed to production in addition to knowledge transfer sessions with the client team members who would take ownership of the implemented components and integrations. The benefits of this approach would be quick implementation and a solid launch point for future IBM i integration projects. In terms of duration, this would typically last 2-3 months and require a formal SOW depending on complexities and expectations. Additionally, this method would require a commercial connector license by the time the project goes live.
Common Integration and Streaming Use Cases
Real time IBM i Data Replication pipeline – works natively with InfoCDC and delivers data change events from InfoCDC Replication Queues to Kafka topics and on to the targets with no custom IBM i or Kafka development
Frequently asked questions
Functionality, compatibility, and pricing
-
How does the connector work?
Via low-level socket-based connections, facilitated via IBM toolbox library. The connector works as a plug-in within the Kafka Connect on-premise, cloud, or Confluent Hub runtime. -
Intent for the products creation?
We wanted to provide Kafka development teams with an easy way to connect their IBM i based systems to Kafka without any special knowledge of IBM i, and without a need to implement and operate another piece of middleware software. -
How is the product priced?
Pricing is based on the number of physical IBM i servers leveraged regardless of server type (production, non-production, DR). For additional pricing and subscription information, please reach out to our team. -
Compatibility with commercial off the shelf IBM i backend systems?
The connector can be used to execute business logic or exchange messages with IBM i based commercial applications -
Compatibility with Confluent Suite?
The Kafka Connector Suite can indeed be leveraged on both Confluent and Apache Kafka stacks, the only difference is that the implementation and configuration steps will be slightly different for the Confluent suite -
Kafka vs JDBC connectors
When leveraging a JDBC connector, changes cannot be captured in real-time, leading to an inevitable time lag. The infoConnect for Kafka enables bidirectional integration directly from Kafka and the IBM i without any additional application servers or code generation in real-time. Furthermore, some database models are complex and additional rules must be applied, in this case our products ability to call back programs instead of replicating business logic in the integration layer is a feature customers have found useful. -
What security comes standard with the connector?
The connector supports SSL, SASL, and ACL as part of the certification process. Each iteration of the connector undergoes security review by the Confluent team.
infoConnect for Apache Kafka Demonstration
Connector suite configuration and Salesforce demonstration
Subscription Models, Delivery, and Support
Available for download on the Confluent Hub. Requires a license available directly through Infoview Systems.
- Standard:During the entirety of the subscription term, support will be provided entailing product deployment, error/bug resolution, best practice advice, as well as subsequent product releases
- Priority:Expedited incident resolution, bug fixes, and small enhancements. Unused support hours can be rolled over for the following month.
- Priority 24×7: Support engineer available for incident resolution during standard business hours and on-call rotations for all nights/weekends/holidays. Unused support hours are rolled over to the following month.
- Dedicated 24×7: A dedicated support engineer is online and ready to jump in at any point in time, day or night. Time outside incident resolution can be used for any additional project work.
Learn more about Infoview’s Kafka Connector Suite
Connector Overview
Confluent Cloud Hub Listing
User Guide
License Agreement
Launch Announcement
Product Support & Maintenance Terms