blob: 4e3260be1e9b81106d1e501e818a2e1f6c861222 [file] [log] [blame]
// kafka-connector options: START
[[camel-milo-server-kafka-connector-sink]]
= camel-milo-server-kafka-connector sink configuration
When using camel-milo-server-kafka-connector as sink make sure to use the following Maven dependency to have support for the connector:
[source,xml]
----
<dependency>
<groupId>org.apache.camel.kafkaconnector</groupId>
<artifactId>camel-milo-server-kafka-connector</artifactId>
<version>x.x.x</version>
<!-- use the same version as your Camel Kafka connector version -->
</dependency>
----
The camel-milo-server sink connector supports 23 options, which are listed below.
[width="100%",cols="2,5,^1,2",options="header"]
|===
| Name | Description | Default | Priority
| *camel.sink.path.itemId* | ID of the item | null | HIGH
| *camel.sink.endpoint.lazyStartProducer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and starting the producer may take a little time and prolong the total processing time of the processing. | false | MEDIUM
| *camel.sink.endpoint.basicPropertyBinding* | Whether the endpoint should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | MEDIUM
| *camel.sink.endpoint.synchronous* | Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). | false | MEDIUM
| *camel.component.milo-server.applicationName* | The application name | null | MEDIUM
| *camel.component.milo-server.applicationUri* | The application URI | null | MEDIUM
| *camel.component.milo-server.bindAddresses* | Set the addresses of the local addresses the server should bind to | null | MEDIUM
| *camel.component.milo-server.bindPort* | The TCP port the server binds to | null | MEDIUM
| *camel.component.milo-server.buildInfo* | Server build info | null | MEDIUM
| *camel.component.milo-server.certificateManager* | Server certificate manager | null | MEDIUM
| *camel.component.milo-server.certificateValidator* | Validator for client certificates | null | MEDIUM
| *camel.component.milo-server.defaultCertificate Validator* | Validator for client certificates using default file based approach | null | MEDIUM
| *camel.component.milo-server.enableAnonymous Authentication* | Enable anonymous authentication, disabled by default | false | MEDIUM
| *camel.component.milo-server.namespaceUri* | The URI of the namespace, defaults to urn:org:apache:camel | null | MEDIUM
| *camel.component.milo-server.path* | The path to be appended to the end of the endpoint url. (doesn't need to start with '/') | null | MEDIUM
| *camel.component.milo-server.productUri* | The product URI | null | MEDIUM
| *camel.component.milo-server.securityPolicies* | Security policies | null | MEDIUM
| *camel.component.milo-server.securityPoliciesById* | Security policies by URI or name | null | MEDIUM
| *camel.component.milo-server.serverCertificate* | Server certificate | null | MEDIUM
| *camel.component.milo-server.userAuthentication Credentials* | Set user password combinations in the form of user1:pwd1,user2:pwd2 Usernames and passwords will be URL decoded | null | MEDIUM
| *camel.component.milo-server.usernameSecurityPolicy Uri* | Set the UserTokenPolicy used when One of: [None] [Basic128Rsa15] [Basic256] [Basic256Sha256] [Aes128_Sha256_RsaOaep] [Aes256_Sha256_RsaPss] | null | MEDIUM
| *camel.component.milo-server.lazyStartProducer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and starting the producer may take a little time and prolong the total processing time of the processing. | false | MEDIUM
| *camel.component.milo-server.basicPropertyBinding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | MEDIUM
|===
// kafka-connector options: END