Page Comparison

...

3. Select to add an endpoint, either REST or Kafka

...

REST Endpoints

...

1. Add a Name, optional Description, Encoding type, and optional port. Select “Save Endpoint”

...

2. Repeat for the Output Endpoint, as required.

Kafka Endpoints

...

1. Kafka endpoints require several fields, as detailed in the screenshot and table below.

...

Field	Type	Description	Example
Name	string	A user-supplied name for the endpoint	“MyKafkaEndpoint1”
Description	string	A user-supplied description for the endpoint	“Kafka Endpoint for consumer transactions”
Encoding	drop-down	The encoding used for serialization/deserialization of the kafka messages	json
BootstrapServers	comma-separated list of strings	A list string	The name and port of the Kafka bootstrap servers.	"kafka1:9002"
Group	string	A consumer group (Consumer Group) (optional)	string	To provide a horizontally scalable solution, a Consumer Group can be used to allow load balancing of requests across multiple ModelOp runtimes. By defining a Consumer Group, ModelOp Center ensures that only one ModelOp runtime in the Consumer Group services a given message.	"fastscore-1"
Principal (optional)	string	An authenticated user in a secure cluster	"kafka/kafka@REALM"
Topic	string	The Kafka topic to consume or push to, depending on if input vs. output endpoint	"MyKafkaTopic"
Keyfile (optional)	string	The location of the keytab file containing pairs of Kerberos principals and encrypted keys	"/fastscore.keytab"

...