Configuring IBM App Connect Enterprise to produce or consume messages from Kafka topics in IBM Event Streams requires careful configuration. In this post, I’ll share the steps I use that help me to avoid missing any required values.
To illustrate this, I’ll create a simple App Connect flow that implements a REST API, where any data I POST to the REST API is sent to a Kafka topic.
The key to getting this to work correctly first time is to make sure that values are accurately copied from Event Streams to App Connect.
To help with this, I use a grid like the one below.
The instructions in this post start with Event Streams, and explain how to populate the grid with the information you need.
Then the instructions will switch to App Connect, and explain how to use the values in the grid to set up your App Connect flow.
| What this is | Values you will see in my screenshots | Your value | |
|---|---|---|---|
| A | Topic name |
THIS.IS.MY.TOPIC
|
|
| B | Bootstrap address |
kafkadev_kafka_bootstrap_demo.itzroks_120000f8p4_f9nd74_6ccd7f378ae819553d37d5f2ee142bd6_0000.eu_gb.containers.appdomain.cloud:443
kafkadev_kafka_bootstrap.demo.svc:9093 kafkadev_kafka_bootstrap.demo.svc:9092 |
|
| C | SASL mechanism |
SCRAM-SHA-512
|
|
| D | SASL config |
org.apache.kafka.common.security.scram.ScramLoginModule required;
|
|
| E | Security protocol |
SASL_SSL
SASL_PLAINTEXT SSL PLAINTEXT |
|
| F | Certificate |
es-cert.jks
|
|
| G | Certificate password |
wo05RndLJQgI
|
|
| H | Username |
app-connect-enterprise
|
|
| I | Password |
AIYJjrM2bSic
|
|
| J | Policy project name |
demo-policies
|
|
| K | Policy name |
demo-eventstreams-policy
|
|
| L | Security identity name |
kafka-credentials
|
|
| M | Truststore identity name |
kafka-truststore
|
