{"id":5010,"date":"2023-10-20T00:13:52","date_gmt":"2023-10-20T00:13:52","guid":{"rendered":"https:\/\/dalelane.co.uk\/blog\/?p=5010"},"modified":"2023-10-20T20:07:58","modified_gmt":"2023-10-20T20:07:58","slug":"connecting-app-connect-enterprise-to-event-endpoint-management","status":"publish","type":"post","link":"https:\/\/dalelane.co.uk\/blog\/?p=5010","title":{"rendered":"Connecting App Connect Enterprise to Event Endpoint Management"},"content":{"rendered":"

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.<\/strong><\/p>\n

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<\/a>. People seem to have found that post useful, so I thought I’d do something similar for topics in Event Endpoint Management this time.<\/p>\n

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.<\/p>\n

<\/a><\/p>\n

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.<\/p>\n

To help with this, I use a grid like the one below.<\/p>\n

The instructions in this post start with Event Endpoint Management, and explain how to populate the grid with the information you need.<\/p>\n

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.<\/p>\n