Configuring an Adapter for Confluent Kafka Consumer Connection
When you configure Adapter for Apache Kafka , you specify information that Integration Server uses to connect to an Confluent Kafka system. You can configure Adapter for Apache Kafka connections manually using the Integration Server Administrator screen.
To configure Consumer connection
1. In the Adapters menu of Integration Server Administrator's navigation area, click webMethods Adapter for Apache Kafka.
2. On the Connections screen, click Configure New Connection.
3. On the Connection Types screen, click Confluent for Kafka Consumer Connection to display the Configure Connection Type screen.
4. In the webMethods Adapter for Confluent Kafka section, use the following fields:
Field | Description/Action |
Package | The package in which to create the connection. You must create the package using Designer before you can specify the package using this parameter. For general information about creating packages, see the webMethods Service Development Help for your release. Note:
Configure the connection in a user-defined package rather than in the adapter's package. For other important considerations when creating packages for Adapter for Apache Kafka, see
Overview of Package Management |
Folder Name | Specifies the folder in which you create the connection. |
Connection Name | Specifies the name you want to give to the connection. Connection names cannot have spaces or use special characters reserved by Integration Server and Designer. For more information about the use of special characters in package, folder, and element names, see the webMethods Service Development Help for your release. |
5. In the Connection Properties section, use the following fields:
Field | Description/Action |
Schema Registry URL | Defines a comma-separated list of URLs, that can be used to register or look up schemas. |
Schema Package | Specifies the package that consists of AVRO schema files. AVRO files should be under schemas folder in the specified package directory. |
Schema Registry Credentials | Specifies the security credentials that you use when connecting to a Schema Registry. Credential Source | Description | USER_INFO | Set the following fields: Schema Registry Credentials to API key: API secret. Specify the pair of API key and secret value, that you use when connecting to a Schema Registry. Security Protocol to SASL_SSL Other Properties to basic.auth.credentials.source=USER_INFO. Note: You can specify additional configuration in Other Properties. Use the following format: propertyName1=value;propertName2=value | SASL_INHERIT | Set the following fields: Security Protocol to SASL_SSL JAAS_CONFIG to the JAAS login context parameters for SASL connections in the format used by JAAS configuration files. Note: If JAAS_CONFIG is specified, the value specified in Schema Registry Credentials field is not considered when connecting to a Schema Registry. Other Properties to basic.auth.credentials.source=SASL_INHERIT. Note: You can specify additional configuration in Other Properties. Use the following format: propertyName1=value;propertName2=value | STATIC_TOKEN | Set the following fields: Schema Registry Credentials to OAuth token. Specify the OAuth token. Security Protocol to SASL_SSL Other Properties to bearer.auth.credentials.source=STATIC_TOKEN. Note: You can specify additional configuration in Other Properties. Use the following format: propertyName1=value;propertName2=value |
|
Other Properties | Specifies the Kafka related properties for additional configuration. Use the following format: propertyName1=value;propertName2=value Some of the Kafka related properties that can be set in the Other Properties field are: schema.registry.url.conn.timeout. Specifies the timeout (milliseconds) used to detect if the Schema Registry URL is reachable. Default value is 60000 milliseconds. The range is between 1000 and 300000 Example of Other Properties: schema.registry.url.conn.timeout=75000;max.poll.records=10 |
6. Click Save Connection.
The connection you created appears on the adapter's Connections screen and in Designer.
You can enable a connection only if the parameters for the connection are valid.