Skip to content

Tutorials and examples

Use these end-to-end scenarios and examples to build your own IBM i change data capture pipeline. They are grouped by the product combination that they use.

InfoCDC and InfoConnect Hub

Scenario What you learn
IBM i data replication to databases Replicate IBM i tables directly to a JDBC database with a Data Flow. Covers automatic table creation, batching, errors and retries, and supported databases.
Replicating many tables with one Data Flow Carry the changes of many tables in one data queue and write each table to its own target table.
Custom SQL templates Control how change events are written to the target database, with an example.
Example: DB2 replication with InfoCDC and the AWS stack Replicate IBM i data through an Amazon SNS topic and an AWS Lambda function.
File sinks for Data Flows Deliver change records as files to cloud storage or SFTP, with examples.
Dynamic data publishing Route the changes of each table to a separate queue, topic, or event hub.
Data Flow states and errors Recover a failed or invalid Data Flow.

InfoCDC and InfoConnect for Kafka

Scenario What you learn
Sample stand-alone Confluent Docker setup Run a Kafka broker, Schema Registry, Kafka Connect, and the InfoConnect connectors in Docker.
Source connector samples Configure the source connector with the JSON, JSON Schema, and Avro converters.
Routing messages from a single data queue to multiple topics Send the changes of many tables from one data queue to a topic per table.
Custom single message transforms (SMTs) Delete records by event type and reorder the columns in the payload.
Storing the license and truststore certificate in a topic Keep the license and the truststore in a Kafka topic instead of on a file system.
Confluent Cloud as a custom connector Upload the connectors to Confluent Cloud.

InfoCDC and InfoConnect for MuleSoft

Scenario What you learn
Configuring the Data Queue Listener Start a Mule flow when a change arrives in the InfoCDC data queue.
Configuring the Data Queue Reader Read messages from a data queue inside a flow.