camel-iec60870-client-kafka-connector sink configuration
Connector Description: IEC 60870 supervisory control and data acquisition (SCADA) client using NeoSCADA implementation.
When using camel-iec60870-client-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-iec60870-client-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.iec60870client.CamelIec60870clientSinkConnector
The camel-iec60870-client sink connector supports 21 options, which are listed below.
Name | Description | Default | Priority |
---|---|---|---|
Required The object information address. |
HIGH |
||
Data module options. |
MEDIUM |
||
Protocol options. |
MEDIUM |
||
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 |
|
Parameter W - Acknowledgment window. |
10 |
MEDIUM |
|
The common ASDU address size. May be either SIZE_1 or SIZE_2. One of: [SIZE_1] [SIZE_2]. Enum values:
|
MEDIUM |
||
The cause of transmission type. May be either SIZE_1 or SIZE_2. One of: [SIZE_1] [SIZE_2]. Enum values:
|
MEDIUM |
||
The information address size. May be either SIZE_1, SIZE_2 or SIZE_3. One of: [SIZE_1] [SIZE_2] [SIZE_3]. Enum values:
|
MEDIUM |
||
Parameter K - Maximum number of un-acknowledged messages. |
15 |
MEDIUM |
|
Timeout T1 in milliseconds. |
15000 |
MEDIUM |
|
Timeout T2 in milliseconds. |
10000 |
MEDIUM |
|
Timeout T3 in milliseconds. |
20000 |
MEDIUM |
|
Whether to include the source address. |
MEDIUM |
||
Timeout in millis to wait for client to establish a connected connection. |
10000 |
MEDIUM |
|
Whether background scan transmissions should be ignored. |
true |
MEDIUM |
|
Whether to ignore or respect DST. |
false |
MEDIUM |
|
The timezone to use. May be any Java time zone string. |
"UTC" |
MEDIUM |
|
An identifier grouping connection instances. |
MEDIUM |
||
Default connection options. |
MEDIUM |
||
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 |
|
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 |
MEDIUM |
The camel-iec60870-client sink connector has no converters out of the box.
The camel-iec60870-client sink connector has no transforms out of the box.
The camel-iec60870-client sink connector has no aggregation strategies out of the box.