Page History

...

Avro clients function in a manner similar manner to other messaging clients but are configured to use the Avro format by default. In addition, there are a few configuration options that are unique to Avro clients:

...

Avro message responders function in a manner similar manner to other responders. Refer to Message Responder Overview for information on configuring and using responders.  In addition, there  There are a few configuration options that are unique to Avro message responders:

...

1. If the Kafka record key is also Avro, add an Apache Avro Client to your test suite and configure it as follows, then save it:
   • Choose the schema for the record key from the Message type menu. You will need to configure the Avro schemas schema's location if you haven't already.
   • On the Request tab, confirm that Form Input is selected as the Input mode and enter the details for the input fields as needed.
   • On the Transport tab, set Transport to None.
2. If the Kafka record key is also Avro, add an XML Data Bank output to the Avro client (right-click the Avro client and choose Add Output > Request > Payload Modeled as XML > XML Data Bank) and configure it as follows, then save it:
   • Extract the record key element (select it and click Extract Element).
   • Modify the extracted element and change the Xpath to */. Ensure that the Extract field is set to Entire Element.
   • Rename the Data Source Column, if needed.
3. Add another Apache Avro Client to the test suite (this will be a producer) and configure it as follows, then save it:
   • Choose the schema for the record message from the Message type menu.
   • On the Request tab, confirm that Form Input is selected as the Input mode and enter the details for the input fields as needed.
   • On the Transport tab, choose Kafka from the Transport menu. If you have more than one custom transport, you will need to choose Custom Extension then choose Kafka from Select Implementation menu.
   • Select Connection and enter the details for your connection settings as needed.
   • Select Producer and enter avro as the Record Key Serializer. Enter a valid Topic and set the Record Key to the name of the Data Source Column from step 2. Complete the other Producer settings as needed.
4. If the consumed record is a different Avro schema than the record that was produced, add another Apache Avro Client to the test suite (this will be a consumer) and configure it as follows, then save it:
   • Choose the schema for the record message from the Message type menu.
   • Enable Send XML instead of Apache Avro when in Form Input or Form XML to avoid any conversion errors, as the request will be ignored by the consumer.
   • On the Request tab, confirm that Form Input is selected as the Input mode and enter the details for the input fields as needed.
   • On the Transport tab, choose Kafka from the Transport menu. If you have more than one custom transport, you will need to choose Custom Extension then choose Kafka from Select Implementation menu.
   • Select Connection and enter the details for your connection settings as needed.
   • Select Consumer and enter a valid Topic and Group ID. Complete the other Consumer settings as needed.
   • If you want to correlate a message based on one or more headers, select Consumer Headers and enter the keys and values as appropriate.

...