Configuring IBM App Connect Enterprise to consume messages from Kafka topics in IBM Event Endpoint Management requires careful configuration. In this post, I’ll share the steps I use that help me to avoid missing any required values.
If this sounds familiar, it might be because I wrote a post like this about using App Connect Enterprise to work with topics from Event Streams. People seem to have found that post useful, so I thought I’d do something similar for topics in Event Endpoint Management this time.
To illustrate this, I’ll create a simple App Connect flow that consumes messages from a Kafka topic and publish them to an MQTT topic.
The key to getting this to work correctly first time is to make sure that values are accurately copied from Event Endpoint Management to App Connect.
To help with this, I use a grid like the one below.
The instructions in this post start with Event Endpoint Management, 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 |
DEMO.ACE
|
|
| B | Bootstrap address |
my-eem-gateway-ibm-egw-rt-event-automation.apps.dalelane.cp.fyre.ibm.com:443
|
|
| C | SASL mechanism |
PLAIN
|
|
| D | SASL config |
org.apache.kafka.common.security.plain.PlainLoginModule required;
|
|
| E | Security protocol |
SASL_SSL
|
|
| F | Certificate |
eem-cert.jks
|
|
| G | Certificate password |
STOREPASSW0RD
|
|
| H | Username |
eem-9c8fc5d9-fddd-48dd-ab41-e062214166e5
|
|
| I | Password |
dd08a1fc-99be-4931-8059-70aef88c1f0c
|
|
| J | Policy project name |
demo-policies
|
|
| K | Policy name |
demo-eem-policy
|
|
| L | Security identity name |
eem-credentials
|
|
| M | Truststore identity name |
eem-truststore
|
