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

infoConnect product implementation

System integration

Custom connector development
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
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



Frequently asked questions
Functionality, compatibility, and pricing
-
How does the connector work?
-
Intent for the products creation?
-
How is the product priced?
-
Compatibility with commercial off the shelf IBM i backend systems?
-
Compatibility with Confluent Suite?
-
Kafka vs JDBC connectors
-
What security comes standard with the connector?
infoConnect for Apache Kafka 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.