# tKafkaConnection

Opens a reusable Kafka connection.

The tKafkaConnection component opens a connection to a given Kafka cluster so that the other Kafka components in subJobs can reuse this connection.

This component is not shipped with your Talend Studio by default. You need to install it using the Feature Manager. For more information, see [Installing features using the Feature Manager](https://help.qlik.com/talend/r/en-US/8.0/studio-user-guide/install-features-to-talend-studio).

## tKafkaConnection Standard properties

These properties are used to configure tKafkaConnection running in the Standard Job framework.

The Standard tKafkaConnection component belongs to the Internet family.

The component in this framework is available in all Talend products with Big Data and in Talend Data Fabric.

## Basic settings

| Properties | Description |
| --- | --- |
| Version | Select the version of the Kafka cluster to be used.<br><br>If you have installed the 8.0.1-R2024-02 Talend Studio Monthly update or a later one delivered by Talend, the Kafka 2.4.x version and previous versions are deprecated. |
| Broker list | Enter the addresses of the broker nodes of the Kafka cluster to be used.<br><br>The form of this address should be *hostname:port*. This<br>information is the name and the port of the hosting node in this Kafka cluster.<br><br>If you need to specify several addresses, separate them using a comma (*,*). |
| Use SSL/TLS | Select this checkbox to enable the SSL or TLS encrypted connection.<br><br>This checkbox is available since Kafka 0.9.0.1. |
| Set keystore | Select this checkbox to enable the SSL or TLS encrypted connection via a<br>tSetKeystore component.<br><br>Then you need to use the tSetKeystore<br>component in the same Job to specify the encryption information.<br><br>This checkbox is available when you select the Use<br>SSL/TLS checkbox.<br><br>Information noteNote: This option is available when you<br>have installed the 8.0.1-R2022-05 Talend Studio Monthly update or a later one delivered by Talend. For more information, check with your administrator. |
| Use Kerberos authentication | If the Kafka cluster to be used is secured with Kerberos, select this<br>checkbox to display the related parameters to be defined:<br><br><ul> <li> <p> <span>JAAS configuration path</span>: enter the                        path, or browse to the JAAS configuration file to be used by the Job to                        authenticate as a client to Kafka.</p> <p>This JAAS file describes how the clients, the Kafka-related                        Jobs in terms of <em> <span>Talend</span> </em>, can connect to the Kafka broker nodes, using either the kinit mode or                        the keytab mode. The JAAS file must be stored in the machine where these                        Jobs are executed.</p> <p> <em> <span>Talend</span> </em>, Kerberos or Kafka does not provide this JAAS file. You need to create                        it by following the explanation in <a href="http://kafka.apache.org/documentation.html#security_sasl_clientconfig" target="_blank">Configuring Kafka                            client</a> depending on the security strategy of your                        organization.</p> </li> <li> <p> <span>Kafka brokers principal name</span>: enter                        the primary part of the Kerberos principal you defined for the brokers when                        you were creating the broker cluster. For example, in this principal <em>kafka/kafka1.hostname.com@EXAMPLE.COM</em>, the primary                        part to be used to fill in this field is <em>kafka</em>.</p> </li> <li> <p> <span>Set kinit command path</span>: Kerberos                        uses a default path to its kinit executable. If you have changed this path,                        select this checkbox and enter the custom access path.</p> <p>If you leave this checkbox clear, the default path is                        used.</p> </li> <li> <p> <span>Set Kerberos configuration path</span>:                        Kerberos uses a default path to its configuration file, the <em>krb5.conf</em> file (or <em>krb5.ini</em>                        in Windows) for Kerberos 5 for example. If you have changed this path,                        select this checkbox and enter the custom access path to the Kerberos                        configuration file.</p> <p>If you leave this checkbox clear, a given strategy is applied                        by Kerberos to attempt to find the configuration information it requires.                        For details about this strategy, see the <em>Locating the                            krb5.conf Configuration File</em> section in <a href="http://docs.oracle.com/javase/7/docs/technotes/guides/security/jgss/tutorials/KerberosReq.html" target="_blank">Kerberos requirements</a>.</p> </li> </ul><br><br>For further information about how a Kafka cluster is secured with<br>Kerberos, see [Authenticating using<br>SASL](http://kafka.apache.org/documentation.html#security_sasl).<br><br>This checkbox is available since Kafka 0.9.0.1. |

## Advanced settings

| Properties | Description |
| --- | --- |
| tStatCatcher Statistics | Select this checkbox to gather the processing metadata at the Job level as<br>well as at each component level. |

## Global Variables

| Variables | Description |
| --- | --- |
| ERROR\_MESSAGE | The error message generated by the component when an error<br>occurs. This is an After variable and it returns a string. |

## Usage

| Usage guidance | Description |
| --- | --- |
| **Usage rule** | This component is used standalone to create the Kafka connection that the<br>other Kafka components can reuse. |