> For the complete documentation index, see [llms.txt](https://docs.buildings.ability.abb/collection/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.buildings.ability.abb/collection/english-v14/connectivity-as-a-service/gerate-mit-abb-buildingpro-verbinden/...mit-kafka/verbindung-konfigurieren.md).

# Configure connection

<div data-full-width="true"><figure><img src="https://content.gitbook.com/content/Nyvwhz1kEMXcHf4HLuZ8/blobs/zLNFuEeKnY0oMqw2tnE1/Docs_Verbindungen%20-%20Verbindungen%20Kafka%202.png" alt=""><figcaption></figcaption></figure></div>

<table><thead><tr><th width="144.33333333333331">Icon</th><th>Description</th><th>Details</th></tr></thead><tbody><tr><td><strong>[A]</strong></td><td>Name</td><td>Enter a name for the connection</td></tr><tr><td><strong>[B]</strong></td><td>Client ID</td><td>Enter the Client ID. The Client ID must be known and is not configured in Eliona</td></tr><tr><td><strong>[C]</strong></td><td>Consumer group</td><td>Optional: Specify the consumer group. If you leave this field empty, the client will be configured as a stand-alone client.</td></tr><tr><td><strong>[D]</strong></td><td>Seeds</td><td>The seeds are the IP addresses and ports to which a connection should be established. IP addresses and ports are separated by a colon. Example: 123.123.0.1:9092</td></tr><tr><td><strong>[E]</strong></td><td>Type</td><td>Here you can choose an authentication type.</td></tr><tr><td><strong>[F]</strong></td><td>Username</td><td>Specify a username for authentication</td></tr><tr><td><strong>[G]</strong></td><td>Password</td><td>Specify a password for authentication</td></tr><tr><td><strong>[H]</strong></td><td>Host</td><td>Optional: Enter the host for a SOCKS5 proxy server</td></tr><tr><td><strong>[I]</strong></td><td>SOCKS5 Port</td><td>Optional: Enter the port for a SOCKS5 proxy server</td></tr><tr><td><strong>[J]</strong></td><td>SOCKS5 Username</td><td>Optional: Enter the username for a SOCKS5 proxy server</td></tr><tr><td><strong>[K]</strong></td><td>SOCKS5 Password</td><td>Optional: Enter the password for a SOCKS5 proxy server</td></tr><tr><td><strong>[L]</strong></td><td>Save</td><td>Deletes the respective connection. ⚠ Attention: If the connection is also used in other projects, it will be deleted there as well.</td></tr><tr><td><strong>[M]</strong></td><td>Existing subscriptions</td><td>Existing subscriptions associated with this connection are displayed here</td></tr><tr><td><strong>[N]</strong></td><td>Create new subscription</td><td>Click to create a new subscription</td></tr><tr><td><strong>[O]</strong></td><td>Test connection</td><td>Click here to test the connection</td></tr><tr><td><strong>[O1]</strong></td><td>Connection status</td><td>The result of the connection test is displayed here</td></tr></tbody></table>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.buildings.ability.abb/collection/english-v14/connectivity-as-a-service/gerate-mit-abb-buildingpro-verbinden/...mit-kafka/verbindung-konfigurieren.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.