Apache Kafka
Consume from, or publish to, a Kafka topic.
Messaging↓ Inbound↑ OutboundKAFKAcamel-kafkaIt confirms every broker in the list accepts a connection. Topic access is not checked yet (see Stage 2).
A restart then continues where it stopped. SASL_SSL needs the username and password.
Worked example
Hospital order events (Kafka) · Inbound · JSON · Test passes on any engine: No - placeholder values
Placeholder brokers on example.com - replace with the hospital's brokers and topic.
{
"direction": "Inbound",
"format": "JSON",
"settings": {
"brokers": "kafka.hospital.example.com:9092",
"topic": "lab-orders",
"groupId": "xellabs-integration-engine",
"security": "PLAINTEXT"
}
}
The addresses above are placeholders on example.com. Replace them with your partner's real details before running Test connection.
This is what the console's Fill example button enters. Secrets are never part of an example. Every setting is explained below.
Settings
Required fields are marked Yes. Fields marked 🔒 (password) are stored encrypted and never sent back to the browser - the console only shows Set / Not set. A field marked inbound only or outbound only appears just for that direction.
| Setting | Type | Required | Default | What to enter |
|---|---|---|---|---|
brokersBootstrap servers | text | Yes | — | Required: host:port of one or more brokers, comma-separated, e.g. kafka1:9092,kafka2:9092. |
topicTopic | text | Yes | — | Required: the topic to read or write, e.g. lab.orders. |
groupIdConsumer group | text | No | xellabs-integration-engine | inbound only. The consumer group, e.g. xellabs-integration-engine. Keep it the same so a restart continues where it stopped. |
securitySecurity | select | Yes | PLAINTEXT | PLAINTEXT on a closed network; SSL or SASL_SSL otherwise. SASL_SSL needs the username and password. Options: PLAINTEXT, SSL, SASL_SSL. |
usernameSASL username | text | No | — | Required for SASL_SSL: the SASL account. |
passwordSASL password | password | No | — | 🔒 secret. Required for SASL_SSL: the SASL password. Stored encrypted. |
What "Test connection" checks
Every broker in the list accepts a connection. Topic access is checked in Stage 2.
Test connection is read-only and says how far it got: verified, reached, checked or failed. See Testing a connection, and Troubleshooting if it fails.