Configuring Consume Service for Confluent Kafka
The Consume service retrieves and removes a message from a specified Kafka topic. When you configure the Consume service, you specify the output signature properties, which become the output document. You configure Adapter for Apache Kafka services using Designer. The adapter supports the following types of consumption:
Subscription: Subscription is considered when input of the service contains only topics.
Manual Assignment: Manual Assignment is considered when input of the service contains topics and partitions.
To configure a Consume service
1. In Designer, right-click the package in which the service should be contained and select New > Adapter Service .
2. Select the parent namespace, type a name for the adapter service, and click Next.
3. Select webMethods Adapter for Apache Kafka as the adapter type and click Next.
4. Select the appropriate Adapter Connection Name of type Confluent Kafka Consumer Connection and click Next.
5. From the list of available templates, select the Consume service template and click Finish
The adapter service editor for the adapter service appears. You can select the Adapter Settings tab at any time to confirm adapter service properties such as the Adapter Name, Adapter Connection Name, and Adapter Service Template, as necessary.
6. Select Consume with Schema tab to configure the following fields:
Field | Description |
Topic | Specifies the topic(s) from which the messages are consumed. Note:
The topic(s) from which the messages are consumed must be unique across the schema. |
Partition(optional) | Specified partition in which the message is stored. |
Offset field | Specifies the field name that specifies the offset of the partition from where the consumer needs to start consuming the messages. |
Value Schema | Specifies the particular avro schema file name. |
Key Schema | Specifies the particular avro schema file name. |
Note:
If the key deserializer class or value deserializer class is io.confluent.kafka.serializers.KafkaAvroDeserializer in the connection parameters and avro files have been placed under schema package/schemas directory, then avro file names would be available for key schema/value schema.