Studio Project workflows for Apache Kafka producing and consuming messages
Apache Kafka is a distributed event streaming platform used for publishing, subscribing to, and processing real-time data feeds across producers and consumers organized into topics.
This project provides a Studio Project built on the Kafka Adapter — a workflow to produce messages to a topic, and a workflow to consume messages, designed to be invoked by an Operations Manager event trigger. See Studio Projects below.
| Asset | Description |
|---|---|
| Studio Projects/ | Itential Platform project containing the Produce Message and Consume Message workflows |
| Requirement | Version |
|---|---|
| Itential Platform | 6.x |
| Apache Kafka | 2.x brokers |
| Kafka Adapter | Required for both workflows below |
Install the Kafka Adapter and configure an instance in Admin > Adapters pointing at your Kafka broker(s), then update the adapterId value in the Produce Message workflow to match your instance name before importing.
The Consume Message workflow isn't meant to be run manually — it's designed to be invoked automatically whenever the Kafka Adapter emits a message event. This repo doesn't ship an exported Automation/Trigger for it (the topic name is tenant-specific), so wire it up manually after importing the Studio Project:
@itentialopensource/adapter-kafkav2 — matches your Kafka Adapter's package nameexample-topic)payload input variable$var.job.payload.Import Apache Kafka 2.x.project.json via Automation Studio > Projects > Import.
| Workflow | Scope |
|---|---|
| Produce Message | Publish one or more messages to a Kafka topic. Inputs: adapterId, topic, messages (array of message strings). Uses a Build Produce Message Request transformation internally to shape the adapter payload. |
| Consume Message | Receives a single message payload and processes it. Input: payload (object) — meant to be populated by the event trigger described above, not supplied manually. |
| Dependency | Notes |
|---|---|
| Kafka Adapter | Required for both workflows. Update adapterId in Produce Message, and reference the adapter's package name as the event source when configuring the trigger. |