Join this online group to communicate across IBM product users and experts by sharing advice and best practices with peers and staying up to date regarding product enhancements.
Introduction
This article will explain how the exiting Kafka use case can be migrated and executed on webMethods.io Integration using the DADA (Develop Anywhere and Deploy Anywhere) capabilities.
Pre-requisite
Audience
This article is targeted for technical architects and technical developers of webMethods.
What is DADA?
https://community.ibm.com/community/user//integration/blogs/john-carter/2023/10/20/what-is-develop-anywhere-deploy-anywhere
What is Integration runtimes?
https://community.ibm.com/community/user/integration/blogs/theo-ezell/2025/03/07/develop-anywhere-deploy-anywhere-what-are-integrat
Use case
In this use case we will discuss how we can migrate the Kafka packages from the self hosted setup to the cloud and execute the transaction on webMethods.io Integration by using the DADA capabilities.
Existing use case Architecture
Target Architecture
Steps to achieve the target architecture
Push assets to the external repository
Link: https://github.ibm.com/Vikash-Sharma5/webMethodsDADA
Pull the assets from repository
Spin the edge runtime
Orchestration
Note: When we do sync the flow service then it sync’s the asset from cloud design time (CDT) to edge runtime (ERT).
Configure the connections
Sample for JAAS config:
Note: When you click on sync, it updates the manifest file with the credentials and other details.
Test the flow service
Note: In the above use case we have discussed about the Kafka producer where you can submit the events to the Kafka system.
Architecture for consuming events from Kafka
Steps to create flow service to consume the Kafka message
Note: