camel-quickfix-kafka-connector sink configuration
When using camel-quickfix-kafka-connector as sink make sure to use the following Maven dependency to have support for the connector:
<dependency>
<groupId>org.apache.camel.kafkaconnector</groupId>
<artifactId>camel-quickfix-kafka-connector</artifactId>
<version>x.x.x</version>
<!-- use the same version as your Camel Kafka connector version -->
</dependency>The camel-quickfix sink connector supports 12 options, which are listed below.
| Name | Description | Default | Priority |
|---|---|---|---|
camel.sink.path.configurationName |
The configFile is the name of the QuickFIX/J configuration to use for the FIX engine (located as a resource found in your classpath). |
null |
HIGH |
camel.sink.endpoint.lazyCreateEngine |
This option allows to create QuickFIX/J engine on demand. Value true means the engine is started when first message is send or there’s consumer configured in route definition. When false value is used, the engine is started at the endpoint creation. When this parameter is missing, the value of component’s property lazyCreateEngines is being used. |
false |
MEDIUM |
camel.sink.endpoint.sessionID |
The optional sessionID identifies a specific FIX session. The format of the sessionID is: (BeginString):(SenderCompID)/(SenderSubID)/(SenderLocationID)-(TargetCompID)/(TargetSubID)/(TargetLocationID) |
null |
MEDIUM |
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.quickfix.lazyCreateEngines |
If set to true, the engines will be created and started when needed (when first message is send) |
false |
MEDIUM |
camel.component.quickfix.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.quickfix.basicPropertyBinding |
Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities |
false |
MEDIUM |
camel.component.quickfix.logFactory |
To use the given LogFactory |
null |
MEDIUM |
camel.component.quickfix.messageFactory |
To use the given MessageFactory |
null |
MEDIUM |
camel.component.quickfix.messageStoreFactory |
To use the given MessageStoreFactory |
null |
MEDIUM |