camel-cm-sms-kafka-connector sink configuration
Connector Description: Send SMS messages via CM SMS Gateway.
When using camel-cm-sms-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-cm-sms-kafka-connector</artifactId>
<version>x.x.x</version>
<!-- use the same version as your Camel Kafka connector version -->
</dependency>To use this Sink connector in Kafka connect you’ll need to set the following connector.class
connector.class=org.apache.camel.kafkaconnector.cmsms.CamelCmsmsSinkConnectorThe camel-cm-sms sink connector supports 8 options, which are listed below.
| Name | Description | Default | Required | Priority |
|---|---|---|---|---|
camel.sink.path.host |
SMS Provider HOST with scheme |
null |
true |
HIGH |
camel.sink.endpoint.defaultFrom |
This is the sender name. The maximum length is 11 characters. |
null |
true |
HIGH |
camel.sink.endpoint.defaultMaxNumberOfParts |
If it is a multipart message forces the max number. Message can be truncated. Technically the gateway will first check if a message is larger than 160 characters, if so, the message will be cut into multiple 153 characters parts limited by these parameters. |
8 |
false |
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 |
false |
MEDIUM |
camel.sink.endpoint.productToken |
The unique token to use |
null |
true |
HIGH |
camel.sink.endpoint.testConnectionOnStartup |
Whether to test the connection to the SMS Gateway on startup |
false |
false |
MEDIUM |
camel.component.cm-sms.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 |
false |
MEDIUM |
camel.component.cm-sms.autowiredEnabled |
Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. |
true |
false |
MEDIUM |
The camel-cm-sms sink connector has no converters out of the box.
The camel-cm-sms sink connector has no transforms out of the box.
The camel-cm-sms sink connector has no aggregation strategies out of the box.