You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@camel.apache.org by ac...@apache.org on 2020/04/29 13:12:50 UTC
[camel-kafka-connector] 01/02: Added docs to website
This is an automated email from the ASF dual-hosted git repository.
acosentino pushed a commit to branch fixed-index
in repository https://gitbox.apache.org/repos/asf/camel-kafka-connector.git
commit 57bb7d738871fb3ae4a12f546f30149e60b53fc6
Author: Andrea Cosentino <an...@gmail.com>
AuthorDate: Wed Apr 29 12:41:07 2020 +0200
Added docs to website
---
.../camel-activemq-kafka-sink-connector.adoc | 159 ++++++++++++++++++++
.../camel-activemq-kafka-source-connector.adoc | 160 +++++++++++++++++++++
.../connectors/camel-ahc-kafka-sink-connector.adoc | 48 +++++++
.../camel-ahc-ws-kafka-sink-connector.adoc | 49 +++++++
.../camel-ahc-ws-kafka-source-connector.adoc | 49 +++++++
.../camel-ahc-wss-kafka-sink-connector.adoc | 49 +++++++
.../camel-ahc-wss-kafka-source-connector.adoc | 49 +++++++
.../camel-amqp-kafka-sink-connector.adoc | 156 ++++++++++++++++++++
.../camel-amqp-kafka-source-connector.adoc | 157 ++++++++++++++++++++
.../camel-apns-kafka-sink-connector.adoc | 31 ++++
.../camel-apns-kafka-source-connector.adoc | 49 +++++++
.../connectors/camel-as2-kafka-sink-connector.adoc | 58 ++++++++
.../camel-as2-kafka-source-connector.adoc | 76 ++++++++++
.../camel-asterisk-kafka-sink-connector.adoc | 33 +++++
.../camel-asterisk-kafka-source-connector.adoc | 34 +++++
.../camel-atmos-kafka-sink-connector.adoc | 42 ++++++
.../camel-atmos-kafka-source-connector.adoc | 44 ++++++
...-atmosphere-websocket-kafka-sink-connector.adoc | 56 ++++++++
...tmosphere-websocket-kafka-source-connector.adoc | 60 ++++++++
.../camel-atom-kafka-source-connector.adoc | 55 +++++++
.../camel-atomix-map-kafka-sink-connector.adoc | 47 ++++++
.../camel-atomix-map-kafka-source-connector.adoc | 49 +++++++
...amel-atomix-messaging-kafka-sink-connector.adoc | 48 +++++++
...el-atomix-messaging-kafka-source-connector.adoc | 50 +++++++
...camel-atomix-multimap-kafka-sink-connector.adoc | 47 ++++++
.../camel-atomix-queue-kafka-sink-connector.adoc | 45 ++++++
.../camel-atomix-queue-kafka-source-connector.adoc | 47 ++++++
.../camel-atomix-set-kafka-sink-connector.adoc | 46 ++++++
.../camel-atomix-set-kafka-source-connector.adoc | 48 +++++++
.../camel-atomix-value-kafka-sink-connector.adoc | 46 ++++++
.../camel-atomix-value-kafka-source-connector.adoc | 48 +++++++
.../camel-avro-kafka-sink-connector.adoc | 39 +++++
.../camel-avro-kafka-source-connector.adoc | 41 ++++++
.../camel-aws-cw-kafka-sink-connector.adoc | 44 ++++++
.../camel-aws-ddb-kafka-sink-connector.adoc | 46 ++++++
...camel-aws-ddbstream-kafka-source-connector.adoc | 61 ++++++++
.../camel-aws-ec2-kafka-sink-connector.adoc | 41 ++++++
.../camel-aws-ecs-kafka-sink-connector.adoc | 41 ++++++
.../camel-aws-eks-kafka-sink-connector.adoc | 41 ++++++
.../camel-aws-iam-kafka-sink-connector.adoc | 41 ++++++
...-aws-kinesis-firehose-kafka-sink-connector.adoc | 40 ++++++
.../camel-aws-kinesis-kafka-sink-connector.adoc | 40 ++++++
.../camel-aws-kinesis-kafka-source-connector.adoc | 63 ++++++++
.../camel-aws-kms-kafka-sink-connector.adoc | 41 ++++++
.../camel-aws-lambda-kafka-sink-connector.adoc | 41 ++++++
.../camel-aws-mq-kafka-sink-connector.adoc | 41 ++++++
.../camel-aws-msk-kafka-sink-connector.adoc | 41 ++++++
.../camel-aws-s3-kafka-sink-connector.adoc | 60 ++++++++
.../camel-aws-s3-kafka-source-connector.adoc | 77 ++++++++++
.../camel-aws-sdb-kafka-sink-connector.adoc | 39 +++++
.../camel-aws-ses-kafka-sink-connector.adoc | 44 ++++++
.../camel-aws-sns-kafka-sink-connector.adoc | 50 +++++++
.../camel-aws-sqs-kafka-sink-connector.adoc | 56 ++++++++
.../camel-aws-sqs-kafka-source-connector.adoc | 83 +++++++++++
.../camel-aws-swf-kafka-sink-connector.adoc | 53 +++++++
.../camel-aws-swf-kafka-source-connector.adoc | 52 +++++++
.../camel-aws-translate-kafka-sink-connector.adoc | 44 ++++++
.../camel-aws2-cw-kafka-sink-connector.adoc | 44 ++++++
.../camel-aws2-ddb-kafka-sink-connector.adoc | 46 ++++++
...amel-aws2-ddbstream-kafka-source-connector.adoc | 61 ++++++++
.../camel-aws2-ec2-kafka-sink-connector.adoc | 41 ++++++
.../camel-aws2-ecs-kafka-sink-connector.adoc | 41 ++++++
.../camel-aws2-eks-kafka-sink-connector.adoc | 41 ++++++
.../camel-aws2-iam-kafka-sink-connector.adoc | 41 ++++++
.../camel-aws2-kms-kafka-sink-connector.adoc | 41 ++++++
.../camel-aws2-mq-kafka-sink-connector.adoc | 41 ++++++
.../camel-aws2-msk-kafka-sink-connector.adoc | 41 ++++++
.../camel-aws2-ses-kafka-sink-connector.adoc | 44 ++++++
.../camel-aws2-sns-kafka-sink-connector.adoc | 49 +++++++
.../camel-aws2-sqs-kafka-sink-connector.adoc | 56 ++++++++
.../camel-aws2-sqs-kafka-source-connector.adoc | 83 +++++++++++
.../camel-aws2-translate-kafka-sink-connector.adoc | 44 ++++++
.../camel-azure-blob-kafka-sink-connector.adoc | 45 ++++++
.../camel-azure-blob-kafka-source-connector.adoc | 41 ++++++
.../camel-azure-queue-kafka-sink-connector.adoc | 36 +++++
.../camel-azure-queue-kafka-source-connector.adoc | 34 +++++
.../camel-bean-kafka-sink-connector.adoc | 35 +++++
.../camel-bean-validator-kafka-sink-connector.adoc | 41 ++++++
.../camel-beanstalk-kafka-sink-connector.adoc | 34 +++++
.../camel-beanstalk-kafka-source-connector.adoc | 55 +++++++
.../camel-bonita-kafka-sink-connector.adoc | 34 +++++
.../connectors/camel-box-kafka-sink-connector.adoc | 47 ++++++
.../camel-box-kafka-source-connector.adoc | 65 +++++++++
.../camel-braintree-kafka-sink-connector.adoc | 44 ++++++
.../camel-braintree-kafka-source-connector.adoc | 62 ++++++++
.../camel-browse-kafka-sink-connector.adoc | 29 ++++
.../camel-browse-kafka-source-connector.adoc | 31 ++++
.../camel-caffeine-cache-kafka-sink-connector.adoc | 45 ++++++
...el-caffeine-loadcache-kafka-sink-connector.adoc | 45 ++++++
.../camel-chatscript-kafka-sink-connector.adoc | 33 +++++
.../camel-chunk-kafka-sink-connector.adoc | 35 +++++
.../camel-class-kafka-sink-connector.adoc | 35 +++++
.../camel-cm-sms-kafka-sink-connector.adoc | 33 +++++
.../camel-cmis-kafka-sink-connector.adoc | 38 +++++
.../camel-cmis-kafka-source-connector.adoc | 40 ++++++
.../camel-coap+tcp-kafka-sink-connector.adoc | 38 +++++
.../camel-coap+tcp-kafka-source-connector.adoc | 41 ++++++
.../camel-coap-kafka-sink-connector.adoc | 38 +++++
.../camel-coap-kafka-source-connector.adoc | 41 ++++++
.../camel-coaps+tcp-kafka-sink-connector.adoc | 38 +++++
.../camel-coaps+tcp-kafka-source-connector.adoc | 41 ++++++
.../camel-coaps-kafka-sink-connector.adoc | 38 +++++
.../camel-coaps-kafka-source-connector.adoc | 41 ++++++
.../camel-cometd-kafka-sink-connector.adoc | 49 +++++++
.../camel-cometd-kafka-source-connector.adoc | 51 +++++++
.../camel-cometds-kafka-sink-connector.adoc | 49 +++++++
.../camel-cometds-kafka-source-connector.adoc | 51 +++++++
.../camel-consul-kafka-sink-connector.adoc | 55 +++++++
.../camel-consul-kafka-source-connector.adoc | 58 ++++++++
.../camel-controlbus-kafka-sink-connector.adoc | 35 +++++
.../camel-corda-kafka-sink-connector.adoc | 33 +++++
.../camel-corda-kafka-source-connector.adoc | 41 ++++++
.../camel-couchbase-kafka-sink-connector.adoc | 51 +++++++
.../camel-couchbase-kafka-source-connector.adoc | 70 +++++++++
.../camel-couchdb-kafka-sink-connector.adoc | 35 +++++
.../camel-couchdb-kafka-source-connector.adoc | 42 ++++++
.../connectors/camel-cql-kafka-sink-connector.adoc | 42 ++++++
.../camel-cql-kafka-source-connector.adoc | 60 ++++++++
.../camel-cron-kafka-source-connector.adoc | 33 +++++
.../camel-crypto-cms-kafka-sink-connector.adoc | 46 ++++++
.../camel-crypto-kafka-sink-connector.adoc | 49 +++++++
.../connectors/camel-cxf-kafka-sink-connector.adoc | 63 ++++++++
.../camel-cxf-kafka-source-connector.adoc | 59 ++++++++
.../camel-cxfrs-kafka-sink-connector.adoc | 55 +++++++
.../camel-cxfrs-kafka-source-connector.adoc | 53 +++++++
.../camel-dataformat-kafka-sink-connector.adoc | 30 ++++
.../camel-dataset-kafka-sink-connector.adoc | 41 ++++++
.../camel-dataset-kafka-source-connector.adoc | 36 +++++
.../camel-dataset-test-kafka-sink-connector.adoc | 43 ++++++
...el-debezium-mongodb-kafka-source-connector.adoc | 71 +++++++++
...amel-debezium-mysql-kafka-source-connector.adoc | 101 +++++++++++++
...l-debezium-postgres-kafka-source-connector.adoc | 93 ++++++++++++
...-debezium-sqlserver-kafka-source-connector.adoc | 75 ++++++++++
.../camel-digitalocean-kafka-sink-connector.adoc | 38 +++++
.../camel-direct-kafka-sink-connector.adoc | 34 +++++
.../camel-direct-kafka-source-connector.adoc | 31 ++++
.../camel-direct-vm-kafka-sink-connector.adoc | 38 +++++
.../camel-direct-vm-kafka-source-connector.adoc | 34 +++++
.../camel-disruptor-kafka-sink-connector.adoc | 38 +++++
.../camel-disruptor-kafka-source-connector.adoc | 40 ++++++
.../camel-disruptor-vm-kafka-sink-connector.adoc | 38 +++++
.../camel-disruptor-vm-kafka-source-connector.adoc | 40 ++++++
.../connectors/camel-dns-kafka-sink-connector.adoc | 29 ++++
.../camel-docker-kafka-sink-connector.adoc | 47 ++++++
.../camel-docker-kafka-source-connector.adoc | 49 +++++++
.../camel-dozer-kafka-sink-connector.adoc | 35 +++++
.../camel-drill-kafka-sink-connector.adoc | 33 +++++
.../camel-dropbox-kafka-sink-connector.adoc | 37 +++++
.../camel-dropbox-kafka-source-connector.adoc | 39 +++++
.../camel-ehcache-kafka-sink-connector.adoc | 45 ++++++
.../camel-ehcache-kafka-source-connector.adoc | 48 +++++++
...el-elasticsearch-rest-kafka-sink-connector.adoc | 56 ++++++++
.../camel-elsql-kafka-sink-connector.adoc | 52 +++++++
.../camel-elsql-kafka-source-connector.adoc | 77 ++++++++++
.../camel-elytron-kafka-sink-connector.adoc | 52 +++++++
.../camel-elytron-kafka-source-connector.adoc | 52 +++++++
.../camel-etcd-keys-kafka-sink-connector.adoc | 43 ++++++
.../camel-etcd-stats-kafka-sink-connector.adoc | 43 ++++++
.../camel-etcd-stats-kafka-source-connector.adoc | 62 ++++++++
.../camel-etcd-watch-kafka-source-connector.adoc | 46 ++++++
.../camel-eventadmin-kafka-sink-connector.adoc | 31 ++++
.../camel-eventadmin-kafka-source-connector.adoc | 33 +++++
.../camel-exec-kafka-sink-connector.adoc | 37 +++++
.../camel-facebook-kafka-sink-connector.adoc | 128 +++++++++++++++++
.../camel-facebook-kafka-source-connector.adoc | 130 +++++++++++++++++
.../camel-fhir-kafka-sink-connector.adoc | 55 +++++++
.../camel-fhir-kafka-source-connector.adoc | 73 ++++++++++
.../camel-file-kafka-sink-connector.adoc | 50 +++++++
.../camel-file-kafka-source-connector.adoc | 103 +++++++++++++
.../camel-file-watch-kafka-source-connector.adoc | 45 ++++++
.../camel-flatpack-kafka-sink-connector.adoc | 36 +++++
.../camel-flatpack-kafka-source-connector.adoc | 54 +++++++
.../camel-flink-kafka-sink-connector.adoc | 38 +++++
.../connectors/camel-fop-kafka-sink-connector.adoc | 31 ++++
.../camel-freemarker-kafka-sink-connector.adoc | 34 +++++
.../connectors/camel-ftp-kafka-sink-connector.adoc | 73 ++++++++++
.../camel-ftp-kafka-source-connector.adoc | 124 ++++++++++++++++
.../camel-ftps-kafka-sink-connector.adoc | 82 +++++++++++
.../camel-ftps-kafka-source-connector.adoc | 133 +++++++++++++++++
.../camel-ganglia-kafka-sink-connector.adoc | 43 ++++++
.../camel-geocoder-kafka-sink-connector.adoc | 42 ++++++
.../connectors/camel-git-kafka-sink-connector.adoc | 37 +++++
.../camel-git-kafka-source-connector.adoc | 38 +++++
.../camel-github-kafka-sink-connector.adoc | 37 +++++
.../camel-github-kafka-source-connector.adoc | 37 +++++
...camel-google-bigquery-kafka-sink-connector.adoc | 36 +++++
...l-google-bigquery-sql-kafka-sink-connector.adoc | 33 +++++
...camel-google-calendar-kafka-sink-connector.adoc | 42 ++++++
...mel-google-calendar-kafka-source-connector.adoc | 60 ++++++++
...gle-calendar-stream-kafka-source-connector.adoc | 60 ++++++++
.../camel-google-drive-kafka-sink-connector.adoc | 40 ++++++
.../camel-google-drive-kafka-source-connector.adoc | 58 ++++++++
.../camel-google-mail-kafka-sink-connector.adoc | 38 +++++
.../camel-google-mail-kafka-source-connector.adoc | 56 ++++++++
...-google-mail-stream-kafka-source-connector.adoc | 58 ++++++++
.../camel-google-pubsub-kafka-sink-connector.adoc | 36 +++++
...camel-google-pubsub-kafka-source-connector.adoc | 38 +++++
.../camel-google-sheets-kafka-sink-connector.adoc | 38 +++++
...camel-google-sheets-kafka-source-connector.adoc | 56 ++++++++
...oogle-sheets-stream-kafka-source-connector.adoc | 62 ++++++++
.../camel-gora-kafka-sink-connector.adoc | 34 +++++
.../camel-gora-kafka-source-connector.adoc | 47 ++++++
.../camel-grape-kafka-sink-connector.adoc | 30 ++++
.../camel-graphql-kafka-sink-connector.adoc | 37 +++++
.../camel-grpc-kafka-sink-connector.adoc | 48 +++++++
.../camel-grpc-kafka-source-connector.adoc | 50 +++++++
.../camel-guava-eventbus-kafka-sink-connector.adoc | 33 +++++
...amel-guava-eventbus-kafka-source-connector.adoc | 35 +++++
...hazelcast-atomicvalue-kafka-sink-connector.adoc | 34 +++++
...-hazelcast-instance-kafka-source-connector.adoc | 36 +++++
.../camel-hazelcast-list-kafka-sink-connector.adoc | 34 +++++
...amel-hazelcast-list-kafka-source-connector.adoc | 36 +++++
.../camel-hazelcast-map-kafka-sink-connector.adoc | 34 +++++
...camel-hazelcast-map-kafka-source-connector.adoc | 36 +++++
...el-hazelcast-multimap-kafka-sink-connector.adoc | 34 +++++
...-hazelcast-multimap-kafka-source-connector.adoc | 36 +++++
...camel-hazelcast-queue-kafka-sink-connector.adoc | 34 +++++
...mel-hazelcast-queue-kafka-source-connector.adoc | 39 +++++
...zelcast-replicatedmap-kafka-sink-connector.adoc | 34 +++++
...lcast-replicatedmap-kafka-source-connector.adoc | 36 +++++
...-hazelcast-ringbuffer-kafka-sink-connector.adoc | 34 +++++
.../camel-hazelcast-seda-kafka-sink-connector.adoc | 39 +++++
...amel-hazelcast-seda-kafka-source-connector.adoc | 41 ++++++
.../camel-hazelcast-set-kafka-sink-connector.adoc | 34 +++++
...camel-hazelcast-set-kafka-source-connector.adoc | 36 +++++
...camel-hazelcast-topic-kafka-sink-connector.adoc | 35 +++++
...mel-hazelcast-topic-kafka-source-connector.adoc | 37 +++++
.../camel-hbase-kafka-sink-connector.adoc | 39 +++++
.../camel-hbase-kafka-source-connector.adoc | 44 ++++++
.../camel-hdfs-kafka-sink-connector.adoc | 55 +++++++
.../camel-hdfs-kafka-source-connector.adoc | 74 ++++++++++
.../camel-hipchat-kafka-sink-connector.adoc | 34 +++++
.../camel-hipchat-kafka-source-connector.adoc | 52 +++++++
.../camel-http-kafka-sink-connector.adoc | 95 ++++++++++++
.../camel-https-kafka-sink-connector.adoc | 95 ++++++++++++
...camel-iec60870-client-kafka-sink-connector.adoc | 46 ++++++
...mel-iec60870-client-kafka-source-connector.adoc | 48 +++++++
...camel-iec60870-server-kafka-sink-connector.adoc | 47 ++++++
...mel-iec60870-server-kafka-source-connector.adoc | 49 +++++++
.../camel-ignite-cache-kafka-sink-connector.adoc | 38 +++++
.../camel-ignite-cache-kafka-source-connector.adoc | 43 ++++++
.../camel-ignite-compute-kafka-sink-connector.adoc | 39 +++++
...camel-ignite-events-kafka-source-connector.adoc | 38 +++++
.../camel-ignite-idgen-kafka-sink-connector.adoc | 37 +++++
...amel-ignite-messaging-kafka-sink-connector.adoc | 37 +++++
...el-ignite-messaging-kafka-source-connector.adoc | 37 +++++
.../camel-ignite-queue-kafka-sink-connector.adoc | 38 +++++
.../camel-ignite-set-kafka-sink-connector.adoc | 36 +++++
.../camel-imap-kafka-sink-connector.adoc | 58 ++++++++
.../camel-imap-kafka-source-connector.adoc | 89 ++++++++++++
.../camel-imaps-kafka-sink-connector.adoc | 58 ++++++++
.../camel-imaps-kafka-source-connector.adoc | 89 ++++++++++++
.../camel-infinispan-kafka-sink-connector.adoc | 41 ++++++
.../camel-infinispan-kafka-source-connector.adoc | 47 ++++++
.../camel-influxdb-kafka-sink-connector.adoc | 34 +++++
.../camel-iota-kafka-sink-connector.adoc | 35 +++++
.../camel-ipfs-kafka-sink-connector.adoc | 32 +++++
.../connectors/camel-irc-kafka-sink-connector.adoc | 54 +++++++
.../camel-irc-kafka-source-connector.adoc | 56 ++++++++
.../camel-ironmq-kafka-sink-connector.adoc | 35 +++++
.../camel-ironmq-kafka-source-connector.adoc | 57 ++++++++
.../camel-jbpm-kafka-sink-connector.adoc | 56 ++++++++
.../camel-jbpm-kafka-source-connector.adoc | 57 ++++++++
.../camel-jcache-kafka-sink-connector.adoc | 48 +++++++
.../camel-jcache-kafka-source-connector.adoc | 53 +++++++
.../camel-jclouds-kafka-sink-connector.adoc | 42 ++++++
.../camel-jclouds-kafka-source-connector.adoc | 36 +++++
.../connectors/camel-jcr-kafka-sink-connector.adoc | 40 ++++++
.../camel-jcr-kafka-source-connector.adoc | 42 ++++++
.../camel-jdbc-kafka-sink-connector.adoc | 42 ++++++
.../camel-jetty-kafka-source-connector.adoc | 90 ++++++++++++
.../camel-jgroups-kafka-sink-connector.adoc | 32 +++++
.../camel-jgroups-kafka-source-connector.adoc | 36 +++++
.../camel-jgroups-raft-kafka-sink-connector.adoc | 33 +++++
.../camel-jgroups-raft-kafka-source-connector.adoc | 36 +++++
.../camel-jing-kafka-sink-connector.adoc | 30 ++++
.../camel-jira-kafka-sink-connector.adoc | 38 +++++
.../camel-jira-kafka-source-connector.adoc | 42 ++++++
.../connectors/camel-jms-kafka-sink-connector.adoc | 155 ++++++++++++++++++++
.../camel-jms-kafka-source-connector.adoc | 156 ++++++++++++++++++++
.../camel-jmx-kafka-source-connector.adoc | 57 ++++++++
.../camel-jolt-kafka-sink-connector.adoc | 34 +++++
.../camel-jooq-kafka-sink-connector.adoc | 33 +++++
.../camel-jooq-kafka-source-connector.adoc | 50 +++++++
.../connectors/camel-jpa-kafka-sink-connector.adoc | 48 +++++++
.../camel-jpa-kafka-source-connector.adoc | 69 +++++++++
.../camel-jslt-kafka-sink-connector.adoc | 32 +++++
.../camel-json-validator-kafka-sink-connector.adoc | 35 +++++
.../camel-jt400-kafka-sink-connector.adoc | 43 ++++++
.../camel-jt400-kafka-source-connector.adoc | 60 ++++++++
.../camel-kafka-kafka-sink-connector.adoc | 95 ++++++++++++
.../camel-kafka-kafka-source-connector.adoc | 92 ++++++++++++
...ubernetes-config-maps-kafka-sink-connector.adoc | 48 +++++++
...ubernetes-deployments-kafka-sink-connector.adoc | 48 +++++++
...ernetes-deployments-kafka-source-connector.adoc | 54 +++++++
.../camel-kubernetes-hpa-kafka-sink-connector.adoc | 48 +++++++
...amel-kubernetes-hpa-kafka-source-connector.adoc | 54 +++++++
.../camel-kubernetes-job-kafka-sink-connector.adoc | 48 +++++++
...amel-kubernetes-job-kafka-source-connector.adoc | 54 +++++++
...kubernetes-namespaces-kafka-sink-connector.adoc | 48 +++++++
...bernetes-namespaces-kafka-source-connector.adoc | 54 +++++++
...amel-kubernetes-nodes-kafka-sink-connector.adoc | 48 +++++++
...el-kubernetes-nodes-kafka-source-connector.adoc | 54 +++++++
...istent-volumes-claims-kafka-sink-connector.adoc | 48 +++++++
...es-persistent-volumes-kafka-sink-connector.adoc | 48 +++++++
...camel-kubernetes-pods-kafka-sink-connector.adoc | 48 +++++++
...mel-kubernetes-pods-kafka-source-connector.adoc | 54 +++++++
...plication-controllers-kafka-sink-connector.adoc | 48 +++++++
...ication-controllers-kafka-source-connector.adoc | 54 +++++++
...netes-resources-quota-kafka-sink-connector.adoc | 48 +++++++
...el-kubernetes-secrets-kafka-sink-connector.adoc | 48 +++++++
...etes-service-accounts-kafka-sink-connector.adoc | 48 +++++++
...l-kubernetes-services-kafka-sink-connector.adoc | 48 +++++++
...kubernetes-services-kafka-source-connector.adoc | 54 +++++++
.../camel-kudu-kafka-sink-connector.adoc | 32 +++++
.../camel-language-kafka-sink-connector.adoc | 35 +++++
.../camel-ldap-kafka-sink-connector.adoc | 33 +++++
.../camel-ldif-kafka-sink-connector.adoc | 29 ++++
.../connectors/camel-log-kafka-sink-connector.adoc | 55 +++++++
.../connectors/camel-lpr-kafka-sink-connector.adoc | 41 ++++++
.../camel-lucene-kafka-sink-connector.adoc | 35 +++++
.../camel-lumberjack-kafka-source-connector.adoc | 35 +++++
.../camel-master-kafka-source-connector.adoc | 34 +++++
.../camel-metrics-kafka-sink-connector.adoc | 37 +++++
.../camel-micrometer-kafka-sink-connector.adoc | 36 +++++
...-microprofile-metrics-kafka-sink-connector.adoc | 42 ++++++
.../camel-milo-client-kafka-sink-connector.adoc | 57 ++++++++
.../camel-milo-client-kafka-source-connector.adoc | 59 ++++++++
.../camel-milo-server-kafka-sink-connector.adoc | 46 ++++++
.../camel-milo-server-kafka-source-connector.adoc | 48 +++++++
.../camel-mina-kafka-sink-connector.adoc | 53 +++++++
.../camel-mina-kafka-source-connector.adoc | 56 ++++++++
.../camel-mllp-kafka-sink-connector.adoc | 49 +++++++
.../camel-mllp-kafka-source-connector.adoc | 56 ++++++++
.../camel-mock-kafka-sink-connector.adoc | 39 +++++
.../camel-mongodb-gridfs-kafka-sink-connector.adoc | 34 +++++
...amel-mongodb-gridfs-kafka-source-connector.adoc | 42 ++++++
.../camel-mongodb-kafka-sink-connector.adoc | 49 +++++++
.../camel-mongodb-kafka-source-connector.adoc | 52 +++++++
.../connectors/camel-msv-kafka-sink-connector.adoc | 40 ++++++
.../camel-mustache-kafka-sink-connector.adoc | 34 +++++
.../camel-mvel-kafka-sink-connector.adoc | 31 ++++
.../camel-mybatis-bean-kafka-sink-connector.adoc | 35 +++++
.../camel-mybatis-kafka-sink-connector.adoc | 35 +++++
.../camel-mybatis-kafka-source-connector.adoc | 55 +++++++
.../camel-nagios-kafka-sink-connector.adoc | 36 +++++
.../camel-nats-kafka-sink-connector.adoc | 49 +++++++
.../camel-nats-kafka-source-connector.adoc | 54 +++++++
.../camel-netty-http-kafka-sink-connector.adoc | 87 +++++++++++
.../camel-netty-http-kafka-source-connector.adoc | 103 +++++++++++++
.../camel-netty-kafka-sink-connector.adoc | 83 +++++++++++
.../camel-netty-kafka-source-connector.adoc | 91 ++++++++++++
.../camel-nitrite-kafka-sink-connector.adoc | 34 +++++
.../camel-nitrite-kafka-source-connector.adoc | 36 +++++
.../connectors/camel-nsq-kafka-sink-connector.adoc | 36 +++++
.../camel-nsq-kafka-source-connector.adoc | 44 ++++++
.../camel-olingo2-kafka-sink-connector.adoc | 43 ++++++
.../camel-olingo2-kafka-source-connector.adoc | 62 ++++++++
.../camel-olingo4-kafka-sink-connector.adoc | 43 ++++++
.../camel-olingo4-kafka-source-connector.adoc | 62 ++++++++
...enshift-build-configs-kafka-sink-connector.adoc | 48 +++++++
...amel-openshift-builds-kafka-sink-connector.adoc | 48 +++++++
...amel-openstack-cinder-kafka-sink-connector.adoc | 37 +++++
...amel-openstack-glance-kafka-sink-connector.adoc | 36 +++++
...el-openstack-keystone-kafka-sink-connector.adoc | 36 +++++
...mel-openstack-neutron-kafka-sink-connector.adoc | 37 +++++
.../camel-openstack-nova-kafka-sink-connector.adoc | 37 +++++
...camel-openstack-swift-kafka-sink-connector.adoc | 37 +++++
.../camel-optaplanner-kafka-sink-connector.adoc | 32 +++++
.../camel-optaplanner-kafka-source-connector.adoc | 32 +++++
.../camel-paho-kafka-sink-connector.adoc | 59 ++++++++
.../camel-paho-kafka-source-connector.adoc | 61 ++++++++
.../camel-paxlogging-kafka-source-connector.adoc | 32 +++++
.../connectors/camel-pdf-kafka-sink-connector.adoc | 37 +++++
...pg-replication-slot-kafka-source-connector.adoc | 56 ++++++++
.../camel-pgevent-kafka-sink-connector.adoc | 35 +++++
.../camel-pgevent-kafka-source-connector.adoc | 37 +++++
...camel-platform-http-kafka-source-connector.adoc | 37 +++++
.../camel-pop3-kafka-sink-connector.adoc | 58 ++++++++
.../camel-pop3-kafka-source-connector.adoc | 89 ++++++++++++
.../camel-pop3s-kafka-sink-connector.adoc | 58 ++++++++
.../camel-pop3s-kafka-source-connector.adoc | 89 ++++++++++++
.../camel-pubnub-kafka-sink-connector.adoc | 38 +++++
.../camel-pubnub-kafka-source-connector.adoc | 40 ++++++
.../camel-pulsar-kafka-sink-connector.adoc | 46 ++++++
.../camel-pulsar-kafka-source-connector.adoc | 48 +++++++
.../camel-quartz-kafka-source-connector.adoc | 58 ++++++++
.../camel-quickfix-kafka-sink-connector.adoc | 36 +++++
.../camel-quickfix-kafka-source-connector.adoc | 38 +++++
.../camel-rabbitmq-kafka-sink-connector.adoc | 116 +++++++++++++++
.../camel-rabbitmq-kafka-source-connector.adoc | 116 +++++++++++++++
...amel-reactive-streams-kafka-sink-connector.adoc | 33 +++++
...el-reactive-streams-kafka-source-connector.adoc | 38 +++++
.../connectors/camel-ref-kafka-sink-connector.adoc | 29 ++++
.../camel-ref-kafka-source-connector.adoc | 31 ++++
.../camel-rest-api-kafka-source-connector.adoc | 34 +++++
.../camel-rest-kafka-sink-connector.adoc | 45 ++++++
.../camel-rest-kafka-source-connector.adoc | 41 ++++++
.../camel-rest-openapi-kafka-sink-connector.adoc | 43 ++++++
.../camel-rest-swagger-kafka-sink-connector.adoc | 44 ++++++
.../camel-robotframework-kafka-sink-connector.adoc | 76 ++++++++++
...amel-robotframework-kafka-source-connector.adoc | 94 ++++++++++++
.../camel-rss-kafka-source-connector.adoc | 55 +++++++
.../camel-saga-kafka-sink-connector.adoc | 29 ++++
.../camel-salesforce-kafka-sink-connector.adoc | 98 +++++++++++++
.../camel-salesforce-kafka-source-connector.adoc | 101 +++++++++++++
.../camel-sap-netweaver-kafka-sink-connector.adoc | 34 +++++
.../camel-scheduler-kafka-source-connector.adoc | 49 +++++++
.../camel-schematron-kafka-sink-connector.adoc | 32 +++++
.../connectors/camel-scp-kafka-sink-connector.adoc | 53 +++++++
.../camel-seda-kafka-sink-connector.adoc | 43 ++++++
.../camel-seda-kafka-source-connector.adoc | 41 ++++++
.../camel-service-kafka-source-connector.adoc | 33 +++++
.../camel-servicenow-kafka-sink-connector.adoc | 85 +++++++++++
.../camel-servlet-kafka-source-connector.adoc | 58 ++++++++
.../camel-sftp-kafka-sink-connector.adoc | 81 +++++++++++
.../camel-sftp-kafka-source-connector.adoc | 134 +++++++++++++++++
.../connectors/camel-sip-kafka-sink-connector.adoc | 67 +++++++++
.../camel-sip-kafka-source-connector.adoc | 71 +++++++++
.../camel-sips-kafka-sink-connector.adoc | 67 +++++++++
.../camel-sips-kafka-source-connector.adoc | 71 +++++++++
.../camel-sjms-batch-kafka-source-connector.adoc | 54 +++++++
.../camel-sjms-kafka-sink-connector.adoc | 65 +++++++++
.../camel-sjms-kafka-source-connector.adoc | 73 ++++++++++
.../camel-sjms2-kafka-sink-connector.adoc | 65 +++++++++
.../camel-sjms2-kafka-source-connector.adoc | 76 ++++++++++
.../camel-slack-kafka-sink-connector.adoc | 34 +++++
.../camel-slack-kafka-source-connector.adoc | 51 +++++++
.../camel-smpp-kafka-sink-connector.adoc | 64 +++++++++
.../camel-smpp-kafka-source-connector.adoc | 53 +++++++
.../camel-smpps-kafka-sink-connector.adoc | 64 +++++++++
.../camel-smpps-kafka-source-connector.adoc | 53 +++++++
.../camel-smtp-kafka-sink-connector.adoc | 58 ++++++++
.../camel-smtp-kafka-source-connector.adoc | 89 ++++++++++++
.../camel-smtps-kafka-sink-connector.adoc | 58 ++++++++
.../camel-smtps-kafka-source-connector.adoc | 89 ++++++++++++
.../camel-snmp-kafka-sink-connector.adoc | 45 ++++++
.../camel-snmp-kafka-source-connector.adoc | 64 +++++++++
.../camel-solr-kafka-sink-connector.adoc | 43 ++++++
.../camel-solrCloud-kafka-sink-connector.adoc | 43 ++++++
.../camel-solrs-kafka-sink-connector.adoc | 43 ++++++
.../camel-soroush-kafka-sink-connector.adoc | 44 ++++++
.../camel-soroush-kafka-source-connector.adoc | 43 ++++++
.../camel-spark-kafka-sink-connector.adoc | 36 +++++
.../camel-spark-rest-kafka-source-connector.adoc | 50 +++++++
.../camel-splunk-kafka-sink-connector.adoc | 46 ++++++
.../camel-splunk-kafka-source-connector.adoc | 65 +++++++++
.../camel-spring-batch-kafka-sink-connector.adoc | 34 +++++
.../camel-spring-event-kafka-sink-connector.adoc | 29 ++++
.../camel-spring-event-kafka-source-connector.adoc | 31 ++++
...el-spring-integration-kafka-sink-connector.adoc | 31 ++++
...-spring-integration-kafka-source-connector.adoc | 33 +++++
.../camel-spring-ldap-kafka-sink-connector.adoc | 31 ++++
.../camel-spring-redis-kafka-sink-connector.adoc | 35 +++++
.../camel-spring-redis-kafka-source-connector.adoc | 38 +++++
.../camel-spring-ws-kafka-sink-connector.adoc | 45 ++++++
.../camel-spring-ws-kafka-source-connector.adoc | 38 +++++
.../connectors/camel-sql-kafka-sink-connector.adoc | 47 ++++++
.../camel-sql-kafka-source-connector.adoc | 72 ++++++++++
.../camel-sql-stored-kafka-sink-connector.adoc | 36 +++++
.../connectors/camel-ssh-kafka-sink-connector.adoc | 56 ++++++++
.../camel-ssh-kafka-source-connector.adoc | 75 ++++++++++
.../camel-stax-kafka-sink-connector.adoc | 29 ++++
.../camel-stomp-kafka-sink-connector.adoc | 44 ++++++
.../camel-stomp-kafka-source-connector.adoc | 46 ++++++
.../camel-stream-kafka-sink-connector.adoc | 35 +++++
.../camel-stream-kafka-source-connector.adoc | 43 ++++++
...camel-string-template-kafka-sink-connector.adoc | 32 +++++
.../camel-stub-kafka-sink-connector.adoc | 43 ++++++
.../camel-stub-kafka-source-connector.adoc | 41 ++++++
.../camel-telegram-kafka-sink-connector.adoc | 40 ++++++
.../camel-telegram-kafka-source-connector.adoc | 59 ++++++++
.../camel-thrift-kafka-sink-connector.adoc | 37 +++++
.../camel-thrift-kafka-source-connector.adoc | 41 ++++++
.../camel-tika-kafka-sink-connector.adoc | 33 +++++
.../camel-timer-kafka-source-connector.adoc | 40 ++++++
.../camel-twilio-kafka-sink-connector.adoc | 36 +++++
.../camel-twilio-kafka-source-connector.adoc | 54 +++++++
...twitter-directmessage-kafka-sink-connector.adoc | 45 ++++++
...itter-directmessage-kafka-source-connector.adoc | 77 ++++++++++
.../camel-twitter-search-kafka-sink-connector.adoc | 45 ++++++
...amel-twitter-search-kafka-source-connector.adoc | 77 ++++++++++
...amel-twitter-timeline-kafka-sink-connector.adoc | 46 ++++++
...el-twitter-timeline-kafka-source-connector.adoc | 78 ++++++++++
.../camel-undertow-kafka-sink-connector.adoc | 48 +++++++
.../camel-undertow-kafka-source-connector.adoc | 48 +++++++
.../camel-validator-kafka-sink-connector.adoc | 39 +++++
.../camel-velocity-kafka-sink-connector.adoc | 34 +++++
.../camel-vertx-kafka-sink-connector.adoc | 36 +++++
.../camel-vertx-kafka-source-connector.adoc | 38 +++++
.../connectors/camel-vm-kafka-sink-connector.adoc | 43 ++++++
.../camel-vm-kafka-source-connector.adoc | 41 ++++++
.../camel-weather-kafka-sink-connector.adoc | 57 ++++++++
.../camel-weather-kafka-source-connector.adoc | 75 ++++++++++
.../camel-web3j-kafka-sink-connector.adoc | 64 +++++++++
.../camel-web3j-kafka-source-connector.adoc | 43 ++++++
.../camel-webhook-kafka-source-connector.adoc | 37 +++++
...amel-websocket-jsr356-kafka-sink-connector.adoc | 31 ++++
...el-websocket-jsr356-kafka-source-connector.adoc | 33 +++++
.../camel-websocket-kafka-sink-connector.adoc | 55 +++++++
.../camel-websocket-kafka-source-connector.adoc | 58 ++++++++
.../camel-weka-kafka-sink-connector.adoc | 38 +++++
.../camel-wordpress-kafka-sink-connector.adoc | 39 +++++
.../camel-wordpress-kafka-source-connector.adoc | 41 ++++++
.../camel-workday-kafka-sink-connector.adoc | 37 +++++
.../camel-xchange-kafka-sink-connector.adoc | 33 +++++
.../connectors/camel-xj-kafka-sink-connector.adoc | 53 +++++++
...amel-xmlsecurity-sign-kafka-sink-connector.adoc | 56 ++++++++
...el-xmlsecurity-verify-kafka-sink-connector.adoc | 46 ++++++
.../camel-xmpp-kafka-sink-connector.adoc | 44 ++++++
.../camel-xmpp-kafka-source-connector.adoc | 48 +++++++
.../camel-xquery-kafka-sink-connector.adoc | 44 ++++++
.../camel-xquery-kafka-source-connector.adoc | 62 ++++++++
.../camel-xslt-kafka-sink-connector.adoc | 46 ++++++
.../camel-xslt-saxon-kafka-sink-connector.adoc | 52 +++++++
.../camel-yammer-kafka-sink-connector.adoc | 39 +++++
.../camel-yammer-kafka-source-connector.adoc | 62 ++++++++
.../camel-zendesk-kafka-sink-connector.adoc | 37 +++++
.../camel-zendesk-kafka-source-connector.adoc | 55 +++++++
.../camel-zookeeper-kafka-sink-connector.adoc | 35 +++++
.../camel-zookeeper-kafka-source-connector.adoc | 38 +++++
...el-zookeeper-master-kafka-source-connector.adoc | 38 +++++
.../maven/AbstractCamelKafkaConnectorMojo.java | 6 +
.../maven/CamelKafkaConnectorUpdateMojo.java | 9 +-
524 files changed, 25966 insertions(+), 1 deletion(-)
diff --git a/docs/modules/ROOT/pages/connectors/camel-activemq-kafka-sink-connector.adoc b/docs/modules/ROOT/pages/connectors/camel-activemq-kafka-sink-connector.adoc
new file mode 100644
index 0000000..54fb13b
--- /dev/null
+++ b/docs/modules/ROOT/pages/connectors/camel-activemq-kafka-sink-connector.adoc
@@ -0,0 +1,159 @@
+// kafka-connector options: START
+== camel-activemq-kafka-connector source configuration
+
+When using camel-activemq-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-activemq-kafka-connector</artifactId>
+ <version>x.x.x</version>
+ <!-- use the same version as your Camel Kafka connector version -->
+</dependency>
+----
+
+
+[width="100%",cols="2,5,^1,2",options="header"]
+|===
+| Name | Description | Default | Priority
+| *camel.sink.path.destinationType* | The kind of destination to use One of: [queue] [topic] [temp-queue] [temp-topic] | "queue" | ConfigDef.Importance.MEDIUM
+| *camel.sink.path.destinationName* | Name of the queue or topic to use as destination | null | ConfigDef.Importance.HIGH
+| *camel.sink.endpoint.clientId* | Sets the JMS client ID to use. Note that this value, if specified, must be unique and can only be used by a single JMS connection instance. It is typically only required for durable topic subscriptions. If using Apache ActiveMQ you may prefer to use Virtual Topics instead. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.connectionFactory* | The connection factory to be use. A connection factory must be configured either on the component or endpoint. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.disableReplyTo* | Specifies whether Camel ignores the JMSReplyTo header in messages. If true, Camel does not send a reply back to the destination specified in the JMSReplyTo header. You can use this option if you want Camel to consume from a route and you do not want Camel to automatically send back a reply message because another component in your code handles the reply message. You can also use this option if you want to use Camel as a proxy between different mes [...]
+| *camel.sink.endpoint.durableSubscriptionName* | The durable subscriber name for specifying durable topic subscriptions. The clientId option must be configured as well. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.jmsMessageType* | Allows you to force the use of a specific javax.jms.Message implementation for sending JMS messages. Possible values are: Bytes, Map, Object, Stream, Text. By default, Camel would determine which JMS message type to use from the In body type. This option allows you to specify it. One of: [Bytes] [Map] [Object] [Stream] [Text] | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.testConnectionOnStartup* | Specifies whether to test the connection on startup. This ensures that when Camel starts that all the JMS consumers have a valid connection to the JMS broker. If a connection cannot be granted then Camel throws an exception on startup. This ensures that Camel is not started with failed connections. The JMS producers is tested as well. | false | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.deliveryDelay* | Sets delivery delay to use for send calls for JMS. This option requires JMS 2.0 compliant broker. | -1L | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.deliveryMode* | Specifies the delivery mode to be used. Possibles values are those defined by javax.jms.DeliveryMode. NON_PERSISTENT = 1 and PERSISTENT = 2. One of: [1] [2] | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.deliveryPersistent* | Specifies whether persistent delivery is used by default. | true | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.explicitQosEnabled* | Set if the deliveryMode, priority or timeToLive qualities of service should be used when sending messages. This option is based on Spring's JmsTemplate. The deliveryMode, priority and timeToLive options are applied to the current endpoint. This contrasts with the preserveMessageQos option, which operates at message granularity, reading QoS properties exclusively from the Camel In message headers. | "false" | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.formatDateHeadersToIso8601* | Sets whether JMS date properties should be formatted according to the ISO 8601 standard. | false | ConfigDef.Importance.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 cre [...]
+| *camel.sink.endpoint.preserveMessageQos* | Set to true, if you want to send message using the QoS settings specified on the message, instead of the QoS settings on the JMS endpoint. The following three headers are considered JMSPriority, JMSDeliveryMode, and JMSExpiration. You can provide all or only some of them. If not provided, Camel will fall back to use the values from the endpoint instead. So, when using this option, the headers override the values from the endpoint. The explicit [...]
+| *camel.sink.endpoint.priority* | Values greater than 1 specify the message priority when sending (where 0 is the lowest priority and 9 is the highest). The explicitQosEnabled option must also be enabled in order for this option to have any effect. One of: [1] [2] [3] [4] [5] [6] [7] [8] [9] | 4 | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.replyToConcurrentConsumers* | Specifies the default number of concurrent consumers when doing request/reply over JMS. See also the maxMessagesPerTask option to control dynamic scaling up/down of threads. | 1 | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.replyToMaxConcurrentConsumers* | Specifies the maximum number of concurrent consumers when using request/reply over JMS. See also the maxMessagesPerTask option to control dynamic scaling up/down of threads. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.replyToOnTimeoutMaxConcurrentConsumers* | Specifies the maximum number of concurrent consumers for continue routing when timeout occurred when using request/reply over JMS. | 1 | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.replyToOverride* | Provides an explicit ReplyTo destination in the JMS message, which overrides the setting of replyTo. It is useful if you want to forward the message to a remote Queue and receive the reply message from the ReplyTo destination. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.replyToType* | Allows for explicitly specifying which kind of strategy to use for replyTo queues when doing request/reply over JMS. Possible values are: Temporary, Shared, or Exclusive. By default Camel will use temporary queues. However if replyTo has been configured, then Shared is used by default. This option allows you to use exclusive queues instead of shared ones. See Camel JMS documentation for more details, and especially the notes about the implications if [...]
+| *camel.sink.endpoint.requestTimeout* | The timeout for waiting for a reply when using the InOut Exchange Pattern (in milliseconds). The default is 20 seconds. You can include the header CamelJmsRequestTimeout to override this endpoint configured timeout value, and thus have per message individual timeout values. See also the requestTimeoutCheckerInterval option. | 20000L | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.timeToLive* | When sending messages, specifies the time-to-live of the message (in milliseconds). | -1L | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.allowAdditionalHeaders* | This option is used to allow additional headers which may have values that are invalid according to JMS specification. For example some message systems such as WMQ do this with header names using prefix JMS_IBM_MQMD_ containing values with byte array or other invalid types. You can specify multiple header names separated by comma, and use as suffix for wildcard matching. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.allowNullBody* | Whether to allow sending messages with no body. If this option is false and the message body is null, then an JMSException is thrown. | true | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.alwaysCopyMessage* | If true, Camel will always make a JMS message copy of the message when it is passed to the producer for sending. Copying the message is needed in some situations, such as when a replyToDestinationSelectorName is set (incidentally, Camel will set the alwaysCopyMessage option to true, if a replyToDestinationSelectorName is set) | false | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.correlationProperty* | When using InOut exchange pattern use this JMS property instead of JMSCorrelationID JMS property to correlate messages. If set messages will be correlated solely on the value of this property JMSCorrelationID property will be ignored and not set by Camel. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.disableTimeToLive* | Use this option to force disabling time to live. For example when you do request/reply over JMS, then Camel will by default use the requestTimeout value as time to live on the message being sent. The problem is that the sender and receiver systems have to have their clocks synchronized, so they are in sync. This is not always so easy to archive. So you can use disableTimeToLive=true to not set a time to live value on the sent message. Then the [...]
+| *camel.sink.endpoint.forceSendOriginalMessage* | When using mapJmsMessage=false Camel will create a new JMS message to send to a new JMS destination if you touch the headers (get or set) during the route. Set this option to true to force Camel to send the original JMS message that was received. | false | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.includeSentJMSMessageID* | Only applicable when sending to JMS destination using InOnly (eg fire and forget). Enabling this option will enrich the Camel Exchange with the actual JMSMessageID that was used by the JMS client when the message was sent to the JMS destination. | false | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.replyToCacheLevelName* | Sets the cache level by name for the reply consumer when doing request/reply over JMS. This option only applies when using fixed reply queues (not temporary). Camel will by default use: CACHE_CONSUMER for exclusive or shared w/ replyToSelectorName. And CACHE_SESSION for shared without replyToSelectorName. Some JMS brokers such as IBM WebSphere may require to set the replyToCacheLevelName=CACHE_NONE to work. Note: If using temporary queues t [...]
+| *camel.sink.endpoint.replyToDestinationSelectorName* | Sets the JMS Selector using the fixed name to be used so you can filter out your own replies from the others when using a shared queue (that is, if you are not using a temporary reply queue). | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.streamMessageTypeEnabled* | Sets whether StreamMessage type is enabled or not. Message payloads of streaming kind such as files, InputStream, etc will either by sent as BytesMessage or StreamMessage. This option controls which kind will be used. By default BytesMessage is used which enforces the entire message payload to be read into memory. By enabling this option the message payload is read into memory in chunks and each chunk is then written to the StreamMessage [...]
+| *camel.sink.endpoint.allowSerializedHeaders* | Controls whether or not to include serialized headers. Applies only when transferExchange is true. This requires that the objects are serializable. Camel will exclude any non-serializable objects and log it at WARN level. | false | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.asyncStartListener* | Whether to startup the JmsConsumer message listener asynchronously, when starting a route. For example if a JmsConsumer cannot get a connection to a remote JMS broker, then it may block while retrying and/or failover. This will cause Camel to block while starting routes. By setting this option to true, you will let routes startup, while the JmsConsumer connects to the JMS broker using a dedicated thread in asynchronous mode. If this option is [...]
+| *camel.sink.endpoint.asyncStopListener* | Whether to stop the JmsConsumer message listener asynchronously, when stopping a route. | false | ConfigDef.Importance.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 | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.destinationResolver* | A pluggable org.springframework.jms.support.destination.DestinationResolver that allows you to use your own resolver (for example, to lookup the real destination in a JNDI registry). | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.errorHandler* | Specifies a org.springframework.util.ErrorHandler to be invoked in case of any uncaught exceptions thrown while processing a Message. By default these exceptions will be logged at the WARN level, if no errorHandler has been configured. You can configure logging level and whether stack traces should be logged using errorHandlerLoggingLevel and errorHandlerLogStackTrace options. This makes it much easier to configure, than having to code a custom erro [...]
+| *camel.sink.endpoint.exceptionListener* | Specifies the JMS Exception Listener that is to be notified of any underlying JMS exceptions. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.headerFilterStrategy* | To use a custom HeaderFilterStrategy to filter header to and from Camel message. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.idleConsumerLimit* | Specify the limit for the number of consumers that are allowed to be idle at any given time. | 1 | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.idleTaskExecutionLimit* | Specifies the limit for idle executions of a receive task, not having received any message within its execution. If this limit is reached, the task will shut down and leave receiving to other executing tasks (in the case of dynamic scheduling; see the maxConcurrentConsumers setting). There is additional doc available from Spring. | 1 | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.includeAllJMSXProperties* | Whether to include all JMSXxxx properties when mapping from JMS to Camel Message. Setting this to true will include properties such as JMSXAppID, and JMSXUserID etc. Note: If you are using a custom headerFilterStrategy then this option does not apply. | false | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.jmsKeyFormatStrategy* | Pluggable strategy for encoding and decoding JMS keys so they can be compliant with the JMS specification. Camel provides two implementations out of the box: default and passthrough. The default strategy will safely marshal dots and hyphens (. and -). The passthrough strategy leaves the key as is. Can be used for JMS brokers which do not care whether JMS header keys contain illegal characters. You can provide your own implementation of the o [...]
+| *camel.sink.endpoint.mapJmsMessage* | Specifies whether Camel should auto map the received JMS message to a suited payload type, such as javax.jms.TextMessage to a String etc. | true | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.maxMessagesPerTask* | The number of messages per task. -1 is unlimited. If you use a range for concurrent consumers (eg min max), then this option can be used to set a value to eg 100 to control how fast the consumers will shrink when less work is required. | -1 | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.messageConverter* | To use a custom Spring org.springframework.jms.support.converter.MessageConverter so you can be in control how to map to/from a javax.jms.Message. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.messageCreatedStrategy* | To use the given MessageCreatedStrategy which are invoked when Camel creates new instances of javax.jms.Message objects when Camel is sending a JMS message. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.messageIdEnabled* | When sending, specifies whether message IDs should be added. This is just an hint to the JMS broker. If the JMS provider accepts this hint, these messages must have the message ID set to null; if the provider ignores the hint, the message ID must be set to its normal unique value. | true | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.messageListenerContainerFactory* | Registry ID of the MessageListenerContainerFactory used to determine what org.springframework.jms.listener.AbstractMessageListenerContainer to use to consume messages. Setting this will automatically set consumerType to Custom. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.messageTimestampEnabled* | Specifies whether timestamps should be enabled by default on sending messages. This is just an hint to the JMS broker. If the JMS provider accepts this hint, these messages must have the timestamp set to zero; if the provider ignores the hint the timestamp must be set to its normal value. | true | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.pubSubNoLocal* | Specifies whether to inhibit the delivery of messages published by its own connection. | false | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.receiveTimeout* | The timeout for receiving messages (in milliseconds). | 1000L | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.recoveryInterval* | Specifies the interval between recovery attempts, i.e. when a connection is being refreshed, in milliseconds. The default is 5000 ms, that is, 5 seconds. | 5000L | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.requestTimeoutCheckerInterval* | Configures how often Camel should check for timed out Exchanges when doing request/reply over JMS. By default Camel checks once per second. But if you must react faster when a timeout occurs, then you can lower this interval, to check more frequently. The timeout is determined by the option requestTimeout. | 1000L | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.synchronous* | Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). | false | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.transferException* | If enabled and you are using Request Reply messaging (InOut) and an Exchange failed on the consumer side, then the caused Exception will be send back in response as a javax.jms.ObjectMessage. If the client is Camel, the returned Exception is rethrown. This allows you to use Camel JMS as a bridge in your routing - for example, using persistent queues to enable robust routing. Notice that if you also have transferExchange enabled, this option tak [...]
+| *camel.sink.endpoint.transferExchange* | You can transfer the exchange over the wire instead of just the body and headers. The following fields are transferred: In body, Out body, Fault body, In headers, Out headers, Fault headers, exchange properties, exchange exception. This requires that the objects are serializable. Camel will exclude any non-serializable objects and log it at WARN level. You must enable this option on both the producer and consumer side, so Camel knows the payload [...]
+| *camel.sink.endpoint.useMessageIDAsCorrelationID* | Specifies whether JMSMessageID should always be used as JMSCorrelationID for InOut messages. | false | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.waitForProvisionCorrelationToBeUpdatedCounter* | Number of times to wait for provisional correlation id to be updated to the actual correlation id when doing request/reply over JMS and when the option useMessageIDAsCorrelationID is enabled. | 50 | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.waitForProvisionCorrelationToBeUpdatedThreadSleepingTime* | Interval in millis to sleep each time while waiting for provisional correlation id to be updated. | 100L | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.password* | Password to use with the ConnectionFactory. You can also configure username/password directly on the ConnectionFactory. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.username* | Username to use with the ConnectionFactory. You can also configure username/password directly on the ConnectionFactory. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.transacted* | Specifies whether to use transacted mode | false | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.lazyCreateTransactionManager* | If true, Camel will create a JmsTransactionManager, if there is no transactionManager injected when option transacted=true. | true | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.transactionManager* | The Spring transaction manager to use. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.transactionName* | The name of the transaction to use. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.transactionTimeout* | The timeout value of the transaction (in seconds), if using transacted mode. | -1 | ConfigDef.Importance.MEDIUM
+| *camel.component.activemq.brokerURL* | Sets the broker URL to use to connect to ActiveMQ | null | ConfigDef.Importance.MEDIUM
+| *camel.component.activemq.clientId* | Sets the JMS client ID to use. Note that this value, if specified, must be unique and can only be used by a single JMS connection instance. It is typically only required for durable topic subscriptions. If using Apache ActiveMQ you may prefer to use Virtual Topics instead. | null | ConfigDef.Importance.MEDIUM
+| *camel.component.activemq.configuration* | Configuration of ActiveMQ | null | ConfigDef.Importance.MEDIUM
+| *camel.component.activemq.connectionFactory* | The connection factory to be use. A connection factory must be configured either on the component or endpoint. | null | ConfigDef.Importance.MEDIUM
+| *camel.component.activemq.durableSubscriptionName* | The durable subscriber name for specifying durable topic subscriptions. The clientId option must be configured as well. | null | ConfigDef.Importance.MEDIUM
+| *camel.component.activemq.testConnectionOnStartup* | Specifies whether to test the connection on startup. This ensures that when Camel starts that all the JMS consumers have a valid connection to the JMS broker. If a connection cannot be granted then Camel throws an exception on startup. This ensures that Camel is not started with failed connections. The JMS producers is tested as well. | false | ConfigDef.Importance.MEDIUM
+| *camel.component.activemq.trustAllPackages* | Define if all Java packages are trusted or not (for Java object JMS message types). Notice its not recommended practice to send Java serialized objects over network. Setting this to true can expose security risks, so use this with care. | false | ConfigDef.Importance.MEDIUM
+| *camel.component.activemq.usePooledConnection* | Enables or disables whether a PooledConnectionFactory will be used so that when messages are sent to ActiveMQ from outside of a message consuming thread, pooling will be used rather than the default with the Spring JmsTemplate which will create a new connection, session, producer for each message then close them all down again. The default value is true. | false | ConfigDef.Importance.MEDIUM
+| *camel.component.activemq.useSingleConnection* | Enables or disables whether a Spring SingleConnectionFactory will be used so that when messages are sent to ActiveMQ from outside of a message consuming thread, pooling will be used rather than the default with the Spring JmsTemplate which will create a new connection, session, producer for each message then close them all down again. The default value is false and a pooled connection is used by default. | false | ConfigDef.Importance.MEDIUM
+| *camel.component.activemq.deliveryMode* | Specifies the delivery mode to be used. Possibles values are those defined by javax.jms.DeliveryMode. NON_PERSISTENT = 1 and PERSISTENT = 2. One of: [1] [2] | null | ConfigDef.Importance.MEDIUM
+| *camel.component.activemq.deliveryPersistent* | Specifies whether persistent delivery is used by default. | true | ConfigDef.Importance.MEDIUM
+| *camel.component.activemq.explicitQosEnabled* | Set if the deliveryMode, priority or timeToLive qualities of service should be used when sending messages. This option is based on Spring's JmsTemplate. The deliveryMode, priority and timeToLive options are applied to the current endpoint. This contrasts with the preserveMessageQos option, which operates at message granularity, reading QoS properties exclusively from the Camel In message headers. | false | ConfigDef.Importance.MEDIUM
+| *camel.component.activemq.formatDateHeadersToIso8601* | Sets whether date headers should be formatted according to the ISO 8601 standard. | false | ConfigDef.Importance.MEDIUM
+| *camel.component.activemq.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 the [...]
+| *camel.component.activemq.preserveMessageQos* | Set to true, if you want to send message using the QoS settings specified on the message, instead of the QoS settings on the JMS endpoint. The following three headers are considered JMSPriority, JMSDeliveryMode, and JMSExpiration. You can provide all or only some of them. If not provided, Camel will fall back to use the values from the endpoint instead. So, when using this option, the headers override the values from the endpoint. The exp [...]
+| *camel.component.activemq.priority* | Values greater than 1 specify the message priority when sending (where 0 is the lowest priority and 9 is the highest). The explicitQosEnabled option must also be enabled in order for this option to have any effect. One of: [1] [2] [3] [4] [5] [6] [7] [8] [9] | 4 | ConfigDef.Importance.MEDIUM
+| *camel.component.activemq.replyOnTimeoutToMaxConcurrentConsumers* | Specifies the maximum number of concurrent consumers for continue routing when timeout occurred when using request/reply over JMS. | 1 | ConfigDef.Importance.MEDIUM
+| *camel.component.activemq.replyToConcurrentConsumers* | Specifies the default number of concurrent consumers when doing request/reply over JMS. See also the maxMessagesPerTask option to control dynamic scaling up/down of threads. | 1 | ConfigDef.Importance.MEDIUM
+| *camel.component.activemq.replyToMaxConcurrentConsumers* | Specifies the maximum number of concurrent consumers when using request/reply over JMS. See also the maxMessagesPerTask option to control dynamic scaling up/down of threads. | null | ConfigDef.Importance.MEDIUM
+| *camel.component.activemq.replyToType* | Allows for explicitly specifying which kind of strategy to use for replyTo queues when doing request/reply over JMS. Possible values are: Temporary, Shared, or Exclusive. By default Camel will use temporary queues. However if replyTo has been configured, then Shared is used by default. This option allows you to use exclusive queues instead of shared ones. See Camel JMS documentation for more details, and especially the notes about the implicatio [...]
+| *camel.component.activemq.requestTimeout* | The timeout for waiting for a reply when using the InOut Exchange Pattern (in milliseconds). The default is 20 seconds. You can include the header CamelJmsRequestTimeout to override this endpoint configured timeout value, and thus have per message individual timeout values. See also the requestTimeoutCheckerInterval option. | 20000L | ConfigDef.Importance.MEDIUM
+| *camel.component.activemq.timeToLive* | When sending messages, specifies the time-to-live of the message (in milliseconds). | -1L | ConfigDef.Importance.MEDIUM
+| *camel.component.activemq.allowAdditionalHeaders* | This option is used to allow additional headers which may have values that are invalid according to JMS specification. For example some message systems such as WMQ do this with header names using prefix JMS_IBM_MQMD_ containing values with byte array or other invalid types. You can specify multiple header names separated by comma, and use as suffix for wildcard matching. | null | ConfigDef.Importance.MEDIUM
+| *camel.component.activemq.allowNullBody* | Whether to allow sending messages with no body. If this option is false and the message body is null, then an JMSException is thrown. | true | ConfigDef.Importance.MEDIUM
+| *camel.component.activemq.alwaysCopyMessage* | If true, Camel will always make a JMS message copy of the message when it is passed to the producer for sending. Copying the message is needed in some situations, such as when a replyToDestinationSelectorName is set (incidentally, Camel will set the alwaysCopyMessage option to true, if a replyToDestinationSelectorName is set). | false | ConfigDef.Importance.MEDIUM
+| *camel.component.activemq.correlationProperty* | Use this JMS property to correlate messages in InOut exchange pattern (request-reply) instead of JMSCorrelationID property. This allows you to exchange messages with systems that do not correlate messages using JMSCorrelationID JMS property. If used JMSCorrelationID will not be used or set by Camel. The value of here named property will be generated if not supplied in the header of the message under the same name. | null | ConfigDef.Impo [...]
+| *camel.component.activemq.forceSendOriginalMessage* | When using mapJmsMessage=false Camel will create a new JMS message to send to a new JMS destination if you touch the headers (get or set) during the route. Set this option to true to force Camel to send the original JMS message that was received. | false | ConfigDef.Importance.MEDIUM
+| *camel.component.activemq.includeSentJMSMessageID* | Only applicable when sending to JMS destination using InOnly (eg fire and forget). Enabling this option will enrich the Camel Exchange with the actual JMSMessageID that was used by the JMS client when the message was sent to the JMS destination. | false | ConfigDef.Importance.MEDIUM
+| *camel.component.activemq.replyToCacheLevelName* | Sets the cache level by name for the reply consumer when doing request/reply over JMS. This option only applies when using fixed reply queues (not temporary). Camel will by default use: CACHE_CONSUMER for exclusive or shared w/ replyToSelectorName. And CACHE_SESSION for shared without replyToSelectorName. Some JMS brokers such as IBM WebSphere may require to set the replyToCacheLevelName=CACHE_NONE to work. Note: If using temporary que [...]
+| *camel.component.activemq.streamMessageTypeEnabled* | Sets whether StreamMessage type is enabled or not. Message payloads of streaming kind such as files, InputStream, etc will either by sent as BytesMessage or StreamMessage. This option controls which kind will be used. By default BytesMessage is used which enforces the entire message payload to be read into memory. By enabling this option the message payload is read into memory in chunks and each chunk is then written to the StreamMe [...]
+| *camel.component.activemq.allowAutoWiredConnectionFactory* | Whether to auto-discover ConnectionFactory from the registry, if no connection factory has been configured. If only one instance of ConnectionFactory is found then it will be used. This is enabled by default. | false | ConfigDef.Importance.MEDIUM
+| *camel.component.activemq.allowAutoWiredDestinationResolver* | Whether to auto-discover DestinationResolver from the registry, if no destination resolver has been configured. If only one instance of DestinationResolver is found then it will be used. This is enabled by default. | false | ConfigDef.Importance.MEDIUM
+| *camel.component.activemq.asyncStartListener* | Whether to startup the JmsConsumer message listener asynchronously, when starting a route. For example if a JmsConsumer cannot get a connection to a remote JMS broker, then it may block while retrying and/or failover. This will cause Camel to block while starting routes. By setting this option to true, you will let routes startup, while the JmsConsumer connects to the JMS broker using a dedicated thread in asynchronous mode. If this optio [...]
+| *camel.component.activemq.asyncStopListener* | Whether to stop the JmsConsumer message listener asynchronously, when stopping a route. | false | ConfigDef.Importance.MEDIUM
+| *camel.component.activemq.basicPropertyBinding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+| *camel.component.activemq.destinationResolver* | A pluggable org.springframework.jms.support.destination.DestinationResolver that allows you to use your own resolver (for example, to lookup the real destination in a JNDI registry). | null | ConfigDef.Importance.MEDIUM
+| *camel.component.activemq.errorHandler* | Specifies a org.springframework.util.ErrorHandler to be invoked in case of any uncaught exceptions thrown while processing a Message. By default these exceptions will be logged at the WARN level, if no errorHandler has been configured. You can configure logging level and whether stack traces should be logged using errorHandlerLoggingLevel and errorHandlerLogStackTrace options. This makes it much easier to configure, than having to code a custom [...]
+| *camel.component.activemq.exceptionListener* | Specifies the JMS Exception Listener that is to be notified of any underlying JMS exceptions. | null | ConfigDef.Importance.MEDIUM
+| *camel.component.activemq.idleConsumerLimit* | Specify the limit for the number of consumers that are allowed to be idle at any given time. | 1 | ConfigDef.Importance.MEDIUM
+| *camel.component.activemq.idleTaskExecutionLimit* | Specifies the limit for idle executions of a receive task, not having received any message within its execution. If this limit is reached, the task will shut down and leave receiving to other executing tasks (in the case of dynamic scheduling; see the maxConcurrentConsumers setting). There is additional doc available from Spring. | 1 | ConfigDef.Importance.MEDIUM
+| *camel.component.activemq.includeAllJMSXProperties* | Whether to include all JMSXxxx properties when mapping from JMS to Camel Message. Setting this to true will include properties such as JMSXAppID, and JMSXUserID etc. Note: If you are using a custom headerFilterStrategy then this option does not apply. | false | ConfigDef.Importance.MEDIUM
+| *camel.component.activemq.jmsKeyFormatStrategy* | Pluggable strategy for encoding and decoding JMS keys so they can be compliant with the JMS specification. Camel provides two implementations out of the box: default and passthrough. The default strategy will safely marshal dots and hyphens (. and -). The passthrough strategy leaves the key as is. Can be used for JMS brokers which do not care whether JMS header keys contain illegal characters. You can provide your own implementation of [...]
+| *camel.component.activemq.jmsOperations* | Allows you to use your own implementation of the org.springframework.jms.core.JmsOperations interface. Camel uses JmsTemplate as default. Can be used for testing purpose, but not used much as stated in the spring API docs. | null | ConfigDef.Importance.MEDIUM
+| *camel.component.activemq.mapJmsMessage* | Specifies whether Camel should auto map the received JMS message to a suited payload type, such as javax.jms.TextMessage to a String etc. | true | ConfigDef.Importance.MEDIUM
+| *camel.component.activemq.maxMessagesPerTask* | The number of messages per task. -1 is unlimited. If you use a range for concurrent consumers (eg min max), then this option can be used to set a value to eg 100 to control how fast the consumers will shrink when less work is required. | -1 | ConfigDef.Importance.MEDIUM
+| *camel.component.activemq.messageConverter* | To use a custom Spring org.springframework.jms.support.converter.MessageConverter so you can be in control how to map to/from a javax.jms.Message. | null | ConfigDef.Importance.MEDIUM
+| *camel.component.activemq.messageCreatedStrategy* | To use the given MessageCreatedStrategy which are invoked when Camel creates new instances of javax.jms.Message objects when Camel is sending a JMS message. | null | ConfigDef.Importance.MEDIUM
+| *camel.component.activemq.messageIdEnabled* | When sending, specifies whether message IDs should be added. This is just an hint to the JMS broker. If the JMS provider accepts this hint, these messages must have the message ID set to null; if the provider ignores the hint, the message ID must be set to its normal unique value. | true | ConfigDef.Importance.MEDIUM
+| *camel.component.activemq.messageTimestampEnabled* | Specifies whether timestamps should be enabled by default on sending messages. This is just an hint to the JMS broker. If the JMS provider accepts this hint, these messages must have the timestamp set to zero; if the provider ignores the hint the timestamp must be set to its normal value. | true | ConfigDef.Importance.MEDIUM
+| *camel.component.activemq.pubSubNoLocal* | Specifies whether to inhibit the delivery of messages published by its own connection. | false | ConfigDef.Importance.MEDIUM
+| *camel.component.activemq.queueBrowseStrategy* | To use a custom QueueBrowseStrategy when browsing queues | null | ConfigDef.Importance.MEDIUM
+| *camel.component.activemq.receiveTimeout* | The timeout for receiving messages (in milliseconds). | 1000L | ConfigDef.Importance.MEDIUM
+| *camel.component.activemq.recoveryInterval* | Specifies the interval between recovery attempts, i.e. when a connection is being refreshed, in milliseconds. The default is 5000 ms, that is, 5 seconds. | 5000L | ConfigDef.Importance.MEDIUM
+| *camel.component.activemq.requestTimeoutCheckerInterval* | Configures how often Camel should check for timed out Exchanges when doing request/reply over JMS. By default Camel checks once per second. But if you must react faster when a timeout occurs, then you can lower this interval, to check more frequently. The timeout is determined by the option requestTimeout. | 1000L | ConfigDef.Importance.MEDIUM
+| *camel.component.activemq.transferException* | If enabled and you are using Request Reply messaging (InOut) and an Exchange failed on the consumer side, then the caused Exception will be send back in response as a javax.jms.ObjectMessage. If the client is Camel, the returned Exception is rethrown. This allows you to use Camel JMS as a bridge in your routing - for example, using persistent queues to enable robust routing. Notice that if you also have transferExchange enabled, this optio [...]
+| *camel.component.activemq.transferExchange* | You can transfer the exchange over the wire instead of just the body and headers. The following fields are transferred: In body, Out body, Fault body, In headers, Out headers, Fault headers, exchange properties, exchange exception. This requires that the objects are serializable. Camel will exclude any non-serializable objects and log it at WARN level. You must enable this option on both the producer and consumer side, so Camel knows the pa [...]
+| *camel.component.activemq.useMessageIDAsCorrelationID* | Specifies whether JMSMessageID should always be used as JMSCorrelationID for InOut messages. | false | ConfigDef.Importance.MEDIUM
+| *camel.component.activemq.waitForProvisionCorrelationToBeUpdatedCounter* | Number of times to wait for provisional correlation id to be updated to the actual correlation id when doing request/reply over JMS and when the option useMessageIDAsCorrelationID is enabled. | 50 | ConfigDef.Importance.MEDIUM
+| *camel.component.activemq.waitForProvisionCorrelationToBeUpdatedThreadSleepingTime* | Interval in millis to sleep each time while waiting for provisional correlation id to be updated. | 100L | ConfigDef.Importance.MEDIUM
+| *camel.component.activemq.headerFilterStrategy* | To use a custom org.apache.camel.spi.HeaderFilterStrategy to filter header to and from Camel message. | null | ConfigDef.Importance.MEDIUM
+| *camel.component.activemq.password* | Password to use with the ConnectionFactory. You can also configure username/password directly on the ConnectionFactory. | null | ConfigDef.Importance.MEDIUM
+| *camel.component.activemq.username* | Username to use with the ConnectionFactory. You can also configure username/password directly on the ConnectionFactory. | null | ConfigDef.Importance.MEDIUM
+| *camel.component.activemq.transacted* | Specifies whether to use transacted mode | false | ConfigDef.Importance.MEDIUM
+| *camel.component.activemq.lazyCreateTransactionManager* | If true, Camel will create a JmsTransactionManager, if there is no transactionManager injected when option transacted=true. | true | ConfigDef.Importance.MEDIUM
+| *camel.component.activemq.transactionManager* | The Spring transaction manager to use. | null | ConfigDef.Importance.MEDIUM
+| *camel.component.activemq.transactionName* | The name of the transaction to use. | null | ConfigDef.Importance.MEDIUM
+| *camel.component.activemq.transactionTimeout* | The timeout value of the transaction (in seconds), if using transacted mode. | -1 | ConfigDef.Importance.MEDIUM
+|===
+
+
+// kafka-connector options: END
diff --git a/docs/modules/ROOT/pages/connectors/camel-activemq-kafka-source-connector.adoc b/docs/modules/ROOT/pages/connectors/camel-activemq-kafka-source-connector.adoc
new file mode 100644
index 0000000..30d68ff
--- /dev/null
+++ b/docs/modules/ROOT/pages/connectors/camel-activemq-kafka-source-connector.adoc
@@ -0,0 +1,160 @@
+// kafka-connector options: START
+== camel-activemq-kafka-connector source configuration
+
+When using camel-activemq-kafka-connector as source 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-activemq-kafka-connector</artifactId>
+ <version>x.x.x</version>
+ <!-- use the same version as your Camel Kafka connector version -->
+</dependency>
+----
+
+
+[width="100%",cols="2,5,^1,2",options="header"]
+|===
+| Name | Description | Default | Priority
+| *camel.source.path.destinationType* | The kind of destination to use One of: [queue] [topic] [temp-queue] [temp-topic] | "queue" | ConfigDef.Importance.MEDIUM
+| *camel.source.path.destinationName* | Name of the queue or topic to use as destination | null | ConfigDef.Importance.HIGH
+| *camel.source.endpoint.clientId* | Sets the JMS client ID to use. Note that this value, if specified, must be unique and can only be used by a single JMS connection instance. It is typically only required for durable topic subscriptions. If using Apache ActiveMQ you may prefer to use Virtual Topics instead. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.connectionFactory* | The connection factory to be use. A connection factory must be configured either on the component or endpoint. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.disableReplyTo* | Specifies whether Camel ignores the JMSReplyTo header in messages. If true, Camel does not send a reply back to the destination specified in the JMSReplyTo header. You can use this option if you want Camel to consume from a route and you do not want Camel to automatically send back a reply message because another component in your code handles the reply message. You can also use this option if you want to use Camel as a proxy between different m [...]
+| *camel.source.endpoint.durableSubscriptionName* | The durable subscriber name for specifying durable topic subscriptions. The clientId option must be configured as well. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.jmsMessageType* | Allows you to force the use of a specific javax.jms.Message implementation for sending JMS messages. Possible values are: Bytes, Map, Object, Stream, Text. By default, Camel would determine which JMS message type to use from the In body type. This option allows you to specify it. One of: [Bytes] [Map] [Object] [Stream] [Text] | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.testConnectionOnStartup* | Specifies whether to test the connection on startup. This ensures that when Camel starts that all the JMS consumers have a valid connection to the JMS broker. If a connection cannot be granted then Camel throws an exception on startup. This ensures that Camel is not started with failed connections. The JMS producers is tested as well. | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.acknowledgementModeName* | The JMS acknowledgement name, which is one of: SESSION_TRANSACTED, CLIENT_ACKNOWLEDGE, AUTO_ACKNOWLEDGE, DUPS_OK_ACKNOWLEDGE One of: [SESSION_TRANSACTED] [CLIENT_ACKNOWLEDGE] [AUTO_ACKNOWLEDGE] [DUPS_OK_ACKNOWLEDGE] | "AUTO_ACKNOWLEDGE" | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.asyncConsumer* | Whether the JmsConsumer processes the Exchange asynchronously. If enabled then the JmsConsumer may pickup the next message from the JMS queue, while the previous message is being processed asynchronously (by the Asynchronous Routing Engine). This means that messages may be processed not 100% strictly in order. If disabled (as default) then the Exchange is fully processed before the JmsConsumer will pickup the next message from the JMS queue. Note [...]
+| *camel.source.endpoint.autoStartup* | Specifies whether the consumer container should auto-startup. | true | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.cacheLevel* | Sets the cache level by ID for the underlying JMS resources. See cacheLevelName option for more details. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.cacheLevelName* | Sets the cache level by name for the underlying JMS resources. Possible values are: CACHE_AUTO, CACHE_CONNECTION, CACHE_CONSUMER, CACHE_NONE, and CACHE_SESSION. The default setting is CACHE_AUTO. See the Spring documentation and Transactions Cache Levels for more information. One of: [CACHE_AUTO] [CACHE_CONNECTION] [CACHE_CONSUMER] [CACHE_NONE] [CACHE_SESSION] | "CACHE_AUTO" | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.concurrentConsumers* | Specifies the default number of concurrent consumers when consuming from JMS (not for request/reply over JMS). See also the maxMessagesPerTask option to control dynamic scaling up/down of threads. When doing request/reply over JMS then the option replyToConcurrentConsumers is used to control number of concurrent consumers on the reply message listener. | 1 | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.maxConcurrentConsumers* | Specifies the maximum number of concurrent consumers when consuming from JMS (not for request/reply over JMS). See also the maxMessagesPerTask option to control dynamic scaling up/down of threads. When doing request/reply over JMS then the option replyToMaxConcurrentConsumers is used to control number of concurrent consumers on the reply message listener. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.replyTo* | Provides an explicit ReplyTo destination, which overrides any incoming value of Message.getJMSReplyTo(). | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.replyToDeliveryPersistent* | Specifies whether to use persistent delivery by default for replies. | true | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.selector* | Sets the JMS selector to use | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.subscriptionDurable* | Set whether to make the subscription durable. The durable subscription name to be used can be specified through the subscriptionName property. Default is false. Set this to true to register a durable subscription, typically in combination with a subscriptionName value (unless your message listener class name is good enough as subscription name). Only makes sense when listening to a topic (pub-sub domain), therefore this method switches the [...]
+| *camel.source.endpoint.subscriptionName* | Set the name of a subscription to create. To be applied in case of a topic (pub-sub domain) with a shared or durable subscription. The subscription name needs to be unique within this client's JMS client id. Default is the class name of the specified message listener. Note: Only 1 concurrent consumer (which is the default of this message listener container) is allowed for each subscription, except for a shared subscription (which requires JMS [...]
+| *camel.source.endpoint.subscriptionShared* | Set whether to make the subscription shared. The shared subscription name to be used can be specified through the subscriptionName property. Default is false. Set this to true to register a shared subscription, typically in combination with a subscriptionName value (unless your message listener class name is good enough as subscription name). Note that shared subscriptions may also be durable, so this flag can (and often will) be combined wi [...]
+| *camel.source.endpoint.acceptMessagesWhileStopping* | Specifies whether the consumer accept messages while it is stopping. You may consider enabling this option, if you start and stop JMS routes at runtime, while there are still messages enqueued on the queue. If this option is false, and you stop the JMS route, then messages may be rejected, and the JMS broker would have to attempt redeliveries, which yet again may be rejected, and eventually the message may be moved at a dead letter [...]
+| *camel.source.endpoint.allowReplyManagerQuickStop* | Whether the DefaultMessageListenerContainer used in the reply managers for request-reply messaging allow the DefaultMessageListenerContainer.runningAllowed flag to quick stop in case JmsConfiguration#isAcceptMessagesWhileStopping is enabled, and org.apache.camel.CamelContext is currently being stopped. This quick stop ability is enabled by default in the regular JMS consumers but to enable for reply managers you must enable this flag [...]
+| *camel.source.endpoint.consumerType* | The consumer type to use, which can be one of: Simple, Default, or Custom. The consumer type determines which Spring JMS listener to use. Default will use org.springframework.jms.listener.DefaultMessageListenerContainer, Simple will use org.springframework.jms.listener.SimpleMessageListenerContainer. When Custom is specified, the MessageListenerContainerFactory defined by the messageListenerContainerFactory option will determine what org.springfra [...]
+| *camel.source.endpoint.defaultTaskExecutorType* | Specifies what default TaskExecutor type to use in the DefaultMessageListenerContainer, for both consumer endpoints and the ReplyTo consumer of producer endpoints. Possible values: SimpleAsync (uses Spring's SimpleAsyncTaskExecutor) or ThreadPool (uses Spring's ThreadPoolTaskExecutor with optimal values - cached threadpool-like). If not set, it defaults to the previous behaviour, which uses a cached thread pool for consumer endpoints an [...]
+| *camel.source.endpoint.eagerLoadingOfProperties* | Enables eager loading of JMS properties and payload as soon as a message is loaded which generally is inefficient as the JMS properties may not be required but sometimes can catch early any issues with the underlying JMS provider and the use of JMS properties. See also the option eagerPoisonBody. | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.eagerPoisonBody* | If eagerLoadingOfProperties is enabled and the JMS message payload (JMS body or JMS properties) is poison (cannot be read/mapped), then set this text as the message body instead so the message can be processed (the cause of the poison are already stored as exception on the Exchange). This can be turned off by setting eagerPoisonBody=false. See also the option eagerLoadingOfProperties. | "Poison JMS message due to ${exception.message}" | ConfigD [...]
+| *camel.source.endpoint.exceptionHandler* | To let the consumer use a custom ExceptionHandler. Notice if the option bridgeErrorHandler is enabled then this option is not in use. By default the consumer will deal with exceptions, that will be logged at WARN or ERROR level and ignored. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.exchangePattern* | Sets the exchange pattern when the consumer creates an exchange. One of: [InOnly] [InOut] [InOptionalOut] | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.exposeListenerSession* | Specifies whether the listener session should be exposed when consuming messages. | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.replyToSameDestinationAllowed* | Whether a JMS consumer is allowed to send a reply message to the same destination that the consumer is using to consume from. This prevents an endless loop by consuming and sending back the same message to itself. | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.taskExecutor* | Allows you to specify a custom task executor for consuming messages. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.allowSerializedHeaders* | Controls whether or not to include serialized headers. Applies only when transferExchange is true. This requires that the objects are serializable. Camel will exclude any non-serializable objects and log it at WARN level. | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.asyncStartListener* | Whether to startup the JmsConsumer message listener asynchronously, when starting a route. For example if a JmsConsumer cannot get a connection to a remote JMS broker, then it may block while retrying and/or failover. This will cause Camel to block while starting routes. By setting this option to true, you will let routes startup, while the JmsConsumer connects to the JMS broker using a dedicated thread in asynchronous mode. If this option i [...]
+| *camel.source.endpoint.asyncStopListener* | Whether to stop the JmsConsumer message listener asynchronously, when stopping a route. | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.basicPropertyBinding* | Whether the endpoint should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.destinationResolver* | A pluggable org.springframework.jms.support.destination.DestinationResolver that allows you to use your own resolver (for example, to lookup the real destination in a JNDI registry). | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.errorHandler* | Specifies a org.springframework.util.ErrorHandler to be invoked in case of any uncaught exceptions thrown while processing a Message. By default these exceptions will be logged at the WARN level, if no errorHandler has been configured. You can configure logging level and whether stack traces should be logged using errorHandlerLoggingLevel and errorHandlerLogStackTrace options. This makes it much easier to configure, than having to code a custom er [...]
+| *camel.source.endpoint.exceptionListener* | Specifies the JMS Exception Listener that is to be notified of any underlying JMS exceptions. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.headerFilterStrategy* | To use a custom HeaderFilterStrategy to filter header to and from Camel message. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.idleConsumerLimit* | Specify the limit for the number of consumers that are allowed to be idle at any given time. | 1 | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.idleTaskExecutionLimit* | Specifies the limit for idle executions of a receive task, not having received any message within its execution. If this limit is reached, the task will shut down and leave receiving to other executing tasks (in the case of dynamic scheduling; see the maxConcurrentConsumers setting). There is additional doc available from Spring. | 1 | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.includeAllJMSXProperties* | Whether to include all JMSXxxx properties when mapping from JMS to Camel Message. Setting this to true will include properties such as JMSXAppID, and JMSXUserID etc. Note: If you are using a custom headerFilterStrategy then this option does not apply. | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.jmsKeyFormatStrategy* | Pluggable strategy for encoding and decoding JMS keys so they can be compliant with the JMS specification. Camel provides two implementations out of the box: default and passthrough. The default strategy will safely marshal dots and hyphens (. and -). The passthrough strategy leaves the key as is. Can be used for JMS brokers which do not care whether JMS header keys contain illegal characters. You can provide your own implementation of the [...]
+| *camel.source.endpoint.mapJmsMessage* | Specifies whether Camel should auto map the received JMS message to a suited payload type, such as javax.jms.TextMessage to a String etc. | true | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.maxMessagesPerTask* | The number of messages per task. -1 is unlimited. If you use a range for concurrent consumers (eg min max), then this option can be used to set a value to eg 100 to control how fast the consumers will shrink when less work is required. | -1 | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.messageConverter* | To use a custom Spring org.springframework.jms.support.converter.MessageConverter so you can be in control how to map to/from a javax.jms.Message. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.messageCreatedStrategy* | To use the given MessageCreatedStrategy which are invoked when Camel creates new instances of javax.jms.Message objects when Camel is sending a JMS message. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.messageIdEnabled* | When sending, specifies whether message IDs should be added. This is just an hint to the JMS broker. If the JMS provider accepts this hint, these messages must have the message ID set to null; if the provider ignores the hint, the message ID must be set to its normal unique value. | true | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.messageListenerContainerFactory* | Registry ID of the MessageListenerContainerFactory used to determine what org.springframework.jms.listener.AbstractMessageListenerContainer to use to consume messages. Setting this will automatically set consumerType to Custom. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.messageTimestampEnabled* | Specifies whether timestamps should be enabled by default on sending messages. This is just an hint to the JMS broker. If the JMS provider accepts this hint, these messages must have the timestamp set to zero; if the provider ignores the hint the timestamp must be set to its normal value. | true | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.pubSubNoLocal* | Specifies whether to inhibit the delivery of messages published by its own connection. | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.receiveTimeout* | The timeout for receiving messages (in milliseconds). | 1000L | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.recoveryInterval* | Specifies the interval between recovery attempts, i.e. when a connection is being refreshed, in milliseconds. The default is 5000 ms, that is, 5 seconds. | 5000L | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.requestTimeoutCheckerInterval* | Configures how often Camel should check for timed out Exchanges when doing request/reply over JMS. By default Camel checks once per second. But if you must react faster when a timeout occurs, then you can lower this interval, to check more frequently. The timeout is determined by the option requestTimeout. | 1000L | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.synchronous* | Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.transferException* | If enabled and you are using Request Reply messaging (InOut) and an Exchange failed on the consumer side, then the caused Exception will be send back in response as a javax.jms.ObjectMessage. If the client is Camel, the returned Exception is rethrown. This allows you to use Camel JMS as a bridge in your routing - for example, using persistent queues to enable robust routing. Notice that if you also have transferExchange enabled, this option t [...]
+| *camel.source.endpoint.transferExchange* | You can transfer the exchange over the wire instead of just the body and headers. The following fields are transferred: In body, Out body, Fault body, In headers, Out headers, Fault headers, exchange properties, exchange exception. This requires that the objects are serializable. Camel will exclude any non-serializable objects and log it at WARN level. You must enable this option on both the producer and consumer side, so Camel knows the paylo [...]
+| *camel.source.endpoint.useMessageIDAsCorrelationID* | Specifies whether JMSMessageID should always be used as JMSCorrelationID for InOut messages. | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.waitForProvisionCorrelationToBeUpdatedCounter* | Number of times to wait for provisional correlation id to be updated to the actual correlation id when doing request/reply over JMS and when the option useMessageIDAsCorrelationID is enabled. | 50 | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.waitForProvisionCorrelationToBeUpdatedThreadSleepingTime* | Interval in millis to sleep each time while waiting for provisional correlation id to be updated. | 100L | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.errorHandlerLoggingLevel* | Allows to configure the default errorHandler logging level for logging uncaught exceptions. One of: [TRACE] [DEBUG] [INFO] [WARN] [ERROR] [OFF] | "WARN" | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.errorHandlerLogStackTrace* | Allows to control whether stacktraces should be logged or not, by the default errorHandler. | true | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.password* | Password to use with the ConnectionFactory. You can also configure username/password directly on the ConnectionFactory. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.username* | Username to use with the ConnectionFactory. You can also configure username/password directly on the ConnectionFactory. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.transacted* | Specifies whether to use transacted mode | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.lazyCreateTransactionManager* | If true, Camel will create a JmsTransactionManager, if there is no transactionManager injected when option transacted=true. | true | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.transactionManager* | The Spring transaction manager to use. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.transactionName* | The name of the transaction to use. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.transactionTimeout* | The timeout value of the transaction (in seconds), if using transacted mode. | -1 | ConfigDef.Importance.MEDIUM
+| *camel.component.activemq.brokerURL* | Sets the broker URL to use to connect to ActiveMQ | null | ConfigDef.Importance.MEDIUM
+| *camel.component.activemq.clientId* | Sets the JMS client ID to use. Note that this value, if specified, must be unique and can only be used by a single JMS connection instance. It is typically only required for durable topic subscriptions. If using Apache ActiveMQ you may prefer to use Virtual Topics instead. | null | ConfigDef.Importance.MEDIUM
+| *camel.component.activemq.configuration* | Configuration of ActiveMQ | null | ConfigDef.Importance.MEDIUM
+| *camel.component.activemq.connectionFactory* | The connection factory to be use. A connection factory must be configured either on the component or endpoint. | null | ConfigDef.Importance.MEDIUM
+| *camel.component.activemq.durableSubscriptionName* | The durable subscriber name for specifying durable topic subscriptions. The clientId option must be configured as well. | null | ConfigDef.Importance.MEDIUM
+| *camel.component.activemq.testConnectionOnStartup* | Specifies whether to test the connection on startup. This ensures that when Camel starts that all the JMS consumers have a valid connection to the JMS broker. If a connection cannot be granted then Camel throws an exception on startup. This ensures that Camel is not started with failed connections. The JMS producers is tested as well. | false | ConfigDef.Importance.MEDIUM
+| *camel.component.activemq.trustAllPackages* | Define if all Java packages are trusted or not (for Java object JMS message types). Notice its not recommended practice to send Java serialized objects over network. Setting this to true can expose security risks, so use this with care. | false | ConfigDef.Importance.MEDIUM
+| *camel.component.activemq.usePooledConnection* | Enables or disables whether a PooledConnectionFactory will be used so that when messages are sent to ActiveMQ from outside of a message consuming thread, pooling will be used rather than the default with the Spring JmsTemplate which will create a new connection, session, producer for each message then close them all down again. The default value is true. | false | ConfigDef.Importance.MEDIUM
+| *camel.component.activemq.useSingleConnection* | Enables or disables whether a Spring SingleConnectionFactory will be used so that when messages are sent to ActiveMQ from outside of a message consuming thread, pooling will be used rather than the default with the Spring JmsTemplate which will create a new connection, session, producer for each message then close them all down again. The default value is false and a pooled connection is used by default. | false | ConfigDef.Importance.MEDIUM
+| *camel.component.activemq.acknowledgementMode* | The JMS acknowledgement mode defined as an Integer. Allows you to set vendor-specific extensions to the acknowledgment mode. For the regular modes, it is preferable to use the acknowledgementModeName instead. | null | ConfigDef.Importance.MEDIUM
+| *camel.component.activemq.acknowledgementModeName* | The JMS acknowledgement name, which is one of: SESSION_TRANSACTED, CLIENT_ACKNOWLEDGE, AUTO_ACKNOWLEDGE, DUPS_OK_ACKNOWLEDGE One of: [SESSION_TRANSACTED] [CLIENT_ACKNOWLEDGE] [AUTO_ACKNOWLEDGE] [DUPS_OK_ACKNOWLEDGE] | "AUTO_ACKNOWLEDGE" | ConfigDef.Importance.MEDIUM
+| *camel.component.activemq.asyncConsumer* | Whether the JmsConsumer processes the Exchange asynchronously. If enabled then the JmsConsumer may pickup the next message from the JMS queue, while the previous message is being processed asynchronously (by the Asynchronous Routing Engine). This means that messages may be processed not 100% strictly in order. If disabled (as default) then the Exchange is fully processed before the JmsConsumer will pickup the next message from the JMS queue. N [...]
+| *camel.component.activemq.autoStartup* | Specifies whether the consumer container should auto-startup. | true | ConfigDef.Importance.MEDIUM
+| *camel.component.activemq.bridgeErrorHandler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | ConfigDef.Importance.MEDIUM
+| *camel.component.activemq.cacheLevel* | Sets the cache level by ID for the underlying JMS resources. See cacheLevelName option for more details. | null | ConfigDef.Importance.MEDIUM
+| *camel.component.activemq.cacheLevelName* | Sets the cache level by name for the underlying JMS resources. Possible values are: CACHE_AUTO, CACHE_CONNECTION, CACHE_CONSUMER, CACHE_NONE, and CACHE_SESSION. The default setting is CACHE_AUTO. See the Spring documentation and Transactions Cache Levels for more information. One of: [CACHE_AUTO] [CACHE_CONNECTION] [CACHE_CONSUMER] [CACHE_NONE] [CACHE_SESSION] | "CACHE_AUTO" | ConfigDef.Importance.MEDIUM
+| *camel.component.activemq.concurrentConsumers* | Specifies the default number of concurrent consumers when consuming from JMS (not for request/reply over JMS). See also the maxMessagesPerTask option to control dynamic scaling up/down of threads. When doing request/reply over JMS then the option replyToConcurrentConsumers is used to control number of concurrent consumers on the reply message listener. | 1 | ConfigDef.Importance.MEDIUM
+| *camel.component.activemq.maxConcurrentConsumers* | Specifies the maximum number of concurrent consumers when consuming from JMS (not for request/reply over JMS). See also the maxMessagesPerTask option to control dynamic scaling up/down of threads. When doing request/reply over JMS then the option replyToMaxConcurrentConsumers is used to control number of concurrent consumers on the reply message listener. | null | ConfigDef.Importance.MEDIUM
+| *camel.component.activemq.subscriptionDurable* | Set whether to make the subscription durable. The durable subscription name to be used can be specified through the subscriptionName property. Default is false. Set this to true to register a durable subscription, typically in combination with a subscriptionName value (unless your message listener class name is good enough as subscription name). Only makes sense when listening to a topic (pub-sub domain), therefore this method switches t [...]
+| *camel.component.activemq.subscriptionName* | Set the name of a subscription to create. To be applied in case of a topic (pub-sub domain) with a shared or durable subscription. The subscription name needs to be unique within this client's JMS client id. Default is the class name of the specified message listener. Note: Only 1 concurrent consumer (which is the default of this message listener container) is allowed for each subscription, except for a shared subscription (which requires J [...]
+| *camel.component.activemq.subscriptionShared* | Set whether to make the subscription shared. The shared subscription name to be used can be specified through the subscriptionName property. Default is false. Set this to true to register a shared subscription, typically in combination with a subscriptionName value (unless your message listener class name is good enough as subscription name). Note that shared subscriptions may also be durable, so this flag can (and often will) be combined [...]
+| *camel.component.activemq.acceptMessagesWhileStopping* | Specifies whether the consumer accept messages while it is stopping. You may consider enabling this option, if you start and stop JMS routes at runtime, while there are still messages enqueued on the queue. If this option is false, and you stop the JMS route, then messages may be rejected, and the JMS broker would have to attempt redeliveries, which yet again may be rejected, and eventually the message may be moved at a dead lett [...]
+| *camel.component.activemq.allowReplyManagerQuickStop* | Whether the DefaultMessageListenerContainer used in the reply managers for request-reply messaging allow the DefaultMessageListenerContainer.runningAllowed flag to quick stop in case JmsConfiguration#isAcceptMessagesWhileStopping is enabled, and org.apache.camel.CamelContext is currently being stopped. This quick stop ability is enabled by default in the regular JMS consumers but to enable for reply managers you must enable this f [...]
+| *camel.component.activemq.defaultTaskExecutorType* | Specifies what default TaskExecutor type to use in the DefaultMessageListenerContainer, for both consumer endpoints and the ReplyTo consumer of producer endpoints. Possible values: SimpleAsync (uses Spring's SimpleAsyncTaskExecutor) or ThreadPool (uses Spring's ThreadPoolTaskExecutor with optimal values - cached threadpool-like). If not set, it defaults to the previous behaviour, which uses a cached thread pool for consumer endpoints [...]
+| *camel.component.activemq.eagerLoadingOfProperties* | Enables eager loading of JMS properties as soon as a message is loaded which generally is inefficient as the JMS properties may not be required but sometimes can catch early any issues with the underlying JMS provider and the use of JMS properties. See also the option eagerLoadingOfBody. | false | ConfigDef.Importance.MEDIUM
+| *camel.component.activemq.eagerPoisonBody* | If eagerLoadingOfProperties is enabled and the JMS message payload (JMS body or JMS properties) is poison (cannot be read/mapped), then set this text as the message body instead so the message can be processed (the cause of the poison are already stored as exception on the Exchange). This can be turned off by setting eagerPoisonBody=false. See also the option eagerLoadingOfProperties. | "Poison JMS message due to ${exception.message}" | Conf [...]
+| *camel.component.activemq.exposeListenerSession* | Specifies whether the listener session should be exposed when consuming messages. | false | ConfigDef.Importance.MEDIUM
+| *camel.component.activemq.taskExecutor* | Allows you to specify a custom task executor for consuming messages. | null | ConfigDef.Importance.MEDIUM
+| *camel.component.activemq.allowAutoWiredConnectionFactory* | Whether to auto-discover ConnectionFactory from the registry, if no connection factory has been configured. If only one instance of ConnectionFactory is found then it will be used. This is enabled by default. | false | ConfigDef.Importance.MEDIUM
+| *camel.component.activemq.allowAutoWiredDestinationResolver* | Whether to auto-discover DestinationResolver from the registry, if no destination resolver has been configured. If only one instance of DestinationResolver is found then it will be used. This is enabled by default. | false | ConfigDef.Importance.MEDIUM
+| *camel.component.activemq.asyncStartListener* | Whether to startup the JmsConsumer message listener asynchronously, when starting a route. For example if a JmsConsumer cannot get a connection to a remote JMS broker, then it may block while retrying and/or failover. This will cause Camel to block while starting routes. By setting this option to true, you will let routes startup, while the JmsConsumer connects to the JMS broker using a dedicated thread in asynchronous mode. If this optio [...]
+| *camel.component.activemq.asyncStopListener* | Whether to stop the JmsConsumer message listener asynchronously, when stopping a route. | false | ConfigDef.Importance.MEDIUM
+| *camel.component.activemq.basicPropertyBinding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+| *camel.component.activemq.destinationResolver* | A pluggable org.springframework.jms.support.destination.DestinationResolver that allows you to use your own resolver (for example, to lookup the real destination in a JNDI registry). | null | ConfigDef.Importance.MEDIUM
+| *camel.component.activemq.errorHandler* | Specifies a org.springframework.util.ErrorHandler to be invoked in case of any uncaught exceptions thrown while processing a Message. By default these exceptions will be logged at the WARN level, if no errorHandler has been configured. You can configure logging level and whether stack traces should be logged using errorHandlerLoggingLevel and errorHandlerLogStackTrace options. This makes it much easier to configure, than having to code a custom [...]
+| *camel.component.activemq.exceptionListener* | Specifies the JMS Exception Listener that is to be notified of any underlying JMS exceptions. | null | ConfigDef.Importance.MEDIUM
+| *camel.component.activemq.idleConsumerLimit* | Specify the limit for the number of consumers that are allowed to be idle at any given time. | 1 | ConfigDef.Importance.MEDIUM
+| *camel.component.activemq.idleTaskExecutionLimit* | Specifies the limit for idle executions of a receive task, not having received any message within its execution. If this limit is reached, the task will shut down and leave receiving to other executing tasks (in the case of dynamic scheduling; see the maxConcurrentConsumers setting). There is additional doc available from Spring. | 1 | ConfigDef.Importance.MEDIUM
+| *camel.component.activemq.includeAllJMSXProperties* | Whether to include all JMSXxxx properties when mapping from JMS to Camel Message. Setting this to true will include properties such as JMSXAppID, and JMSXUserID etc. Note: If you are using a custom headerFilterStrategy then this option does not apply. | false | ConfigDef.Importance.MEDIUM
+| *camel.component.activemq.jmsKeyFormatStrategy* | Pluggable strategy for encoding and decoding JMS keys so they can be compliant with the JMS specification. Camel provides two implementations out of the box: default and passthrough. The default strategy will safely marshal dots and hyphens (. and -). The passthrough strategy leaves the key as is. Can be used for JMS brokers which do not care whether JMS header keys contain illegal characters. You can provide your own implementation of [...]
+| *camel.component.activemq.jmsOperations* | Allows you to use your own implementation of the org.springframework.jms.core.JmsOperations interface. Camel uses JmsTemplate as default. Can be used for testing purpose, but not used much as stated in the spring API docs. | null | ConfigDef.Importance.MEDIUM
+| *camel.component.activemq.mapJmsMessage* | Specifies whether Camel should auto map the received JMS message to a suited payload type, such as javax.jms.TextMessage to a String etc. | true | ConfigDef.Importance.MEDIUM
+| *camel.component.activemq.maxMessagesPerTask* | The number of messages per task. -1 is unlimited. If you use a range for concurrent consumers (eg min max), then this option can be used to set a value to eg 100 to control how fast the consumers will shrink when less work is required. | -1 | ConfigDef.Importance.MEDIUM
+| *camel.component.activemq.messageConverter* | To use a custom Spring org.springframework.jms.support.converter.MessageConverter so you can be in control how to map to/from a javax.jms.Message. | null | ConfigDef.Importance.MEDIUM
+| *camel.component.activemq.messageCreatedStrategy* | To use the given MessageCreatedStrategy which are invoked when Camel creates new instances of javax.jms.Message objects when Camel is sending a JMS message. | null | ConfigDef.Importance.MEDIUM
+| *camel.component.activemq.messageIdEnabled* | When sending, specifies whether message IDs should be added. This is just an hint to the JMS broker. If the JMS provider accepts this hint, these messages must have the message ID set to null; if the provider ignores the hint, the message ID must be set to its normal unique value. | true | ConfigDef.Importance.MEDIUM
+| *camel.component.activemq.messageTimestampEnabled* | Specifies whether timestamps should be enabled by default on sending messages. This is just an hint to the JMS broker. If the JMS provider accepts this hint, these messages must have the timestamp set to zero; if the provider ignores the hint the timestamp must be set to its normal value. | true | ConfigDef.Importance.MEDIUM
+| *camel.component.activemq.pubSubNoLocal* | Specifies whether to inhibit the delivery of messages published by its own connection. | false | ConfigDef.Importance.MEDIUM
+| *camel.component.activemq.queueBrowseStrategy* | To use a custom QueueBrowseStrategy when browsing queues | null | ConfigDef.Importance.MEDIUM
+| *camel.component.activemq.receiveTimeout* | The timeout for receiving messages (in milliseconds). | 1000L | ConfigDef.Importance.MEDIUM
+| *camel.component.activemq.recoveryInterval* | Specifies the interval between recovery attempts, i.e. when a connection is being refreshed, in milliseconds. The default is 5000 ms, that is, 5 seconds. | 5000L | ConfigDef.Importance.MEDIUM
+| *camel.component.activemq.requestTimeoutCheckerInterval* | Configures how often Camel should check for timed out Exchanges when doing request/reply over JMS. By default Camel checks once per second. But if you must react faster when a timeout occurs, then you can lower this interval, to check more frequently. The timeout is determined by the option requestTimeout. | 1000L | ConfigDef.Importance.MEDIUM
+| *camel.component.activemq.transferException* | If enabled and you are using Request Reply messaging (InOut) and an Exchange failed on the consumer side, then the caused Exception will be send back in response as a javax.jms.ObjectMessage. If the client is Camel, the returned Exception is rethrown. This allows you to use Camel JMS as a bridge in your routing - for example, using persistent queues to enable robust routing. Notice that if you also have transferExchange enabled, this optio [...]
+| *camel.component.activemq.transferExchange* | You can transfer the exchange over the wire instead of just the body and headers. The following fields are transferred: In body, Out body, Fault body, In headers, Out headers, Fault headers, exchange properties, exchange exception. This requires that the objects are serializable. Camel will exclude any non-serializable objects and log it at WARN level. You must enable this option on both the producer and consumer side, so Camel knows the pa [...]
+| *camel.component.activemq.useMessageIDAsCorrelationID* | Specifies whether JMSMessageID should always be used as JMSCorrelationID for InOut messages. | false | ConfigDef.Importance.MEDIUM
+| *camel.component.activemq.waitForProvisionCorrelationToBeUpdatedCounter* | Number of times to wait for provisional correlation id to be updated to the actual correlation id when doing request/reply over JMS and when the option useMessageIDAsCorrelationID is enabled. | 50 | ConfigDef.Importance.MEDIUM
+| *camel.component.activemq.waitForProvisionCorrelationToBeUpdatedThreadSleepingTime* | Interval in millis to sleep each time while waiting for provisional correlation id to be updated. | 100L | ConfigDef.Importance.MEDIUM
+| *camel.component.activemq.errorHandlerLoggingLevel* | Allows to configure the default errorHandler logging level for logging uncaught exceptions. One of: [TRACE] [DEBUG] [INFO] [WARN] [ERROR] [OFF] | "WARN" | ConfigDef.Importance.MEDIUM
+| *camel.component.activemq.errorHandlerLogStackTrace* | Allows to control whether stacktraces should be logged or not, by the default errorHandler. | true | ConfigDef.Importance.MEDIUM
+| *camel.component.activemq.headerFilterStrategy* | To use a custom org.apache.camel.spi.HeaderFilterStrategy to filter header to and from Camel message. | null | ConfigDef.Importance.MEDIUM
+| *camel.component.activemq.password* | Password to use with the ConnectionFactory. You can also configure username/password directly on the ConnectionFactory. | null | ConfigDef.Importance.MEDIUM
+| *camel.component.activemq.username* | Username to use with the ConnectionFactory. You can also configure username/password directly on the ConnectionFactory. | null | ConfigDef.Importance.MEDIUM
+| *camel.component.activemq.transacted* | Specifies whether to use transacted mode | false | ConfigDef.Importance.MEDIUM
+| *camel.component.activemq.lazyCreateTransactionManager* | If true, Camel will create a JmsTransactionManager, if there is no transactionManager injected when option transacted=true. | true | ConfigDef.Importance.MEDIUM
+| *camel.component.activemq.transactionManager* | The Spring transaction manager to use. | null | ConfigDef.Importance.MEDIUM
+| *camel.component.activemq.transactionName* | The name of the transaction to use. | null | ConfigDef.Importance.MEDIUM
+| *camel.component.activemq.transactionTimeout* | The timeout value of the transaction (in seconds), if using transacted mode. | -1 | ConfigDef.Importance.MEDIUM
+|===
+
+
+// kafka-connector options: END
diff --git a/docs/modules/ROOT/pages/connectors/camel-ahc-kafka-sink-connector.adoc b/docs/modules/ROOT/pages/connectors/camel-ahc-kafka-sink-connector.adoc
new file mode 100644
index 0000000..6ac55fd
--- /dev/null
+++ b/docs/modules/ROOT/pages/connectors/camel-ahc-kafka-sink-connector.adoc
@@ -0,0 +1,48 @@
+// kafka-connector options: START
+== camel-ahc-kafka-connector source configuration
+
+When using camel-ahc-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-ahc-kafka-connector</artifactId>
+ <version>x.x.x</version>
+ <!-- use the same version as your Camel Kafka connector version -->
+</dependency>
+----
+
+
+[width="100%",cols="2,5,^1,2",options="header"]
+|===
+| Name | Description | Default | Priority
+| *camel.sink.path.httpUri* | The URI to use such as \http://hostname:port/path | null | ConfigDef.Importance.HIGH
+| *camel.sink.endpoint.bridgeEndpoint* | If the option is true, then the Exchange.HTTP_URI header is ignored, and use the endpoint's URI for request. You may also set the throwExceptionOnFailure to be false to let the AhcProducer send all the fault response back. | false | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.bufferSize* | The initial in-memory buffer size used when transferring data between Camel and AHC Client. | 4096 | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.connectionClose* | Define if the Connection Close header has to be added to HTTP Request. This parameter is false by default | false | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.cookieHandler* | Configure a cookie handler to maintain a HTTP session | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.headerFilterStrategy* | To use a custom HeaderFilterStrategy to filter header to and from Camel message. | null | ConfigDef.Importance.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 cre [...]
+| *camel.sink.endpoint.throwExceptionOnFailure* | Option to disable throwing the AhcOperationFailedException in case of failed responses from the remote server. This allows you to get all responses regardless of the HTTP status code. | true | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.transferException* | If enabled and an Exchange failed processing on the consumer side, and if the caused Exception was send back serialized in the response as a application/x-java-serialized-object content type (for example using Jetty or Servlet Camel components). On the producer side the exception will be deserialized and thrown as is, instead of the AhcOperationFailedException. The caused exception is required to be serialized. This is by default turned off. If [...]
+| *camel.sink.endpoint.basicPropertyBinding* | Whether the endpoint should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.binding* | To use a custom AhcBinding which allows to control how to bind between AHC and Camel. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.clientConfig* | To configure the AsyncHttpClient to use a custom com.ning.http.client.AsyncHttpClientConfig instance. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.clientConfigOptions* | To configure the AsyncHttpClientConfig using the key/values from the Map. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.synchronous* | Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). | false | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.clientConfigRealmOptions* | To configure the AsyncHttpClientConfig Realm using the key/values from the Map. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.sslContextParameters* | Reference to a org.apache.camel.support.jsse.SSLContextParameters in the Registry. This reference overrides any configured SSLContextParameters at the component level. See Using the JSSE Configuration Utility. Note that configuring this option will override any SSL/TLS configuration options provided through the clientConfig option at the endpoint or component level. | null | ConfigDef.Importance.MEDIUM
+| *camel.component.ahc.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 cre [...]
+| *camel.component.ahc.allowJavaSerializedObject* | Whether to allow java serialization when a request uses context-type=application/x-java-serialized-object This is by default turned off. If you enable this then be aware that Java will deserialize the incoming data from the request to Java and that can be a potential security risk. | false | ConfigDef.Importance.MEDIUM
+| *camel.component.ahc.basicPropertyBinding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+| *camel.component.ahc.binding* | To use a custom AhcBinding which allows to control how to bind between AHC and Camel. | null | ConfigDef.Importance.MEDIUM
+| *camel.component.ahc.client* | To use a custom AsyncHttpClient | null | ConfigDef.Importance.MEDIUM
+| *camel.component.ahc.clientConfig* | To configure the AsyncHttpClient to use a custom com.ning.http.client.AsyncHttpClientConfig instance. | null | ConfigDef.Importance.MEDIUM
+| *camel.component.ahc.headerFilterStrategy* | To use a custom org.apache.camel.spi.HeaderFilterStrategy to filter header to and from Camel message. | null | ConfigDef.Importance.MEDIUM
+| *camel.component.ahc.sslContextParameters* | Reference to a org.apache.camel.support.jsse.SSLContextParameters in the Registry. Note that configuring this option will override any SSL/TLS configuration options provided through the clientConfig option at the endpoint or component level. | null | ConfigDef.Importance.MEDIUM
+| *camel.component.ahc.useGlobalSslContextParameters* | Enable usage of global SSL context parameters. | false | ConfigDef.Importance.MEDIUM
+|===
+
+
+// kafka-connector options: END
diff --git a/docs/modules/ROOT/pages/connectors/camel-ahc-ws-kafka-sink-connector.adoc b/docs/modules/ROOT/pages/connectors/camel-ahc-ws-kafka-sink-connector.adoc
new file mode 100644
index 0000000..764de24
--- /dev/null
+++ b/docs/modules/ROOT/pages/connectors/camel-ahc-ws-kafka-sink-connector.adoc
@@ -0,0 +1,49 @@
+// kafka-connector options: START
+== camel-ahc-ws-kafka-connector source configuration
+
+When using camel-ahc-ws-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-ahc-ws-kafka-connector</artifactId>
+ <version>x.x.x</version>
+ <!-- use the same version as your Camel Kafka connector version -->
+</dependency>
+----
+
+
+[width="100%",cols="2,5,^1,2",options="header"]
+|===
+| Name | Description | Default | Priority
+| *camel.sink.path.httpUri* | The URI to use such as \http://hostname:port/path | null | ConfigDef.Importance.HIGH
+| *camel.sink.endpoint.bridgeEndpoint* | If the option is true, then the Exchange.HTTP_URI header is ignored, and use the endpoint's URI for request. You may also set the throwExceptionOnFailure to be false to let the AhcProducer send all the fault response back. | false | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.bufferSize* | The initial in-memory buffer size used when transferring data between Camel and AHC Client. | 4096 | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.headerFilterStrategy* | To use a custom HeaderFilterStrategy to filter header to and from Camel message. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.throwExceptionOnFailure* | Option to disable throwing the AhcOperationFailedException in case of failed responses from the remote server. This allows you to get all responses regardless of the HTTP status code. | true | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.transferException* | If enabled and an Exchange failed processing on the consumer side, and if the caused Exception was send back serialized in the response as a application/x-java-serialized-object content type (for example using Jetty or Servlet Camel components). On the producer side the exception will be deserialized and thrown as is, instead of the AhcOperationFailedException. The caused exception is required to be serialized. This is by default turned off. If [...]
+| *camel.sink.endpoint.connectionClose* | Define if the Connection Close header has to be added to HTTP Request. This parameter is false by default | false | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.cookieHandler* | Configure a cookie handler to maintain a HTTP session | null | ConfigDef.Importance.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 cre [...]
+| *camel.sink.endpoint.useStreaming* | To enable streaming to send data as multiple text fragments. | false | ConfigDef.Importance.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 | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.binding* | To use a custom AhcBinding which allows to control how to bind between AHC and Camel. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.clientConfig* | To configure the AsyncHttpClient to use a custom com.ning.http.client.AsyncHttpClientConfig instance. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.clientConfigOptions* | To configure the AsyncHttpClientConfig using the key/values from the Map. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.synchronous* | Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). | false | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.clientConfigRealmOptions* | To configure the AsyncHttpClientConfig Realm using the key/values from the Map. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.sslContextParameters* | Reference to a org.apache.camel.support.jsse.SSLContextParameters in the Registry. This reference overrides any configured SSLContextParameters at the component level. See Using the JSSE Configuration Utility. Note that configuring this option will override any SSL/TLS configuration options provided through the clientConfig option at the endpoint or component level. | null | ConfigDef.Importance.MEDIUM
+| *camel.component.ahc-ws.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 [...]
+| *camel.component.ahc-ws.allowJavaSerializedObject* | Whether to allow java serialization when a request uses context-type=application/x-java-serialized-object This is by default turned off. If you enable this then be aware that Java will deserialize the incoming data from the request to Java and that can be a potential security risk. | false | ConfigDef.Importance.MEDIUM
+| *camel.component.ahc-ws.basicPropertyBinding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+| *camel.component.ahc-ws.binding* | To use a custom AhcBinding which allows to control how to bind between AHC and Camel. | null | ConfigDef.Importance.MEDIUM
+| *camel.component.ahc-ws.client* | To use a custom AsyncHttpClient | null | ConfigDef.Importance.MEDIUM
+| *camel.component.ahc-ws.clientConfig* | To configure the AsyncHttpClient to use a custom com.ning.http.client.AsyncHttpClientConfig instance. | null | ConfigDef.Importance.MEDIUM
+| *camel.component.ahc-ws.headerFilterStrategy* | To use a custom org.apache.camel.spi.HeaderFilterStrategy to filter header to and from Camel message. | null | ConfigDef.Importance.MEDIUM
+| *camel.component.ahc-ws.sslContextParameters* | Reference to a org.apache.camel.support.jsse.SSLContextParameters in the Registry. Note that configuring this option will override any SSL/TLS configuration options provided through the clientConfig option at the endpoint or component level. | null | ConfigDef.Importance.MEDIUM
+| *camel.component.ahc-ws.useGlobalSslContextParameters* | Enable usage of global SSL context parameters. | false | ConfigDef.Importance.MEDIUM
+|===
+
+
+// kafka-connector options: END
diff --git a/docs/modules/ROOT/pages/connectors/camel-ahc-ws-kafka-source-connector.adoc b/docs/modules/ROOT/pages/connectors/camel-ahc-ws-kafka-source-connector.adoc
new file mode 100644
index 0000000..441e18a
--- /dev/null
+++ b/docs/modules/ROOT/pages/connectors/camel-ahc-ws-kafka-source-connector.adoc
@@ -0,0 +1,49 @@
+// kafka-connector options: START
+== camel-ahc-ws-kafka-connector source configuration
+
+When using camel-ahc-ws-kafka-connector as source 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-ahc-ws-kafka-connector</artifactId>
+ <version>x.x.x</version>
+ <!-- use the same version as your Camel Kafka connector version -->
+</dependency>
+----
+
+
+[width="100%",cols="2,5,^1,2",options="header"]
+|===
+| Name | Description | Default | Priority
+| *camel.source.path.httpUri* | The URI to use such as \http://hostname:port/path | null | ConfigDef.Importance.HIGH
+| *camel.source.endpoint.bridgeEndpoint* | If the option is true, then the Exchange.HTTP_URI header is ignored, and use the endpoint's URI for request. You may also set the throwExceptionOnFailure to be false to let the AhcProducer send all the fault response back. | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.bufferSize* | The initial in-memory buffer size used when transferring data between Camel and AHC Client. | 4096 | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.headerFilterStrategy* | To use a custom HeaderFilterStrategy to filter header to and from Camel message. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.throwExceptionOnFailure* | Option to disable throwing the AhcOperationFailedException in case of failed responses from the remote server. This allows you to get all responses regardless of the HTTP status code. | true | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.transferException* | If enabled and an Exchange failed processing on the consumer side, and if the caused Exception was send back serialized in the response as a application/x-java-serialized-object content type (for example using Jetty or Servlet Camel components). On the producer side the exception will be deserialized and thrown as is, instead of the AhcOperationFailedException. The caused exception is required to be serialized. This is by default turned off. [...]
+| *camel.source.endpoint.bridgeErrorHandler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.sendMessageOnError* | Whether to send an message if the web-socket listener received an error. | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.exceptionHandler* | To let the consumer use a custom ExceptionHandler. Notice if the option bridgeErrorHandler is enabled then this option is not in use. By default the consumer will deal with exceptions, that will be logged at WARN or ERROR level and ignored. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.exchangePattern* | Sets the exchange pattern when the consumer creates an exchange. One of: [InOnly] [InOut] [InOptionalOut] | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.basicPropertyBinding* | Whether the endpoint should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.binding* | To use a custom AhcBinding which allows to control how to bind between AHC and Camel. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.clientConfig* | To configure the AsyncHttpClient to use a custom com.ning.http.client.AsyncHttpClientConfig instance. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.clientConfigOptions* | To configure the AsyncHttpClientConfig using the key/values from the Map. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.synchronous* | Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.clientConfigRealmOptions* | To configure the AsyncHttpClientConfig Realm using the key/values from the Map. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.sslContextParameters* | Reference to a org.apache.camel.support.jsse.SSLContextParameters in the Registry. This reference overrides any configured SSLContextParameters at the component level. See Using the JSSE Configuration Utility. Note that configuring this option will override any SSL/TLS configuration options provided through the clientConfig option at the endpoint or component level. | null | ConfigDef.Importance.MEDIUM
+| *camel.component.ahc-ws.bridgeErrorHandler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | ConfigDef.Importance.MEDIUM
+| *camel.component.ahc-ws.allowJavaSerializedObject* | Whether to allow java serialization when a request uses context-type=application/x-java-serialized-object This is by default turned off. If you enable this then be aware that Java will deserialize the incoming data from the request to Java and that can be a potential security risk. | false | ConfigDef.Importance.MEDIUM
+| *camel.component.ahc-ws.basicPropertyBinding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+| *camel.component.ahc-ws.binding* | To use a custom AhcBinding which allows to control how to bind between AHC and Camel. | null | ConfigDef.Importance.MEDIUM
+| *camel.component.ahc-ws.client* | To use a custom AsyncHttpClient | null | ConfigDef.Importance.MEDIUM
+| *camel.component.ahc-ws.clientConfig* | To configure the AsyncHttpClient to use a custom com.ning.http.client.AsyncHttpClientConfig instance. | null | ConfigDef.Importance.MEDIUM
+| *camel.component.ahc-ws.headerFilterStrategy* | To use a custom org.apache.camel.spi.HeaderFilterStrategy to filter header to and from Camel message. | null | ConfigDef.Importance.MEDIUM
+| *camel.component.ahc-ws.sslContextParameters* | Reference to a org.apache.camel.support.jsse.SSLContextParameters in the Registry. Note that configuring this option will override any SSL/TLS configuration options provided through the clientConfig option at the endpoint or component level. | null | ConfigDef.Importance.MEDIUM
+| *camel.component.ahc-ws.useGlobalSslContextParameters* | Enable usage of global SSL context parameters. | false | ConfigDef.Importance.MEDIUM
+|===
+
+
+// kafka-connector options: END
diff --git a/docs/modules/ROOT/pages/connectors/camel-ahc-wss-kafka-sink-connector.adoc b/docs/modules/ROOT/pages/connectors/camel-ahc-wss-kafka-sink-connector.adoc
new file mode 100644
index 0000000..5cb4407
--- /dev/null
+++ b/docs/modules/ROOT/pages/connectors/camel-ahc-wss-kafka-sink-connector.adoc
@@ -0,0 +1,49 @@
+// kafka-connector options: START
+== camel-ahc-wss-kafka-connector source configuration
+
+When using camel-ahc-wss-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-ahc-wss-kafka-connector</artifactId>
+ <version>x.x.x</version>
+ <!-- use the same version as your Camel Kafka connector version -->
+</dependency>
+----
+
+
+[width="100%",cols="2,5,^1,2",options="header"]
+|===
+| Name | Description | Default | Priority
+| *camel.sink.path.httpUri* | The URI to use such as \http://hostname:port/path | null | ConfigDef.Importance.HIGH
+| *camel.sink.endpoint.bridgeEndpoint* | If the option is true, then the Exchange.HTTP_URI header is ignored, and use the endpoint's URI for request. You may also set the throwExceptionOnFailure to be false to let the AhcProducer send all the fault response back. | false | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.bufferSize* | The initial in-memory buffer size used when transferring data between Camel and AHC Client. | 4096 | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.headerFilterStrategy* | To use a custom HeaderFilterStrategy to filter header to and from Camel message. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.throwExceptionOnFailure* | Option to disable throwing the AhcOperationFailedException in case of failed responses from the remote server. This allows you to get all responses regardless of the HTTP status code. | true | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.transferException* | If enabled and an Exchange failed processing on the consumer side, and if the caused Exception was send back serialized in the response as a application/x-java-serialized-object content type (for example using Jetty or Servlet Camel components). On the producer side the exception will be deserialized and thrown as is, instead of the AhcOperationFailedException. The caused exception is required to be serialized. This is by default turned off. If [...]
+| *camel.sink.endpoint.connectionClose* | Define if the Connection Close header has to be added to HTTP Request. This parameter is false by default | false | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.cookieHandler* | Configure a cookie handler to maintain a HTTP session | null | ConfigDef.Importance.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 cre [...]
+| *camel.sink.endpoint.useStreaming* | To enable streaming to send data as multiple text fragments. | false | ConfigDef.Importance.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 | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.binding* | To use a custom AhcBinding which allows to control how to bind between AHC and Camel. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.clientConfig* | To configure the AsyncHttpClient to use a custom com.ning.http.client.AsyncHttpClientConfig instance. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.clientConfigOptions* | To configure the AsyncHttpClientConfig using the key/values from the Map. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.synchronous* | Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). | false | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.clientConfigRealmOptions* | To configure the AsyncHttpClientConfig Realm using the key/values from the Map. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.sslContextParameters* | Reference to a org.apache.camel.support.jsse.SSLContextParameters in the Registry. This reference overrides any configured SSLContextParameters at the component level. See Using the JSSE Configuration Utility. Note that configuring this option will override any SSL/TLS configuration options provided through the clientConfig option at the endpoint or component level. | null | ConfigDef.Importance.MEDIUM
+| *camel.component.ahc-wss.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 [...]
+| *camel.component.ahc-wss.allowJavaSerializedObject* | Whether to allow java serialization when a request uses context-type=application/x-java-serialized-object This is by default turned off. If you enable this then be aware that Java will deserialize the incoming data from the request to Java and that can be a potential security risk. | false | ConfigDef.Importance.MEDIUM
+| *camel.component.ahc-wss.basicPropertyBinding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+| *camel.component.ahc-wss.binding* | To use a custom AhcBinding which allows to control how to bind between AHC and Camel. | null | ConfigDef.Importance.MEDIUM
+| *camel.component.ahc-wss.client* | To use a custom AsyncHttpClient | null | ConfigDef.Importance.MEDIUM
+| *camel.component.ahc-wss.clientConfig* | To configure the AsyncHttpClient to use a custom com.ning.http.client.AsyncHttpClientConfig instance. | null | ConfigDef.Importance.MEDIUM
+| *camel.component.ahc-wss.headerFilterStrategy* | To use a custom org.apache.camel.spi.HeaderFilterStrategy to filter header to and from Camel message. | null | ConfigDef.Importance.MEDIUM
+| *camel.component.ahc-wss.sslContextParameters* | Reference to a org.apache.camel.support.jsse.SSLContextParameters in the Registry. Note that configuring this option will override any SSL/TLS configuration options provided through the clientConfig option at the endpoint or component level. | null | ConfigDef.Importance.MEDIUM
+| *camel.component.ahc-wss.useGlobalSslContextParameters* | Enable usage of global SSL context parameters. | false | ConfigDef.Importance.MEDIUM
+|===
+
+
+// kafka-connector options: END
diff --git a/docs/modules/ROOT/pages/connectors/camel-ahc-wss-kafka-source-connector.adoc b/docs/modules/ROOT/pages/connectors/camel-ahc-wss-kafka-source-connector.adoc
new file mode 100644
index 0000000..0420ea7
--- /dev/null
+++ b/docs/modules/ROOT/pages/connectors/camel-ahc-wss-kafka-source-connector.adoc
@@ -0,0 +1,49 @@
+// kafka-connector options: START
+== camel-ahc-wss-kafka-connector source configuration
+
+When using camel-ahc-wss-kafka-connector as source 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-ahc-wss-kafka-connector</artifactId>
+ <version>x.x.x</version>
+ <!-- use the same version as your Camel Kafka connector version -->
+</dependency>
+----
+
+
+[width="100%",cols="2,5,^1,2",options="header"]
+|===
+| Name | Description | Default | Priority
+| *camel.source.path.httpUri* | The URI to use such as \http://hostname:port/path | null | ConfigDef.Importance.HIGH
+| *camel.source.endpoint.bridgeEndpoint* | If the option is true, then the Exchange.HTTP_URI header is ignored, and use the endpoint's URI for request. You may also set the throwExceptionOnFailure to be false to let the AhcProducer send all the fault response back. | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.bufferSize* | The initial in-memory buffer size used when transferring data between Camel and AHC Client. | 4096 | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.headerFilterStrategy* | To use a custom HeaderFilterStrategy to filter header to and from Camel message. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.throwExceptionOnFailure* | Option to disable throwing the AhcOperationFailedException in case of failed responses from the remote server. This allows you to get all responses regardless of the HTTP status code. | true | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.transferException* | If enabled and an Exchange failed processing on the consumer side, and if the caused Exception was send back serialized in the response as a application/x-java-serialized-object content type (for example using Jetty or Servlet Camel components). On the producer side the exception will be deserialized and thrown as is, instead of the AhcOperationFailedException. The caused exception is required to be serialized. This is by default turned off. [...]
+| *camel.source.endpoint.bridgeErrorHandler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.sendMessageOnError* | Whether to send an message if the web-socket listener received an error. | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.exceptionHandler* | To let the consumer use a custom ExceptionHandler. Notice if the option bridgeErrorHandler is enabled then this option is not in use. By default the consumer will deal with exceptions, that will be logged at WARN or ERROR level and ignored. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.exchangePattern* | Sets the exchange pattern when the consumer creates an exchange. One of: [InOnly] [InOut] [InOptionalOut] | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.basicPropertyBinding* | Whether the endpoint should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.binding* | To use a custom AhcBinding which allows to control how to bind between AHC and Camel. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.clientConfig* | To configure the AsyncHttpClient to use a custom com.ning.http.client.AsyncHttpClientConfig instance. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.clientConfigOptions* | To configure the AsyncHttpClientConfig using the key/values from the Map. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.synchronous* | Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.clientConfigRealmOptions* | To configure the AsyncHttpClientConfig Realm using the key/values from the Map. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.sslContextParameters* | Reference to a org.apache.camel.support.jsse.SSLContextParameters in the Registry. This reference overrides any configured SSLContextParameters at the component level. See Using the JSSE Configuration Utility. Note that configuring this option will override any SSL/TLS configuration options provided through the clientConfig option at the endpoint or component level. | null | ConfigDef.Importance.MEDIUM
+| *camel.component.ahc-wss.bridgeErrorHandler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | ConfigDef.Importance.MEDIUM
+| *camel.component.ahc-wss.allowJavaSerializedObject* | Whether to allow java serialization when a request uses context-type=application/x-java-serialized-object This is by default turned off. If you enable this then be aware that Java will deserialize the incoming data from the request to Java and that can be a potential security risk. | false | ConfigDef.Importance.MEDIUM
+| *camel.component.ahc-wss.basicPropertyBinding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+| *camel.component.ahc-wss.binding* | To use a custom AhcBinding which allows to control how to bind between AHC and Camel. | null | ConfigDef.Importance.MEDIUM
+| *camel.component.ahc-wss.client* | To use a custom AsyncHttpClient | null | ConfigDef.Importance.MEDIUM
+| *camel.component.ahc-wss.clientConfig* | To configure the AsyncHttpClient to use a custom com.ning.http.client.AsyncHttpClientConfig instance. | null | ConfigDef.Importance.MEDIUM
+| *camel.component.ahc-wss.headerFilterStrategy* | To use a custom org.apache.camel.spi.HeaderFilterStrategy to filter header to and from Camel message. | null | ConfigDef.Importance.MEDIUM
+| *camel.component.ahc-wss.sslContextParameters* | Reference to a org.apache.camel.support.jsse.SSLContextParameters in the Registry. Note that configuring this option will override any SSL/TLS configuration options provided through the clientConfig option at the endpoint or component level. | null | ConfigDef.Importance.MEDIUM
+| *camel.component.ahc-wss.useGlobalSslContextParameters* | Enable usage of global SSL context parameters. | false | ConfigDef.Importance.MEDIUM
+|===
+
+
+// kafka-connector options: END
diff --git a/docs/modules/ROOT/pages/connectors/camel-amqp-kafka-sink-connector.adoc b/docs/modules/ROOT/pages/connectors/camel-amqp-kafka-sink-connector.adoc
new file mode 100644
index 0000000..9d1ae9a
--- /dev/null
+++ b/docs/modules/ROOT/pages/connectors/camel-amqp-kafka-sink-connector.adoc
@@ -0,0 +1,156 @@
+// kafka-connector options: START
+== camel-amqp-kafka-connector source configuration
+
+When using camel-amqp-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-amqp-kafka-connector</artifactId>
+ <version>x.x.x</version>
+ <!-- use the same version as your Camel Kafka connector version -->
+</dependency>
+----
+
+
+[width="100%",cols="2,5,^1,2",options="header"]
+|===
+| Name | Description | Default | Priority
+| *camel.sink.path.destinationType* | The kind of destination to use One of: [queue] [topic] [temp-queue] [temp-topic] | "queue" | ConfigDef.Importance.MEDIUM
+| *camel.sink.path.destinationName* | Name of the queue or topic to use as destination | null | ConfigDef.Importance.HIGH
+| *camel.sink.endpoint.clientId* | Sets the JMS client ID to use. Note that this value, if specified, must be unique and can only be used by a single JMS connection instance. It is typically only required for durable topic subscriptions. If using Apache ActiveMQ you may prefer to use Virtual Topics instead. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.connectionFactory* | The connection factory to be use. A connection factory must be configured either on the component or endpoint. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.disableReplyTo* | Specifies whether Camel ignores the JMSReplyTo header in messages. If true, Camel does not send a reply back to the destination specified in the JMSReplyTo header. You can use this option if you want Camel to consume from a route and you do not want Camel to automatically send back a reply message because another component in your code handles the reply message. You can also use this option if you want to use Camel as a proxy between different mes [...]
+| *camel.sink.endpoint.durableSubscriptionName* | The durable subscriber name for specifying durable topic subscriptions. The clientId option must be configured as well. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.jmsMessageType* | Allows you to force the use of a specific javax.jms.Message implementation for sending JMS messages. Possible values are: Bytes, Map, Object, Stream, Text. By default, Camel would determine which JMS message type to use from the In body type. This option allows you to specify it. One of: [Bytes] [Map] [Object] [Stream] [Text] | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.testConnectionOnStartup* | Specifies whether to test the connection on startup. This ensures that when Camel starts that all the JMS consumers have a valid connection to the JMS broker. If a connection cannot be granted then Camel throws an exception on startup. This ensures that Camel is not started with failed connections. The JMS producers is tested as well. | false | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.deliveryDelay* | Sets delivery delay to use for send calls for JMS. This option requires JMS 2.0 compliant broker. | -1L | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.deliveryMode* | Specifies the delivery mode to be used. Possibles values are those defined by javax.jms.DeliveryMode. NON_PERSISTENT = 1 and PERSISTENT = 2. One of: [1] [2] | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.deliveryPersistent* | Specifies whether persistent delivery is used by default. | true | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.explicitQosEnabled* | Set if the deliveryMode, priority or timeToLive qualities of service should be used when sending messages. This option is based on Spring's JmsTemplate. The deliveryMode, priority and timeToLive options are applied to the current endpoint. This contrasts with the preserveMessageQos option, which operates at message granularity, reading QoS properties exclusively from the Camel In message headers. | "false" | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.formatDateHeadersToIso8601* | Sets whether JMS date properties should be formatted according to the ISO 8601 standard. | false | ConfigDef.Importance.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 cre [...]
+| *camel.sink.endpoint.preserveMessageQos* | Set to true, if you want to send message using the QoS settings specified on the message, instead of the QoS settings on the JMS endpoint. The following three headers are considered JMSPriority, JMSDeliveryMode, and JMSExpiration. You can provide all or only some of them. If not provided, Camel will fall back to use the values from the endpoint instead. So, when using this option, the headers override the values from the endpoint. The explicit [...]
+| *camel.sink.endpoint.priority* | Values greater than 1 specify the message priority when sending (where 0 is the lowest priority and 9 is the highest). The explicitQosEnabled option must also be enabled in order for this option to have any effect. One of: [1] [2] [3] [4] [5] [6] [7] [8] [9] | 4 | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.replyToConcurrentConsumers* | Specifies the default number of concurrent consumers when doing request/reply over JMS. See also the maxMessagesPerTask option to control dynamic scaling up/down of threads. | 1 | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.replyToMaxConcurrentConsumers* | Specifies the maximum number of concurrent consumers when using request/reply over JMS. See also the maxMessagesPerTask option to control dynamic scaling up/down of threads. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.replyToOnTimeoutMaxConcurrentConsumers* | Specifies the maximum number of concurrent consumers for continue routing when timeout occurred when using request/reply over JMS. | 1 | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.replyToOverride* | Provides an explicit ReplyTo destination in the JMS message, which overrides the setting of replyTo. It is useful if you want to forward the message to a remote Queue and receive the reply message from the ReplyTo destination. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.replyToType* | Allows for explicitly specifying which kind of strategy to use for replyTo queues when doing request/reply over JMS. Possible values are: Temporary, Shared, or Exclusive. By default Camel will use temporary queues. However if replyTo has been configured, then Shared is used by default. This option allows you to use exclusive queues instead of shared ones. See Camel JMS documentation for more details, and especially the notes about the implications if [...]
+| *camel.sink.endpoint.requestTimeout* | The timeout for waiting for a reply when using the InOut Exchange Pattern (in milliseconds). The default is 20 seconds. You can include the header CamelJmsRequestTimeout to override this endpoint configured timeout value, and thus have per message individual timeout values. See also the requestTimeoutCheckerInterval option. | 20000L | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.timeToLive* | When sending messages, specifies the time-to-live of the message (in milliseconds). | -1L | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.allowAdditionalHeaders* | This option is used to allow additional headers which may have values that are invalid according to JMS specification. For example some message systems such as WMQ do this with header names using prefix JMS_IBM_MQMD_ containing values with byte array or other invalid types. You can specify multiple header names separated by comma, and use as suffix for wildcard matching. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.allowNullBody* | Whether to allow sending messages with no body. If this option is false and the message body is null, then an JMSException is thrown. | true | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.alwaysCopyMessage* | If true, Camel will always make a JMS message copy of the message when it is passed to the producer for sending. Copying the message is needed in some situations, such as when a replyToDestinationSelectorName is set (incidentally, Camel will set the alwaysCopyMessage option to true, if a replyToDestinationSelectorName is set) | false | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.correlationProperty* | When using InOut exchange pattern use this JMS property instead of JMSCorrelationID JMS property to correlate messages. If set messages will be correlated solely on the value of this property JMSCorrelationID property will be ignored and not set by Camel. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.disableTimeToLive* | Use this option to force disabling time to live. For example when you do request/reply over JMS, then Camel will by default use the requestTimeout value as time to live on the message being sent. The problem is that the sender and receiver systems have to have their clocks synchronized, so they are in sync. This is not always so easy to archive. So you can use disableTimeToLive=true to not set a time to live value on the sent message. Then the [...]
+| *camel.sink.endpoint.forceSendOriginalMessage* | When using mapJmsMessage=false Camel will create a new JMS message to send to a new JMS destination if you touch the headers (get or set) during the route. Set this option to true to force Camel to send the original JMS message that was received. | false | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.includeSentJMSMessageID* | Only applicable when sending to JMS destination using InOnly (eg fire and forget). Enabling this option will enrich the Camel Exchange with the actual JMSMessageID that was used by the JMS client when the message was sent to the JMS destination. | false | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.replyToCacheLevelName* | Sets the cache level by name for the reply consumer when doing request/reply over JMS. This option only applies when using fixed reply queues (not temporary). Camel will by default use: CACHE_CONSUMER for exclusive or shared w/ replyToSelectorName. And CACHE_SESSION for shared without replyToSelectorName. Some JMS brokers such as IBM WebSphere may require to set the replyToCacheLevelName=CACHE_NONE to work. Note: If using temporary queues t [...]
+| *camel.sink.endpoint.replyToDestinationSelectorName* | Sets the JMS Selector using the fixed name to be used so you can filter out your own replies from the others when using a shared queue (that is, if you are not using a temporary reply queue). | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.streamMessageTypeEnabled* | Sets whether StreamMessage type is enabled or not. Message payloads of streaming kind such as files, InputStream, etc will either by sent as BytesMessage or StreamMessage. This option controls which kind will be used. By default BytesMessage is used which enforces the entire message payload to be read into memory. By enabling this option the message payload is read into memory in chunks and each chunk is then written to the StreamMessage [...]
+| *camel.sink.endpoint.allowSerializedHeaders* | Controls whether or not to include serialized headers. Applies only when transferExchange is true. This requires that the objects are serializable. Camel will exclude any non-serializable objects and log it at WARN level. | false | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.asyncStartListener* | Whether to startup the JmsConsumer message listener asynchronously, when starting a route. For example if a JmsConsumer cannot get a connection to a remote JMS broker, then it may block while retrying and/or failover. This will cause Camel to block while starting routes. By setting this option to true, you will let routes startup, while the JmsConsumer connects to the JMS broker using a dedicated thread in asynchronous mode. If this option is [...]
+| *camel.sink.endpoint.asyncStopListener* | Whether to stop the JmsConsumer message listener asynchronously, when stopping a route. | false | ConfigDef.Importance.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 | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.destinationResolver* | A pluggable org.springframework.jms.support.destination.DestinationResolver that allows you to use your own resolver (for example, to lookup the real destination in a JNDI registry). | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.errorHandler* | Specifies a org.springframework.util.ErrorHandler to be invoked in case of any uncaught exceptions thrown while processing a Message. By default these exceptions will be logged at the WARN level, if no errorHandler has been configured. You can configure logging level and whether stack traces should be logged using errorHandlerLoggingLevel and errorHandlerLogStackTrace options. This makes it much easier to configure, than having to code a custom erro [...]
+| *camel.sink.endpoint.exceptionListener* | Specifies the JMS Exception Listener that is to be notified of any underlying JMS exceptions. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.headerFilterStrategy* | To use a custom HeaderFilterStrategy to filter header to and from Camel message. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.idleConsumerLimit* | Specify the limit for the number of consumers that are allowed to be idle at any given time. | 1 | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.idleTaskExecutionLimit* | Specifies the limit for idle executions of a receive task, not having received any message within its execution. If this limit is reached, the task will shut down and leave receiving to other executing tasks (in the case of dynamic scheduling; see the maxConcurrentConsumers setting). There is additional doc available from Spring. | 1 | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.includeAllJMSXProperties* | Whether to include all JMSXxxx properties when mapping from JMS to Camel Message. Setting this to true will include properties such as JMSXAppID, and JMSXUserID etc. Note: If you are using a custom headerFilterStrategy then this option does not apply. | false | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.jmsKeyFormatStrategy* | Pluggable strategy for encoding and decoding JMS keys so they can be compliant with the JMS specification. Camel provides two implementations out of the box: default and passthrough. The default strategy will safely marshal dots and hyphens (. and -). The passthrough strategy leaves the key as is. Can be used for JMS brokers which do not care whether JMS header keys contain illegal characters. You can provide your own implementation of the o [...]
+| *camel.sink.endpoint.mapJmsMessage* | Specifies whether Camel should auto map the received JMS message to a suited payload type, such as javax.jms.TextMessage to a String etc. | true | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.maxMessagesPerTask* | The number of messages per task. -1 is unlimited. If you use a range for concurrent consumers (eg min max), then this option can be used to set a value to eg 100 to control how fast the consumers will shrink when less work is required. | -1 | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.messageConverter* | To use a custom Spring org.springframework.jms.support.converter.MessageConverter so you can be in control how to map to/from a javax.jms.Message. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.messageCreatedStrategy* | To use the given MessageCreatedStrategy which are invoked when Camel creates new instances of javax.jms.Message objects when Camel is sending a JMS message. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.messageIdEnabled* | When sending, specifies whether message IDs should be added. This is just an hint to the JMS broker. If the JMS provider accepts this hint, these messages must have the message ID set to null; if the provider ignores the hint, the message ID must be set to its normal unique value. | true | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.messageListenerContainerFactory* | Registry ID of the MessageListenerContainerFactory used to determine what org.springframework.jms.listener.AbstractMessageListenerContainer to use to consume messages. Setting this will automatically set consumerType to Custom. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.messageTimestampEnabled* | Specifies whether timestamps should be enabled by default on sending messages. This is just an hint to the JMS broker. If the JMS provider accepts this hint, these messages must have the timestamp set to zero; if the provider ignores the hint the timestamp must be set to its normal value. | true | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.pubSubNoLocal* | Specifies whether to inhibit the delivery of messages published by its own connection. | false | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.receiveTimeout* | The timeout for receiving messages (in milliseconds). | 1000L | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.recoveryInterval* | Specifies the interval between recovery attempts, i.e. when a connection is being refreshed, in milliseconds. The default is 5000 ms, that is, 5 seconds. | 5000L | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.requestTimeoutCheckerInterval* | Configures how often Camel should check for timed out Exchanges when doing request/reply over JMS. By default Camel checks once per second. But if you must react faster when a timeout occurs, then you can lower this interval, to check more frequently. The timeout is determined by the option requestTimeout. | 1000L | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.synchronous* | Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). | false | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.transferException* | If enabled and you are using Request Reply messaging (InOut) and an Exchange failed on the consumer side, then the caused Exception will be send back in response as a javax.jms.ObjectMessage. If the client is Camel, the returned Exception is rethrown. This allows you to use Camel JMS as a bridge in your routing - for example, using persistent queues to enable robust routing. Notice that if you also have transferExchange enabled, this option tak [...]
+| *camel.sink.endpoint.transferExchange* | You can transfer the exchange over the wire instead of just the body and headers. The following fields are transferred: In body, Out body, Fault body, In headers, Out headers, Fault headers, exchange properties, exchange exception. This requires that the objects are serializable. Camel will exclude any non-serializable objects and log it at WARN level. You must enable this option on both the producer and consumer side, so Camel knows the payload [...]
+| *camel.sink.endpoint.useMessageIDAsCorrelationID* | Specifies whether JMSMessageID should always be used as JMSCorrelationID for InOut messages. | false | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.waitForProvisionCorrelationToBeUpdatedCounter* | Number of times to wait for provisional correlation id to be updated to the actual correlation id when doing request/reply over JMS and when the option useMessageIDAsCorrelationID is enabled. | 50 | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.waitForProvisionCorrelationToBeUpdatedThreadSleepingTime* | Interval in millis to sleep each time while waiting for provisional correlation id to be updated. | 100L | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.password* | Password to use with the ConnectionFactory. You can also configure username/password directly on the ConnectionFactory. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.username* | Username to use with the ConnectionFactory. You can also configure username/password directly on the ConnectionFactory. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.transacted* | Specifies whether to use transacted mode | false | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.lazyCreateTransactionManager* | If true, Camel will create a JmsTransactionManager, if there is no transactionManager injected when option transacted=true. | true | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.transactionManager* | The Spring transaction manager to use. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.transactionName* | The name of the transaction to use. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.transactionTimeout* | The timeout value of the transaction (in seconds), if using transacted mode. | -1 | ConfigDef.Importance.MEDIUM
+| *camel.component.amqp.clientId* | Sets the JMS client ID to use. Note that this value, if specified, must be unique and can only be used by a single JMS connection instance. It is typically only required for durable topic subscriptions. If using Apache ActiveMQ you may prefer to use Virtual Topics instead. | null | ConfigDef.Importance.MEDIUM
+| *camel.component.amqp.connectionFactory* | The connection factory to be use. A connection factory must be configured either on the component or endpoint. | null | ConfigDef.Importance.MEDIUM
+| *camel.component.amqp.durableSubscriptionName* | The durable subscriber name for specifying durable topic subscriptions. The clientId option must be configured as well. | null | ConfigDef.Importance.MEDIUM
+| *camel.component.amqp.includeAmqpAnnotations* | Whether to include AMQP annotations when mapping from AMQP to Camel Message. Setting this to true will map AMQP message annotations to message headers. Due to limitations in Apache Qpid JMS API, currently delivery annotations are ignored. | false | ConfigDef.Importance.MEDIUM
+| *camel.component.amqp.testConnectionOnStartup* | Specifies whether to test the connection on startup. This ensures that when Camel starts that all the JMS consumers have a valid connection to the JMS broker. If a connection cannot be granted then Camel throws an exception on startup. This ensures that Camel is not started with failed connections. The JMS producers is tested as well. | false | ConfigDef.Importance.MEDIUM
+| *camel.component.amqp.deliveryMode* | Specifies the delivery mode to be used. Possibles values are those defined by javax.jms.DeliveryMode. NON_PERSISTENT = 1 and PERSISTENT = 2. One of: [1] [2] | null | ConfigDef.Importance.MEDIUM
+| *camel.component.amqp.deliveryPersistent* | Specifies whether persistent delivery is used by default. | true | ConfigDef.Importance.MEDIUM
+| *camel.component.amqp.explicitQosEnabled* | Set if the deliveryMode, priority or timeToLive qualities of service should be used when sending messages. This option is based on Spring's JmsTemplate. The deliveryMode, priority and timeToLive options are applied to the current endpoint. This contrasts with the preserveMessageQos option, which operates at message granularity, reading QoS properties exclusively from the Camel In message headers. | false | ConfigDef.Importance.MEDIUM
+| *camel.component.amqp.formatDateHeadersToIso8601* | Sets whether date headers should be formatted according to the ISO 8601 standard. | false | ConfigDef.Importance.MEDIUM
+| *camel.component.amqp.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 cr [...]
+| *camel.component.amqp.preserveMessageQos* | Set to true, if you want to send message using the QoS settings specified on the message, instead of the QoS settings on the JMS endpoint. The following three headers are considered JMSPriority, JMSDeliveryMode, and JMSExpiration. You can provide all or only some of them. If not provided, Camel will fall back to use the values from the endpoint instead. So, when using this option, the headers override the values from the endpoint. The explici [...]
+| *camel.component.amqp.priority* | Values greater than 1 specify the message priority when sending (where 0 is the lowest priority and 9 is the highest). The explicitQosEnabled option must also be enabled in order for this option to have any effect. One of: [1] [2] [3] [4] [5] [6] [7] [8] [9] | 4 | ConfigDef.Importance.MEDIUM
+| *camel.component.amqp.replyOnTimeoutToMaxConcurrentConsumers* | Specifies the maximum number of concurrent consumers for continue routing when timeout occurred when using request/reply over JMS. | 1 | ConfigDef.Importance.MEDIUM
+| *camel.component.amqp.replyToConcurrentConsumers* | Specifies the default number of concurrent consumers when doing request/reply over JMS. See also the maxMessagesPerTask option to control dynamic scaling up/down of threads. | 1 | ConfigDef.Importance.MEDIUM
+| *camel.component.amqp.replyToMaxConcurrentConsumers* | Specifies the maximum number of concurrent consumers when using request/reply over JMS. See also the maxMessagesPerTask option to control dynamic scaling up/down of threads. | null | ConfigDef.Importance.MEDIUM
+| *camel.component.amqp.replyToType* | Allows for explicitly specifying which kind of strategy to use for replyTo queues when doing request/reply over JMS. Possible values are: Temporary, Shared, or Exclusive. By default Camel will use temporary queues. However if replyTo has been configured, then Shared is used by default. This option allows you to use exclusive queues instead of shared ones. See Camel JMS documentation for more details, and especially the notes about the implications i [...]
+| *camel.component.amqp.requestTimeout* | The timeout for waiting for a reply when using the InOut Exchange Pattern (in milliseconds). The default is 20 seconds. You can include the header CamelJmsRequestTimeout to override this endpoint configured timeout value, and thus have per message individual timeout values. See also the requestTimeoutCheckerInterval option. | 20000L | ConfigDef.Importance.MEDIUM
+| *camel.component.amqp.timeToLive* | When sending messages, specifies the time-to-live of the message (in milliseconds). | -1L | ConfigDef.Importance.MEDIUM
+| *camel.component.amqp.allowAdditionalHeaders* | This option is used to allow additional headers which may have values that are invalid according to JMS specification. For example some message systems such as WMQ do this with header names using prefix JMS_IBM_MQMD_ containing values with byte array or other invalid types. You can specify multiple header names separated by comma, and use as suffix for wildcard matching. | null | ConfigDef.Importance.MEDIUM
+| *camel.component.amqp.allowNullBody* | Whether to allow sending messages with no body. If this option is false and the message body is null, then an JMSException is thrown. | true | ConfigDef.Importance.MEDIUM
+| *camel.component.amqp.alwaysCopyMessage* | If true, Camel will always make a JMS message copy of the message when it is passed to the producer for sending. Copying the message is needed in some situations, such as when a replyToDestinationSelectorName is set (incidentally, Camel will set the alwaysCopyMessage option to true, if a replyToDestinationSelectorName is set). | false | ConfigDef.Importance.MEDIUM
+| *camel.component.amqp.correlationProperty* | Use this JMS property to correlate messages in InOut exchange pattern (request-reply) instead of JMSCorrelationID property. This allows you to exchange messages with systems that do not correlate messages using JMSCorrelationID JMS property. If used JMSCorrelationID will not be used or set by Camel. The value of here named property will be generated if not supplied in the header of the message under the same name. | null | ConfigDef.Importan [...]
+| *camel.component.amqp.forceSendOriginalMessage* | When using mapJmsMessage=false Camel will create a new JMS message to send to a new JMS destination if you touch the headers (get or set) during the route. Set this option to true to force Camel to send the original JMS message that was received. | false | ConfigDef.Importance.MEDIUM
+| *camel.component.amqp.includeSentJMSMessageID* | Only applicable when sending to JMS destination using InOnly (eg fire and forget). Enabling this option will enrich the Camel Exchange with the actual JMSMessageID that was used by the JMS client when the message was sent to the JMS destination. | false | ConfigDef.Importance.MEDIUM
+| *camel.component.amqp.replyToCacheLevelName* | Sets the cache level by name for the reply consumer when doing request/reply over JMS. This option only applies when using fixed reply queues (not temporary). Camel will by default use: CACHE_CONSUMER for exclusive or shared w/ replyToSelectorName. And CACHE_SESSION for shared without replyToSelectorName. Some JMS brokers such as IBM WebSphere may require to set the replyToCacheLevelName=CACHE_NONE to work. Note: If using temporary queues [...]
+| *camel.component.amqp.streamMessageTypeEnabled* | Sets whether StreamMessage type is enabled or not. Message payloads of streaming kind such as files, InputStream, etc will either by sent as BytesMessage or StreamMessage. This option controls which kind will be used. By default BytesMessage is used which enforces the entire message payload to be read into memory. By enabling this option the message payload is read into memory in chunks and each chunk is then written to the StreamMessag [...]
+| *camel.component.amqp.allowAutoWiredConnectionFactory* | Whether to auto-discover ConnectionFactory from the registry, if no connection factory has been configured. If only one instance of ConnectionFactory is found then it will be used. This is enabled by default. | false | ConfigDef.Importance.MEDIUM
+| *camel.component.amqp.allowAutoWiredDestinationResolver* | Whether to auto-discover DestinationResolver from the registry, if no destination resolver has been configured. If only one instance of DestinationResolver is found then it will be used. This is enabled by default. | false | ConfigDef.Importance.MEDIUM
+| *camel.component.amqp.asyncStartListener* | Whether to startup the JmsConsumer message listener asynchronously, when starting a route. For example if a JmsConsumer cannot get a connection to a remote JMS broker, then it may block while retrying and/or failover. This will cause Camel to block while starting routes. By setting this option to true, you will let routes startup, while the JmsConsumer connects to the JMS broker using a dedicated thread in asynchronous mode. If this option is [...]
+| *camel.component.amqp.asyncStopListener* | Whether to stop the JmsConsumer message listener asynchronously, when stopping a route. | false | ConfigDef.Importance.MEDIUM
+| *camel.component.amqp.basicPropertyBinding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+| *camel.component.amqp.configuration* | To use a shared JMS configuration | null | ConfigDef.Importance.MEDIUM
+| *camel.component.amqp.destinationResolver* | A pluggable org.springframework.jms.support.destination.DestinationResolver that allows you to use your own resolver (for example, to lookup the real destination in a JNDI registry). | null | ConfigDef.Importance.MEDIUM
+| *camel.component.amqp.errorHandler* | Specifies a org.springframework.util.ErrorHandler to be invoked in case of any uncaught exceptions thrown while processing a Message. By default these exceptions will be logged at the WARN level, if no errorHandler has been configured. You can configure logging level and whether stack traces should be logged using errorHandlerLoggingLevel and errorHandlerLogStackTrace options. This makes it much easier to configure, than having to code a custom err [...]
+| *camel.component.amqp.exceptionListener* | Specifies the JMS Exception Listener that is to be notified of any underlying JMS exceptions. | null | ConfigDef.Importance.MEDIUM
+| *camel.component.amqp.idleConsumerLimit* | Specify the limit for the number of consumers that are allowed to be idle at any given time. | 1 | ConfigDef.Importance.MEDIUM
+| *camel.component.amqp.idleTaskExecutionLimit* | Specifies the limit for idle executions of a receive task, not having received any message within its execution. If this limit is reached, the task will shut down and leave receiving to other executing tasks (in the case of dynamic scheduling; see the maxConcurrentConsumers setting). There is additional doc available from Spring. | 1 | ConfigDef.Importance.MEDIUM
+| *camel.component.amqp.includeAllJMSXProperties* | Whether to include all JMSXxxx properties when mapping from JMS to Camel Message. Setting this to true will include properties such as JMSXAppID, and JMSXUserID etc. Note: If you are using a custom headerFilterStrategy then this option does not apply. | false | ConfigDef.Importance.MEDIUM
+| *camel.component.amqp.jmsKeyFormatStrategy* | Pluggable strategy for encoding and decoding JMS keys so they can be compliant with the JMS specification. Camel provides two implementations out of the box: default and passthrough. The default strategy will safely marshal dots and hyphens (. and -). The passthrough strategy leaves the key as is. Can be used for JMS brokers which do not care whether JMS header keys contain illegal characters. You can provide your own implementation of the [...]
+| *camel.component.amqp.jmsOperations* | Allows you to use your own implementation of the org.springframework.jms.core.JmsOperations interface. Camel uses JmsTemplate as default. Can be used for testing purpose, but not used much as stated in the spring API docs. | null | ConfigDef.Importance.MEDIUM
+| *camel.component.amqp.mapJmsMessage* | Specifies whether Camel should auto map the received JMS message to a suited payload type, such as javax.jms.TextMessage to a String etc. | true | ConfigDef.Importance.MEDIUM
+| *camel.component.amqp.maxMessagesPerTask* | The number of messages per task. -1 is unlimited. If you use a range for concurrent consumers (eg min max), then this option can be used to set a value to eg 100 to control how fast the consumers will shrink when less work is required. | -1 | ConfigDef.Importance.MEDIUM
+| *camel.component.amqp.messageConverter* | To use a custom Spring org.springframework.jms.support.converter.MessageConverter so you can be in control how to map to/from a javax.jms.Message. | null | ConfigDef.Importance.MEDIUM
+| *camel.component.amqp.messageCreatedStrategy* | To use the given MessageCreatedStrategy which are invoked when Camel creates new instances of javax.jms.Message objects when Camel is sending a JMS message. | null | ConfigDef.Importance.MEDIUM
+| *camel.component.amqp.messageIdEnabled* | When sending, specifies whether message IDs should be added. This is just an hint to the JMS broker. If the JMS provider accepts this hint, these messages must have the message ID set to null; if the provider ignores the hint, the message ID must be set to its normal unique value. | true | ConfigDef.Importance.MEDIUM
+| *camel.component.amqp.messageTimestampEnabled* | Specifies whether timestamps should be enabled by default on sending messages. This is just an hint to the JMS broker. If the JMS provider accepts this hint, these messages must have the timestamp set to zero; if the provider ignores the hint the timestamp must be set to its normal value. | true | ConfigDef.Importance.MEDIUM
+| *camel.component.amqp.pubSubNoLocal* | Specifies whether to inhibit the delivery of messages published by its own connection. | false | ConfigDef.Importance.MEDIUM
+| *camel.component.amqp.queueBrowseStrategy* | To use a custom QueueBrowseStrategy when browsing queues | null | ConfigDef.Importance.MEDIUM
+| *camel.component.amqp.receiveTimeout* | The timeout for receiving messages (in milliseconds). | 1000L | ConfigDef.Importance.MEDIUM
+| *camel.component.amqp.recoveryInterval* | Specifies the interval between recovery attempts, i.e. when a connection is being refreshed, in milliseconds. The default is 5000 ms, that is, 5 seconds. | 5000L | ConfigDef.Importance.MEDIUM
+| *camel.component.amqp.requestTimeoutCheckerInterval* | Configures how often Camel should check for timed out Exchanges when doing request/reply over JMS. By default Camel checks once per second. But if you must react faster when a timeout occurs, then you can lower this interval, to check more frequently. The timeout is determined by the option requestTimeout. | 1000L | ConfigDef.Importance.MEDIUM
+| *camel.component.amqp.transferException* | If enabled and you are using Request Reply messaging (InOut) and an Exchange failed on the consumer side, then the caused Exception will be send back in response as a javax.jms.ObjectMessage. If the client is Camel, the returned Exception is rethrown. This allows you to use Camel JMS as a bridge in your routing - for example, using persistent queues to enable robust routing. Notice that if you also have transferExchange enabled, this option ta [...]
+| *camel.component.amqp.transferExchange* | You can transfer the exchange over the wire instead of just the body and headers. The following fields are transferred: In body, Out body, Fault body, In headers, Out headers, Fault headers, exchange properties, exchange exception. This requires that the objects are serializable. Camel will exclude any non-serializable objects and log it at WARN level. You must enable this option on both the producer and consumer side, so Camel knows the payloa [...]
+| *camel.component.amqp.useMessageIDAsCorrelationID* | Specifies whether JMSMessageID should always be used as JMSCorrelationID for InOut messages. | false | ConfigDef.Importance.MEDIUM
+| *camel.component.amqp.waitForProvisionCorrelationToBeUpdatedCounter* | Number of times to wait for provisional correlation id to be updated to the actual correlation id when doing request/reply over JMS and when the option useMessageIDAsCorrelationID is enabled. | 50 | ConfigDef.Importance.MEDIUM
+| *camel.component.amqp.waitForProvisionCorrelationToBeUpdatedThreadSleepingTime* | Interval in millis to sleep each time while waiting for provisional correlation id to be updated. | 100L | ConfigDef.Importance.MEDIUM
+| *camel.component.amqp.headerFilterStrategy* | To use a custom org.apache.camel.spi.HeaderFilterStrategy to filter header to and from Camel message. | null | ConfigDef.Importance.MEDIUM
+| *camel.component.amqp.password* | Password to use with the ConnectionFactory. You can also configure username/password directly on the ConnectionFactory. | null | ConfigDef.Importance.MEDIUM
+| *camel.component.amqp.username* | Username to use with the ConnectionFactory. You can also configure username/password directly on the ConnectionFactory. | null | ConfigDef.Importance.MEDIUM
+| *camel.component.amqp.transacted* | Specifies whether to use transacted mode | false | ConfigDef.Importance.MEDIUM
+| *camel.component.amqp.lazyCreateTransactionManager* | If true, Camel will create a JmsTransactionManager, if there is no transactionManager injected when option transacted=true. | true | ConfigDef.Importance.MEDIUM
+| *camel.component.amqp.transactionManager* | The Spring transaction manager to use. | null | ConfigDef.Importance.MEDIUM
+| *camel.component.amqp.transactionName* | The name of the transaction to use. | null | ConfigDef.Importance.MEDIUM
+| *camel.component.amqp.transactionTimeout* | The timeout value of the transaction (in seconds), if using transacted mode. | -1 | ConfigDef.Importance.MEDIUM
+|===
+
+
+// kafka-connector options: END
diff --git a/docs/modules/ROOT/pages/connectors/camel-amqp-kafka-source-connector.adoc b/docs/modules/ROOT/pages/connectors/camel-amqp-kafka-source-connector.adoc
new file mode 100644
index 0000000..30f62de
--- /dev/null
+++ b/docs/modules/ROOT/pages/connectors/camel-amqp-kafka-source-connector.adoc
@@ -0,0 +1,157 @@
+// kafka-connector options: START
+== camel-amqp-kafka-connector source configuration
+
+When using camel-amqp-kafka-connector as source 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-amqp-kafka-connector</artifactId>
+ <version>x.x.x</version>
+ <!-- use the same version as your Camel Kafka connector version -->
+</dependency>
+----
+
+
+[width="100%",cols="2,5,^1,2",options="header"]
+|===
+| Name | Description | Default | Priority
+| *camel.source.path.destinationType* | The kind of destination to use One of: [queue] [topic] [temp-queue] [temp-topic] | "queue" | ConfigDef.Importance.MEDIUM
+| *camel.source.path.destinationName* | Name of the queue or topic to use as destination | null | ConfigDef.Importance.HIGH
+| *camel.source.endpoint.clientId* | Sets the JMS client ID to use. Note that this value, if specified, must be unique and can only be used by a single JMS connection instance. It is typically only required for durable topic subscriptions. If using Apache ActiveMQ you may prefer to use Virtual Topics instead. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.connectionFactory* | The connection factory to be use. A connection factory must be configured either on the component or endpoint. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.disableReplyTo* | Specifies whether Camel ignores the JMSReplyTo header in messages. If true, Camel does not send a reply back to the destination specified in the JMSReplyTo header. You can use this option if you want Camel to consume from a route and you do not want Camel to automatically send back a reply message because another component in your code handles the reply message. You can also use this option if you want to use Camel as a proxy between different m [...]
+| *camel.source.endpoint.durableSubscriptionName* | The durable subscriber name for specifying durable topic subscriptions. The clientId option must be configured as well. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.jmsMessageType* | Allows you to force the use of a specific javax.jms.Message implementation for sending JMS messages. Possible values are: Bytes, Map, Object, Stream, Text. By default, Camel would determine which JMS message type to use from the In body type. This option allows you to specify it. One of: [Bytes] [Map] [Object] [Stream] [Text] | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.testConnectionOnStartup* | Specifies whether to test the connection on startup. This ensures that when Camel starts that all the JMS consumers have a valid connection to the JMS broker. If a connection cannot be granted then Camel throws an exception on startup. This ensures that Camel is not started with failed connections. The JMS producers is tested as well. | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.acknowledgementModeName* | The JMS acknowledgement name, which is one of: SESSION_TRANSACTED, CLIENT_ACKNOWLEDGE, AUTO_ACKNOWLEDGE, DUPS_OK_ACKNOWLEDGE One of: [SESSION_TRANSACTED] [CLIENT_ACKNOWLEDGE] [AUTO_ACKNOWLEDGE] [DUPS_OK_ACKNOWLEDGE] | "AUTO_ACKNOWLEDGE" | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.asyncConsumer* | Whether the JmsConsumer processes the Exchange asynchronously. If enabled then the JmsConsumer may pickup the next message from the JMS queue, while the previous message is being processed asynchronously (by the Asynchronous Routing Engine). This means that messages may be processed not 100% strictly in order. If disabled (as default) then the Exchange is fully processed before the JmsConsumer will pickup the next message from the JMS queue. Note [...]
+| *camel.source.endpoint.autoStartup* | Specifies whether the consumer container should auto-startup. | true | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.cacheLevel* | Sets the cache level by ID for the underlying JMS resources. See cacheLevelName option for more details. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.cacheLevelName* | Sets the cache level by name for the underlying JMS resources. Possible values are: CACHE_AUTO, CACHE_CONNECTION, CACHE_CONSUMER, CACHE_NONE, and CACHE_SESSION. The default setting is CACHE_AUTO. See the Spring documentation and Transactions Cache Levels for more information. One of: [CACHE_AUTO] [CACHE_CONNECTION] [CACHE_CONSUMER] [CACHE_NONE] [CACHE_SESSION] | "CACHE_AUTO" | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.concurrentConsumers* | Specifies the default number of concurrent consumers when consuming from JMS (not for request/reply over JMS). See also the maxMessagesPerTask option to control dynamic scaling up/down of threads. When doing request/reply over JMS then the option replyToConcurrentConsumers is used to control number of concurrent consumers on the reply message listener. | 1 | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.maxConcurrentConsumers* | Specifies the maximum number of concurrent consumers when consuming from JMS (not for request/reply over JMS). See also the maxMessagesPerTask option to control dynamic scaling up/down of threads. When doing request/reply over JMS then the option replyToMaxConcurrentConsumers is used to control number of concurrent consumers on the reply message listener. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.replyTo* | Provides an explicit ReplyTo destination, which overrides any incoming value of Message.getJMSReplyTo(). | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.replyToDeliveryPersistent* | Specifies whether to use persistent delivery by default for replies. | true | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.selector* | Sets the JMS selector to use | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.subscriptionDurable* | Set whether to make the subscription durable. The durable subscription name to be used can be specified through the subscriptionName property. Default is false. Set this to true to register a durable subscription, typically in combination with a subscriptionName value (unless your message listener class name is good enough as subscription name). Only makes sense when listening to a topic (pub-sub domain), therefore this method switches the [...]
+| *camel.source.endpoint.subscriptionName* | Set the name of a subscription to create. To be applied in case of a topic (pub-sub domain) with a shared or durable subscription. The subscription name needs to be unique within this client's JMS client id. Default is the class name of the specified message listener. Note: Only 1 concurrent consumer (which is the default of this message listener container) is allowed for each subscription, except for a shared subscription (which requires JMS [...]
+| *camel.source.endpoint.subscriptionShared* | Set whether to make the subscription shared. The shared subscription name to be used can be specified through the subscriptionName property. Default is false. Set this to true to register a shared subscription, typically in combination with a subscriptionName value (unless your message listener class name is good enough as subscription name). Note that shared subscriptions may also be durable, so this flag can (and often will) be combined wi [...]
+| *camel.source.endpoint.acceptMessagesWhileStopping* | Specifies whether the consumer accept messages while it is stopping. You may consider enabling this option, if you start and stop JMS routes at runtime, while there are still messages enqueued on the queue. If this option is false, and you stop the JMS route, then messages may be rejected, and the JMS broker would have to attempt redeliveries, which yet again may be rejected, and eventually the message may be moved at a dead letter [...]
+| *camel.source.endpoint.allowReplyManagerQuickStop* | Whether the DefaultMessageListenerContainer used in the reply managers for request-reply messaging allow the DefaultMessageListenerContainer.runningAllowed flag to quick stop in case JmsConfiguration#isAcceptMessagesWhileStopping is enabled, and org.apache.camel.CamelContext is currently being stopped. This quick stop ability is enabled by default in the regular JMS consumers but to enable for reply managers you must enable this flag [...]
+| *camel.source.endpoint.consumerType* | The consumer type to use, which can be one of: Simple, Default, or Custom. The consumer type determines which Spring JMS listener to use. Default will use org.springframework.jms.listener.DefaultMessageListenerContainer, Simple will use org.springframework.jms.listener.SimpleMessageListenerContainer. When Custom is specified, the MessageListenerContainerFactory defined by the messageListenerContainerFactory option will determine what org.springfra [...]
+| *camel.source.endpoint.defaultTaskExecutorType* | Specifies what default TaskExecutor type to use in the DefaultMessageListenerContainer, for both consumer endpoints and the ReplyTo consumer of producer endpoints. Possible values: SimpleAsync (uses Spring's SimpleAsyncTaskExecutor) or ThreadPool (uses Spring's ThreadPoolTaskExecutor with optimal values - cached threadpool-like). If not set, it defaults to the previous behaviour, which uses a cached thread pool for consumer endpoints an [...]
+| *camel.source.endpoint.eagerLoadingOfProperties* | Enables eager loading of JMS properties and payload as soon as a message is loaded which generally is inefficient as the JMS properties may not be required but sometimes can catch early any issues with the underlying JMS provider and the use of JMS properties. See also the option eagerPoisonBody. | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.eagerPoisonBody* | If eagerLoadingOfProperties is enabled and the JMS message payload (JMS body or JMS properties) is poison (cannot be read/mapped), then set this text as the message body instead so the message can be processed (the cause of the poison are already stored as exception on the Exchange). This can be turned off by setting eagerPoisonBody=false. See also the option eagerLoadingOfProperties. | "Poison JMS message due to ${exception.message}" | ConfigD [...]
+| *camel.source.endpoint.exceptionHandler* | To let the consumer use a custom ExceptionHandler. Notice if the option bridgeErrorHandler is enabled then this option is not in use. By default the consumer will deal with exceptions, that will be logged at WARN or ERROR level and ignored. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.exchangePattern* | Sets the exchange pattern when the consumer creates an exchange. One of: [InOnly] [InOut] [InOptionalOut] | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.exposeListenerSession* | Specifies whether the listener session should be exposed when consuming messages. | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.replyToSameDestinationAllowed* | Whether a JMS consumer is allowed to send a reply message to the same destination that the consumer is using to consume from. This prevents an endless loop by consuming and sending back the same message to itself. | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.taskExecutor* | Allows you to specify a custom task executor for consuming messages. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.allowSerializedHeaders* | Controls whether or not to include serialized headers. Applies only when transferExchange is true. This requires that the objects are serializable. Camel will exclude any non-serializable objects and log it at WARN level. | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.asyncStartListener* | Whether to startup the JmsConsumer message listener asynchronously, when starting a route. For example if a JmsConsumer cannot get a connection to a remote JMS broker, then it may block while retrying and/or failover. This will cause Camel to block while starting routes. By setting this option to true, you will let routes startup, while the JmsConsumer connects to the JMS broker using a dedicated thread in asynchronous mode. If this option i [...]
+| *camel.source.endpoint.asyncStopListener* | Whether to stop the JmsConsumer message listener asynchronously, when stopping a route. | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.basicPropertyBinding* | Whether the endpoint should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.destinationResolver* | A pluggable org.springframework.jms.support.destination.DestinationResolver that allows you to use your own resolver (for example, to lookup the real destination in a JNDI registry). | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.errorHandler* | Specifies a org.springframework.util.ErrorHandler to be invoked in case of any uncaught exceptions thrown while processing a Message. By default these exceptions will be logged at the WARN level, if no errorHandler has been configured. You can configure logging level and whether stack traces should be logged using errorHandlerLoggingLevel and errorHandlerLogStackTrace options. This makes it much easier to configure, than having to code a custom er [...]
+| *camel.source.endpoint.exceptionListener* | Specifies the JMS Exception Listener that is to be notified of any underlying JMS exceptions. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.headerFilterStrategy* | To use a custom HeaderFilterStrategy to filter header to and from Camel message. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.idleConsumerLimit* | Specify the limit for the number of consumers that are allowed to be idle at any given time. | 1 | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.idleTaskExecutionLimit* | Specifies the limit for idle executions of a receive task, not having received any message within its execution. If this limit is reached, the task will shut down and leave receiving to other executing tasks (in the case of dynamic scheduling; see the maxConcurrentConsumers setting). There is additional doc available from Spring. | 1 | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.includeAllJMSXProperties* | Whether to include all JMSXxxx properties when mapping from JMS to Camel Message. Setting this to true will include properties such as JMSXAppID, and JMSXUserID etc. Note: If you are using a custom headerFilterStrategy then this option does not apply. | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.jmsKeyFormatStrategy* | Pluggable strategy for encoding and decoding JMS keys so they can be compliant with the JMS specification. Camel provides two implementations out of the box: default and passthrough. The default strategy will safely marshal dots and hyphens (. and -). The passthrough strategy leaves the key as is. Can be used for JMS brokers which do not care whether JMS header keys contain illegal characters. You can provide your own implementation of the [...]
+| *camel.source.endpoint.mapJmsMessage* | Specifies whether Camel should auto map the received JMS message to a suited payload type, such as javax.jms.TextMessage to a String etc. | true | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.maxMessagesPerTask* | The number of messages per task. -1 is unlimited. If you use a range for concurrent consumers (eg min max), then this option can be used to set a value to eg 100 to control how fast the consumers will shrink when less work is required. | -1 | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.messageConverter* | To use a custom Spring org.springframework.jms.support.converter.MessageConverter so you can be in control how to map to/from a javax.jms.Message. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.messageCreatedStrategy* | To use the given MessageCreatedStrategy which are invoked when Camel creates new instances of javax.jms.Message objects when Camel is sending a JMS message. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.messageIdEnabled* | When sending, specifies whether message IDs should be added. This is just an hint to the JMS broker. If the JMS provider accepts this hint, these messages must have the message ID set to null; if the provider ignores the hint, the message ID must be set to its normal unique value. | true | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.messageListenerContainerFactory* | Registry ID of the MessageListenerContainerFactory used to determine what org.springframework.jms.listener.AbstractMessageListenerContainer to use to consume messages. Setting this will automatically set consumerType to Custom. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.messageTimestampEnabled* | Specifies whether timestamps should be enabled by default on sending messages. This is just an hint to the JMS broker. If the JMS provider accepts this hint, these messages must have the timestamp set to zero; if the provider ignores the hint the timestamp must be set to its normal value. | true | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.pubSubNoLocal* | Specifies whether to inhibit the delivery of messages published by its own connection. | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.receiveTimeout* | The timeout for receiving messages (in milliseconds). | 1000L | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.recoveryInterval* | Specifies the interval between recovery attempts, i.e. when a connection is being refreshed, in milliseconds. The default is 5000 ms, that is, 5 seconds. | 5000L | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.requestTimeoutCheckerInterval* | Configures how often Camel should check for timed out Exchanges when doing request/reply over JMS. By default Camel checks once per second. But if you must react faster when a timeout occurs, then you can lower this interval, to check more frequently. The timeout is determined by the option requestTimeout. | 1000L | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.synchronous* | Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.transferException* | If enabled and you are using Request Reply messaging (InOut) and an Exchange failed on the consumer side, then the caused Exception will be send back in response as a javax.jms.ObjectMessage. If the client is Camel, the returned Exception is rethrown. This allows you to use Camel JMS as a bridge in your routing - for example, using persistent queues to enable robust routing. Notice that if you also have transferExchange enabled, this option t [...]
+| *camel.source.endpoint.transferExchange* | You can transfer the exchange over the wire instead of just the body and headers. The following fields are transferred: In body, Out body, Fault body, In headers, Out headers, Fault headers, exchange properties, exchange exception. This requires that the objects are serializable. Camel will exclude any non-serializable objects and log it at WARN level. You must enable this option on both the producer and consumer side, so Camel knows the paylo [...]
+| *camel.source.endpoint.useMessageIDAsCorrelationID* | Specifies whether JMSMessageID should always be used as JMSCorrelationID for InOut messages. | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.waitForProvisionCorrelationToBeUpdatedCounter* | Number of times to wait for provisional correlation id to be updated to the actual correlation id when doing request/reply over JMS and when the option useMessageIDAsCorrelationID is enabled. | 50 | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.waitForProvisionCorrelationToBeUpdatedThreadSleepingTime* | Interval in millis to sleep each time while waiting for provisional correlation id to be updated. | 100L | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.errorHandlerLoggingLevel* | Allows to configure the default errorHandler logging level for logging uncaught exceptions. One of: [TRACE] [DEBUG] [INFO] [WARN] [ERROR] [OFF] | "WARN" | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.errorHandlerLogStackTrace* | Allows to control whether stacktraces should be logged or not, by the default errorHandler. | true | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.password* | Password to use with the ConnectionFactory. You can also configure username/password directly on the ConnectionFactory. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.username* | Username to use with the ConnectionFactory. You can also configure username/password directly on the ConnectionFactory. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.transacted* | Specifies whether to use transacted mode | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.lazyCreateTransactionManager* | If true, Camel will create a JmsTransactionManager, if there is no transactionManager injected when option transacted=true. | true | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.transactionManager* | The Spring transaction manager to use. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.transactionName* | The name of the transaction to use. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.transactionTimeout* | The timeout value of the transaction (in seconds), if using transacted mode. | -1 | ConfigDef.Importance.MEDIUM
+| *camel.component.amqp.clientId* | Sets the JMS client ID to use. Note that this value, if specified, must be unique and can only be used by a single JMS connection instance. It is typically only required for durable topic subscriptions. If using Apache ActiveMQ you may prefer to use Virtual Topics instead. | null | ConfigDef.Importance.MEDIUM
+| *camel.component.amqp.connectionFactory* | The connection factory to be use. A connection factory must be configured either on the component or endpoint. | null | ConfigDef.Importance.MEDIUM
+| *camel.component.amqp.durableSubscriptionName* | The durable subscriber name for specifying durable topic subscriptions. The clientId option must be configured as well. | null | ConfigDef.Importance.MEDIUM
+| *camel.component.amqp.includeAmqpAnnotations* | Whether to include AMQP annotations when mapping from AMQP to Camel Message. Setting this to true will map AMQP message annotations to message headers. Due to limitations in Apache Qpid JMS API, currently delivery annotations are ignored. | false | ConfigDef.Importance.MEDIUM
+| *camel.component.amqp.testConnectionOnStartup* | Specifies whether to test the connection on startup. This ensures that when Camel starts that all the JMS consumers have a valid connection to the JMS broker. If a connection cannot be granted then Camel throws an exception on startup. This ensures that Camel is not started with failed connections. The JMS producers is tested as well. | false | ConfigDef.Importance.MEDIUM
+| *camel.component.amqp.acknowledgementMode* | The JMS acknowledgement mode defined as an Integer. Allows you to set vendor-specific extensions to the acknowledgment mode. For the regular modes, it is preferable to use the acknowledgementModeName instead. | null | ConfigDef.Importance.MEDIUM
+| *camel.component.amqp.acknowledgementModeName* | The JMS acknowledgement name, which is one of: SESSION_TRANSACTED, CLIENT_ACKNOWLEDGE, AUTO_ACKNOWLEDGE, DUPS_OK_ACKNOWLEDGE One of: [SESSION_TRANSACTED] [CLIENT_ACKNOWLEDGE] [AUTO_ACKNOWLEDGE] [DUPS_OK_ACKNOWLEDGE] | "AUTO_ACKNOWLEDGE" | ConfigDef.Importance.MEDIUM
+| *camel.component.amqp.asyncConsumer* | Whether the JmsConsumer processes the Exchange asynchronously. If enabled then the JmsConsumer may pickup the next message from the JMS queue, while the previous message is being processed asynchronously (by the Asynchronous Routing Engine). This means that messages may be processed not 100% strictly in order. If disabled (as default) then the Exchange is fully processed before the JmsConsumer will pickup the next message from the JMS queue. Note [...]
+| *camel.component.amqp.autoStartup* | Specifies whether the consumer container should auto-startup. | true | ConfigDef.Importance.MEDIUM
+| *camel.component.amqp.bridgeErrorHandler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | ConfigDef.Importance.MEDIUM
+| *camel.component.amqp.cacheLevel* | Sets the cache level by ID for the underlying JMS resources. See cacheLevelName option for more details. | null | ConfigDef.Importance.MEDIUM
+| *camel.component.amqp.cacheLevelName* | Sets the cache level by name for the underlying JMS resources. Possible values are: CACHE_AUTO, CACHE_CONNECTION, CACHE_CONSUMER, CACHE_NONE, and CACHE_SESSION. The default setting is CACHE_AUTO. See the Spring documentation and Transactions Cache Levels for more information. One of: [CACHE_AUTO] [CACHE_CONNECTION] [CACHE_CONSUMER] [CACHE_NONE] [CACHE_SESSION] | "CACHE_AUTO" | ConfigDef.Importance.MEDIUM
+| *camel.component.amqp.concurrentConsumers* | Specifies the default number of concurrent consumers when consuming from JMS (not for request/reply over JMS). See also the maxMessagesPerTask option to control dynamic scaling up/down of threads. When doing request/reply over JMS then the option replyToConcurrentConsumers is used to control number of concurrent consumers on the reply message listener. | 1 | ConfigDef.Importance.MEDIUM
+| *camel.component.amqp.maxConcurrentConsumers* | Specifies the maximum number of concurrent consumers when consuming from JMS (not for request/reply over JMS). See also the maxMessagesPerTask option to control dynamic scaling up/down of threads. When doing request/reply over JMS then the option replyToMaxConcurrentConsumers is used to control number of concurrent consumers on the reply message listener. | null | ConfigDef.Importance.MEDIUM
+| *camel.component.amqp.subscriptionDurable* | Set whether to make the subscription durable. The durable subscription name to be used can be specified through the subscriptionName property. Default is false. Set this to true to register a durable subscription, typically in combination with a subscriptionName value (unless your message listener class name is good enough as subscription name). Only makes sense when listening to a topic (pub-sub domain), therefore this method switches the p [...]
+| *camel.component.amqp.subscriptionName* | Set the name of a subscription to create. To be applied in case of a topic (pub-sub domain) with a shared or durable subscription. The subscription name needs to be unique within this client's JMS client id. Default is the class name of the specified message listener. Note: Only 1 concurrent consumer (which is the default of this message listener container) is allowed for each subscription, except for a shared subscription (which requires JMS 2 [...]
+| *camel.component.amqp.subscriptionShared* | Set whether to make the subscription shared. The shared subscription name to be used can be specified through the subscriptionName property. Default is false. Set this to true to register a shared subscription, typically in combination with a subscriptionName value (unless your message listener class name is good enough as subscription name). Note that shared subscriptions may also be durable, so this flag can (and often will) be combined wit [...]
+| *camel.component.amqp.acceptMessagesWhileStopping* | Specifies whether the consumer accept messages while it is stopping. You may consider enabling this option, if you start and stop JMS routes at runtime, while there are still messages enqueued on the queue. If this option is false, and you stop the JMS route, then messages may be rejected, and the JMS broker would have to attempt redeliveries, which yet again may be rejected, and eventually the message may be moved at a dead letter q [...]
+| *camel.component.amqp.allowReplyManagerQuickStop* | Whether the DefaultMessageListenerContainer used in the reply managers for request-reply messaging allow the DefaultMessageListenerContainer.runningAllowed flag to quick stop in case JmsConfiguration#isAcceptMessagesWhileStopping is enabled, and org.apache.camel.CamelContext is currently being stopped. This quick stop ability is enabled by default in the regular JMS consumers but to enable for reply managers you must enable this flag. [...]
+| *camel.component.amqp.defaultTaskExecutorType* | Specifies what default TaskExecutor type to use in the DefaultMessageListenerContainer, for both consumer endpoints and the ReplyTo consumer of producer endpoints. Possible values: SimpleAsync (uses Spring's SimpleAsyncTaskExecutor) or ThreadPool (uses Spring's ThreadPoolTaskExecutor with optimal values - cached threadpool-like). If not set, it defaults to the previous behaviour, which uses a cached thread pool for consumer endpoints and [...]
+| *camel.component.amqp.eagerLoadingOfProperties* | Enables eager loading of JMS properties as soon as a message is loaded which generally is inefficient as the JMS properties may not be required but sometimes can catch early any issues with the underlying JMS provider and the use of JMS properties. See also the option eagerLoadingOfBody. | false | ConfigDef.Importance.MEDIUM
+| *camel.component.amqp.eagerPoisonBody* | If eagerLoadingOfProperties is enabled and the JMS message payload (JMS body or JMS properties) is poison (cannot be read/mapped), then set this text as the message body instead so the message can be processed (the cause of the poison are already stored as exception on the Exchange). This can be turned off by setting eagerPoisonBody=false. See also the option eagerLoadingOfProperties. | "Poison JMS message due to ${exception.message}" | ConfigDe [...]
+| *camel.component.amqp.exposeListenerSession* | Specifies whether the listener session should be exposed when consuming messages. | false | ConfigDef.Importance.MEDIUM
+| *camel.component.amqp.taskExecutor* | Allows you to specify a custom task executor for consuming messages. | null | ConfigDef.Importance.MEDIUM
+| *camel.component.amqp.allowAutoWiredConnectionFactory* | Whether to auto-discover ConnectionFactory from the registry, if no connection factory has been configured. If only one instance of ConnectionFactory is found then it will be used. This is enabled by default. | false | ConfigDef.Importance.MEDIUM
+| *camel.component.amqp.allowAutoWiredDestinationResolver* | Whether to auto-discover DestinationResolver from the registry, if no destination resolver has been configured. If only one instance of DestinationResolver is found then it will be used. This is enabled by default. | false | ConfigDef.Importance.MEDIUM
+| *camel.component.amqp.asyncStartListener* | Whether to startup the JmsConsumer message listener asynchronously, when starting a route. For example if a JmsConsumer cannot get a connection to a remote JMS broker, then it may block while retrying and/or failover. This will cause Camel to block while starting routes. By setting this option to true, you will let routes startup, while the JmsConsumer connects to the JMS broker using a dedicated thread in asynchronous mode. If this option is [...]
+| *camel.component.amqp.asyncStopListener* | Whether to stop the JmsConsumer message listener asynchronously, when stopping a route. | false | ConfigDef.Importance.MEDIUM
+| *camel.component.amqp.basicPropertyBinding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+| *camel.component.amqp.configuration* | To use a shared JMS configuration | null | ConfigDef.Importance.MEDIUM
+| *camel.component.amqp.destinationResolver* | A pluggable org.springframework.jms.support.destination.DestinationResolver that allows you to use your own resolver (for example, to lookup the real destination in a JNDI registry). | null | ConfigDef.Importance.MEDIUM
+| *camel.component.amqp.errorHandler* | Specifies a org.springframework.util.ErrorHandler to be invoked in case of any uncaught exceptions thrown while processing a Message. By default these exceptions will be logged at the WARN level, if no errorHandler has been configured. You can configure logging level and whether stack traces should be logged using errorHandlerLoggingLevel and errorHandlerLogStackTrace options. This makes it much easier to configure, than having to code a custom err [...]
+| *camel.component.amqp.exceptionListener* | Specifies the JMS Exception Listener that is to be notified of any underlying JMS exceptions. | null | ConfigDef.Importance.MEDIUM
+| *camel.component.amqp.idleConsumerLimit* | Specify the limit for the number of consumers that are allowed to be idle at any given time. | 1 | ConfigDef.Importance.MEDIUM
+| *camel.component.amqp.idleTaskExecutionLimit* | Specifies the limit for idle executions of a receive task, not having received any message within its execution. If this limit is reached, the task will shut down and leave receiving to other executing tasks (in the case of dynamic scheduling; see the maxConcurrentConsumers setting). There is additional doc available from Spring. | 1 | ConfigDef.Importance.MEDIUM
+| *camel.component.amqp.includeAllJMSXProperties* | Whether to include all JMSXxxx properties when mapping from JMS to Camel Message. Setting this to true will include properties such as JMSXAppID, and JMSXUserID etc. Note: If you are using a custom headerFilterStrategy then this option does not apply. | false | ConfigDef.Importance.MEDIUM
+| *camel.component.amqp.jmsKeyFormatStrategy* | Pluggable strategy for encoding and decoding JMS keys so they can be compliant with the JMS specification. Camel provides two implementations out of the box: default and passthrough. The default strategy will safely marshal dots and hyphens (. and -). The passthrough strategy leaves the key as is. Can be used for JMS brokers which do not care whether JMS header keys contain illegal characters. You can provide your own implementation of the [...]
+| *camel.component.amqp.jmsOperations* | Allows you to use your own implementation of the org.springframework.jms.core.JmsOperations interface. Camel uses JmsTemplate as default. Can be used for testing purpose, but not used much as stated in the spring API docs. | null | ConfigDef.Importance.MEDIUM
+| *camel.component.amqp.mapJmsMessage* | Specifies whether Camel should auto map the received JMS message to a suited payload type, such as javax.jms.TextMessage to a String etc. | true | ConfigDef.Importance.MEDIUM
+| *camel.component.amqp.maxMessagesPerTask* | The number of messages per task. -1 is unlimited. If you use a range for concurrent consumers (eg min max), then this option can be used to set a value to eg 100 to control how fast the consumers will shrink when less work is required. | -1 | ConfigDef.Importance.MEDIUM
+| *camel.component.amqp.messageConverter* | To use a custom Spring org.springframework.jms.support.converter.MessageConverter so you can be in control how to map to/from a javax.jms.Message. | null | ConfigDef.Importance.MEDIUM
+| *camel.component.amqp.messageCreatedStrategy* | To use the given MessageCreatedStrategy which are invoked when Camel creates new instances of javax.jms.Message objects when Camel is sending a JMS message. | null | ConfigDef.Importance.MEDIUM
+| *camel.component.amqp.messageIdEnabled* | When sending, specifies whether message IDs should be added. This is just an hint to the JMS broker. If the JMS provider accepts this hint, these messages must have the message ID set to null; if the provider ignores the hint, the message ID must be set to its normal unique value. | true | ConfigDef.Importance.MEDIUM
+| *camel.component.amqp.messageTimestampEnabled* | Specifies whether timestamps should be enabled by default on sending messages. This is just an hint to the JMS broker. If the JMS provider accepts this hint, these messages must have the timestamp set to zero; if the provider ignores the hint the timestamp must be set to its normal value. | true | ConfigDef.Importance.MEDIUM
+| *camel.component.amqp.pubSubNoLocal* | Specifies whether to inhibit the delivery of messages published by its own connection. | false | ConfigDef.Importance.MEDIUM
+| *camel.component.amqp.queueBrowseStrategy* | To use a custom QueueBrowseStrategy when browsing queues | null | ConfigDef.Importance.MEDIUM
+| *camel.component.amqp.receiveTimeout* | The timeout for receiving messages (in milliseconds). | 1000L | ConfigDef.Importance.MEDIUM
+| *camel.component.amqp.recoveryInterval* | Specifies the interval between recovery attempts, i.e. when a connection is being refreshed, in milliseconds. The default is 5000 ms, that is, 5 seconds. | 5000L | ConfigDef.Importance.MEDIUM
+| *camel.component.amqp.requestTimeoutCheckerInterval* | Configures how often Camel should check for timed out Exchanges when doing request/reply over JMS. By default Camel checks once per second. But if you must react faster when a timeout occurs, then you can lower this interval, to check more frequently. The timeout is determined by the option requestTimeout. | 1000L | ConfigDef.Importance.MEDIUM
+| *camel.component.amqp.transferException* | If enabled and you are using Request Reply messaging (InOut) and an Exchange failed on the consumer side, then the caused Exception will be send back in response as a javax.jms.ObjectMessage. If the client is Camel, the returned Exception is rethrown. This allows you to use Camel JMS as a bridge in your routing - for example, using persistent queues to enable robust routing. Notice that if you also have transferExchange enabled, this option ta [...]
+| *camel.component.amqp.transferExchange* | You can transfer the exchange over the wire instead of just the body and headers. The following fields are transferred: In body, Out body, Fault body, In headers, Out headers, Fault headers, exchange properties, exchange exception. This requires that the objects are serializable. Camel will exclude any non-serializable objects and log it at WARN level. You must enable this option on both the producer and consumer side, so Camel knows the payloa [...]
+| *camel.component.amqp.useMessageIDAsCorrelationID* | Specifies whether JMSMessageID should always be used as JMSCorrelationID for InOut messages. | false | ConfigDef.Importance.MEDIUM
+| *camel.component.amqp.waitForProvisionCorrelationToBeUpdatedCounter* | Number of times to wait for provisional correlation id to be updated to the actual correlation id when doing request/reply over JMS and when the option useMessageIDAsCorrelationID is enabled. | 50 | ConfigDef.Importance.MEDIUM
+| *camel.component.amqp.waitForProvisionCorrelationToBeUpdatedThreadSleepingTime* | Interval in millis to sleep each time while waiting for provisional correlation id to be updated. | 100L | ConfigDef.Importance.MEDIUM
+| *camel.component.amqp.errorHandlerLoggingLevel* | Allows to configure the default errorHandler logging level for logging uncaught exceptions. One of: [TRACE] [DEBUG] [INFO] [WARN] [ERROR] [OFF] | "WARN" | ConfigDef.Importance.MEDIUM
+| *camel.component.amqp.errorHandlerLogStackTrace* | Allows to control whether stacktraces should be logged or not, by the default errorHandler. | true | ConfigDef.Importance.MEDIUM
+| *camel.component.amqp.headerFilterStrategy* | To use a custom org.apache.camel.spi.HeaderFilterStrategy to filter header to and from Camel message. | null | ConfigDef.Importance.MEDIUM
+| *camel.component.amqp.password* | Password to use with the ConnectionFactory. You can also configure username/password directly on the ConnectionFactory. | null | ConfigDef.Importance.MEDIUM
+| *camel.component.amqp.username* | Username to use with the ConnectionFactory. You can also configure username/password directly on the ConnectionFactory. | null | ConfigDef.Importance.MEDIUM
+| *camel.component.amqp.transacted* | Specifies whether to use transacted mode | false | ConfigDef.Importance.MEDIUM
+| *camel.component.amqp.lazyCreateTransactionManager* | If true, Camel will create a JmsTransactionManager, if there is no transactionManager injected when option transacted=true. | true | ConfigDef.Importance.MEDIUM
+| *camel.component.amqp.transactionManager* | The Spring transaction manager to use. | null | ConfigDef.Importance.MEDIUM
+| *camel.component.amqp.transactionName* | The name of the transaction to use. | null | ConfigDef.Importance.MEDIUM
+| *camel.component.amqp.transactionTimeout* | The timeout value of the transaction (in seconds), if using transacted mode. | -1 | ConfigDef.Importance.MEDIUM
+|===
+
+
+// kafka-connector options: END
diff --git a/docs/modules/ROOT/pages/connectors/camel-apns-kafka-sink-connector.adoc b/docs/modules/ROOT/pages/connectors/camel-apns-kafka-sink-connector.adoc
new file mode 100644
index 0000000..bb32e24
--- /dev/null
+++ b/docs/modules/ROOT/pages/connectors/camel-apns-kafka-sink-connector.adoc
@@ -0,0 +1,31 @@
+// kafka-connector options: START
+== camel-apns-kafka-connector source configuration
+
+When using camel-apns-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-apns-kafka-connector</artifactId>
+ <version>x.x.x</version>
+ <!-- use the same version as your Camel Kafka connector version -->
+</dependency>
+----
+
+
+[width="100%",cols="2,5,^1,2",options="header"]
+|===
+| Name | Description | Default | Priority
+| *camel.sink.path.name* | Name of the endpoint | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.tokens* | Configure this property in case you want to statically declare tokens related to devices you want to notify. Tokens are separated by comma. | null | ConfigDef.Importance.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 cre [...]
+| *camel.sink.endpoint.basicPropertyBinding* | Whether the endpoint should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.synchronous* | Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). | false | ConfigDef.Importance.MEDIUM
+| *camel.component.apns.apnsService* | The ApnsService to use. The org.apache.camel.component.apns.factory.ApnsServiceFactory can be used to build a ApnsService | null | ConfigDef.Importance.HIGH
+| *camel.component.apns.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 cr [...]
+| *camel.component.apns.basicPropertyBinding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+|===
+
+
+// kafka-connector options: END
diff --git a/docs/modules/ROOT/pages/connectors/camel-apns-kafka-source-connector.adoc b/docs/modules/ROOT/pages/connectors/camel-apns-kafka-source-connector.adoc
new file mode 100644
index 0000000..4c16521
--- /dev/null
+++ b/docs/modules/ROOT/pages/connectors/camel-apns-kafka-source-connector.adoc
@@ -0,0 +1,49 @@
+// kafka-connector options: START
+== camel-apns-kafka-connector source configuration
+
+When using camel-apns-kafka-connector as source 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-apns-kafka-connector</artifactId>
+ <version>x.x.x</version>
+ <!-- use the same version as your Camel Kafka connector version -->
+</dependency>
+----
+
+
+[width="100%",cols="2,5,^1,2",options="header"]
+|===
+| Name | Description | Default | Priority
+| *camel.source.path.name* | Name of the endpoint | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.tokens* | Configure this property in case you want to statically declare tokens related to devices you want to notify. Tokens are separated by comma. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.bridgeErrorHandler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.sendEmptyMessageWhenIdle* | If the polling consumer did not poll any files, you can enable this option to send an empty message (no body) instead. | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.exceptionHandler* | To let the consumer use a custom ExceptionHandler. Notice if the option bridgeErrorHandler is enabled then this option is not in use. By default the consumer will deal with exceptions, that will be logged at WARN or ERROR level and ignored. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.exchangePattern* | Sets the exchange pattern when the consumer creates an exchange. One of: [InOnly] [InOut] [InOptionalOut] | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.pollStrategy* | A pluggable org.apache.camel.PollingConsumerPollingStrategy allowing you to provide your custom implementation to control error handling usually occurred during the poll operation before an Exchange have been created and being routed in Camel. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.basicPropertyBinding* | Whether the endpoint should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.synchronous* | Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.backoffErrorThreshold* | The number of subsequent error polls (failed due some error) that should happen before the backoffMultipler should kick-in. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.backoffIdleThreshold* | The number of subsequent idle polls that should happen before the backoffMultipler should kick-in. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.backoffMultiplier* | To let the scheduled polling consumer backoff if there has been a number of subsequent idles/errors in a row. The multiplier is then the number of polls that will be skipped before the next actual attempt is happening again. When this option is in use then backoffIdleThreshold and/or backoffErrorThreshold must also be configured. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.delay* | Milliseconds before the next poll. You can also specify time values using units, such as 60s (60 seconds), 5m30s (5 minutes and 30 seconds), and 1h (1 hour). | 500L | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.greedy* | If greedy is enabled, then the ScheduledPollConsumer will run immediately again, if the previous run polled 1 or more messages. | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.initialDelay* | Milliseconds before the first poll starts. You can also specify time values using units, such as 60s (60 seconds), 5m30s (5 minutes and 30 seconds), and 1h (1 hour). | 1000L | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.repeatCount* | Specifies a maximum limit of number of fires. So if you set it to 1, the scheduler will only fire once. If you set it to 5, it will only fire five times. A value of zero or negative means fire forever. | 0L | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.runLoggingLevel* | The consumer logs a start/complete log line when it polls. This option allows you to configure the logging level for that. One of: [TRACE] [DEBUG] [INFO] [WARN] [ERROR] [OFF] | "TRACE" | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.scheduledExecutorService* | Allows for configuring a custom/shared thread pool to use for the consumer. By default each consumer has its own single threaded thread pool. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.scheduler* | To use a cron scheduler from either camel-spring or camel-quartz component One of: [none] [spring] [quartz] | "none" | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.schedulerProperties* | To configure additional properties when using a custom scheduler or any of the Quartz, Spring based scheduler. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.startScheduler* | Whether the scheduler should be auto started. | true | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.timeUnit* | Time unit for initialDelay and delay options. One of: [NANOSECONDS] [MICROSECONDS] [MILLISECONDS] [SECONDS] [MINUTES] [HOURS] [DAYS] | "MILLISECONDS" | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.useFixedDelay* | Controls if fixed delay or fixed rate is used. See ScheduledExecutorService in JDK for details. | true | ConfigDef.Importance.MEDIUM
+| *camel.component.apns.apnsService* | The ApnsService to use. The org.apache.camel.component.apns.factory.ApnsServiceFactory can be used to build a ApnsService | null | ConfigDef.Importance.HIGH
+| *camel.component.apns.bridgeErrorHandler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | ConfigDef.Importance.MEDIUM
+| *camel.component.apns.basicPropertyBinding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+|===
+
+
+// kafka-connector options: END
diff --git a/docs/modules/ROOT/pages/connectors/camel-as2-kafka-sink-connector.adoc b/docs/modules/ROOT/pages/connectors/camel-as2-kafka-sink-connector.adoc
new file mode 100644
index 0000000..4c70458
--- /dev/null
+++ b/docs/modules/ROOT/pages/connectors/camel-as2-kafka-sink-connector.adoc
@@ -0,0 +1,58 @@
+// kafka-connector options: START
+== camel-as2-kafka-connector source configuration
+
+When using camel-as2-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-as2-kafka-connector</artifactId>
+ <version>x.x.x</version>
+ <!-- use the same version as your Camel Kafka connector version -->
+</dependency>
+----
+
+
+[width="100%",cols="2,5,^1,2",options="header"]
+|===
+| Name | Description | Default | Priority
+| *camel.sink.path.apiName* | What kind of operation to perform One of: [CLIENT] [SERVER] | null | ConfigDef.Importance.HIGH
+| *camel.sink.path.methodName* | What sub operation to use for the selected operation | null | ConfigDef.Importance.HIGH
+| *camel.sink.endpoint.as2From* | The value of the AS2From header of AS2 message. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.as2MessageStructure* | The structure of AS2 Message. One of: PLAIN - No encryption, no signature, SIGNED - No encryption, signature, ENCRYPTED - Encryption, no signature, ENCRYPTED_SIGNED - Encryption, signature One of: [PLAIN] [SIGNED] [ENCRYPTED] [SIGNED_ENCRYPTED] [PLAIN_COMPRESSED] [SIGNED_COMPRESSED] [ENCRYPTED_COMPRESSED] [ENCRYPTED_COMPRESSED_SIGNED] | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.as2To* | The value of the AS2To header of AS2 message. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.as2Version* | The version of the AS2 protocol. One of: [1.0] [1.1] | "1.1" | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.clientFqdn* | The Client Fully Qualified Domain Name (FQDN). Used in message ids sent by endpoint. | "camel.apache.org" | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.compressionAlgorithm* | The algorithm used to compress EDI message. One of: [ZLIB] | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.decryptingPrivateKey* | The key used to encrypt the EDI message. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.dispositionNotificationTo* | The value of the Disposition-Notification-To header. Assigning a value to this parameter requests a message disposition notification (MDN) for the AS2 message. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.ediMessageTransferEncoding* | The transfer encoding of EDI message. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.ediMessageType* | The content type of EDI message. One of application/edifact, application/edi-x12, application/edi-consent | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.encryptingAlgorithm* | The algorithm used to encrypt EDI message. One of: [AES128_CBC] [AES192_CBC] [AES256_CBC] [AES128_CCM] [AES192_CCM] [AES256_CCM] [AES128_GCM] [AES192_GCM] [AES256_GCM] [CAMELLIA128_CBC] [CAMELLIA192_CBC] [CAMELLIA256_CBC] [CAST5_CBC] [DES_CBC] [DES_EDE3_CBC] [GOST28147_GCFB] [IDEA_CBC] [RC2_CBC] [RC4] [SEED_CBC] | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.encryptingCertificateChain* | The chain of certificates used to encrypt EDI message. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.from* | The value of the From header of AS2 message. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.inBody* | Sets the name of a parameter to be passed in the exchange In Body | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.mdnMessageTemplate* | The template used to format MDN message | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.requestUri* | The request URI of EDI message. | "/" | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.server* | The value included in the Server message header identifying the AS2 Server. | "Camel AS2 Server Endpoint" | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.serverFqdn* | The Server Fully Qualified Domain Name (FQDN). Used in message ids sent by endpoint. | "camel.apache.org" | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.serverPortNumber* | The port number of server. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.signedReceiptMicAlgorithms* | The list of algorithms, in order of preference, requested to generate a message integrity check (MIC) returned in message dispostion notification (MDN) | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.signingAlgorithm* | The algorithm used to sign EDI message. One of: [SHA3_224WITHRSA] [SHA3_256WITHRSA] [SHA3_384withRSA] [SHA3_512WITHRSA] [MD5WITHRSA] [SHA1WITHRSA] [MD2WITHRSA] [SHA224WITHRSA] [SHA256WITHRSA] [SHA384WITHRSA] [SHA512WITHRSA] [RIPEMD128WITHRSA] [RIPEMD160WITHRSA] [RIPEMD256WITHRSA] [SHA224WITHDSA] [SHA256WITHDSA] [SHA384WITHDSA] [SHA512WITHDSA] [SHA3_224WITHDSA] [SHA3_256WITHDSA] [SHA3_384WITHDSA] [SHA3_512WITHDSA] [SHA1WITHDSA] [SHA3_224WITHECDSA [...]
+| *camel.sink.endpoint.signingCertificateChain* | The chain of certificates used to sign EDI message. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.signingPrivateKey* | The key used to sign the EDI message. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.subject* | The value of Subject header of AS2 message. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.targetHostname* | The host name (IP or DNS name) of target host. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.targetPortNumber* | The port number of target host. -1 indicates the scheme default port. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.userAgent* | The value included in the User-Agent message header identifying the AS2 user agent. | "Camel AS2 Client Endpoint" | ConfigDef.Importance.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 cre [...]
+| *camel.sink.endpoint.basicPropertyBinding* | Whether the endpoint should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.synchronous* | Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). | false | ConfigDef.Importance.MEDIUM
+| *camel.component.as2.configuration* | To use the shared configuration | null | ConfigDef.Importance.MEDIUM
+| *camel.component.as2.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 cre [...]
+| *camel.component.as2.basicPropertyBinding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+|===
+
+
+// kafka-connector options: END
diff --git a/docs/modules/ROOT/pages/connectors/camel-as2-kafka-source-connector.adoc b/docs/modules/ROOT/pages/connectors/camel-as2-kafka-source-connector.adoc
new file mode 100644
index 0000000..390ac87
--- /dev/null
+++ b/docs/modules/ROOT/pages/connectors/camel-as2-kafka-source-connector.adoc
@@ -0,0 +1,76 @@
+// kafka-connector options: START
+== camel-as2-kafka-connector source configuration
+
+When using camel-as2-kafka-connector as source 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-as2-kafka-connector</artifactId>
+ <version>x.x.x</version>
+ <!-- use the same version as your Camel Kafka connector version -->
+</dependency>
+----
+
+
+[width="100%",cols="2,5,^1,2",options="header"]
+|===
+| Name | Description | Default | Priority
+| *camel.source.path.apiName* | What kind of operation to perform One of: [CLIENT] [SERVER] | null | ConfigDef.Importance.HIGH
+| *camel.source.path.methodName* | What sub operation to use for the selected operation | null | ConfigDef.Importance.HIGH
+| *camel.source.endpoint.as2From* | The value of the AS2From header of AS2 message. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.as2MessageStructure* | The structure of AS2 Message. One of: PLAIN - No encryption, no signature, SIGNED - No encryption, signature, ENCRYPTED - Encryption, no signature, ENCRYPTED_SIGNED - Encryption, signature One of: [PLAIN] [SIGNED] [ENCRYPTED] [SIGNED_ENCRYPTED] [PLAIN_COMPRESSED] [SIGNED_COMPRESSED] [ENCRYPTED_COMPRESSED] [ENCRYPTED_COMPRESSED_SIGNED] | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.as2To* | The value of the AS2To header of AS2 message. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.as2Version* | The version of the AS2 protocol. One of: [1.0] [1.1] | "1.1" | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.clientFqdn* | The Client Fully Qualified Domain Name (FQDN). Used in message ids sent by endpoint. | "camel.apache.org" | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.compressionAlgorithm* | The algorithm used to compress EDI message. One of: [ZLIB] | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.decryptingPrivateKey* | The key used to encrypt the EDI message. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.dispositionNotificationTo* | The value of the Disposition-Notification-To header. Assigning a value to this parameter requests a message disposition notification (MDN) for the AS2 message. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.ediMessageTransferEncoding* | The transfer encoding of EDI message. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.ediMessageType* | The content type of EDI message. One of application/edifact, application/edi-x12, application/edi-consent | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.encryptingAlgorithm* | The algorithm used to encrypt EDI message. One of: [AES128_CBC] [AES192_CBC] [AES256_CBC] [AES128_CCM] [AES192_CCM] [AES256_CCM] [AES128_GCM] [AES192_GCM] [AES256_GCM] [CAMELLIA128_CBC] [CAMELLIA192_CBC] [CAMELLIA256_CBC] [CAST5_CBC] [DES_CBC] [DES_EDE3_CBC] [GOST28147_GCFB] [IDEA_CBC] [RC2_CBC] [RC4] [SEED_CBC] | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.encryptingCertificateChain* | The chain of certificates used to encrypt EDI message. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.from* | The value of the From header of AS2 message. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.inBody* | Sets the name of a parameter to be passed in the exchange In Body | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.mdnMessageTemplate* | The template used to format MDN message | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.requestUri* | The request URI of EDI message. | "/" | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.server* | The value included in the Server message header identifying the AS2 Server. | "Camel AS2 Server Endpoint" | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.serverFqdn* | The Server Fully Qualified Domain Name (FQDN). Used in message ids sent by endpoint. | "camel.apache.org" | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.serverPortNumber* | The port number of server. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.signedReceiptMicAlgorithms* | The list of algorithms, in order of preference, requested to generate a message integrity check (MIC) returned in message dispostion notification (MDN) | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.signingAlgorithm* | The algorithm used to sign EDI message. One of: [SHA3_224WITHRSA] [SHA3_256WITHRSA] [SHA3_384withRSA] [SHA3_512WITHRSA] [MD5WITHRSA] [SHA1WITHRSA] [MD2WITHRSA] [SHA224WITHRSA] [SHA256WITHRSA] [SHA384WITHRSA] [SHA512WITHRSA] [RIPEMD128WITHRSA] [RIPEMD160WITHRSA] [RIPEMD256WITHRSA] [SHA224WITHDSA] [SHA256WITHDSA] [SHA384WITHDSA] [SHA512WITHDSA] [SHA3_224WITHDSA] [SHA3_256WITHDSA] [SHA3_384WITHDSA] [SHA3_512WITHDSA] [SHA1WITHDSA] [SHA3_224WITHECD [...]
+| *camel.source.endpoint.signingCertificateChain* | The chain of certificates used to sign EDI message. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.signingPrivateKey* | The key used to sign the EDI message. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.subject* | The value of Subject header of AS2 message. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.targetHostname* | The host name (IP or DNS name) of target host. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.targetPortNumber* | The port number of target host. -1 indicates the scheme default port. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.userAgent* | The value included in the User-Agent message header identifying the AS2 user agent. | "Camel AS2 Client Endpoint" | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.bridgeErrorHandler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.sendEmptyMessageWhenIdle* | If the polling consumer did not poll any files, you can enable this option to send an empty message (no body) instead. | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.exceptionHandler* | To let the consumer use a custom ExceptionHandler. Notice if the option bridgeErrorHandler is enabled then this option is not in use. By default the consumer will deal with exceptions, that will be logged at WARN or ERROR level and ignored. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.exchangePattern* | Sets the exchange pattern when the consumer creates an exchange. One of: [InOnly] [InOut] [InOptionalOut] | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.pollStrategy* | A pluggable org.apache.camel.PollingConsumerPollingStrategy allowing you to provide your custom implementation to control error handling usually occurred during the poll operation before an Exchange have been created and being routed in Camel. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.basicPropertyBinding* | Whether the endpoint should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.synchronous* | Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.backoffErrorThreshold* | The number of subsequent error polls (failed due some error) that should happen before the backoffMultipler should kick-in. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.backoffIdleThreshold* | The number of subsequent idle polls that should happen before the backoffMultipler should kick-in. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.backoffMultiplier* | To let the scheduled polling consumer backoff if there has been a number of subsequent idles/errors in a row. The multiplier is then the number of polls that will be skipped before the next actual attempt is happening again. When this option is in use then backoffIdleThreshold and/or backoffErrorThreshold must also be configured. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.delay* | Milliseconds before the next poll. You can also specify time values using units, such as 60s (60 seconds), 5m30s (5 minutes and 30 seconds), and 1h (1 hour). | 500L | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.greedy* | If greedy is enabled, then the ScheduledPollConsumer will run immediately again, if the previous run polled 1 or more messages. | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.initialDelay* | Milliseconds before the first poll starts. You can also specify time values using units, such as 60s (60 seconds), 5m30s (5 minutes and 30 seconds), and 1h (1 hour). | 1000L | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.repeatCount* | Specifies a maximum limit of number of fires. So if you set it to 1, the scheduler will only fire once. If you set it to 5, it will only fire five times. A value of zero or negative means fire forever. | 0L | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.runLoggingLevel* | The consumer logs a start/complete log line when it polls. This option allows you to configure the logging level for that. One of: [TRACE] [DEBUG] [INFO] [WARN] [ERROR] [OFF] | "TRACE" | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.scheduledExecutorService* | Allows for configuring a custom/shared thread pool to use for the consumer. By default each consumer has its own single threaded thread pool. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.scheduler* | To use a cron scheduler from either camel-spring or camel-quartz component One of: [none] [spring] [quartz] | "none" | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.schedulerProperties* | To configure additional properties when using a custom scheduler or any of the Quartz, Spring based scheduler. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.startScheduler* | Whether the scheduler should be auto started. | true | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.timeUnit* | Time unit for initialDelay and delay options. One of: [NANOSECONDS] [MICROSECONDS] [MILLISECONDS] [SECONDS] [MINUTES] [HOURS] [DAYS] | "MILLISECONDS" | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.useFixedDelay* | Controls if fixed delay or fixed rate is used. See ScheduledExecutorService in JDK for details. | true | ConfigDef.Importance.MEDIUM
+| *camel.component.as2.configuration* | To use the shared configuration | null | ConfigDef.Importance.MEDIUM
+| *camel.component.as2.bridgeErrorHandler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | ConfigDef.Importance.MEDIUM
+| *camel.component.as2.basicPropertyBinding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+|===
+
+
+// kafka-connector options: END
diff --git a/docs/modules/ROOT/pages/connectors/camel-asterisk-kafka-sink-connector.adoc b/docs/modules/ROOT/pages/connectors/camel-asterisk-kafka-sink-connector.adoc
new file mode 100644
index 0000000..e522a5b
--- /dev/null
+++ b/docs/modules/ROOT/pages/connectors/camel-asterisk-kafka-sink-connector.adoc
@@ -0,0 +1,33 @@
+// kafka-connector options: START
+== camel-asterisk-kafka-connector source configuration
+
+When using camel-asterisk-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-asterisk-kafka-connector</artifactId>
+ <version>x.x.x</version>
+ <!-- use the same version as your Camel Kafka connector version -->
+</dependency>
+----
+
+
+[width="100%",cols="2,5,^1,2",options="header"]
+|===
+| Name | Description | Default | Priority
+| *camel.sink.path.name* | Name of component | null | ConfigDef.Importance.HIGH
+| *camel.sink.endpoint.hostname* | The hostname of the asterisk server | null | ConfigDef.Importance.HIGH
+| *camel.sink.endpoint.password* | Login password | null | ConfigDef.Importance.HIGH
+| *camel.sink.endpoint.username* | Login username | null | ConfigDef.Importance.HIGH
+| *camel.sink.endpoint.action* | What action to perform such as getting queue status, sip peers or extension state. One of: [QUEUE_STATUS] [SIP_PEERS] [EXTENSION_STATE] | null | ConfigDef.Importance.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 cre [...]
+| *camel.sink.endpoint.basicPropertyBinding* | Whether the endpoint should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.synchronous* | Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). | false | ConfigDef.Importance.MEDIUM
+| *camel.component.asterisk.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 the [...]
+| *camel.component.asterisk.basicPropertyBinding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+|===
+
+
+// kafka-connector options: END
diff --git a/docs/modules/ROOT/pages/connectors/camel-asterisk-kafka-source-connector.adoc b/docs/modules/ROOT/pages/connectors/camel-asterisk-kafka-source-connector.adoc
new file mode 100644
index 0000000..92eefe1
--- /dev/null
+++ b/docs/modules/ROOT/pages/connectors/camel-asterisk-kafka-source-connector.adoc
@@ -0,0 +1,34 @@
+// kafka-connector options: START
+== camel-asterisk-kafka-connector source configuration
+
+When using camel-asterisk-kafka-connector as source 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-asterisk-kafka-connector</artifactId>
+ <version>x.x.x</version>
+ <!-- use the same version as your Camel Kafka connector version -->
+</dependency>
+----
+
+
+[width="100%",cols="2,5,^1,2",options="header"]
+|===
+| Name | Description | Default | Priority
+| *camel.source.path.name* | Name of component | null | ConfigDef.Importance.HIGH
+| *camel.source.endpoint.hostname* | The hostname of the asterisk server | null | ConfigDef.Importance.HIGH
+| *camel.source.endpoint.password* | Login password | null | ConfigDef.Importance.HIGH
+| *camel.source.endpoint.username* | Login username | null | ConfigDef.Importance.HIGH
+| *camel.source.endpoint.bridgeErrorHandler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.exceptionHandler* | To let the consumer use a custom ExceptionHandler. Notice if the option bridgeErrorHandler is enabled then this option is not in use. By default the consumer will deal with exceptions, that will be logged at WARN or ERROR level and ignored. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.exchangePattern* | Sets the exchange pattern when the consumer creates an exchange. One of: [InOnly] [InOut] [InOptionalOut] | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.basicPropertyBinding* | Whether the endpoint should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.synchronous* | Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). | false | ConfigDef.Importance.MEDIUM
+| *camel.component.asterisk.bridgeErrorHandler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | ConfigDef.Importance.MEDIUM
+| *camel.component.asterisk.basicPropertyBinding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+|===
+
+
+// kafka-connector options: END
diff --git a/docs/modules/ROOT/pages/connectors/camel-atmos-kafka-sink-connector.adoc b/docs/modules/ROOT/pages/connectors/camel-atmos-kafka-sink-connector.adoc
new file mode 100644
index 0000000..cb12d28
--- /dev/null
+++ b/docs/modules/ROOT/pages/connectors/camel-atmos-kafka-sink-connector.adoc
@@ -0,0 +1,42 @@
+// kafka-connector options: START
+== camel-atmos-kafka-connector source configuration
+
+When using camel-atmos-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-atmos-kafka-connector</artifactId>
+ <version>x.x.x</version>
+ <!-- use the same version as your Camel Kafka connector version -->
+</dependency>
+----
+
+
+[width="100%",cols="2,5,^1,2",options="header"]
+|===
+| Name | Description | Default | Priority
+| *camel.sink.path.name* | Atmos name | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.path.operation* | Operation to perform One of: [put] [del] [search] [get] [move] | null | ConfigDef.Importance.HIGH
+| *camel.sink.endpoint.localPath* | Local path to put files | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.newRemotePath* | New path on Atmos when moving files | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.query* | Search query on Atmos | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.remotePath* | Where to put files on Atmos | null | ConfigDef.Importance.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 cre [...]
+| *camel.sink.endpoint.basicPropertyBinding* | Whether the endpoint should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.synchronous* | Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). | false | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.uri* | Atomos server uri | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.fullTokenId* | Atmos client fullTokenId | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.secretKey* | The secret key to pass to the Atmos client (should be base64 encoded) | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.sslValidation* | Atmos SSL validation | false | ConfigDef.Importance.MEDIUM
+| *camel.component.atmos.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 c [...]
+| *camel.component.atmos.basicPropertyBinding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+| *camel.component.atmos.uri* | The URI of the server for the Atmos client to connect to | null | ConfigDef.Importance.MEDIUM
+| *camel.component.atmos.fullTokenId* | The token id to pass to the Atmos client | null | ConfigDef.Importance.MEDIUM
+| *camel.component.atmos.secretKey* | The secret key to pass to the Atmos client (should be base64 encoded) | null | ConfigDef.Importance.MEDIUM
+| *camel.component.atmos.sslValidation* | Whether the Atmos client should perform SSL validation | false | ConfigDef.Importance.MEDIUM
+|===
+
+
+// kafka-connector options: END
diff --git a/docs/modules/ROOT/pages/connectors/camel-atmos-kafka-source-connector.adoc b/docs/modules/ROOT/pages/connectors/camel-atmos-kafka-source-connector.adoc
new file mode 100644
index 0000000..8f9ae44
--- /dev/null
+++ b/docs/modules/ROOT/pages/connectors/camel-atmos-kafka-source-connector.adoc
@@ -0,0 +1,44 @@
+// kafka-connector options: START
+== camel-atmos-kafka-connector source configuration
+
+When using camel-atmos-kafka-connector as source 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-atmos-kafka-connector</artifactId>
+ <version>x.x.x</version>
+ <!-- use the same version as your Camel Kafka connector version -->
+</dependency>
+----
+
+
+[width="100%",cols="2,5,^1,2",options="header"]
+|===
+| Name | Description | Default | Priority
+| *camel.source.path.name* | Atmos name | null | ConfigDef.Importance.MEDIUM
+| *camel.source.path.operation* | Operation to perform One of: [put] [del] [search] [get] [move] | null | ConfigDef.Importance.HIGH
+| *camel.source.endpoint.localPath* | Local path to put files | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.newRemotePath* | New path on Atmos when moving files | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.query* | Search query on Atmos | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.remotePath* | Where to put files on Atmos | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.bridgeErrorHandler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.exceptionHandler* | To let the consumer use a custom ExceptionHandler. Notice if the option bridgeErrorHandler is enabled then this option is not in use. By default the consumer will deal with exceptions, that will be logged at WARN or ERROR level and ignored. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.exchangePattern* | Sets the exchange pattern when the consumer creates an exchange. One of: [InOnly] [InOut] [InOptionalOut] | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.basicPropertyBinding* | Whether the endpoint should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.synchronous* | Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.uri* | Atomos server uri | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.fullTokenId* | Atmos client fullTokenId | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.secretKey* | The secret key to pass to the Atmos client (should be base64 encoded) | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.sslValidation* | Atmos SSL validation | false | ConfigDef.Importance.MEDIUM
+| *camel.component.atmos.bridgeErrorHandler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | ConfigDef.Importance.MEDIUM
+| *camel.component.atmos.basicPropertyBinding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+| *camel.component.atmos.uri* | The URI of the server for the Atmos client to connect to | null | ConfigDef.Importance.MEDIUM
+| *camel.component.atmos.fullTokenId* | The token id to pass to the Atmos client | null | ConfigDef.Importance.MEDIUM
+| *camel.component.atmos.secretKey* | The secret key to pass to the Atmos client (should be base64 encoded) | null | ConfigDef.Importance.MEDIUM
+| *camel.component.atmos.sslValidation* | Whether the Atmos client should perform SSL validation | false | ConfigDef.Importance.MEDIUM
+|===
+
+
+// kafka-connector options: END
diff --git a/docs/modules/ROOT/pages/connectors/camel-atmosphere-websocket-kafka-sink-connector.adoc b/docs/modules/ROOT/pages/connectors/camel-atmosphere-websocket-kafka-sink-connector.adoc
new file mode 100644
index 0000000..7d0c612
--- /dev/null
+++ b/docs/modules/ROOT/pages/connectors/camel-atmosphere-websocket-kafka-sink-connector.adoc
@@ -0,0 +1,56 @@
+// kafka-connector options: START
+== camel-atmosphere-websocket-kafka-connector source configuration
+
+When using camel-atmosphere-websocket-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-atmosphere-websocket-kafka-connector</artifactId>
+ <version>x.x.x</version>
+ <!-- use the same version as your Camel Kafka connector version -->
+</dependency>
+----
+
+
+[width="100%",cols="2,5,^1,2",options="header"]
+|===
+| Name | Description | Default | Priority
+| *camel.sink.path.servicePath* | Name of websocket endpoint | null | ConfigDef.Importance.HIGH
+| *camel.sink.endpoint.chunked* | If this option is false the Servlet will disable the HTTP streaming and set the content-length header on the response | true | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.disableStreamCache* | Determines whether or not the raw input stream from Servlet is cached or not (Camel will read the stream into a in memory/overflow to file, Stream caching) cache. By default Camel will cache the Servlet input stream to support reading it multiple times to ensure it Camel can retrieve all data from the stream. However you can set this option to true when you for example need to access the raw stream, such as streaming it directly to a file or o [...]
+| *camel.sink.endpoint.headerFilterStrategy* | To use a custom HeaderFilterStrategy to filter header to and from Camel message. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.sendToAll* | Whether to send to all (broadcast) or send to a single receiver. | false | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.transferException* | If enabled and an Exchange failed processing on the consumer side, and if the caused Exception was send back serialized in the response as a application/x-java-serialized-object content type. On the producer side the exception will be deserialized and thrown as is, instead of the HttpOperationFailedException. The caused exception is required to be serialized. This is by default turned off. If you enable this then be aware that Java will deseria [...]
+| *camel.sink.endpoint.useStreaming* | To enable streaming to send data as multiple text fragments. | false | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.httpBinding* | To use a custom HttpBinding to control the mapping between Camel message and HttpClient. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.bridgeEndpoint* | If the option is true, HttpProducer will ignore the Exchange.HTTP_URI header, and use the endpoint's URI for request. You may also set the option throwExceptionOnFailure to be false to let the HttpProducer send all the fault response back. | false | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.connectionClose* | Specifies whether a Connection Close header must be added to HTTP Request. By default connectionClose is false. | false | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.copyHeaders* | If this option is true then IN exchange headers will be copied to OUT exchange headers according to copy strategy. Setting this to false, allows to only include the headers from the HTTP response (not propagating IN headers). | true | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.httpMethod* | Configure the HTTP method to use. The HttpMethod header cannot override this option if set. One of: [GET] [POST] [PUT] [DELETE] [HEAD] [OPTIONS] [TRACE] [PATCH] | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.ignoreResponseBody* | If this option is true, The http producer won't read response body and cache the input stream | false | ConfigDef.Importance.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 cre [...]
+| *camel.sink.endpoint.preserveHostHeader* | If the option is true, HttpProducer will set the Host header to the value contained in the current exchange Host header, useful in reverse proxy applications where you want the Host header received by the downstream server to reflect the URL called by the upstream client, this allows applications which use the Host header to generate accurate URL's for a proxied service | false | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.throwExceptionOnFailure* | Option to disable throwing the HttpOperationFailedException in case of failed responses from the remote server. This allows you to get all responses regardless of the HTTP status code. | true | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.cookieHandler* | Configure a cookie handler to maintain a HTTP session | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.okStatusCodeRange* | The status codes which are considered a success response. The values are inclusive. Multiple ranges can be defined, separated by comma, e.g. 200-204,209,301-304. Each range must be a single number or from-to with the dash included. | "200-299" | ConfigDef.Importance.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 | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.mapHttpMessageBody* | If this option is true then IN exchange Body of the exchange will be mapped to HTTP body. Setting this to false will avoid the HTTP mapping. | true | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.mapHttpMessageFormUrlEncodedBody* | If this option is true then IN exchange Form Encoded body of the exchange will be mapped to HTTP. Setting this to false will avoid the HTTP Form Encoded body mapping. | true | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.mapHttpMessageHeaders* | If this option is true then IN exchange Headers of the exchange will be mapped to HTTP headers. Setting this to false will avoid the HTTP Headers mapping. | true | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.synchronous* | Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). | false | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.proxyAuthScheme* | Proxy authentication scheme to use One of: [http] [https] | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.proxyHost* | Proxy hostname to use | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.proxyPort* | Proxy port to use | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.authHost* | Authentication host to use with NTML | null | ConfigDef.Importance.MEDIUM
+| *camel.component.atmosphere-websocket.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 p [...]
+| *camel.component.atmosphere-websocket.allowJavaSerializedObject* | Whether to allow java serialization when a request uses context-type=application/x-java-serialized-object. This is by default turned off. If you enable this then be aware that Java will deserialize the incoming data from the request to Java and that can be a potential security risk. | false | ConfigDef.Importance.MEDIUM
+| *camel.component.atmosphere-websocket.basicPropertyBinding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+| *camel.component.atmosphere-websocket.httpBinding* | To use a custom HttpBinding to control the mapping between Camel message and HttpClient. | null | ConfigDef.Importance.MEDIUM
+| *camel.component.atmosphere-websocket.httpConfiguration* | To use the shared HttpConfiguration as base configuration. | null | ConfigDef.Importance.MEDIUM
+| *camel.component.atmosphere-websocket.headerFilterStrategy* | To use a custom org.apache.camel.spi.HeaderFilterStrategy to filter header to and from Camel message. | null | ConfigDef.Importance.MEDIUM
+|===
+
+
+// kafka-connector options: END
diff --git a/docs/modules/ROOT/pages/connectors/camel-atmosphere-websocket-kafka-source-connector.adoc b/docs/modules/ROOT/pages/connectors/camel-atmosphere-websocket-kafka-source-connector.adoc
new file mode 100644
index 0000000..4a2d4af
--- /dev/null
+++ b/docs/modules/ROOT/pages/connectors/camel-atmosphere-websocket-kafka-source-connector.adoc
@@ -0,0 +1,60 @@
+// kafka-connector options: START
+== camel-atmosphere-websocket-kafka-connector source configuration
+
+When using camel-atmosphere-websocket-kafka-connector as source 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-atmosphere-websocket-kafka-connector</artifactId>
+ <version>x.x.x</version>
+ <!-- use the same version as your Camel Kafka connector version -->
+</dependency>
+----
+
+
+[width="100%",cols="2,5,^1,2",options="header"]
+|===
+| Name | Description | Default | Priority
+| *camel.source.path.servicePath* | Name of websocket endpoint | null | ConfigDef.Importance.HIGH
+| *camel.source.endpoint.chunked* | If this option is false the Servlet will disable the HTTP streaming and set the content-length header on the response | true | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.disableStreamCache* | Determines whether or not the raw input stream from Servlet is cached or not (Camel will read the stream into a in memory/overflow to file, Stream caching) cache. By default Camel will cache the Servlet input stream to support reading it multiple times to ensure it Camel can retrieve all data from the stream. However you can set this option to true when you for example need to access the raw stream, such as streaming it directly to a file or [...]
+| *camel.source.endpoint.headerFilterStrategy* | To use a custom HeaderFilterStrategy to filter header to and from Camel message. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.sendToAll* | Whether to send to all (broadcast) or send to a single receiver. | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.transferException* | If enabled and an Exchange failed processing on the consumer side, and if the caused Exception was send back serialized in the response as a application/x-java-serialized-object content type. On the producer side the exception will be deserialized and thrown as is, instead of the HttpOperationFailedException. The caused exception is required to be serialized. This is by default turned off. If you enable this then be aware that Java will deser [...]
+| *camel.source.endpoint.useStreaming* | To enable streaming to send data as multiple text fragments. | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.httpBinding* | To use a custom HttpBinding to control the mapping between Camel message and HttpClient. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.async* | Configure the consumer to work in async mode | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.bridgeErrorHandler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.httpMethodRestrict* | Used to only allow consuming if the HttpMethod matches, such as GET/POST/PUT etc. Multiple methods can be specified separated by comma. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.matchOnUriPrefix* | Whether or not the consumer should try to find a target consumer by matching the URI prefix if no exact match is found. | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.muteException* | If enabled and an Exchange failed processing on the consumer side the response's body won't contain the exception's stack trace. | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.responseBufferSize* | To use a custom buffer size on the javax.servlet.ServletResponse. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.servletName* | Name of the servlet to use | "CamelServlet" | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.attachmentMultipartBinding* | Whether to automatic bind multipart/form-data as attachments on the Camel Exchange. The options attachmentMultipartBinding=true and disableStreamCache=false cannot work together. Remove disableStreamCache to use AttachmentMultipartBinding. This is turn off by default as this may require servlet specific configuration to enable this when using Servlet's. | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.eagerCheckContentAvailable* | Whether to eager check whether the HTTP requests has content if the content-length header is 0 or not present. This can be turned on in case HTTP clients do not send streamed data. | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.exceptionHandler* | To let the consumer use a custom ExceptionHandler. Notice if the option bridgeErrorHandler is enabled then this option is not in use. By default the consumer will deal with exceptions, that will be logged at WARN or ERROR level and ignored. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.exchangePattern* | Sets the exchange pattern when the consumer creates an exchange. One of: [InOnly] [InOut] [InOptionalOut] | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.fileNameExtWhitelist* | Whitelist of accepted filename extensions for accepting uploaded files. Multiple extensions can be separated by comma, such as txt,xml. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.optionsEnabled* | Specifies whether to enable HTTP OPTIONS for this Servlet consumer. By default OPTIONS is turned off. | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.traceEnabled* | Specifies whether to enable HTTP TRACE for this Servlet consumer. By default TRACE is turned off. | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.basicPropertyBinding* | Whether the endpoint should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.mapHttpMessageBody* | If this option is true then IN exchange Body of the exchange will be mapped to HTTP body. Setting this to false will avoid the HTTP mapping. | true | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.mapHttpMessageFormUrlEncodedBody* | If this option is true then IN exchange Form Encoded body of the exchange will be mapped to HTTP. Setting this to false will avoid the HTTP Form Encoded body mapping. | true | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.mapHttpMessageHeaders* | If this option is true then IN exchange Headers of the exchange will be mapped to HTTP headers. Setting this to false will avoid the HTTP Headers mapping. | true | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.synchronous* | Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). | false | ConfigDef.Importance.MEDIUM
+| *camel.component.atmosphere-websocket.bridgeErrorHandler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | ConfigDef.I [...]
+| *camel.component.atmosphere-websocket.servletName* | Default name of servlet to use. The default name is CamelServlet. | "CamelServlet" | ConfigDef.Importance.MEDIUM
+| *camel.component.atmosphere-websocket.attachmentMultipartBinding* | Whether to automatic bind multipart/form-data as attachments on the Camel Exchange. The options attachmentMultipartBinding=true and disableStreamCache=false cannot work together. Remove disableStreamCache to use AttachmentMultipartBinding. This is turn off by default as this may require servlet specific configuration to enable this when using Servlet's. | false | ConfigDef.Importance.MEDIUM
+| *camel.component.atmosphere-websocket.fileNameExtWhitelist* | Whitelist of accepted filename extensions for accepting uploaded files. Multiple extensions can be separated by comma, such as txt,xml. | null | ConfigDef.Importance.MEDIUM
+| *camel.component.atmosphere-websocket.httpRegistry* | To use a custom org.apache.camel.component.servlet.HttpRegistry. | null | ConfigDef.Importance.MEDIUM
+| *camel.component.atmosphere-websocket.allowJavaSerializedObject* | Whether to allow java serialization when a request uses context-type=application/x-java-serialized-object. This is by default turned off. If you enable this then be aware that Java will deserialize the incoming data from the request to Java and that can be a potential security risk. | false | ConfigDef.Importance.MEDIUM
+| *camel.component.atmosphere-websocket.basicPropertyBinding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+| *camel.component.atmosphere-websocket.httpBinding* | To use a custom HttpBinding to control the mapping between Camel message and HttpClient. | null | ConfigDef.Importance.MEDIUM
+| *camel.component.atmosphere-websocket.httpConfiguration* | To use the shared HttpConfiguration as base configuration. | null | ConfigDef.Importance.MEDIUM
+| *camel.component.atmosphere-websocket.headerFilterStrategy* | To use a custom org.apache.camel.spi.HeaderFilterStrategy to filter header to and from Camel message. | null | ConfigDef.Importance.MEDIUM
+|===
+
+
+// kafka-connector options: END
diff --git a/docs/modules/ROOT/pages/connectors/camel-atom-kafka-source-connector.adoc b/docs/modules/ROOT/pages/connectors/camel-atom-kafka-source-connector.adoc
new file mode 100644
index 0000000..c45f3bf
--- /dev/null
+++ b/docs/modules/ROOT/pages/connectors/camel-atom-kafka-source-connector.adoc
@@ -0,0 +1,55 @@
+// kafka-connector options: START
+== camel-atom-kafka-connector source configuration
+
+When using camel-atom-kafka-connector as source 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-atom-kafka-connector</artifactId>
+ <version>x.x.x</version>
+ <!-- use the same version as your Camel Kafka connector version -->
+</dependency>
+----
+
+
+[width="100%",cols="2,5,^1,2",options="header"]
+|===
+| Name | Description | Default | Priority
+| *camel.source.path.feedUri* | The URI to the feed to poll. | null | ConfigDef.Importance.HIGH
+| *camel.source.endpoint.bridgeErrorHandler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.feedHeader* | Sets whether to add the feed object as a header. | true | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.filter* | Sets whether to use filtering or not of the entries. | true | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.lastUpdate* | Sets the timestamp to be used for filtering entries from the atom feeds. This options is only in conjunction with the splitEntries. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.password* | Sets the password to be used for basic authentication when polling from a HTTP feed. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.sendEmptyMessageWhenIdle* | If the polling consumer did not poll any files, you can enable this option to send an empty message (no body) instead. | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.sortEntries* | Sets whether to sort entries by published date. Only works when splitEntries = true. | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.splitEntries* | Sets whether or not entries should be sent individually or whether the entire feed should be sent as a single message | true | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.throttleEntries* | Sets whether all entries identified in a single feed poll should be delivered immediately. If true, only one entry is processed per consumer.delay. Only applicable when splitEntries = true. | true | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.username* | Sets the username to be used for basic authentication when polling from a HTTP feed. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.exceptionHandler* | To let the consumer use a custom ExceptionHandler. Notice if the option bridgeErrorHandler is enabled then this option is not in use. By default the consumer will deal with exceptions, that will be logged at WARN or ERROR level and ignored. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.exchangePattern* | Sets the exchange pattern when the consumer creates an exchange. One of: [InOnly] [InOut] [InOptionalOut] | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.pollStrategy* | A pluggable org.apache.camel.PollingConsumerPollingStrategy allowing you to provide your custom implementation to control error handling usually occurred during the poll operation before an Exchange have been created and being routed in Camel. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.basicPropertyBinding* | Whether the endpoint should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.synchronous* | Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.backoffErrorThreshold* | The number of subsequent error polls (failed due some error) that should happen before the backoffMultipler should kick-in. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.backoffIdleThreshold* | The number of subsequent idle polls that should happen before the backoffMultipler should kick-in. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.backoffMultiplier* | To let the scheduled polling consumer backoff if there has been a number of subsequent idles/errors in a row. The multiplier is then the number of polls that will be skipped before the next actual attempt is happening again. When this option is in use then backoffIdleThreshold and/or backoffErrorThreshold must also be configured. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.delay* | Milliseconds before the next poll. You can also specify time values using units, such as 60s (60 seconds), 5m30s (5 minutes and 30 seconds), and 1h (1 hour). | 500L | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.greedy* | If greedy is enabled, then the ScheduledPollConsumer will run immediately again, if the previous run polled 1 or more messages. | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.initialDelay* | Milliseconds before the first poll starts. You can also specify time values using units, such as 60s (60 seconds), 5m30s (5 minutes and 30 seconds), and 1h (1 hour). | 1000L | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.repeatCount* | Specifies a maximum limit of number of fires. So if you set it to 1, the scheduler will only fire once. If you set it to 5, it will only fire five times. A value of zero or negative means fire forever. | 0L | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.runLoggingLevel* | The consumer logs a start/complete log line when it polls. This option allows you to configure the logging level for that. One of: [TRACE] [DEBUG] [INFO] [WARN] [ERROR] [OFF] | "TRACE" | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.scheduledExecutorService* | Allows for configuring a custom/shared thread pool to use for the consumer. By default each consumer has its own single threaded thread pool. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.scheduler* | To use a cron scheduler from either camel-spring or camel-quartz component One of: [none] [spring] [quartz] | "none" | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.schedulerProperties* | To configure additional properties when using a custom scheduler or any of the Quartz, Spring based scheduler. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.startScheduler* | Whether the scheduler should be auto started. | true | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.timeUnit* | Time unit for initialDelay and delay options. One of: [NANOSECONDS] [MICROSECONDS] [MILLISECONDS] [SECONDS] [MINUTES] [HOURS] [DAYS] | "MILLISECONDS" | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.useFixedDelay* | Controls if fixed delay or fixed rate is used. See ScheduledExecutorService in JDK for details. | true | ConfigDef.Importance.MEDIUM
+| *camel.component.atom.bridgeErrorHandler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | ConfigDef.Importance.MEDIUM
+| *camel.component.atom.basicPropertyBinding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+|===
+
+
+// kafka-connector options: END
diff --git a/docs/modules/ROOT/pages/connectors/camel-atomix-map-kafka-sink-connector.adoc b/docs/modules/ROOT/pages/connectors/camel-atomix-map-kafka-sink-connector.adoc
new file mode 100644
index 0000000..6f24c73
--- /dev/null
+++ b/docs/modules/ROOT/pages/connectors/camel-atomix-map-kafka-sink-connector.adoc
@@ -0,0 +1,47 @@
+// kafka-connector options: START
+== camel-atomix-map-kafka-connector source configuration
+
+When using camel-atomix-map-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-atomix-map-kafka-connector</artifactId>
+ <version>x.x.x</version>
+ <!-- use the same version as your Camel Kafka connector version -->
+</dependency>
+----
+
+
+[width="100%",cols="2,5,^1,2",options="header"]
+|===
+| Name | Description | Default | Priority
+| *camel.sink.path.resourceName* | The distributed resource name | null | ConfigDef.Importance.HIGH
+| *camel.sink.endpoint.atomix* | The Atomix instance to use | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.configurationUri* | The Atomix configuration uri. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.defaultAction* | The default action. One of: [PUT] [PUT_IF_ABSENT] [GET] [CLEAR] [SIZE] [CONTAINS_KEY] [CONTAINS_VALUE] [IS_EMPTY] [ENTRY_SET] [REMOVE] [REPLACE] [VALUES] | "PUT" | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.key* | The key to use if none is set in the header or to listen for events for a specific key. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.nodes* | The address of the nodes composing the cluster. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.resultHeader* | The header that wil carry the result. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.transportClassName* | The class name (fqn) of the Atomix transport | "io.atomix.catalyst.transport.netty.NettyTransport" | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.ttl* | The resource ttl. | null | ConfigDef.Importance.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 cre [...]
+| *camel.sink.endpoint.basicPropertyBinding* | Whether the endpoint should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.defaultResourceConfig* | The cluster wide default resource configuration. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.defaultResourceOptions* | The local default resource options. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.ephemeral* | Sets if the local member should join groups as PersistentMember or not. If set to ephemeral the local member will receive an auto generated ID thus the local one is ignored. | false | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.readConsistency* | The read consistency level. One of: [ATOMIC] [ATOMIC_LEASE] [SEQUENTIAL] [LOCAL] | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.resourceConfigs* | Cluster wide resources configuration. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.resourceOptions* | Local resources configurations | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.synchronous* | Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). | false | ConfigDef.Importance.MEDIUM
+| *camel.component.atomix-map.atomix* | The shared AtomixClient instance | null | ConfigDef.Importance.MEDIUM
+| *camel.component.atomix-map.configuration* | The shared component configuration | null | ConfigDef.Importance.MEDIUM
+| *camel.component.atomix-map.configurationUri* | The path to the AtomixClient configuration | null | ConfigDef.Importance.MEDIUM
+| *camel.component.atomix-map.nodes* | The nodes the AtomixClient should connect to | null | ConfigDef.Importance.MEDIUM
+| *camel.component.atomix-map.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 t [...]
+| *camel.component.atomix-map.basicPropertyBinding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+|===
+
+
+// kafka-connector options: END
diff --git a/docs/modules/ROOT/pages/connectors/camel-atomix-map-kafka-source-connector.adoc b/docs/modules/ROOT/pages/connectors/camel-atomix-map-kafka-source-connector.adoc
new file mode 100644
index 0000000..c888481
--- /dev/null
+++ b/docs/modules/ROOT/pages/connectors/camel-atomix-map-kafka-source-connector.adoc
@@ -0,0 +1,49 @@
+// kafka-connector options: START
+== camel-atomix-map-kafka-connector source configuration
+
+When using camel-atomix-map-kafka-connector as source 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-atomix-map-kafka-connector</artifactId>
+ <version>x.x.x</version>
+ <!-- use the same version as your Camel Kafka connector version -->
+</dependency>
+----
+
+
+[width="100%",cols="2,5,^1,2",options="header"]
+|===
+| Name | Description | Default | Priority
+| *camel.source.path.resourceName* | The distributed resource name | null | ConfigDef.Importance.HIGH
+| *camel.source.endpoint.atomix* | The Atomix instance to use | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.configurationUri* | The Atomix configuration uri. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.defaultAction* | The default action. One of: [PUT] [PUT_IF_ABSENT] [GET] [CLEAR] [SIZE] [CONTAINS_KEY] [CONTAINS_VALUE] [IS_EMPTY] [ENTRY_SET] [REMOVE] [REPLACE] [VALUES] | "PUT" | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.key* | The key to use if none is set in the header or to listen for events for a specific key. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.nodes* | The address of the nodes composing the cluster. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.resultHeader* | The header that wil carry the result. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.transportClassName* | The class name (fqn) of the Atomix transport | "io.atomix.catalyst.transport.netty.NettyTransport" | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.ttl* | The resource ttl. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.bridgeErrorHandler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.exceptionHandler* | To let the consumer use a custom ExceptionHandler. Notice if the option bridgeErrorHandler is enabled then this option is not in use. By default the consumer will deal with exceptions, that will be logged at WARN or ERROR level and ignored. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.exchangePattern* | Sets the exchange pattern when the consumer creates an exchange. One of: [InOnly] [InOut] [InOptionalOut] | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.basicPropertyBinding* | Whether the endpoint should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.defaultResourceConfig* | The cluster wide default resource configuration. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.defaultResourceOptions* | The local default resource options. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.ephemeral* | Sets if the local member should join groups as PersistentMember or not. If set to ephemeral the local member will receive an auto generated ID thus the local one is ignored. | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.readConsistency* | The read consistency level. One of: [ATOMIC] [ATOMIC_LEASE] [SEQUENTIAL] [LOCAL] | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.resourceConfigs* | Cluster wide resources configuration. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.resourceOptions* | Local resources configurations | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.synchronous* | Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). | false | ConfigDef.Importance.MEDIUM
+| *camel.component.atomix-map.atomix* | The shared AtomixClient instance | null | ConfigDef.Importance.MEDIUM
+| *camel.component.atomix-map.configuration* | The shared component configuration | null | ConfigDef.Importance.MEDIUM
+| *camel.component.atomix-map.configurationUri* | The path to the AtomixClient configuration | null | ConfigDef.Importance.MEDIUM
+| *camel.component.atomix-map.nodes* | The nodes the AtomixClient should connect to | null | ConfigDef.Importance.MEDIUM
+| *camel.component.atomix-map.bridgeErrorHandler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | ConfigDef.Importance.MEDIUM
+| *camel.component.atomix-map.basicPropertyBinding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+|===
+
+
+// kafka-connector options: END
diff --git a/docs/modules/ROOT/pages/connectors/camel-atomix-messaging-kafka-sink-connector.adoc b/docs/modules/ROOT/pages/connectors/camel-atomix-messaging-kafka-sink-connector.adoc
new file mode 100644
index 0000000..cdf2f3a
--- /dev/null
+++ b/docs/modules/ROOT/pages/connectors/camel-atomix-messaging-kafka-sink-connector.adoc
@@ -0,0 +1,48 @@
+// kafka-connector options: START
+== camel-atomix-messaging-kafka-connector source configuration
+
+When using camel-atomix-messaging-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-atomix-messaging-kafka-connector</artifactId>
+ <version>x.x.x</version>
+ <!-- use the same version as your Camel Kafka connector version -->
+</dependency>
+----
+
+
+[width="100%",cols="2,5,^1,2",options="header"]
+|===
+| Name | Description | Default | Priority
+| *camel.sink.path.resourceName* | The distributed resource name | null | ConfigDef.Importance.HIGH
+| *camel.sink.endpoint.atomix* | The Atomix instance to use | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.broadcastType* | The broadcast type. One of: [ALL] [RANDOM] | "ALL" | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.channelName* | The messaging channel name | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.configurationUri* | The Atomix configuration uri. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.defaultAction* | The default action. One of: [DIRECT] [BROADCAST] | "DIRECT" | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.memberName* | The Atomix Group member name | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.nodes* | The address of the nodes composing the cluster. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.resultHeader* | The header that wil carry the result. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.transportClassName* | The class name (fqn) of the Atomix transport | "io.atomix.catalyst.transport.netty.NettyTransport" | ConfigDef.Importance.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 cre [...]
+| *camel.sink.endpoint.basicPropertyBinding* | Whether the endpoint should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.defaultResourceConfig* | The cluster wide default resource configuration. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.defaultResourceOptions* | The local default resource options. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.ephemeral* | Sets if the local member should join groups as PersistentMember or not. If set to ephemeral the local member will receive an auto generated ID thus the local one is ignored. | false | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.readConsistency* | The read consistency level. One of: [ATOMIC] [ATOMIC_LEASE] [SEQUENTIAL] [LOCAL] | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.resourceConfigs* | Cluster wide resources configuration. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.resourceOptions* | Local resources configurations | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.synchronous* | Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). | false | ConfigDef.Importance.MEDIUM
+| *camel.component.atomix-messaging.atomix* | The shared AtomixClient instance | null | ConfigDef.Importance.MEDIUM
+| *camel.component.atomix-messaging.configuration* | The shared component configuration | null | ConfigDef.Importance.MEDIUM
+| *camel.component.atomix-messaging.configurationUri* | The path to the AtomixClient configuration | null | ConfigDef.Importance.MEDIUM
+| *camel.component.atomix-messaging.nodes* | The nodes the AtomixClient should connect to | null | ConfigDef.Importance.MEDIUM
+| *camel.component.atomix-messaging.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 proce [...]
+| *camel.component.atomix-messaging.basicPropertyBinding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+|===
+
+
+// kafka-connector options: END
diff --git a/docs/modules/ROOT/pages/connectors/camel-atomix-messaging-kafka-source-connector.adoc b/docs/modules/ROOT/pages/connectors/camel-atomix-messaging-kafka-source-connector.adoc
new file mode 100644
index 0000000..436502d
--- /dev/null
+++ b/docs/modules/ROOT/pages/connectors/camel-atomix-messaging-kafka-source-connector.adoc
@@ -0,0 +1,50 @@
+// kafka-connector options: START
+== camel-atomix-messaging-kafka-connector source configuration
+
+When using camel-atomix-messaging-kafka-connector as source 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-atomix-messaging-kafka-connector</artifactId>
+ <version>x.x.x</version>
+ <!-- use the same version as your Camel Kafka connector version -->
+</dependency>
+----
+
+
+[width="100%",cols="2,5,^1,2",options="header"]
+|===
+| Name | Description | Default | Priority
+| *camel.source.path.resourceName* | The distributed resource name | null | ConfigDef.Importance.HIGH
+| *camel.source.endpoint.atomix* | The Atomix instance to use | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.broadcastType* | The broadcast type. One of: [ALL] [RANDOM] | "ALL" | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.channelName* | The messaging channel name | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.configurationUri* | The Atomix configuration uri. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.defaultAction* | The default action. One of: [DIRECT] [BROADCAST] | "DIRECT" | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.memberName* | The Atomix Group member name | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.nodes* | The address of the nodes composing the cluster. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.resultHeader* | The header that wil carry the result. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.transportClassName* | The class name (fqn) of the Atomix transport | "io.atomix.catalyst.transport.netty.NettyTransport" | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.bridgeErrorHandler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.exceptionHandler* | To let the consumer use a custom ExceptionHandler. Notice if the option bridgeErrorHandler is enabled then this option is not in use. By default the consumer will deal with exceptions, that will be logged at WARN or ERROR level and ignored. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.exchangePattern* | Sets the exchange pattern when the consumer creates an exchange. One of: [InOnly] [InOut] [InOptionalOut] | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.basicPropertyBinding* | Whether the endpoint should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.defaultResourceConfig* | The cluster wide default resource configuration. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.defaultResourceOptions* | The local default resource options. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.ephemeral* | Sets if the local member should join groups as PersistentMember or not. If set to ephemeral the local member will receive an auto generated ID thus the local one is ignored. | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.readConsistency* | The read consistency level. One of: [ATOMIC] [ATOMIC_LEASE] [SEQUENTIAL] [LOCAL] | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.resourceConfigs* | Cluster wide resources configuration. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.resourceOptions* | Local resources configurations | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.synchronous* | Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). | false | ConfigDef.Importance.MEDIUM
+| *camel.component.atomix-messaging.atomix* | The shared AtomixClient instance | null | ConfigDef.Importance.MEDIUM
+| *camel.component.atomix-messaging.configuration* | The shared component configuration | null | ConfigDef.Importance.MEDIUM
+| *camel.component.atomix-messaging.configurationUri* | The path to the AtomixClient configuration | null | ConfigDef.Importance.MEDIUM
+| *camel.component.atomix-messaging.nodes* | The nodes the AtomixClient should connect to | null | ConfigDef.Importance.MEDIUM
+| *camel.component.atomix-messaging.bridgeErrorHandler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | ConfigDef.Impor [...]
+| *camel.component.atomix-messaging.basicPropertyBinding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+|===
+
+
+// kafka-connector options: END
diff --git a/docs/modules/ROOT/pages/connectors/camel-atomix-multimap-kafka-sink-connector.adoc b/docs/modules/ROOT/pages/connectors/camel-atomix-multimap-kafka-sink-connector.adoc
new file mode 100644
index 0000000..c71caec
--- /dev/null
+++ b/docs/modules/ROOT/pages/connectors/camel-atomix-multimap-kafka-sink-connector.adoc
@@ -0,0 +1,47 @@
+// kafka-connector options: START
+== camel-atomix-multimap-kafka-connector source configuration
+
+When using camel-atomix-multimap-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-atomix-multimap-kafka-connector</artifactId>
+ <version>x.x.x</version>
+ <!-- use the same version as your Camel Kafka connector version -->
+</dependency>
+----
+
+
+[width="100%",cols="2,5,^1,2",options="header"]
+|===
+| Name | Description | Default | Priority
+| *camel.sink.path.resourceName* | The distributed resource name | null | ConfigDef.Importance.HIGH
+| *camel.sink.endpoint.atomix* | The Atomix instance to use | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.configurationUri* | The Atomix configuration uri. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.defaultAction* | The default action. One of: [PUT] [GET] [CLEAR] [SIZE] [CONTAINS_KEY] [IS_EMPTY] [REMOVE] [REMOVE_VALUE] | "PUT" | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.key* | The key to use if none is set in the header or to listen for events for a specific key. | null | ConfigDef.Importance.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 cre [...]
+| *camel.sink.endpoint.nodes* | The address of the nodes composing the cluster. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.resultHeader* | The header that wil carry the result. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.transportClassName* | The class name (fqn) of the Atomix transport | "io.atomix.catalyst.transport.netty.NettyTransport" | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.ttl* | The resource ttl. | null | ConfigDef.Importance.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 | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.defaultResourceConfig* | The cluster wide default resource configuration. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.defaultResourceOptions* | The local default resource options. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.ephemeral* | Sets if the local member should join groups as PersistentMember or not. If set to ephemeral the local member will receive an auto generated ID thus the local one is ignored. | false | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.readConsistency* | The read consistency level. One of: [ATOMIC] [ATOMIC_LEASE] [SEQUENTIAL] [LOCAL] | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.resourceConfigs* | Cluster wide resources configuration. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.resourceOptions* | Local resources configurations | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.synchronous* | Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). | false | ConfigDef.Importance.MEDIUM
+| *camel.component.atomix-multimap.atomix* | The shared AtomixClient instance | null | ConfigDef.Importance.MEDIUM
+| *camel.component.atomix-multimap.configuration* | The shared component configuration | null | ConfigDef.Importance.MEDIUM
+| *camel.component.atomix-multimap.configurationUri* | The path to the AtomixClient configuration | null | ConfigDef.Importance.MEDIUM
+| *camel.component.atomix-multimap.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 proces [...]
+| *camel.component.atomix-multimap.nodes* | The nodes the AtomixClient should connect to | null | ConfigDef.Importance.MEDIUM
+| *camel.component.atomix-multimap.basicPropertyBinding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+|===
+
+
+// kafka-connector options: END
diff --git a/docs/modules/ROOT/pages/connectors/camel-atomix-queue-kafka-sink-connector.adoc b/docs/modules/ROOT/pages/connectors/camel-atomix-queue-kafka-sink-connector.adoc
new file mode 100644
index 0000000..0fcd11a
--- /dev/null
+++ b/docs/modules/ROOT/pages/connectors/camel-atomix-queue-kafka-sink-connector.adoc
@@ -0,0 +1,45 @@
+// kafka-connector options: START
+== camel-atomix-queue-kafka-connector source configuration
+
+When using camel-atomix-queue-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-atomix-queue-kafka-connector</artifactId>
+ <version>x.x.x</version>
+ <!-- use the same version as your Camel Kafka connector version -->
+</dependency>
+----
+
+
+[width="100%",cols="2,5,^1,2",options="header"]
+|===
+| Name | Description | Default | Priority
+| *camel.sink.path.resourceName* | The distributed resource name | null | ConfigDef.Importance.HIGH
+| *camel.sink.endpoint.atomix* | The Atomix instance to use | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.configurationUri* | The Atomix configuration uri. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.defaultAction* | The default action. One of: [ADD] [OFFER] [PEEK] [POLL] [CLEAR] [CONTAINS] [IS_EMPTY] [REMOVE] [SIZE] | "ADD" | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.nodes* | The address of the nodes composing the cluster. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.resultHeader* | The header that wil carry the result. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.transportClassName* | The class name (fqn) of the Atomix transport | "io.atomix.catalyst.transport.netty.NettyTransport" | ConfigDef.Importance.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 cre [...]
+| *camel.sink.endpoint.basicPropertyBinding* | Whether the endpoint should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.defaultResourceConfig* | The cluster wide default resource configuration. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.defaultResourceOptions* | The local default resource options. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.ephemeral* | Sets if the local member should join groups as PersistentMember or not. If set to ephemeral the local member will receive an auto generated ID thus the local one is ignored. | false | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.readConsistency* | The read consistency level. One of: [ATOMIC] [ATOMIC_LEASE] [SEQUENTIAL] [LOCAL] | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.resourceConfigs* | Cluster wide resources configuration. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.resourceOptions* | Local resources configurations | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.synchronous* | Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). | false | ConfigDef.Importance.MEDIUM
+| *camel.component.atomix-queue.atomix* | The shared AtomixClient instance | null | ConfigDef.Importance.MEDIUM
+| *camel.component.atomix-queue.configuration* | The shared component configuration | null | ConfigDef.Importance.MEDIUM
+| *camel.component.atomix-queue.configurationUri* | The path to the AtomixClient configuration | null | ConfigDef.Importance.MEDIUM
+| *camel.component.atomix-queue.nodes* | The nodes the AtomixClient should connect to | null | ConfigDef.Importance.MEDIUM
+| *camel.component.atomix-queue.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 [...]
+| *camel.component.atomix-queue.basicPropertyBinding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+|===
+
+
+// kafka-connector options: END
diff --git a/docs/modules/ROOT/pages/connectors/camel-atomix-queue-kafka-source-connector.adoc b/docs/modules/ROOT/pages/connectors/camel-atomix-queue-kafka-source-connector.adoc
new file mode 100644
index 0000000..b4ae3dd
--- /dev/null
+++ b/docs/modules/ROOT/pages/connectors/camel-atomix-queue-kafka-source-connector.adoc
@@ -0,0 +1,47 @@
+// kafka-connector options: START
+== camel-atomix-queue-kafka-connector source configuration
+
+When using camel-atomix-queue-kafka-connector as source 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-atomix-queue-kafka-connector</artifactId>
+ <version>x.x.x</version>
+ <!-- use the same version as your Camel Kafka connector version -->
+</dependency>
+----
+
+
+[width="100%",cols="2,5,^1,2",options="header"]
+|===
+| Name | Description | Default | Priority
+| *camel.source.path.resourceName* | The distributed resource name | null | ConfigDef.Importance.HIGH
+| *camel.source.endpoint.atomix* | The Atomix instance to use | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.configurationUri* | The Atomix configuration uri. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.defaultAction* | The default action. One of: [ADD] [OFFER] [PEEK] [POLL] [CLEAR] [CONTAINS] [IS_EMPTY] [REMOVE] [SIZE] | "ADD" | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.nodes* | The address of the nodes composing the cluster. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.resultHeader* | The header that wil carry the result. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.transportClassName* | The class name (fqn) of the Atomix transport | "io.atomix.catalyst.transport.netty.NettyTransport" | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.bridgeErrorHandler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.exceptionHandler* | To let the consumer use a custom ExceptionHandler. Notice if the option bridgeErrorHandler is enabled then this option is not in use. By default the consumer will deal with exceptions, that will be logged at WARN or ERROR level and ignored. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.exchangePattern* | Sets the exchange pattern when the consumer creates an exchange. One of: [InOnly] [InOut] [InOptionalOut] | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.basicPropertyBinding* | Whether the endpoint should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.defaultResourceConfig* | The cluster wide default resource configuration. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.defaultResourceOptions* | The local default resource options. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.ephemeral* | Sets if the local member should join groups as PersistentMember or not. If set to ephemeral the local member will receive an auto generated ID thus the local one is ignored. | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.readConsistency* | The read consistency level. One of: [ATOMIC] [ATOMIC_LEASE] [SEQUENTIAL] [LOCAL] | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.resourceConfigs* | Cluster wide resources configuration. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.resourceOptions* | Local resources configurations | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.synchronous* | Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). | false | ConfigDef.Importance.MEDIUM
+| *camel.component.atomix-queue.atomix* | The shared AtomixClient instance | null | ConfigDef.Importance.MEDIUM
+| *camel.component.atomix-queue.configuration* | The shared component configuration | null | ConfigDef.Importance.MEDIUM
+| *camel.component.atomix-queue.configurationUri* | The path to the AtomixClient configuration | null | ConfigDef.Importance.MEDIUM
+| *camel.component.atomix-queue.nodes* | The nodes the AtomixClient should connect to | null | ConfigDef.Importance.MEDIUM
+| *camel.component.atomix-queue.bridgeErrorHandler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | ConfigDef.Importanc [...]
+| *camel.component.atomix-queue.basicPropertyBinding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+|===
+
+
+// kafka-connector options: END
diff --git a/docs/modules/ROOT/pages/connectors/camel-atomix-set-kafka-sink-connector.adoc b/docs/modules/ROOT/pages/connectors/camel-atomix-set-kafka-sink-connector.adoc
new file mode 100644
index 0000000..0478b5c
--- /dev/null
+++ b/docs/modules/ROOT/pages/connectors/camel-atomix-set-kafka-sink-connector.adoc
@@ -0,0 +1,46 @@
+// kafka-connector options: START
+== camel-atomix-set-kafka-connector source configuration
+
+When using camel-atomix-set-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-atomix-set-kafka-connector</artifactId>
+ <version>x.x.x</version>
+ <!-- use the same version as your Camel Kafka connector version -->
+</dependency>
+----
+
+
+[width="100%",cols="2,5,^1,2",options="header"]
+|===
+| Name | Description | Default | Priority
+| *camel.sink.path.resourceName* | The distributed resource name | null | ConfigDef.Importance.HIGH
+| *camel.sink.endpoint.atomix* | The Atomix instance to use | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.configurationUri* | The Atomix configuration uri. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.defaultAction* | The default action. One of: [ADD] [CLEAR] [CONTAINS] [IS_EMPTY] [REMOVE] [SIZE] | "ADD" | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.nodes* | The address of the nodes composing the cluster. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.resultHeader* | The header that wil carry the result. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.transportClassName* | The class name (fqn) of the Atomix transport | "io.atomix.catalyst.transport.netty.NettyTransport" | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.ttl* | The resource ttl. | null | ConfigDef.Importance.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 cre [...]
+| *camel.sink.endpoint.basicPropertyBinding* | Whether the endpoint should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.defaultResourceConfig* | The cluster wide default resource configuration. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.defaultResourceOptions* | The local default resource options. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.ephemeral* | Sets if the local member should join groups as PersistentMember or not. If set to ephemeral the local member will receive an auto generated ID thus the local one is ignored. | false | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.readConsistency* | The read consistency level. One of: [ATOMIC] [ATOMIC_LEASE] [SEQUENTIAL] [LOCAL] | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.resourceConfigs* | Cluster wide resources configuration. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.resourceOptions* | Local resources configurations | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.synchronous* | Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). | false | ConfigDef.Importance.MEDIUM
+| *camel.component.atomix-set.atomix* | The shared AtomixClient instance | null | ConfigDef.Importance.MEDIUM
+| *camel.component.atomix-set.configuration* | The shared component configuration | null | ConfigDef.Importance.MEDIUM
+| *camel.component.atomix-set.configurationUri* | The path to the AtomixClient configuration | null | ConfigDef.Importance.MEDIUM
+| *camel.component.atomix-set.nodes* | The nodes the AtomixClient should connect to | null | ConfigDef.Importance.MEDIUM
+| *camel.component.atomix-set.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 t [...]
+| *camel.component.atomix-set.basicPropertyBinding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+|===
+
+
+// kafka-connector options: END
diff --git a/docs/modules/ROOT/pages/connectors/camel-atomix-set-kafka-source-connector.adoc b/docs/modules/ROOT/pages/connectors/camel-atomix-set-kafka-source-connector.adoc
new file mode 100644
index 0000000..95ce83a
--- /dev/null
+++ b/docs/modules/ROOT/pages/connectors/camel-atomix-set-kafka-source-connector.adoc
@@ -0,0 +1,48 @@
+// kafka-connector options: START
+== camel-atomix-set-kafka-connector source configuration
+
+When using camel-atomix-set-kafka-connector as source 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-atomix-set-kafka-connector</artifactId>
+ <version>x.x.x</version>
+ <!-- use the same version as your Camel Kafka connector version -->
+</dependency>
+----
+
+
+[width="100%",cols="2,5,^1,2",options="header"]
+|===
+| Name | Description | Default | Priority
+| *camel.source.path.resourceName* | The distributed resource name | null | ConfigDef.Importance.HIGH
+| *camel.source.endpoint.atomix* | The Atomix instance to use | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.configurationUri* | The Atomix configuration uri. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.defaultAction* | The default action. One of: [ADD] [CLEAR] [CONTAINS] [IS_EMPTY] [REMOVE] [SIZE] | "ADD" | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.nodes* | The address of the nodes composing the cluster. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.resultHeader* | The header that wil carry the result. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.transportClassName* | The class name (fqn) of the Atomix transport | "io.atomix.catalyst.transport.netty.NettyTransport" | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.ttl* | The resource ttl. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.bridgeErrorHandler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.exceptionHandler* | To let the consumer use a custom ExceptionHandler. Notice if the option bridgeErrorHandler is enabled then this option is not in use. By default the consumer will deal with exceptions, that will be logged at WARN or ERROR level and ignored. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.exchangePattern* | Sets the exchange pattern when the consumer creates an exchange. One of: [InOnly] [InOut] [InOptionalOut] | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.basicPropertyBinding* | Whether the endpoint should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.defaultResourceConfig* | The cluster wide default resource configuration. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.defaultResourceOptions* | The local default resource options. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.ephemeral* | Sets if the local member should join groups as PersistentMember or not. If set to ephemeral the local member will receive an auto generated ID thus the local one is ignored. | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.readConsistency* | The read consistency level. One of: [ATOMIC] [ATOMIC_LEASE] [SEQUENTIAL] [LOCAL] | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.resourceConfigs* | Cluster wide resources configuration. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.resourceOptions* | Local resources configurations | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.synchronous* | Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). | false | ConfigDef.Importance.MEDIUM
+| *camel.component.atomix-set.atomix* | The shared AtomixClient instance | null | ConfigDef.Importance.MEDIUM
+| *camel.component.atomix-set.configuration* | The shared component configuration | null | ConfigDef.Importance.MEDIUM
+| *camel.component.atomix-set.configurationUri* | The path to the AtomixClient configuration | null | ConfigDef.Importance.MEDIUM
+| *camel.component.atomix-set.nodes* | The nodes the AtomixClient should connect to | null | ConfigDef.Importance.MEDIUM
+| *camel.component.atomix-set.bridgeErrorHandler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | ConfigDef.Importance.MEDIUM
+| *camel.component.atomix-set.basicPropertyBinding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+|===
+
+
+// kafka-connector options: END
diff --git a/docs/modules/ROOT/pages/connectors/camel-atomix-value-kafka-sink-connector.adoc b/docs/modules/ROOT/pages/connectors/camel-atomix-value-kafka-sink-connector.adoc
new file mode 100644
index 0000000..76f5b8e
--- /dev/null
+++ b/docs/modules/ROOT/pages/connectors/camel-atomix-value-kafka-sink-connector.adoc
@@ -0,0 +1,46 @@
+// kafka-connector options: START
+== camel-atomix-value-kafka-connector source configuration
+
+When using camel-atomix-value-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-atomix-value-kafka-connector</artifactId>
+ <version>x.x.x</version>
+ <!-- use the same version as your Camel Kafka connector version -->
+</dependency>
+----
+
+
+[width="100%",cols="2,5,^1,2",options="header"]
+|===
+| Name | Description | Default | Priority
+| *camel.sink.path.resourceName* | The distributed resource name | null | ConfigDef.Importance.HIGH
+| *camel.sink.endpoint.atomix* | The Atomix instance to use | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.configurationUri* | The Atomix configuration uri. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.defaultAction* | The default action. One of: [SET] [GET] [GET_AND_SET] [COMPARE_AND_SET] | "SET" | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.nodes* | The address of the nodes composing the cluster. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.resultHeader* | The header that wil carry the result. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.transportClassName* | The class name (fqn) of the Atomix transport | "io.atomix.catalyst.transport.netty.NettyTransport" | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.ttl* | The resource ttl. | null | ConfigDef.Importance.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 cre [...]
+| *camel.sink.endpoint.basicPropertyBinding* | Whether the endpoint should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.defaultResourceConfig* | The cluster wide default resource configuration. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.defaultResourceOptions* | The local default resource options. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.ephemeral* | Sets if the local member should join groups as PersistentMember or not. If set to ephemeral the local member will receive an auto generated ID thus the local one is ignored. | false | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.readConsistency* | The read consistency level. One of: [ATOMIC] [ATOMIC_LEASE] [SEQUENTIAL] [LOCAL] | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.resourceConfigs* | Cluster wide resources configuration. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.resourceOptions* | Local resources configurations | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.synchronous* | Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). | false | ConfigDef.Importance.MEDIUM
+| *camel.component.atomix-value.atomix* | The shared AtomixClient instance | null | ConfigDef.Importance.MEDIUM
+| *camel.component.atomix-value.configuration* | The shared component configuration | null | ConfigDef.Importance.MEDIUM
+| *camel.component.atomix-value.configurationUri* | The path to the AtomixClient configuration | null | ConfigDef.Importance.MEDIUM
+| *camel.component.atomix-value.nodes* | The nodes the AtomixClient should connect to | null | ConfigDef.Importance.MEDIUM
+| *camel.component.atomix-value.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 [...]
+| *camel.component.atomix-value.basicPropertyBinding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+|===
+
+
+// kafka-connector options: END
diff --git a/docs/modules/ROOT/pages/connectors/camel-atomix-value-kafka-source-connector.adoc b/docs/modules/ROOT/pages/connectors/camel-atomix-value-kafka-source-connector.adoc
new file mode 100644
index 0000000..68ff21f
--- /dev/null
+++ b/docs/modules/ROOT/pages/connectors/camel-atomix-value-kafka-source-connector.adoc
@@ -0,0 +1,48 @@
+// kafka-connector options: START
+== camel-atomix-value-kafka-connector source configuration
+
+When using camel-atomix-value-kafka-connector as source 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-atomix-value-kafka-connector</artifactId>
+ <version>x.x.x</version>
+ <!-- use the same version as your Camel Kafka connector version -->
+</dependency>
+----
+
+
+[width="100%",cols="2,5,^1,2",options="header"]
+|===
+| Name | Description | Default | Priority
+| *camel.source.path.resourceName* | The distributed resource name | null | ConfigDef.Importance.HIGH
+| *camel.source.endpoint.atomix* | The Atomix instance to use | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.configurationUri* | The Atomix configuration uri. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.defaultAction* | The default action. One of: [SET] [GET] [GET_AND_SET] [COMPARE_AND_SET] | "SET" | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.nodes* | The address of the nodes composing the cluster. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.resultHeader* | The header that wil carry the result. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.transportClassName* | The class name (fqn) of the Atomix transport | "io.atomix.catalyst.transport.netty.NettyTransport" | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.ttl* | The resource ttl. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.bridgeErrorHandler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.exceptionHandler* | To let the consumer use a custom ExceptionHandler. Notice if the option bridgeErrorHandler is enabled then this option is not in use. By default the consumer will deal with exceptions, that will be logged at WARN or ERROR level and ignored. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.exchangePattern* | Sets the exchange pattern when the consumer creates an exchange. One of: [InOnly] [InOut] [InOptionalOut] | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.basicPropertyBinding* | Whether the endpoint should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.defaultResourceConfig* | The cluster wide default resource configuration. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.defaultResourceOptions* | The local default resource options. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.ephemeral* | Sets if the local member should join groups as PersistentMember or not. If set to ephemeral the local member will receive an auto generated ID thus the local one is ignored. | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.readConsistency* | The read consistency level. One of: [ATOMIC] [ATOMIC_LEASE] [SEQUENTIAL] [LOCAL] | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.resourceConfigs* | Cluster wide resources configuration. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.resourceOptions* | Local resources configurations | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.synchronous* | Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). | false | ConfigDef.Importance.MEDIUM
+| *camel.component.atomix-value.atomix* | The shared AtomixClient instance | null | ConfigDef.Importance.MEDIUM
+| *camel.component.atomix-value.configuration* | The shared component configuration | null | ConfigDef.Importance.MEDIUM
+| *camel.component.atomix-value.configurationUri* | The path to the AtomixClient configuration | null | ConfigDef.Importance.MEDIUM
+| *camel.component.atomix-value.nodes* | The nodes the AtomixClient should connect to | null | ConfigDef.Importance.MEDIUM
+| *camel.component.atomix-value.bridgeErrorHandler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | ConfigDef.Importanc [...]
+| *camel.component.atomix-value.basicPropertyBinding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+|===
+
+
+// kafka-connector options: END
diff --git a/docs/modules/ROOT/pages/connectors/camel-avro-kafka-sink-connector.adoc b/docs/modules/ROOT/pages/connectors/camel-avro-kafka-sink-connector.adoc
new file mode 100644
index 0000000..60f712e
--- /dev/null
+++ b/docs/modules/ROOT/pages/connectors/camel-avro-kafka-sink-connector.adoc
@@ -0,0 +1,39 @@
+// kafka-connector options: START
+== camel-avro-kafka-connector source configuration
+
+When using camel-avro-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-avro-kafka-connector</artifactId>
+ <version>x.x.x</version>
+ <!-- use the same version as your Camel Kafka connector version -->
+</dependency>
+----
+
+
+[width="100%",cols="2,5,^1,2",options="header"]
+|===
+| Name | Description | Default | Priority
+| *camel.sink.path.transport* | Transport to use, can be either http or netty One of: [http] [netty] | null | ConfigDef.Importance.HIGH
+| *camel.sink.path.port* | Port number to use | null | ConfigDef.Importance.HIGH
+| *camel.sink.path.host* | Hostname to use | null | ConfigDef.Importance.HIGH
+| *camel.sink.path.messageName* | The name of the message to send. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.protocol* | Avro protocol to use | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.protocolClassName* | Avro protocol to use defined by the FQN class name | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.protocolLocation* | Avro protocol location | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.reflectionProtocol* | If protocol object provided is reflection protocol. Should be used only with protocol parameter because for protocolClassName protocol type will be auto detected | false | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.singleParameter* | If true, consumer parameter won't be wrapped into array. Will fail if protocol specifies more then 1 parameter for the message | false | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.uriAuthority* | Authority to use (username and password) | null | ConfigDef.Importance.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 cre [...]
+| *camel.sink.endpoint.basicPropertyBinding* | Whether the endpoint should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.synchronous* | Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). | false | ConfigDef.Importance.MEDIUM
+| *camel.component.avro.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 cr [...]
+| *camel.component.avro.basicPropertyBinding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+| *camel.component.avro.configuration* | To use a shared AvroConfiguration to configure options once | null | ConfigDef.Importance.MEDIUM
+|===
+
+
+// kafka-connector options: END
diff --git a/docs/modules/ROOT/pages/connectors/camel-avro-kafka-source-connector.adoc b/docs/modules/ROOT/pages/connectors/camel-avro-kafka-source-connector.adoc
new file mode 100644
index 0000000..75e07ba
--- /dev/null
+++ b/docs/modules/ROOT/pages/connectors/camel-avro-kafka-source-connector.adoc
@@ -0,0 +1,41 @@
+// kafka-connector options: START
+== camel-avro-kafka-connector source configuration
+
+When using camel-avro-kafka-connector as source 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-avro-kafka-connector</artifactId>
+ <version>x.x.x</version>
+ <!-- use the same version as your Camel Kafka connector version -->
+</dependency>
+----
+
+
+[width="100%",cols="2,5,^1,2",options="header"]
+|===
+| Name | Description | Default | Priority
+| *camel.source.path.transport* | Transport to use, can be either http or netty One of: [http] [netty] | null | ConfigDef.Importance.HIGH
+| *camel.source.path.port* | Port number to use | null | ConfigDef.Importance.HIGH
+| *camel.source.path.host* | Hostname to use | null | ConfigDef.Importance.HIGH
+| *camel.source.path.messageName* | The name of the message to send. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.protocol* | Avro protocol to use | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.protocolClassName* | Avro protocol to use defined by the FQN class name | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.protocolLocation* | Avro protocol location | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.reflectionProtocol* | If protocol object provided is reflection protocol. Should be used only with protocol parameter because for protocolClassName protocol type will be auto detected | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.singleParameter* | If true, consumer parameter won't be wrapped into array. Will fail if protocol specifies more then 1 parameter for the message | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.uriAuthority* | Authority to use (username and password) | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.bridgeErrorHandler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.exceptionHandler* | To let the consumer use a custom ExceptionHandler. Notice if the option bridgeErrorHandler is enabled then this option is not in use. By default the consumer will deal with exceptions, that will be logged at WARN or ERROR level and ignored. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.exchangePattern* | Sets the exchange pattern when the consumer creates an exchange. One of: [InOnly] [InOut] [InOptionalOut] | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.basicPropertyBinding* | Whether the endpoint should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.synchronous* | Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). | false | ConfigDef.Importance.MEDIUM
+| *camel.component.avro.bridgeErrorHandler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | ConfigDef.Importance.MEDIUM
+| *camel.component.avro.basicPropertyBinding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+| *camel.component.avro.configuration* | To use a shared AvroConfiguration to configure options once | null | ConfigDef.Importance.MEDIUM
+|===
+
+
+// kafka-connector options: END
diff --git a/docs/modules/ROOT/pages/connectors/camel-aws-cw-kafka-sink-connector.adoc b/docs/modules/ROOT/pages/connectors/camel-aws-cw-kafka-sink-connector.adoc
new file mode 100644
index 0000000..1e2c343
--- /dev/null
+++ b/docs/modules/ROOT/pages/connectors/camel-aws-cw-kafka-sink-connector.adoc
@@ -0,0 +1,44 @@
+// kafka-connector options: START
+== camel-aws-cw-kafka-connector source configuration
+
+When using camel-aws-cw-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-aws-cw-kafka-connector</artifactId>
+ <version>x.x.x</version>
+ <!-- use the same version as your Camel Kafka connector version -->
+</dependency>
+----
+
+
+[width="100%",cols="2,5,^1,2",options="header"]
+|===
+| Name | Description | Default | Priority
+| *camel.sink.path.namespace* | The metric namespace | null | ConfigDef.Importance.HIGH
+| *camel.sink.endpoint.amazonCwClient* | To use the AmazonCloudWatch as the client | null | ConfigDef.Importance.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 cre [...]
+| *camel.sink.endpoint.name* | The metric name | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.proxyHost* | To define a proxy host when instantiating the CW client | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.proxyPort* | To define a proxy port when instantiating the CW client | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.proxyProtocol* | To define a proxy protocol when instantiating the CW client One of: [HTTP] [HTTPS] | "HTTPS" | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.region* | The region in which CW client needs to work. When using this parameter, the configuration will expect the capitalized name of the region (for example AP_EAST_1) You'll need to use the name Regions.EU_WEST_1.name() | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.timestamp* | The metric timestamp | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.unit* | The metric unit | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.value* | The metric value | null | ConfigDef.Importance.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 | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.synchronous* | Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). | false | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.accessKey* | Amazon AWS Access Key | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.secretKey* | Amazon AWS Secret Key | null | ConfigDef.Importance.MEDIUM
+| *camel.component.aws-cw.accessKey* | Amazon AWS Access Key | null | ConfigDef.Importance.MEDIUM
+| *camel.component.aws-cw.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 [...]
+| *camel.component.aws-cw.region* | The region in which CW client needs to work | null | ConfigDef.Importance.MEDIUM
+| *camel.component.aws-cw.secretKey* | Amazon AWS Secret Key | null | ConfigDef.Importance.MEDIUM
+| *camel.component.aws-cw.basicPropertyBinding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+| *camel.component.aws-cw.configuration* | The AWS CW default configuration | null | ConfigDef.Importance.MEDIUM
+|===
+
+
+// kafka-connector options: END
diff --git a/docs/modules/ROOT/pages/connectors/camel-aws-ddb-kafka-sink-connector.adoc b/docs/modules/ROOT/pages/connectors/camel-aws-ddb-kafka-sink-connector.adoc
new file mode 100644
index 0000000..ba0c69b
--- /dev/null
+++ b/docs/modules/ROOT/pages/connectors/camel-aws-ddb-kafka-sink-connector.adoc
@@ -0,0 +1,46 @@
+// kafka-connector options: START
+== camel-aws-ddb-kafka-connector source configuration
+
+When using camel-aws-ddb-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-aws-ddb-kafka-connector</artifactId>
+ <version>x.x.x</version>
+ <!-- use the same version as your Camel Kafka connector version -->
+</dependency>
+----
+
+
+[width="100%",cols="2,5,^1,2",options="header"]
+|===
+| Name | Description | Default | Priority
+| *camel.sink.path.tableName* | The name of the table currently worked with. | null | ConfigDef.Importance.HIGH
+| *camel.sink.endpoint.amazonDDBClient* | To use the AmazonDynamoDB as the client | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.consistentRead* | Determines whether or not strong consistency should be enforced when data is read. | false | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.keyAttributeName* | Attribute name when creating table | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.keyAttributeType* | Attribute type when creating table | null | ConfigDef.Importance.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 cre [...]
+| *camel.sink.endpoint.operation* | What operation to perform One of: [BatchGetItems] [DeleteItem] [DeleteTable] [DescribeTable] [GetItem] [PutItem] [Query] [Scan] [UpdateItem] [UpdateTable] | "PutItem" | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.proxyHost* | To define a proxy host when instantiating the DDB client | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.proxyPort* | To define a proxy port when instantiating the DDB client. When using this parameter, the configuration will expect the capitalized name of the region (for example AP_EAST_1) You'll need to use the name Regions.EU_WEST_1.name() | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.proxyProtocol* | To define a proxy protocol when instantiating the DDB client One of: [HTTP] [HTTPS] | "HTTPS" | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.readCapacity* | The provisioned throughput to reserve for reading resources from your table | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.region* | The region in which DDB client needs to work | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.writeCapacity* | The provisioned throughput to reserved for writing resources to your table | null | ConfigDef.Importance.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 | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.synchronous* | Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). | false | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.accessKey* | Amazon AWS Access Key | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.secretKey* | Amazon AWS Secret Key | null | ConfigDef.Importance.MEDIUM
+| *camel.component.aws-ddb.accessKey* | Amazon AWS Access Key | null | ConfigDef.Importance.MEDIUM
+| *camel.component.aws-ddb.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 [...]
+| *camel.component.aws-ddb.region* | The region in which DDB client needs to work | null | ConfigDef.Importance.MEDIUM
+| *camel.component.aws-ddb.secretKey* | Amazon AWS Secret Key | null | ConfigDef.Importance.MEDIUM
+| *camel.component.aws-ddb.basicPropertyBinding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+| *camel.component.aws-ddb.configuration* | The AWS DDB default configuration | null | ConfigDef.Importance.MEDIUM
+|===
+
+
+// kafka-connector options: END
diff --git a/docs/modules/ROOT/pages/connectors/camel-aws-ddbstream-kafka-source-connector.adoc b/docs/modules/ROOT/pages/connectors/camel-aws-ddbstream-kafka-source-connector.adoc
new file mode 100644
index 0000000..0142dec
--- /dev/null
+++ b/docs/modules/ROOT/pages/connectors/camel-aws-ddbstream-kafka-source-connector.adoc
@@ -0,0 +1,61 @@
+// kafka-connector options: START
+== camel-aws-ddbstream-kafka-connector source configuration
+
+When using camel-aws-ddbstream-kafka-connector as source 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-aws-ddbstream-kafka-connector</artifactId>
+ <version>x.x.x</version>
+ <!-- use the same version as your Camel Kafka connector version -->
+</dependency>
+----
+
+
+[width="100%",cols="2,5,^1,2",options="header"]
+|===
+| Name | Description | Default | Priority
+| *camel.source.path.tableName* | Name of the dynamodb table | null | ConfigDef.Importance.HIGH
+| *camel.source.endpoint.amazonDynamoDbStreamsClient* | Amazon DynamoDB client to use for all requests for this endpoint | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.bridgeErrorHandler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.iteratorType* | Defines where in the DynaboDB stream to start getting records. Note that using TRIM_HORIZON can cause a significant delay before the stream has caught up to real-time. if {AT,AFTER}_SEQUENCE_NUMBER are used, then a sequenceNumberProvider MUST be supplied. One of: [TRIM_HORIZON] [LATEST] [AT_SEQUENCE_NUMBER] [AFTER_SEQUENCE_NUMBER] | "LATEST" | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.maxResultsPerRequest* | Maximum number of records that will be fetched in each poll | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.proxyHost* | To define a proxy host when instantiating the DDBStreams client | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.proxyPort* | To define a proxy port when instantiating the DDBStreams client | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.proxyProtocol* | To define a proxy protocol when instantiating the DDBStreams client One of: [HTTP] [HTTPS] | "HTTPS" | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.region* | The region in which DDBStreams client needs to work | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.sendEmptyMessageWhenIdle* | If the polling consumer did not poll any files, you can enable this option to send an empty message (no body) instead. | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.sequenceNumberProvider* | Provider for the sequence number when using one of the two ShardIteratorType.{AT,AFTER}_SEQUENCE_NUMBER iterator types. Can be a registry reference or a literal sequence number. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.exceptionHandler* | To let the consumer use a custom ExceptionHandler. Notice if the option bridgeErrorHandler is enabled then this option is not in use. By default the consumer will deal with exceptions, that will be logged at WARN or ERROR level and ignored. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.exchangePattern* | Sets the exchange pattern when the consumer creates an exchange. One of: [InOnly] [InOut] [InOptionalOut] | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.pollStrategy* | A pluggable org.apache.camel.PollingConsumerPollingStrategy allowing you to provide your custom implementation to control error handling usually occurred during the poll operation before an Exchange have been created and being routed in Camel. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.basicPropertyBinding* | Whether the endpoint should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.synchronous* | Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.backoffErrorThreshold* | The number of subsequent error polls (failed due some error) that should happen before the backoffMultipler should kick-in. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.backoffIdleThreshold* | The number of subsequent idle polls that should happen before the backoffMultipler should kick-in. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.backoffMultiplier* | To let the scheduled polling consumer backoff if there has been a number of subsequent idles/errors in a row. The multiplier is then the number of polls that will be skipped before the next actual attempt is happening again. When this option is in use then backoffIdleThreshold and/or backoffErrorThreshold must also be configured. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.delay* | Milliseconds before the next poll. You can also specify time values using units, such as 60s (60 seconds), 5m30s (5 minutes and 30 seconds), and 1h (1 hour). | 500L | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.greedy* | If greedy is enabled, then the ScheduledPollConsumer will run immediately again, if the previous run polled 1 or more messages. | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.initialDelay* | Milliseconds before the first poll starts. You can also specify time values using units, such as 60s (60 seconds), 5m30s (5 minutes and 30 seconds), and 1h (1 hour). | 1000L | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.repeatCount* | Specifies a maximum limit of number of fires. So if you set it to 1, the scheduler will only fire once. If you set it to 5, it will only fire five times. A value of zero or negative means fire forever. | 0L | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.runLoggingLevel* | The consumer logs a start/complete log line when it polls. This option allows you to configure the logging level for that. One of: [TRACE] [DEBUG] [INFO] [WARN] [ERROR] [OFF] | "TRACE" | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.scheduledExecutorService* | Allows for configuring a custom/shared thread pool to use for the consumer. By default each consumer has its own single threaded thread pool. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.scheduler* | To use a cron scheduler from either camel-spring or camel-quartz component One of: [none] [spring] [quartz] | "none" | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.schedulerProperties* | To configure additional properties when using a custom scheduler or any of the Quartz, Spring based scheduler. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.startScheduler* | Whether the scheduler should be auto started. | true | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.timeUnit* | Time unit for initialDelay and delay options. One of: [NANOSECONDS] [MICROSECONDS] [MILLISECONDS] [SECONDS] [MINUTES] [HOURS] [DAYS] | "MILLISECONDS" | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.useFixedDelay* | Controls if fixed delay or fixed rate is used. See ScheduledExecutorService in JDK for details. | true | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.accessKey* | Amazon AWS Access Key | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.secretKey* | Amazon AWS Secret Key | null | ConfigDef.Importance.MEDIUM
+| *camel.component.aws-ddbstream.accessKey* | Amazon AWS Access Key | null | ConfigDef.Importance.MEDIUM
+| *camel.component.aws-ddbstream.bridgeErrorHandler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | ConfigDef.Importan [...]
+| *camel.component.aws-ddbstream.region* | Amazon AWS Region | null | ConfigDef.Importance.MEDIUM
+| *camel.component.aws-ddbstream.secretKey* | Amazon AWS Secret Key | null | ConfigDef.Importance.MEDIUM
+| *camel.component.aws-ddbstream.basicPropertyBinding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+| *camel.component.aws-ddbstream.configuration* | The AWS DDB stream default configuration | null | ConfigDef.Importance.MEDIUM
+|===
+
+
+// kafka-connector options: END
diff --git a/docs/modules/ROOT/pages/connectors/camel-aws-ec2-kafka-sink-connector.adoc b/docs/modules/ROOT/pages/connectors/camel-aws-ec2-kafka-sink-connector.adoc
new file mode 100644
index 0000000..d4b50f0
--- /dev/null
+++ b/docs/modules/ROOT/pages/connectors/camel-aws-ec2-kafka-sink-connector.adoc
@@ -0,0 +1,41 @@
+// kafka-connector options: START
+== camel-aws-ec2-kafka-connector source configuration
+
+When using camel-aws-ec2-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-aws-ec2-kafka-connector</artifactId>
+ <version>x.x.x</version>
+ <!-- use the same version as your Camel Kafka connector version -->
+</dependency>
+----
+
+
+[width="100%",cols="2,5,^1,2",options="header"]
+|===
+| Name | Description | Default | Priority
+| *camel.sink.path.label* | Logical name | null | ConfigDef.Importance.HIGH
+| *camel.sink.endpoint.accessKey* | Amazon AWS Access Key | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.amazonEc2Client* | To use a existing configured AmazonEC2Client as client | null | ConfigDef.Importance.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 cre [...]
+| *camel.sink.endpoint.operation* | The operation to perform. It can be createAndRunInstances, startInstances, stopInstances, terminateInstances, describeInstances, describeInstancesStatus, rebootInstances, monitorInstances, unmonitorInstances, createTags or deleteTags One of: [createAndRunInstances] [startInstances] [stopInstances] [terminateInstances] [describeInstances] [describeInstancesStatus] [rebootInstances] [monitorInstances] [unmonitorInstances] [createTags] [deleteTags] | null [...]
+| *camel.sink.endpoint.proxyHost* | To define a proxy host when instantiating the EC2 client | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.proxyPort* | To define a proxy port when instantiating the EC2 client | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.proxyProtocol* | To define a proxy protocol when instantiating the EC2 client One of: [HTTP] [HTTPS] | "HTTPS" | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.region* | The region in which EC2 client needs to work. When using this parameter, the configuration will expect the capitalized name of the region (for example AP_EAST_1) You'll need to use the name Regions.EU_WEST_1.name() | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.secretKey* | Amazon AWS Secret Key | null | ConfigDef.Importance.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 | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.synchronous* | Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). | false | ConfigDef.Importance.MEDIUM
+| *camel.component.aws-ec2.accessKey* | Amazon AWS Access Key | null | ConfigDef.Importance.MEDIUM
+| *camel.component.aws-ec2.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 [...]
+| *camel.component.aws-ec2.region* | The region in which EC2 client needs to work | null | ConfigDef.Importance.MEDIUM
+| *camel.component.aws-ec2.secretKey* | Amazon AWS Secret Key | null | ConfigDef.Importance.MEDIUM
+| *camel.component.aws-ec2.basicPropertyBinding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+| *camel.component.aws-ec2.configuration* | The AWS EC2 default configuration | null | ConfigDef.Importance.MEDIUM
+|===
+
+
+// kafka-connector options: END
diff --git a/docs/modules/ROOT/pages/connectors/camel-aws-ecs-kafka-sink-connector.adoc b/docs/modules/ROOT/pages/connectors/camel-aws-ecs-kafka-sink-connector.adoc
new file mode 100644
index 0000000..f19de4d
--- /dev/null
+++ b/docs/modules/ROOT/pages/connectors/camel-aws-ecs-kafka-sink-connector.adoc
@@ -0,0 +1,41 @@
+// kafka-connector options: START
+== camel-aws-ecs-kafka-connector source configuration
+
+When using camel-aws-ecs-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-aws-ecs-kafka-connector</artifactId>
+ <version>x.x.x</version>
+ <!-- use the same version as your Camel Kafka connector version -->
+</dependency>
+----
+
+
+[width="100%",cols="2,5,^1,2",options="header"]
+|===
+| Name | Description | Default | Priority
+| *camel.sink.path.label* | Logical name | null | ConfigDef.Importance.HIGH
+| *camel.sink.endpoint.accessKey* | Amazon AWS Access Key | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.ecsClient* | To use a existing configured AWS ECS as client | null | ConfigDef.Importance.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 cre [...]
+| *camel.sink.endpoint.operation* | The operation to perform One of: [listClusters] [describeCluster] [createCluster] [deleteCluster] | null | ConfigDef.Importance.HIGH
+| *camel.sink.endpoint.proxyHost* | To define a proxy host when instantiating the ECS client | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.proxyPort* | To define a proxy port when instantiating the ECS client | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.proxyProtocol* | To define a proxy protocol when instantiating the ECS client One of: [HTTP] [HTTPS] | "HTTPS" | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.region* | The region in which ECS client needs to work. When using this parameter, the configuration will expect the capitalized name of the region (for example AP_EAST_1) You'll need to use the name Regions.EU_WEST_1.name() | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.secretKey* | Amazon AWS Secret Key | null | ConfigDef.Importance.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 | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.synchronous* | Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). | false | ConfigDef.Importance.MEDIUM
+| *camel.component.aws-ecs.accessKey* | Amazon AWS Access Key | null | ConfigDef.Importance.MEDIUM
+| *camel.component.aws-ecs.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 [...]
+| *camel.component.aws-ecs.region* | The region in which ECS client needs to work | null | ConfigDef.Importance.MEDIUM
+| *camel.component.aws-ecs.secretKey* | Amazon AWS Secret Key | null | ConfigDef.Importance.MEDIUM
+| *camel.component.aws-ecs.basicPropertyBinding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+| *camel.component.aws-ecs.configuration* | The AWS ECS default configuration | null | ConfigDef.Importance.MEDIUM
+|===
+
+
+// kafka-connector options: END
diff --git a/docs/modules/ROOT/pages/connectors/camel-aws-eks-kafka-sink-connector.adoc b/docs/modules/ROOT/pages/connectors/camel-aws-eks-kafka-sink-connector.adoc
new file mode 100644
index 0000000..a47b7b5
--- /dev/null
+++ b/docs/modules/ROOT/pages/connectors/camel-aws-eks-kafka-sink-connector.adoc
@@ -0,0 +1,41 @@
+// kafka-connector options: START
+== camel-aws-eks-kafka-connector source configuration
+
+When using camel-aws-eks-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-aws-eks-kafka-connector</artifactId>
+ <version>x.x.x</version>
+ <!-- use the same version as your Camel Kafka connector version -->
+</dependency>
+----
+
+
+[width="100%",cols="2,5,^1,2",options="header"]
+|===
+| Name | Description | Default | Priority
+| *camel.sink.path.label* | Logical name | null | ConfigDef.Importance.HIGH
+| *camel.sink.endpoint.accessKey* | Amazon AWS Access Key | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.eksClient* | To use a existing configured AWS EKS as client | null | ConfigDef.Importance.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 cre [...]
+| *camel.sink.endpoint.operation* | The operation to perform One of: [listClusters] [describeCluster] [createCluster] [deleteCluster] | null | ConfigDef.Importance.HIGH
+| *camel.sink.endpoint.proxyHost* | To define a proxy host when instantiating the EKS client | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.proxyPort* | To define a proxy port when instantiating the EKS client | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.proxyProtocol* | To define a proxy protocol when instantiating the EKS client One of: [HTTP] [HTTPS] | "HTTPS" | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.region* | The region in which EKS client needs to work. When using this parameter, the configuration will expect the capitalized name of the region (for example AP_EAST_1) You'll need to use the name Regions.EU_WEST_1.name() | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.secretKey* | Amazon AWS Secret Key | null | ConfigDef.Importance.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 | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.synchronous* | Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). | false | ConfigDef.Importance.MEDIUM
+| *camel.component.aws-eks.accessKey* | Amazon AWS Access Key | null | ConfigDef.Importance.MEDIUM
+| *camel.component.aws-eks.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 [...]
+| *camel.component.aws-eks.region* | The region in which EKS client needs to work | null | ConfigDef.Importance.MEDIUM
+| *camel.component.aws-eks.secretKey* | Amazon AWS Secret Key | null | ConfigDef.Importance.MEDIUM
+| *camel.component.aws-eks.basicPropertyBinding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+| *camel.component.aws-eks.configuration* | The AWS EKS default configuration | null | ConfigDef.Importance.MEDIUM
+|===
+
+
+// kafka-connector options: END
diff --git a/docs/modules/ROOT/pages/connectors/camel-aws-iam-kafka-sink-connector.adoc b/docs/modules/ROOT/pages/connectors/camel-aws-iam-kafka-sink-connector.adoc
new file mode 100644
index 0000000..0cf9bb8
--- /dev/null
+++ b/docs/modules/ROOT/pages/connectors/camel-aws-iam-kafka-sink-connector.adoc
@@ -0,0 +1,41 @@
+// kafka-connector options: START
+== camel-aws-iam-kafka-connector source configuration
+
+When using camel-aws-iam-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-aws-iam-kafka-connector</artifactId>
+ <version>x.x.x</version>
+ <!-- use the same version as your Camel Kafka connector version -->
+</dependency>
+----
+
+
+[width="100%",cols="2,5,^1,2",options="header"]
+|===
+| Name | Description | Default | Priority
+| *camel.sink.path.label* | Logical name | null | ConfigDef.Importance.HIGH
+| *camel.sink.endpoint.accessKey* | Amazon AWS Access Key | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.iamClient* | To use a existing configured AWS IAM as client | null | ConfigDef.Importance.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 cre [...]
+| *camel.sink.endpoint.operation* | The operation to perform One of: [listAccessKeys] [createUser] [deleteUser] [getUser] [listUsers] [createAccessKey] [deleteAccessKey] [updateAccessKey] [createGroup] [deleteGroup] [listGroups] [addUserToGroup] [removeUserFromGroup] | null | ConfigDef.Importance.HIGH
+| *camel.sink.endpoint.proxyHost* | To define a proxy host when instantiating the IAM client | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.proxyPort* | To define a proxy port when instantiating the IAM client | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.proxyProtocol* | To define a proxy protocol when instantiating the IAM client One of: [HTTP] [HTTPS] | "HTTPS" | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.region* | The region in which IAM client needs to work. When using this parameter, the configuration will expect the capitalized name of the region (for example AP_EAST_1) You'll need to use the name Regions.EU_WEST_1.name() | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.secretKey* | Amazon AWS Secret Key | null | ConfigDef.Importance.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 | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.synchronous* | Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). | false | ConfigDef.Importance.MEDIUM
+| *camel.component.aws-iam.accessKey* | Amazon AWS Access Key | null | ConfigDef.Importance.MEDIUM
+| *camel.component.aws-iam.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 [...]
+| *camel.component.aws-iam.region* | The region in which IAM client needs to work | null | ConfigDef.Importance.MEDIUM
+| *camel.component.aws-iam.secretKey* | Amazon AWS Secret Key | null | ConfigDef.Importance.MEDIUM
+| *camel.component.aws-iam.basicPropertyBinding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+| *camel.component.aws-iam.configuration* | The AWS IAM default configuration | null | ConfigDef.Importance.MEDIUM
+|===
+
+
+// kafka-connector options: END
diff --git a/docs/modules/ROOT/pages/connectors/camel-aws-kinesis-firehose-kafka-sink-connector.adoc b/docs/modules/ROOT/pages/connectors/camel-aws-kinesis-firehose-kafka-sink-connector.adoc
new file mode 100644
index 0000000..838a2f0
--- /dev/null
+++ b/docs/modules/ROOT/pages/connectors/camel-aws-kinesis-firehose-kafka-sink-connector.adoc
@@ -0,0 +1,40 @@
+// kafka-connector options: START
+== camel-aws-kinesis-firehose-kafka-connector source configuration
+
+When using camel-aws-kinesis-firehose-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-aws-kinesis-firehose-kafka-connector</artifactId>
+ <version>x.x.x</version>
+ <!-- use the same version as your Camel Kafka connector version -->
+</dependency>
+----
+
+
+[width="100%",cols="2,5,^1,2",options="header"]
+|===
+| Name | Description | Default | Priority
+| *camel.sink.path.streamName* | Name of the stream | null | ConfigDef.Importance.HIGH
+| *camel.sink.endpoint.amazonKinesisFirehoseClient* | Amazon Kinesis Firehose client to use for all requests for this endpoint | null | ConfigDef.Importance.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 cre [...]
+| *camel.sink.endpoint.proxyHost* | To define a proxy host when instantiating the Kinesis Firehose client | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.proxyPort* | To define a proxy port when instantiating the Kinesis Firehose client | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.proxyProtocol* | To define a proxy protocol when instantiating the Kinesis Firehose client One of: [HTTP] [HTTPS] | "HTTPS" | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.region* | The region in which Kinesis client needs to work. When using this parameter, the configuration will expect the capitalized name of the region (for example AP_EAST_1)You'll need to use the name Regions.EU_WEST_1.name() | null | ConfigDef.Importance.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 | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.synchronous* | Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). | false | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.accessKey* | Amazon AWS Access Key | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.secretKey* | Amazon AWS Secret Key | null | ConfigDef.Importance.MEDIUM
+| *camel.component.aws-kinesis-firehose.accessKey* | Amazon AWS Access Key | null | ConfigDef.Importance.MEDIUM
+| *camel.component.aws-kinesis-firehose.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 p [...]
+| *camel.component.aws-kinesis-firehose.region* | Amazon AWS Region | null | ConfigDef.Importance.MEDIUM
+| *camel.component.aws-kinesis-firehose.secretKey* | Amazon AWS Secret Key | null | ConfigDef.Importance.MEDIUM
+| *camel.component.aws-kinesis-firehose.basicPropertyBinding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+| *camel.component.aws-kinesis-firehose.configuration* | The AWS Kinesis Firehose default configuration | null | ConfigDef.Importance.MEDIUM
+|===
+
+
+// kafka-connector options: END
diff --git a/docs/modules/ROOT/pages/connectors/camel-aws-kinesis-kafka-sink-connector.adoc b/docs/modules/ROOT/pages/connectors/camel-aws-kinesis-kafka-sink-connector.adoc
new file mode 100644
index 0000000..7e1c754
--- /dev/null
+++ b/docs/modules/ROOT/pages/connectors/camel-aws-kinesis-kafka-sink-connector.adoc
@@ -0,0 +1,40 @@
+// kafka-connector options: START
+== camel-aws-kinesis-kafka-connector source configuration
+
+When using camel-aws-kinesis-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-aws-kinesis-kafka-connector</artifactId>
+ <version>x.x.x</version>
+ <!-- use the same version as your Camel Kafka connector version -->
+</dependency>
+----
+
+
+[width="100%",cols="2,5,^1,2",options="header"]
+|===
+| Name | Description | Default | Priority
+| *camel.sink.path.streamName* | Name of the stream | null | ConfigDef.Importance.HIGH
+| *camel.sink.endpoint.amazonKinesisClient* | Amazon Kinesis client to use for all requests for this endpoint | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.proxyHost* | To define a proxy host when instantiating the Kinesis client | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.proxyPort* | To define a proxy port when instantiating the Kinesis client | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.proxyProtocol* | To define a proxy protocol when instantiating the Kinesis client One of: [HTTP] [HTTPS] | "HTTPS" | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.region* | The region in which Kinesis client needs to work. When using this parameter, the configuration will expect the capitalized name of the region (for example AP_EAST_1)You'll need to use the name Regions.EU_WEST_1.name() | null | ConfigDef.Importance.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 cre [...]
+| *camel.sink.endpoint.basicPropertyBinding* | Whether the endpoint should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.synchronous* | Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). | false | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.accessKey* | Amazon AWS Access Key | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.secretKey* | Amazon AWS Secret Key | null | ConfigDef.Importance.MEDIUM
+| *camel.component.aws-kinesis.accessKey* | Amazon AWS Access Key | null | ConfigDef.Importance.MEDIUM
+| *camel.component.aws-kinesis.region* | Amazon AWS Region | null | ConfigDef.Importance.MEDIUM
+| *camel.component.aws-kinesis.secretKey* | Amazon AWS Secret Key | null | ConfigDef.Importance.MEDIUM
+| *camel.component.aws-kinesis.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 [...]
+| *camel.component.aws-kinesis.basicPropertyBinding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+| *camel.component.aws-kinesis.configuration* | The AWS S3 default configuration | null | ConfigDef.Importance.MEDIUM
+|===
+
+
+// kafka-connector options: END
diff --git a/docs/modules/ROOT/pages/connectors/camel-aws-kinesis-kafka-source-connector.adoc b/docs/modules/ROOT/pages/connectors/camel-aws-kinesis-kafka-source-connector.adoc
new file mode 100644
index 0000000..757691d
--- /dev/null
+++ b/docs/modules/ROOT/pages/connectors/camel-aws-kinesis-kafka-source-connector.adoc
@@ -0,0 +1,63 @@
+// kafka-connector options: START
+== camel-aws-kinesis-kafka-connector source configuration
+
+When using camel-aws-kinesis-kafka-connector as source 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-aws-kinesis-kafka-connector</artifactId>
+ <version>x.x.x</version>
+ <!-- use the same version as your Camel Kafka connector version -->
+</dependency>
+----
+
+
+[width="100%",cols="2,5,^1,2",options="header"]
+|===
+| Name | Description | Default | Priority
+| *camel.source.path.streamName* | Name of the stream | null | ConfigDef.Importance.HIGH
+| *camel.source.endpoint.amazonKinesisClient* | Amazon Kinesis client to use for all requests for this endpoint | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.proxyHost* | To define a proxy host when instantiating the Kinesis client | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.proxyPort* | To define a proxy port when instantiating the Kinesis client | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.proxyProtocol* | To define a proxy protocol when instantiating the Kinesis client One of: [HTTP] [HTTPS] | "HTTPS" | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.region* | The region in which Kinesis client needs to work. When using this parameter, the configuration will expect the capitalized name of the region (for example AP_EAST_1)You'll need to use the name Regions.EU_WEST_1.name() | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.bridgeErrorHandler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.iteratorType* | Defines where in the Kinesis stream to start getting records One of: [AT_SEQUENCE_NUMBER] [AFTER_SEQUENCE_NUMBER] [TRIM_HORIZON] [LATEST] [AT_TIMESTAMP] | "TRIM_HORIZON" | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.maxResultsPerRequest* | Maximum number of records that will be fetched in each poll | 1 | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.sendEmptyMessageWhenIdle* | If the polling consumer did not poll any files, you can enable this option to send an empty message (no body) instead. | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.sequenceNumber* | The sequence number to start polling from. Required if iteratorType is set to AFTER_SEQUENCE_NUMBER or AT_SEQUENCE_NUMBER | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.shardClosed* | Define what will be the behavior in case of shard closed. Possible value are ignore, silent and fail. In case of ignore a message will be logged and the consumer will restart from the beginning,in case of silent there will be no logging and the consumer will start from the beginning,in case of fail a ReachedClosedStateException will be raised One of: [ignore] [fail] [silent] | "ignore" | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.shardId* | Defines which shardId in the Kinesis stream to get records from | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.exceptionHandler* | To let the consumer use a custom ExceptionHandler. Notice if the option bridgeErrorHandler is enabled then this option is not in use. By default the consumer will deal with exceptions, that will be logged at WARN or ERROR level and ignored. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.exchangePattern* | Sets the exchange pattern when the consumer creates an exchange. One of: [InOnly] [InOut] [InOptionalOut] | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.pollStrategy* | A pluggable org.apache.camel.PollingConsumerPollingStrategy allowing you to provide your custom implementation to control error handling usually occurred during the poll operation before an Exchange have been created and being routed in Camel. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.basicPropertyBinding* | Whether the endpoint should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.synchronous* | Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.backoffErrorThreshold* | The number of subsequent error polls (failed due some error) that should happen before the backoffMultipler should kick-in. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.backoffIdleThreshold* | The number of subsequent idle polls that should happen before the backoffMultipler should kick-in. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.backoffMultiplier* | To let the scheduled polling consumer backoff if there has been a number of subsequent idles/errors in a row. The multiplier is then the number of polls that will be skipped before the next actual attempt is happening again. When this option is in use then backoffIdleThreshold and/or backoffErrorThreshold must also be configured. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.delay* | Milliseconds before the next poll. You can also specify time values using units, such as 60s (60 seconds), 5m30s (5 minutes and 30 seconds), and 1h (1 hour). | 500L | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.greedy* | If greedy is enabled, then the ScheduledPollConsumer will run immediately again, if the previous run polled 1 or more messages. | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.initialDelay* | Milliseconds before the first poll starts. You can also specify time values using units, such as 60s (60 seconds), 5m30s (5 minutes and 30 seconds), and 1h (1 hour). | 1000L | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.repeatCount* | Specifies a maximum limit of number of fires. So if you set it to 1, the scheduler will only fire once. If you set it to 5, it will only fire five times. A value of zero or negative means fire forever. | 0L | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.runLoggingLevel* | The consumer logs a start/complete log line when it polls. This option allows you to configure the logging level for that. One of: [TRACE] [DEBUG] [INFO] [WARN] [ERROR] [OFF] | "TRACE" | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.scheduledExecutorService* | Allows for configuring a custom/shared thread pool to use for the consumer. By default each consumer has its own single threaded thread pool. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.scheduler* | To use a cron scheduler from either camel-spring or camel-quartz component One of: [none] [spring] [quartz] | "none" | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.schedulerProperties* | To configure additional properties when using a custom scheduler or any of the Quartz, Spring based scheduler. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.startScheduler* | Whether the scheduler should be auto started. | true | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.timeUnit* | Time unit for initialDelay and delay options. One of: [NANOSECONDS] [MICROSECONDS] [MILLISECONDS] [SECONDS] [MINUTES] [HOURS] [DAYS] | "MILLISECONDS" | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.useFixedDelay* | Controls if fixed delay or fixed rate is used. See ScheduledExecutorService in JDK for details. | true | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.accessKey* | Amazon AWS Access Key | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.secretKey* | Amazon AWS Secret Key | null | ConfigDef.Importance.MEDIUM
+| *camel.component.aws-kinesis.accessKey* | Amazon AWS Access Key | null | ConfigDef.Importance.MEDIUM
+| *camel.component.aws-kinesis.region* | Amazon AWS Region | null | ConfigDef.Importance.MEDIUM
+| *camel.component.aws-kinesis.secretKey* | Amazon AWS Secret Key | null | ConfigDef.Importance.MEDIUM
+| *camel.component.aws-kinesis.bridgeErrorHandler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | ConfigDef.Importance.MEDIUM
+| *camel.component.aws-kinesis.basicPropertyBinding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+| *camel.component.aws-kinesis.configuration* | The AWS S3 default configuration | null | ConfigDef.Importance.MEDIUM
+|===
+
+
+// kafka-connector options: END
diff --git a/docs/modules/ROOT/pages/connectors/camel-aws-kms-kafka-sink-connector.adoc b/docs/modules/ROOT/pages/connectors/camel-aws-kms-kafka-sink-connector.adoc
new file mode 100644
index 0000000..07b1d94
--- /dev/null
+++ b/docs/modules/ROOT/pages/connectors/camel-aws-kms-kafka-sink-connector.adoc
@@ -0,0 +1,41 @@
+// kafka-connector options: START
+== camel-aws-kms-kafka-connector source configuration
+
+When using camel-aws-kms-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-aws-kms-kafka-connector</artifactId>
+ <version>x.x.x</version>
+ <!-- use the same version as your Camel Kafka connector version -->
+</dependency>
+----
+
+
+[width="100%",cols="2,5,^1,2",options="header"]
+|===
+| Name | Description | Default | Priority
+| *camel.sink.path.label* | Logical name | null | ConfigDef.Importance.HIGH
+| *camel.sink.endpoint.accessKey* | Amazon AWS Access Key | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.kmsClient* | To use a existing configured AWS KMS as client | null | ConfigDef.Importance.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 cre [...]
+| *camel.sink.endpoint.operation* | The operation to perform One of: [listKeys] [createKey] [disableKey] [scheduleKeyDeletion] [describeKey] [enableKey] | null | ConfigDef.Importance.HIGH
+| *camel.sink.endpoint.proxyHost* | To define a proxy host when instantiating the KMS client | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.proxyPort* | To define a proxy port when instantiating the KMS client | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.proxyProtocol* | To define a proxy protocol when instantiating the KMS client One of: [HTTP] [HTTPS] | "HTTPS" | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.region* | The region in which KMS client needs to work. When using this parameter, the configuration will expect the capitalized name of the region (for example AP_EAST_1) You'll need to use the name Regions.EU_WEST_1.name() | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.secretKey* | Amazon AWS Secret Key | null | ConfigDef.Importance.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 | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.synchronous* | Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). | false | ConfigDef.Importance.MEDIUM
+| *camel.component.aws-kms.accessKey* | Amazon AWS Access Key | null | ConfigDef.Importance.MEDIUM
+| *camel.component.aws-kms.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 [...]
+| *camel.component.aws-kms.region* | The region in which KMS client needs to work | null | ConfigDef.Importance.MEDIUM
+| *camel.component.aws-kms.secretKey* | Amazon AWS Secret Key | null | ConfigDef.Importance.MEDIUM
+| *camel.component.aws-kms.basicPropertyBinding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+| *camel.component.aws-kms.configuration* | The AWS KMS default configuration | null | ConfigDef.Importance.MEDIUM
+|===
+
+
+// kafka-connector options: END
diff --git a/docs/modules/ROOT/pages/connectors/camel-aws-lambda-kafka-sink-connector.adoc b/docs/modules/ROOT/pages/connectors/camel-aws-lambda-kafka-sink-connector.adoc
new file mode 100644
index 0000000..7ce802c
--- /dev/null
+++ b/docs/modules/ROOT/pages/connectors/camel-aws-lambda-kafka-sink-connector.adoc
@@ -0,0 +1,41 @@
+// kafka-connector options: START
+== camel-aws-lambda-kafka-connector source configuration
+
+When using camel-aws-lambda-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-aws-lambda-kafka-connector</artifactId>
+ <version>x.x.x</version>
+ <!-- use the same version as your Camel Kafka connector version -->
+</dependency>
+----
+
+
+[width="100%",cols="2,5,^1,2",options="header"]
+|===
+| Name | Description | Default | Priority
+| *camel.sink.path.function* | Name of the Lambda function. | null | ConfigDef.Importance.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 cre [...]
+| *camel.sink.endpoint.operation* | The operation to perform. It can be listFunctions, getFunction, createFunction, deleteFunction or invokeFunction One of: [listFunctions] [getFunction] [createAlias] [deleteAlias] [getAlias] [listAliases] [createFunction] [deleteFunction] [invokeFunction] [updateFunction] [createEventSourceMapping] [deleteEventSourceMapping] [listEventSourceMapping] [listTags] [tagResource] [untagResource] [publishVersion] [listVersions] | "invokeFunction" | ConfigDef.I [...]
+| *camel.sink.endpoint.region* | Amazon AWS Region. When using this parameter, the configuration will expect the capitalized name of the region (for example AP_EAST_1) You'll need to use the name Regions.EU_WEST_1.name() | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.awsLambdaClient* | To use a existing configured AwsLambdaClient as client | null | ConfigDef.Importance.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 | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.synchronous* | Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). | false | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.proxyHost* | To define a proxy host when instantiating the Lambda client | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.proxyPort* | To define a proxy port when instantiating the Lambda client | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.proxyProtocol* | To define a proxy protocol when instantiating the Lambda client One of: [HTTP] [HTTPS] | "HTTPS" | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.accessKey* | Amazon AWS Access Key | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.secretKey* | Amazon AWS Secret Key | null | ConfigDef.Importance.MEDIUM
+| *camel.component.aws-lambda.accessKey* | Amazon AWS Access Key | null | ConfigDef.Importance.MEDIUM
+| *camel.component.aws-lambda.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 t [...]
+| *camel.component.aws-lambda.region* | Amazon AWS Region | null | ConfigDef.Importance.MEDIUM
+| *camel.component.aws-lambda.secretKey* | Amazon AWS Secret Key | null | ConfigDef.Importance.MEDIUM
+| *camel.component.aws-lambda.basicPropertyBinding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+| *camel.component.aws-lambda.configuration* | The AWS Lambda default configuration | null | ConfigDef.Importance.MEDIUM
+|===
+
+
+// kafka-connector options: END
diff --git a/docs/modules/ROOT/pages/connectors/camel-aws-mq-kafka-sink-connector.adoc b/docs/modules/ROOT/pages/connectors/camel-aws-mq-kafka-sink-connector.adoc
new file mode 100644
index 0000000..947bf8d
--- /dev/null
+++ b/docs/modules/ROOT/pages/connectors/camel-aws-mq-kafka-sink-connector.adoc
@@ -0,0 +1,41 @@
+// kafka-connector options: START
+== camel-aws-mq-kafka-connector source configuration
+
+When using camel-aws-mq-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-aws-mq-kafka-connector</artifactId>
+ <version>x.x.x</version>
+ <!-- use the same version as your Camel Kafka connector version -->
+</dependency>
+----
+
+
+[width="100%",cols="2,5,^1,2",options="header"]
+|===
+| Name | Description | Default | Priority
+| *camel.sink.path.label* | Logical name | null | ConfigDef.Importance.HIGH
+| *camel.sink.endpoint.accessKey* | Amazon AWS Access Key | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.amazonMqClient* | To use a existing configured AmazonMQClient as client | null | ConfigDef.Importance.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 cre [...]
+| *camel.sink.endpoint.operation* | The operation to perform. It can be listBrokers,createBroker,deleteBroker One of: [listBrokers] [createBroker] [deleteBroker] [rebootBroker] [updateBroker] [describeBroker] | null | ConfigDef.Importance.HIGH
+| *camel.sink.endpoint.proxyHost* | To define a proxy host when instantiating the MQ client | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.proxyPort* | To define a proxy port when instantiating the MQ client | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.proxyProtocol* | To define a proxy protocol when instantiating the MQ client One of: [HTTP] [HTTPS] | "HTTPS" | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.region* | The region in which MQ client needs to work. When using this parameter, the configuration will expect the capitalized name of the region (for example AP_EAST_1) You'll need to use the name Regions.EU_WEST_1.name() | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.secretKey* | Amazon AWS Secret Key | null | ConfigDef.Importance.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 | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.synchronous* | Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). | false | ConfigDef.Importance.MEDIUM
+| *camel.component.aws-mq.accessKey* | Amazon AWS Access Key | null | ConfigDef.Importance.MEDIUM
+| *camel.component.aws-mq.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 [...]
+| *camel.component.aws-mq.region* | The region in which MQ client needs to work | null | ConfigDef.Importance.MEDIUM
+| *camel.component.aws-mq.secretKey* | Amazon AWS Secret Key | null | ConfigDef.Importance.MEDIUM
+| *camel.component.aws-mq.basicPropertyBinding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+| *camel.component.aws-mq.configuration* | The AWS MQ default configuration | null | ConfigDef.Importance.MEDIUM
+|===
+
+
+// kafka-connector options: END
diff --git a/docs/modules/ROOT/pages/connectors/camel-aws-msk-kafka-sink-connector.adoc b/docs/modules/ROOT/pages/connectors/camel-aws-msk-kafka-sink-connector.adoc
new file mode 100644
index 0000000..a473abd
--- /dev/null
+++ b/docs/modules/ROOT/pages/connectors/camel-aws-msk-kafka-sink-connector.adoc
@@ -0,0 +1,41 @@
+// kafka-connector options: START
+== camel-aws-msk-kafka-connector source configuration
+
+When using camel-aws-msk-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-aws-msk-kafka-connector</artifactId>
+ <version>x.x.x</version>
+ <!-- use the same version as your Camel Kafka connector version -->
+</dependency>
+----
+
+
+[width="100%",cols="2,5,^1,2",options="header"]
+|===
+| Name | Description | Default | Priority
+| *camel.sink.path.label* | Logical name | null | ConfigDef.Importance.HIGH
+| *camel.sink.endpoint.accessKey* | Amazon AWS Access Key | null | ConfigDef.Importance.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 cre [...]
+| *camel.sink.endpoint.mskClient* | To use a existing configured AWS MSK as client | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.operation* | The operation to perform One of: [listClusters] [createCluster] [deleteCluster] [describeCluster] | null | ConfigDef.Importance.HIGH
+| *camel.sink.endpoint.proxyHost* | To define a proxy host when instantiating the MSK client | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.proxyPort* | To define a proxy port when instantiating the MSK client | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.proxyProtocol* | To define a proxy protocol when instantiating the MSK client One of: [HTTP] [HTTPS] | "HTTPS" | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.region* | The region in which MSK client needs to work. When using this parameter, the configuration will expect the capitalized name of the region (for example AP_EAST_1) You'll need to use the name Regions.EU_WEST_1.name() | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.secretKey* | Amazon AWS Secret Key | null | ConfigDef.Importance.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 | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.synchronous* | Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). | false | ConfigDef.Importance.MEDIUM
+| *camel.component.aws-msk.accessKey* | Amazon AWS Access Key | null | ConfigDef.Importance.MEDIUM
+| *camel.component.aws-msk.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 [...]
+| *camel.component.aws-msk.region* | The region in which MSK client needs to work | null | ConfigDef.Importance.MEDIUM
+| *camel.component.aws-msk.secretKey* | Amazon AWS Secret Key | null | ConfigDef.Importance.MEDIUM
+| *camel.component.aws-msk.basicPropertyBinding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+| *camel.component.aws-msk.configuration* | The AWS MSK default configuration | null | ConfigDef.Importance.MEDIUM
+|===
+
+
+// kafka-connector options: END
diff --git a/docs/modules/ROOT/pages/connectors/camel-aws-s3-kafka-sink-connector.adoc b/docs/modules/ROOT/pages/connectors/camel-aws-s3-kafka-sink-connector.adoc
new file mode 100644
index 0000000..1c2bc0f
--- /dev/null
+++ b/docs/modules/ROOT/pages/connectors/camel-aws-s3-kafka-sink-connector.adoc
@@ -0,0 +1,60 @@
+// kafka-connector options: START
+== camel-aws-s3-kafka-connector source configuration
+
+When using camel-aws-s3-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-aws-s3-kafka-connector</artifactId>
+ <version>x.x.x</version>
+ <!-- use the same version as your Camel Kafka connector version -->
+</dependency>
+----
+
+
+[width="100%",cols="2,5,^1,2",options="header"]
+|===
+| Name | Description | Default | Priority
+| *camel.sink.path.bucketNameOrArn* | Bucket name or ARN | null | ConfigDef.Importance.HIGH
+| *camel.sink.endpoint.amazonS3Client* | Reference to a com.amazonaws.services.s3.AmazonS3 in the registry. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.autoCreateBucket* | Setting the autocreation of the bucket | true | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.pathStyleAccess* | Whether or not the S3 client should use path style access | false | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.policy* | The policy for this queue to set in the com.amazonaws.services.s3.AmazonS3#setBucketPolicy() method. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.proxyHost* | To define a proxy host when instantiating the SQS client | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.proxyPort* | Specify a proxy port to be used inside the client definition. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.proxyProtocol* | To define a proxy protocol when instantiating the S3 client One of: [HTTP] [HTTPS] | "HTTPS" | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.region* | The region in which S3 client needs to work. When using this parameter, the configuration will expect the capitalized name of the region (for example AP_EAST_1) You'll need to use the name Regions.EU_WEST_1.name() | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.useIAMCredentials* | Set whether the S3 client should expect to load credentials on an EC2 instance or to expect static credentials to be passed in. | false | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.encryptionMaterials* | The encryption materials to use in case of Symmetric/Asymmetric client usage | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.useEncryption* | Define if encryption must be used or not | false | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.deleteAfterWrite* | Delete file object after the S3 file has been uploaded | false | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.keyName* | Setting the key name for an element in the bucket through endpoint parameter | null | ConfigDef.Importance.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 cre [...]
+| *camel.sink.endpoint.multiPartUpload* | If it is true, camel will upload the file with multi part format, the part size is decided by the option of partSize | false | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.operation* | The operation to do in case the user don't want to do only an upload One of: [copyObject] [deleteBucket] [listBuckets] [downloadLink] | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.partSize* | Setup the partSize which is used in multi part upload, the default size is 25M. | 26214400L | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.serverSideEncryption* | Sets the server-side encryption algorithm when encrypting the object using AWS-managed keys. For example use AES256. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.storageClass* | The storage class to set in the com.amazonaws.services.s3.model.PutObjectRequest request. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.awsKMSKeyId* | Define the id of KMS key to use in case KMS is enabled | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.useAwsKMS* | Define if KMS must be used or not | false | ConfigDef.Importance.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 | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.synchronous* | Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). | false | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.accelerateModeEnabled* | Define if Accelerate Mode enabled is true or false | false | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.chunkedEncodingDisabled* | Define if disabled Chunked Encoding is true or false | false | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.dualstackEnabled* | Define if Dualstack enabled is true or false | false | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.forceGlobalBucketAccessEnabled* | Define if Force Global Bucket Access enabled is true or false | false | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.payloadSigningEnabled* | Define if Payload Signing enabled is true or false | false | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.accessKey* | Amazon AWS Access Key | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.secretKey* | Amazon AWS Secret Key | null | ConfigDef.Importance.MEDIUM
+| *camel.component.aws-s3.accessKey* | Amazon AWS Access Key | null | ConfigDef.Importance.MEDIUM
+| *camel.component.aws-s3.region* | The region where the bucket is located. This option is used in the com.amazonaws.services.s3.model.CreateBucketRequest. | null | ConfigDef.Importance.MEDIUM
+| *camel.component.aws-s3.secretKey* | Amazon AWS Secret Key | null | ConfigDef.Importance.MEDIUM
+| *camel.component.aws-s3.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 [...]
+| *camel.component.aws-s3.basicPropertyBinding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+| *camel.component.aws-s3.configuration* | The AWS S3 default configuration | null | ConfigDef.Importance.MEDIUM
+|===
+
+
+// kafka-connector options: END
diff --git a/docs/modules/ROOT/pages/connectors/camel-aws-s3-kafka-source-connector.adoc b/docs/modules/ROOT/pages/connectors/camel-aws-s3-kafka-source-connector.adoc
new file mode 100644
index 0000000..93424af
--- /dev/null
+++ b/docs/modules/ROOT/pages/connectors/camel-aws-s3-kafka-source-connector.adoc
@@ -0,0 +1,77 @@
+// kafka-connector options: START
+== camel-aws-s3-kafka-connector source configuration
+
+When using camel-aws-s3-kafka-connector as source 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-aws-s3-kafka-connector</artifactId>
+ <version>x.x.x</version>
+ <!-- use the same version as your Camel Kafka connector version -->
+</dependency>
+----
+
+
+[width="100%",cols="2,5,^1,2",options="header"]
+|===
+| Name | Description | Default | Priority
+| *camel.source.path.bucketNameOrArn* | Bucket name or ARN | null | ConfigDef.Importance.HIGH
+| *camel.source.endpoint.amazonS3Client* | Reference to a com.amazonaws.services.s3.AmazonS3 in the registry. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.autoCreateBucket* | Setting the autocreation of the bucket | true | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.pathStyleAccess* | Whether or not the S3 client should use path style access | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.policy* | The policy for this queue to set in the com.amazonaws.services.s3.AmazonS3#setBucketPolicy() method. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.proxyHost* | To define a proxy host when instantiating the SQS client | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.proxyPort* | Specify a proxy port to be used inside the client definition. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.proxyProtocol* | To define a proxy protocol when instantiating the S3 client One of: [HTTP] [HTTPS] | "HTTPS" | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.region* | The region in which S3 client needs to work. When using this parameter, the configuration will expect the capitalized name of the region (for example AP_EAST_1) You'll need to use the name Regions.EU_WEST_1.name() | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.useIAMCredentials* | Set whether the S3 client should expect to load credentials on an EC2 instance or to expect static credentials to be passed in. | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.encryptionMaterials* | The encryption materials to use in case of Symmetric/Asymmetric client usage | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.useEncryption* | Define if encryption must be used or not | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.bridgeErrorHandler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.deleteAfterRead* | Delete objects from S3 after they have been retrieved. The delete is only performed if the Exchange is committed. If a rollback occurs, the object is not deleted. If this option is false, then the same objects will be retrieve over and over again on the polls. Therefore you need to use the Idempotent Consumer EIP in the route to filter out duplicates. You can filter using the S3Constants#BUCKET_NAME and S3Constants#KEY headers, or only the S3Co [...]
+| *camel.source.endpoint.delimiter* | The delimiter which is used in the com.amazonaws.services.s3.model.ListObjectsRequest to only consume objects we are interested in. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.fileName* | To get the object from the bucket with the given file name | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.includeBody* | If it is true, the exchange body will be set to a stream to the contents of the file. If false, the headers will be set with the S3 object metadata, but the body will be null. This option is strongly related to autocloseBody option. In case of setting includeBody to true and autocloseBody to false, it will be up to the caller to close the S3Object stream. Setting autocloseBody to true, will close the S3Object stream automatically. | true | ConfigDe [...]
+| *camel.source.endpoint.maxConnections* | Set the maxConnections parameter in the S3 client configuration | 60 | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.maxMessagesPerPoll* | Gets the maximum number of messages as a limit to poll at each polling. Gets the maximum number of messages as a limit to poll at each polling. The default value is 10. Use 0 or a negative number to set it as unlimited. | 10 | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.prefix* | The prefix which is used in the com.amazonaws.services.s3.model.ListObjectsRequest to only consume objects we are interested in. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.sendEmptyMessageWhenIdle* | If the polling consumer did not poll any files, you can enable this option to send an empty message (no body) instead. | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.autocloseBody* | If this option is true and includeBody is true, then the S3Object.close() method will be called on exchange completion. This option is strongly related to includeBody option. In case of setting includeBody to true and autocloseBody to false, it will be up to the caller to close the S3Object stream. Setting autocloseBody to true, will close the S3Object stream automatically. | true | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.exceptionHandler* | To let the consumer use a custom ExceptionHandler. Notice if the option bridgeErrorHandler is enabled then this option is not in use. By default the consumer will deal with exceptions, that will be logged at WARN or ERROR level and ignored. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.exchangePattern* | Sets the exchange pattern when the consumer creates an exchange. One of: [InOnly] [InOut] [InOptionalOut] | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.pollStrategy* | A pluggable org.apache.camel.PollingConsumerPollingStrategy allowing you to provide your custom implementation to control error handling usually occurred during the poll operation before an Exchange have been created and being routed in Camel. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.basicPropertyBinding* | Whether the endpoint should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.synchronous* | Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.accelerateModeEnabled* | Define if Accelerate Mode enabled is true or false | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.chunkedEncodingDisabled* | Define if disabled Chunked Encoding is true or false | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.dualstackEnabled* | Define if Dualstack enabled is true or false | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.forceGlobalBucketAccessEnabled* | Define if Force Global Bucket Access enabled is true or false | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.payloadSigningEnabled* | Define if Payload Signing enabled is true or false | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.backoffErrorThreshold* | The number of subsequent error polls (failed due some error) that should happen before the backoffMultipler should kick-in. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.backoffIdleThreshold* | The number of subsequent idle polls that should happen before the backoffMultipler should kick-in. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.backoffMultiplier* | To let the scheduled polling consumer backoff if there has been a number of subsequent idles/errors in a row. The multiplier is then the number of polls that will be skipped before the next actual attempt is happening again. When this option is in use then backoffIdleThreshold and/or backoffErrorThreshold must also be configured. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.delay* | Milliseconds before the next poll. You can also specify time values using units, such as 60s (60 seconds), 5m30s (5 minutes and 30 seconds), and 1h (1 hour). | 500L | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.greedy* | If greedy is enabled, then the ScheduledPollConsumer will run immediately again, if the previous run polled 1 or more messages. | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.initialDelay* | Milliseconds before the first poll starts. You can also specify time values using units, such as 60s (60 seconds), 5m30s (5 minutes and 30 seconds), and 1h (1 hour). | 1000L | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.repeatCount* | Specifies a maximum limit of number of fires. So if you set it to 1, the scheduler will only fire once. If you set it to 5, it will only fire five times. A value of zero or negative means fire forever. | 0L | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.runLoggingLevel* | The consumer logs a start/complete log line when it polls. This option allows you to configure the logging level for that. One of: [TRACE] [DEBUG] [INFO] [WARN] [ERROR] [OFF] | "TRACE" | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.scheduledExecutorService* | Allows for configuring a custom/shared thread pool to use for the consumer. By default each consumer has its own single threaded thread pool. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.scheduler* | To use a cron scheduler from either camel-spring or camel-quartz component One of: [none] [spring] [quartz] | "none" | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.schedulerProperties* | To configure additional properties when using a custom scheduler or any of the Quartz, Spring based scheduler. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.startScheduler* | Whether the scheduler should be auto started. | true | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.timeUnit* | Time unit for initialDelay and delay options. One of: [NANOSECONDS] [MICROSECONDS] [MILLISECONDS] [SECONDS] [MINUTES] [HOURS] [DAYS] | "MILLISECONDS" | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.useFixedDelay* | Controls if fixed delay or fixed rate is used. See ScheduledExecutorService in JDK for details. | true | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.accessKey* | Amazon AWS Access Key | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.secretKey* | Amazon AWS Secret Key | null | ConfigDef.Importance.MEDIUM
+| *camel.component.aws-s3.accessKey* | Amazon AWS Access Key | null | ConfigDef.Importance.MEDIUM
+| *camel.component.aws-s3.region* | The region where the bucket is located. This option is used in the com.amazonaws.services.s3.model.CreateBucketRequest. | null | ConfigDef.Importance.MEDIUM
+| *camel.component.aws-s3.secretKey* | Amazon AWS Secret Key | null | ConfigDef.Importance.MEDIUM
+| *camel.component.aws-s3.bridgeErrorHandler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | ConfigDef.Importance.MEDIUM
+| *camel.component.aws-s3.basicPropertyBinding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+| *camel.component.aws-s3.configuration* | The AWS S3 default configuration | null | ConfigDef.Importance.MEDIUM
+|===
+
+
+// kafka-connector options: END
diff --git a/docs/modules/ROOT/pages/connectors/camel-aws-sdb-kafka-sink-connector.adoc b/docs/modules/ROOT/pages/connectors/camel-aws-sdb-kafka-sink-connector.adoc
new file mode 100644
index 0000000..5c5e06a
--- /dev/null
+++ b/docs/modules/ROOT/pages/connectors/camel-aws-sdb-kafka-sink-connector.adoc
@@ -0,0 +1,39 @@
+// kafka-connector options: START
+== camel-aws-sdb-kafka-connector source configuration
+
+When using camel-aws-sdb-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-aws-sdb-kafka-connector</artifactId>
+ <version>x.x.x</version>
+ <!-- use the same version as your Camel Kafka connector version -->
+</dependency>
+----
+
+
+[width="100%",cols="2,5,^1,2",options="header"]
+|===
+| Name | Description | Default | Priority
+| *camel.sink.path.domainName* | The name of the domain currently worked with. | null | ConfigDef.Importance.HIGH
+| *camel.sink.endpoint.accessKey* | Amazon AWS Access Key | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.amazonSDBClient* | To use the AmazonSimpleDB as the client | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.consistentRead* | Determines whether or not strong consistency should be enforced when data is read. | false | ConfigDef.Importance.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 cre [...]
+| *camel.sink.endpoint.maxNumberOfDomains* | The maximum number of domain names you want returned. The range is 1 to 100. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.operation* | Operation to perform One of: [BatchDeleteAttributes] [BatchPutAttributes] [DeleteAttributes] [DeleteDomain] [DomainMetadata] [GetAttributes] [ListDomains] [PutAttributes] [Select] | "PutAttributes" | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.proxyHost* | To define a proxy host when instantiating the SDB client | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.proxyPort* | To define a proxy port when instantiating the SDB client | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.proxyProtocol* | To define a proxy protocol when instantiating the SDB client One of: [HTTP] [HTTPS] | "HTTPS" | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.region* | The region in which SDB client needs to work. When using this parameter, the configuration will expect the capitalized name of the region (for example AP_EAST_1) You'll need to use the name Regions.EU_WEST_1.name() | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.secretKey* | Amazon AWS Secret Key | null | ConfigDef.Importance.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 | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.synchronous* | Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). | false | ConfigDef.Importance.MEDIUM
+| *camel.component.aws-sdb.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 [...]
+| *camel.component.aws-sdb.basicPropertyBinding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+|===
+
+
+// kafka-connector options: END
diff --git a/docs/modules/ROOT/pages/connectors/camel-aws-ses-kafka-sink-connector.adoc b/docs/modules/ROOT/pages/connectors/camel-aws-ses-kafka-sink-connector.adoc
new file mode 100644
index 0000000..a10a005
--- /dev/null
+++ b/docs/modules/ROOT/pages/connectors/camel-aws-ses-kafka-sink-connector.adoc
@@ -0,0 +1,44 @@
+// kafka-connector options: START
+== camel-aws-ses-kafka-connector source configuration
+
+When using camel-aws-ses-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-aws-ses-kafka-connector</artifactId>
+ <version>x.x.x</version>
+ <!-- use the same version as your Camel Kafka connector version -->
+</dependency>
+----
+
+
+[width="100%",cols="2,5,^1,2",options="header"]
+|===
+| Name | Description | Default | Priority
+| *camel.sink.path.from* | The sender's email address. | null | ConfigDef.Importance.HIGH
+| *camel.sink.endpoint.amazonSESClient* | To use the AmazonSimpleEmailService as the client | null | ConfigDef.Importance.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 cre [...]
+| *camel.sink.endpoint.proxyHost* | To define a proxy host when instantiating the SES client | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.proxyPort* | To define a proxy port when instantiating the SES client | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.proxyProtocol* | To define a proxy protocol when instantiating the SES client One of: [HTTP] [HTTPS] | "HTTPS" | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.region* | The region in which SES client needs to work. When using this parameter, the configuration will expect the capitalized name of the region (for example AP_EAST_1) You'll need to use the name Regions.EU_WEST_1.name() | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.replyToAddresses* | List of reply-to email address(es) for the message, override it using 'CamelAwsSesReplyToAddresses' header. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.returnPath* | The email address to which bounce notifications are to be forwarded, override it using 'CamelAwsSesReturnPath' header. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.subject* | The subject which is used if the message header 'CamelAwsSesSubject' is not present. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.to* | List of destination email address. Can be overriden with 'CamelAwsSesTo' header. | null | ConfigDef.Importance.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 | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.synchronous* | Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). | false | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.accessKey* | Amazon AWS Access Key | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.secretKey* | Amazon AWS Secret Key | null | ConfigDef.Importance.MEDIUM
+| *camel.component.aws-ses.accessKey* | Amazon AWS Access Key | null | ConfigDef.Importance.MEDIUM
+| *camel.component.aws-ses.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 [...]
+| *camel.component.aws-ses.region* | The region in which SES client needs to work | null | ConfigDef.Importance.MEDIUM
+| *camel.component.aws-ses.secretKey* | Amazon AWS Secret Key | null | ConfigDef.Importance.MEDIUM
+| *camel.component.aws-ses.basicPropertyBinding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+| *camel.component.aws-ses.configuration* | The AWS SES default configuration | null | ConfigDef.Importance.MEDIUM
+|===
+
+
+// kafka-connector options: END
diff --git a/docs/modules/ROOT/pages/connectors/camel-aws-sns-kafka-sink-connector.adoc b/docs/modules/ROOT/pages/connectors/camel-aws-sns-kafka-sink-connector.adoc
new file mode 100644
index 0000000..778d173
--- /dev/null
+++ b/docs/modules/ROOT/pages/connectors/camel-aws-sns-kafka-sink-connector.adoc
@@ -0,0 +1,50 @@
+// kafka-connector options: START
+== camel-aws-sns-kafka-connector source configuration
+
+When using camel-aws-sns-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-aws-sns-kafka-connector</artifactId>
+ <version>x.x.x</version>
+ <!-- use the same version as your Camel Kafka connector version -->
+</dependency>
+----
+
+
+[width="100%",cols="2,5,^1,2",options="header"]
+|===
+| Name | Description | Default | Priority
+| *camel.sink.path.topicNameOrArn* | Topic name or ARN | null | ConfigDef.Importance.HIGH
+| *camel.sink.endpoint.amazonSNSClient* | To use the AmazonSNS as the client | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.amazonSQSClient* | An SQS Client to use as bridge between SNS and SQS | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.autoCreateTopic* | Setting the autocreation of the topic | true | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.headerFilterStrategy* | To use a custom HeaderFilterStrategy to map headers to/from Camel. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.kmsMasterKeyId* | The ID of an AWS-managed customer master key (CMK) for Amazon SNS or a custom CMK. | null | ConfigDef.Importance.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 cre [...]
+| *camel.sink.endpoint.messageStructure* | The message structure to use such as json | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.policy* | The policy for this queue | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.proxyHost* | To define a proxy host when instantiating the SNS client | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.proxyPort* | To define a proxy port when instantiating the SNS client | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.proxyProtocol* | To define a proxy protocol when instantiating the SNS client One of: [HTTP] [HTTPS] | "HTTPS" | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.queueUrl* | The queueUrl to subscribe to | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.region* | The region in which SNS client needs to work. When using this parameter, the configuration will expect the capitalized name of the region (for example AP_EAST_1) You'll need to use the name Regions.EU_WEST_1.name() | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.serverSideEncryptionEnabled* | Define if Server Side Encryption is enabled or not on the topic | false | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.subject* | The subject which is used if the message header 'CamelAwsSnsSubject' is not present. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.subscribeSNStoSQS* | Define if the subscription between SNS Topic and SQS must be done or not | false | ConfigDef.Importance.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 | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.synchronous* | Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). | false | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.accessKey* | Amazon AWS Access Key | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.secretKey* | Amazon AWS Secret Key | null | ConfigDef.Importance.MEDIUM
+| *camel.component.aws-sns.accessKey* | Amazon AWS Access Key | null | ConfigDef.Importance.MEDIUM
+| *camel.component.aws-sns.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 [...]
+| *camel.component.aws-sns.region* | The region in which SNS client needs to work | null | ConfigDef.Importance.MEDIUM
+| *camel.component.aws-sns.secretKey* | Amazon AWS Secret Key | null | ConfigDef.Importance.MEDIUM
+| *camel.component.aws-sns.basicPropertyBinding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+| *camel.component.aws-sns.configuration* | The AWS SNS default configuration | null | ConfigDef.Importance.MEDIUM
+|===
+
+
+// kafka-connector options: END
diff --git a/docs/modules/ROOT/pages/connectors/camel-aws-sqs-kafka-sink-connector.adoc b/docs/modules/ROOT/pages/connectors/camel-aws-sqs-kafka-sink-connector.adoc
new file mode 100644
index 0000000..4487a35
--- /dev/null
+++ b/docs/modules/ROOT/pages/connectors/camel-aws-sqs-kafka-sink-connector.adoc
@@ -0,0 +1,56 @@
+// kafka-connector options: START
+== camel-aws-sqs-kafka-connector source configuration
+
+When using camel-aws-sqs-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-aws-sqs-kafka-connector</artifactId>
+ <version>x.x.x</version>
+ <!-- use the same version as your Camel Kafka connector version -->
+</dependency>
+----
+
+
+[width="100%",cols="2,5,^1,2",options="header"]
+|===
+| Name | Description | Default | Priority
+| *camel.sink.path.queueNameOrArn* | Queue name or ARN | null | ConfigDef.Importance.HIGH
+| *camel.sink.endpoint.amazonAWSHost* | The hostname of the Amazon AWS cloud. | "amazonaws.com" | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.amazonSQSClient* | To use the AmazonSQS as client | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.autoCreateQueue* | Setting the autocreation of the queue | true | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.headerFilterStrategy* | To use a custom HeaderFilterStrategy to map headers to/from Camel. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.protocol* | The underlying protocol used to communicate with SQS | "https" | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.proxyProtocol* | To define a proxy protocol when instantiating the SQS client One of: [HTTP] [HTTPS] | "HTTPS" | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.queueOwnerAWSAccountId* | Specify the queue owner aws account id when you need to connect the queue with different account owner. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.region* | Specify the queue region which could be used with queueOwnerAWSAccountId to build the service URL. When using this parameter, the configuration will expect the capitalized name of the region (for example AP_EAST_1) You'll need to use the name Regions.EU_WEST_1.name() | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.delaySeconds* | Delay sending messages for a number of seconds. | null | ConfigDef.Importance.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 cre [...]
+| *camel.sink.endpoint.messageDeduplicationIdStrategy* | Only for FIFO queues. Strategy for setting the messageDeduplicationId on the message. Can be one of the following options: useExchangeId, useContentBasedDeduplication. For the useContentBasedDeduplication option, no messageDeduplicationId will be set on the message. One of: [useExchangeId] [useContentBasedDeduplication] | "useExchangeId" | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.messageGroupIdStrategy* | Only for FIFO queues. Strategy for setting the messageGroupId on the message. Can be one of the following options: useConstant, useExchangeId, usePropertyValue. For the usePropertyValue option, the value of property CamelAwsMessageGroupId will be used. One of: [useConstant] [useExchangeId] [usePropertyValue] | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.operation* | The operation to do in case the user don't want to send only a message One of: [sendBatchMessage] [deleteMessage] [listQueues] | null | ConfigDef.Importance.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 | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.delayQueue* | Define if you want to apply delaySeconds option to the queue or on single messages | false | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.queueUrl* | To define the queueUrl explicitly. All other parameters, which would influence the queueUrl, are ignored. This parameter is intended to be used, to connect to a mock implementation of SQS, for testing purposes. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.synchronous* | Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). | false | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.proxyHost* | To define a proxy host when instantiating the SQS client | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.proxyPort* | To define a proxy port when instantiating the SQS client | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.maximumMessageSize* | The maximumMessageSize (in bytes) an SQS message can contain for this queue. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.messageRetentionPeriod* | The messageRetentionPeriod (in seconds) a message will be retained by SQS for this queue. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.policy* | The policy for this queue | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.receiveMessageWaitTimeSeconds* | If you do not specify WaitTimeSeconds in the request, the queue attribute ReceiveMessageWaitTimeSeconds is used to determine how long to wait. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.redrivePolicy* | Specify the policy that send message to DeadLetter queue. See detail at Amazon docs. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.accessKey* | Amazon AWS Access Key | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.secretKey* | Amazon AWS Secret Key | null | ConfigDef.Importance.MEDIUM
+| *camel.component.aws-sqs.accessKey* | Amazon AWS Access Key | null | ConfigDef.Importance.MEDIUM
+| *camel.component.aws-sqs.region* | Specify the queue region which could be used with queueOwnerAWSAccountId to build the service URL. | null | ConfigDef.Importance.MEDIUM
+| *camel.component.aws-sqs.secretKey* | Amazon AWS Secret Key | null | ConfigDef.Importance.MEDIUM
+| *camel.component.aws-sqs.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 [...]
+| *camel.component.aws-sqs.basicPropertyBinding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+| *camel.component.aws-sqs.configuration* | The AWS SQS default configuration | null | ConfigDef.Importance.MEDIUM
+|===
+
+
+// kafka-connector options: END
diff --git a/docs/modules/ROOT/pages/connectors/camel-aws-sqs-kafka-source-connector.adoc b/docs/modules/ROOT/pages/connectors/camel-aws-sqs-kafka-source-connector.adoc
new file mode 100644
index 0000000..dd0c58d
--- /dev/null
+++ b/docs/modules/ROOT/pages/connectors/camel-aws-sqs-kafka-source-connector.adoc
@@ -0,0 +1,83 @@
+// kafka-connector options: START
+== camel-aws-sqs-kafka-connector source configuration
+
+When using camel-aws-sqs-kafka-connector as source 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-aws-sqs-kafka-connector</artifactId>
+ <version>x.x.x</version>
+ <!-- use the same version as your Camel Kafka connector version -->
+</dependency>
+----
+
+
+[width="100%",cols="2,5,^1,2",options="header"]
+|===
+| Name | Description | Default | Priority
+| *camel.source.path.queueNameOrArn* | Queue name or ARN | null | ConfigDef.Importance.HIGH
+| *camel.source.endpoint.amazonAWSHost* | The hostname of the Amazon AWS cloud. | "amazonaws.com" | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.amazonSQSClient* | To use the AmazonSQS as client | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.autoCreateQueue* | Setting the autocreation of the queue | true | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.headerFilterStrategy* | To use a custom HeaderFilterStrategy to map headers to/from Camel. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.protocol* | The underlying protocol used to communicate with SQS | "https" | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.proxyProtocol* | To define a proxy protocol when instantiating the SQS client One of: [HTTP] [HTTPS] | "HTTPS" | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.queueOwnerAWSAccountId* | Specify the queue owner aws account id when you need to connect the queue with different account owner. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.region* | Specify the queue region which could be used with queueOwnerAWSAccountId to build the service URL. When using this parameter, the configuration will expect the capitalized name of the region (for example AP_EAST_1) You'll need to use the name Regions.EU_WEST_1.name() | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.attributeNames* | A list of attribute names to receive when consuming. Multiple names can be separated by comma. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.bridgeErrorHandler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.concurrentConsumers* | Allows you to use multiple threads to poll the sqs queue to increase throughput | 1 | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.defaultVisibilityTimeout* | The default visibility timeout (in seconds) | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.deleteAfterRead* | Delete message from SQS after it has been read | true | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.deleteIfFiltered* | Whether or not to send the DeleteMessage to the SQS queue if an exchange fails to get through a filter. If 'false' and exchange does not make it through a Camel filter upstream in the route, then don't send DeleteMessage. | true | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.extendMessageVisibility* | If enabled then a scheduled background task will keep extending the message visibility on SQS. This is needed if it takes a long time to process the message. If set to true defaultVisibilityTimeout must be set. See details at Amazon docs. | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.kmsDataKeyReusePeriodSeconds* | The length of time, in seconds, for which Amazon SQS can reuse a data key to encrypt or decrypt messages before calling AWS KMS again. An integer representing seconds, between 60 seconds (1 minute) and 86,400 seconds (24 hours). Default: 300 (5 minutes). | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.kmsMasterKeyId* | The ID of an AWS-managed customer master key (CMK) for Amazon SQS or a custom CMK. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.maxMessagesPerPoll* | Gets the maximum number of messages as a limit to poll at each polling. Is default unlimited, but use 0 or negative number to disable it as unlimited. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.messageAttributeNames* | A list of message attribute names to receive when consuming. Multiple names can be separated by comma. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.sendEmptyMessageWhenIdle* | If the polling consumer did not poll any files, you can enable this option to send an empty message (no body) instead. | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.serverSideEncryptionEnabled* | Define if Server Side Encryption is enabled or not on the queue | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.visibilityTimeout* | The duration (in seconds) that the received messages are hidden from subsequent retrieve requests after being retrieved by a ReceiveMessage request to set in the com.amazonaws.services.sqs.model.SetQueueAttributesRequest. This only make sense if its different from defaultVisibilityTimeout. It changes the queue visibility timeout attribute permanently. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.waitTimeSeconds* | Duration in seconds (0 to 20) that the ReceiveMessage action call will wait until a message is in the queue to include in the response. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.exceptionHandler* | To let the consumer use a custom ExceptionHandler. Notice if the option bridgeErrorHandler is enabled then this option is not in use. By default the consumer will deal with exceptions, that will be logged at WARN or ERROR level and ignored. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.exchangePattern* | Sets the exchange pattern when the consumer creates an exchange. One of: [InOnly] [InOut] [InOptionalOut] | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.pollStrategy* | A pluggable org.apache.camel.PollingConsumerPollingStrategy allowing you to provide your custom implementation to control error handling usually occurred during the poll operation before an Exchange have been created and being routed in Camel. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.basicPropertyBinding* | Whether the endpoint should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.delayQueue* | Define if you want to apply delaySeconds option to the queue or on single messages | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.queueUrl* | To define the queueUrl explicitly. All other parameters, which would influence the queueUrl, are ignored. This parameter is intended to be used, to connect to a mock implementation of SQS, for testing purposes. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.synchronous* | Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.backoffErrorThreshold* | The number of subsequent error polls (failed due some error) that should happen before the backoffMultipler should kick-in. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.backoffIdleThreshold* | The number of subsequent idle polls that should happen before the backoffMultipler should kick-in. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.backoffMultiplier* | To let the scheduled polling consumer backoff if there has been a number of subsequent idles/errors in a row. The multiplier is then the number of polls that will be skipped before the next actual attempt is happening again. When this option is in use then backoffIdleThreshold and/or backoffErrorThreshold must also be configured. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.delay* | Milliseconds before the next poll. You can also specify time values using units, such as 60s (60 seconds), 5m30s (5 minutes and 30 seconds), and 1h (1 hour). | 500L | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.greedy* | If greedy is enabled, then the ScheduledPollConsumer will run immediately again, if the previous run polled 1 or more messages. | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.initialDelay* | Milliseconds before the first poll starts. You can also specify time values using units, such as 60s (60 seconds), 5m30s (5 minutes and 30 seconds), and 1h (1 hour). | 1000L | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.repeatCount* | Specifies a maximum limit of number of fires. So if you set it to 1, the scheduler will only fire once. If you set it to 5, it will only fire five times. A value of zero or negative means fire forever. | 0L | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.runLoggingLevel* | The consumer logs a start/complete log line when it polls. This option allows you to configure the logging level for that. One of: [TRACE] [DEBUG] [INFO] [WARN] [ERROR] [OFF] | "TRACE" | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.scheduledExecutorService* | Allows for configuring a custom/shared thread pool to use for the consumer. By default each consumer has its own single threaded thread pool. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.scheduler* | To use a cron scheduler from either camel-spring or camel-quartz component One of: [none] [spring] [quartz] | "none" | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.schedulerProperties* | To configure additional properties when using a custom scheduler or any of the Quartz, Spring based scheduler. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.startScheduler* | Whether the scheduler should be auto started. | true | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.timeUnit* | Time unit for initialDelay and delay options. One of: [NANOSECONDS] [MICROSECONDS] [MILLISECONDS] [SECONDS] [MINUTES] [HOURS] [DAYS] | "MILLISECONDS" | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.useFixedDelay* | Controls if fixed delay or fixed rate is used. See ScheduledExecutorService in JDK for details. | true | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.proxyHost* | To define a proxy host when instantiating the SQS client | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.proxyPort* | To define a proxy port when instantiating the SQS client | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.maximumMessageSize* | The maximumMessageSize (in bytes) an SQS message can contain for this queue. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.messageRetentionPeriod* | The messageRetentionPeriod (in seconds) a message will be retained by SQS for this queue. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.policy* | The policy for this queue | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.receiveMessageWaitTimeSeconds* | If you do not specify WaitTimeSeconds in the request, the queue attribute ReceiveMessageWaitTimeSeconds is used to determine how long to wait. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.redrivePolicy* | Specify the policy that send message to DeadLetter queue. See detail at Amazon docs. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.accessKey* | Amazon AWS Access Key | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.secretKey* | Amazon AWS Secret Key | null | ConfigDef.Importance.MEDIUM
+| *camel.component.aws-sqs.accessKey* | Amazon AWS Access Key | null | ConfigDef.Importance.MEDIUM
+| *camel.component.aws-sqs.region* | Specify the queue region which could be used with queueOwnerAWSAccountId to build the service URL. | null | ConfigDef.Importance.MEDIUM
+| *camel.component.aws-sqs.secretKey* | Amazon AWS Secret Key | null | ConfigDef.Importance.MEDIUM
+| *camel.component.aws-sqs.bridgeErrorHandler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | ConfigDef.Importance.MEDIUM
+| *camel.component.aws-sqs.basicPropertyBinding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+| *camel.component.aws-sqs.configuration* | The AWS SQS default configuration | null | ConfigDef.Importance.MEDIUM
+|===
+
+
+// kafka-connector options: END
diff --git a/docs/modules/ROOT/pages/connectors/camel-aws-swf-kafka-sink-connector.adoc b/docs/modules/ROOT/pages/connectors/camel-aws-swf-kafka-sink-connector.adoc
new file mode 100644
index 0000000..f169906
--- /dev/null
+++ b/docs/modules/ROOT/pages/connectors/camel-aws-swf-kafka-sink-connector.adoc
@@ -0,0 +1,53 @@
+// kafka-connector options: START
+== camel-aws-swf-kafka-connector source configuration
+
+When using camel-aws-swf-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-aws-swf-kafka-connector</artifactId>
+ <version>x.x.x</version>
+ <!-- use the same version as your Camel Kafka connector version -->
+</dependency>
+----
+
+
+[width="100%",cols="2,5,^1,2",options="header"]
+|===
+| Name | Description | Default | Priority
+| *camel.sink.path.type* | Activity or workflow One of: [activity] [workflow] | null | ConfigDef.Importance.HIGH
+| *camel.sink.endpoint.amazonSWClient* | To use the given AmazonSimpleWorkflowClient as client | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.dataConverter* | An instance of com.amazonaws.services.simpleworkflow.flow.DataConverter to use for serializing/deserializing the data. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.domainName* | The workflow domain to use. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.eventName* | The workflow or activity event name to use. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.region* | Amazon AWS Region. When using this parameter, the configuration will expect the capitalized name of the region (for example AP_EAST_1) You'll need to use the name Regions.EU_WEST_1.name() | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.version* | The workflow or activity event version to use. | null | ConfigDef.Importance.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 cre [...]
+| *camel.sink.endpoint.basicPropertyBinding* | Whether the endpoint should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.clientConfigurationParameters* | To configure the ClientConfiguration using the key/values from the Map. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.startWorkflowOptionsParameters* | To configure the StartWorkflowOptions using the key/values from the Map. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.sWClientParameters* | To configure the AmazonSimpleWorkflowClient using the key/values from the Map. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.synchronous* | Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). | false | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.activitySchedulingOptions* | Activity scheduling options | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.childPolicy* | The policy to use on child workflows when terminating a workflow. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.executionStartToCloseTimeout* | Set the execution start to close timeout. | "3600" | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.operation* | Workflow operation One of: [SIGNAL] [CANCEL] [TERMINATE] [GET_STATE] [START] [DESCRIBE] [GET_HISTORY] | "START" | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.signalName* | The name of the signal to send to the workflow. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.stateResultType* | The type of the result when a workflow state is queried. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.taskStartToCloseTimeout* | Set the task start to close timeout. | "600" | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.terminationDetails* | Details for terminating a workflow. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.terminationReason* | The reason for terminating a workflow. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.accessKey* | Amazon AWS Access Key. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.secretKey* | Amazon AWS Secret Key. | null | ConfigDef.Importance.MEDIUM
+| *camel.component.aws-swf.accessKey* | Amazon AWS Access Key. | null | ConfigDef.Importance.MEDIUM
+| *camel.component.aws-swf.region* | Amazon AWS Region. | null | ConfigDef.Importance.MEDIUM
+| *camel.component.aws-swf.secretKey* | Amazon AWS Secret Key. | null | ConfigDef.Importance.MEDIUM
+| *camel.component.aws-swf.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 [...]
+| *camel.component.aws-swf.basicPropertyBinding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+| *camel.component.aws-swf.configuration* | The AWS SWF default configuration | null | ConfigDef.Importance.MEDIUM
+|===
+
+
+// kafka-connector options: END
diff --git a/docs/modules/ROOT/pages/connectors/camel-aws-swf-kafka-source-connector.adoc b/docs/modules/ROOT/pages/connectors/camel-aws-swf-kafka-source-connector.adoc
new file mode 100644
index 0000000..dcf4aed
--- /dev/null
+++ b/docs/modules/ROOT/pages/connectors/camel-aws-swf-kafka-source-connector.adoc
@@ -0,0 +1,52 @@
+// kafka-connector options: START
+== camel-aws-swf-kafka-connector source configuration
+
+When using camel-aws-swf-kafka-connector as source 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-aws-swf-kafka-connector</artifactId>
+ <version>x.x.x</version>
+ <!-- use the same version as your Camel Kafka connector version -->
+</dependency>
+----
+
+
+[width="100%",cols="2,5,^1,2",options="header"]
+|===
+| Name | Description | Default | Priority
+| *camel.source.path.type* | Activity or workflow One of: [activity] [workflow] | null | ConfigDef.Importance.HIGH
+| *camel.source.endpoint.amazonSWClient* | To use the given AmazonSimpleWorkflowClient as client | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.dataConverter* | An instance of com.amazonaws.services.simpleworkflow.flow.DataConverter to use for serializing/deserializing the data. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.domainName* | The workflow domain to use. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.eventName* | The workflow or activity event name to use. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.region* | Amazon AWS Region. When using this parameter, the configuration will expect the capitalized name of the region (for example AP_EAST_1) You'll need to use the name Regions.EU_WEST_1.name() | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.version* | The workflow or activity event version to use. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.bridgeErrorHandler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.exceptionHandler* | To let the consumer use a custom ExceptionHandler. Notice if the option bridgeErrorHandler is enabled then this option is not in use. By default the consumer will deal with exceptions, that will be logged at WARN or ERROR level and ignored. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.exchangePattern* | Sets the exchange pattern when the consumer creates an exchange. One of: [InOnly] [InOut] [InOptionalOut] | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.basicPropertyBinding* | Whether the endpoint should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.clientConfigurationParameters* | To configure the ClientConfiguration using the key/values from the Map. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.startWorkflowOptionsParameters* | To configure the StartWorkflowOptions using the key/values from the Map. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.sWClientParameters* | To configure the AmazonSimpleWorkflowClient using the key/values from the Map. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.synchronous* | Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.activityList* | The list name to consume activities from. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.activityThreadPoolSize* | Maximum number of threads in work pool for activity. | 100 | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.activityTypeExecutionOptions* | Activity execution options | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.activityTypeRegistrationOptions* | Activity registration options | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.workflowList* | The list name to consume workflows from. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.workflowTypeRegistrationOptions* | Workflow registration options | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.accessKey* | Amazon AWS Access Key. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.secretKey* | Amazon AWS Secret Key. | null | ConfigDef.Importance.MEDIUM
+| *camel.component.aws-swf.accessKey* | Amazon AWS Access Key. | null | ConfigDef.Importance.MEDIUM
+| *camel.component.aws-swf.region* | Amazon AWS Region. | null | ConfigDef.Importance.MEDIUM
+| *camel.component.aws-swf.secretKey* | Amazon AWS Secret Key. | null | ConfigDef.Importance.MEDIUM
+| *camel.component.aws-swf.bridgeErrorHandler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | ConfigDef.Importance.MEDIUM
+| *camel.component.aws-swf.basicPropertyBinding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+| *camel.component.aws-swf.configuration* | The AWS SWF default configuration | null | ConfigDef.Importance.MEDIUM
+|===
+
+
+// kafka-connector options: END
diff --git a/docs/modules/ROOT/pages/connectors/camel-aws-translate-kafka-sink-connector.adoc b/docs/modules/ROOT/pages/connectors/camel-aws-translate-kafka-sink-connector.adoc
new file mode 100644
index 0000000..c0c9af3
--- /dev/null
+++ b/docs/modules/ROOT/pages/connectors/camel-aws-translate-kafka-sink-connector.adoc
@@ -0,0 +1,44 @@
+// kafka-connector options: START
+== camel-aws-translate-kafka-connector source configuration
+
+When using camel-aws-translate-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-aws-translate-kafka-connector</artifactId>
+ <version>x.x.x</version>
+ <!-- use the same version as your Camel Kafka connector version -->
+</dependency>
+----
+
+
+[width="100%",cols="2,5,^1,2",options="header"]
+|===
+| Name | Description | Default | Priority
+| *camel.sink.path.label* | Logical name | null | ConfigDef.Importance.HIGH
+| *camel.sink.endpoint.accessKey* | Amazon AWS Access Key | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.autodetectSourceLanguage* | Being able to autodetect the source language | false | ConfigDef.Importance.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 cre [...]
+| *camel.sink.endpoint.operation* | The operation to perform One of: [translateText] | "translateText" | ConfigDef.Importance.HIGH
+| *camel.sink.endpoint.proxyHost* | To define a proxy host when instantiating the Translate client | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.proxyPort* | To define a proxy port when instantiating the Translate client | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.proxyProtocol* | To define a proxy protocol when instantiating the Translate client One of: [HTTP] [HTTPS] | "HTTPS" | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.region* | The region in which Translate client needs to work. When using this parameter, the configuration will expect the capitalized name of the region (for example AP_EAST_1) You'll need to use the name Regions.EU_WEST_1.name() | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.secretKey* | Amazon AWS Secret Key | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.sourceLanguage* | Source language to use | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.targetLanguage* | Target language to use | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.translateClient* | To use a existing configured AWS Translate as client | null | ConfigDef.Importance.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 | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.synchronous* | Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). | false | ConfigDef.Importance.MEDIUM
+| *camel.component.aws-translate.accessKey* | Amazon AWS Access Key | null | ConfigDef.Importance.MEDIUM
+| *camel.component.aws-translate.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 processe [...]
+| *camel.component.aws-translate.region* | The region in which Translate client needs to work | null | ConfigDef.Importance.MEDIUM
+| *camel.component.aws-translate.secretKey* | Amazon AWS Secret Key | null | ConfigDef.Importance.MEDIUM
+| *camel.component.aws-translate.basicPropertyBinding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+| *camel.component.aws-translate.configuration* | The AWS Translate default configuration | null | ConfigDef.Importance.MEDIUM
+|===
+
+
+// kafka-connector options: END
diff --git a/docs/modules/ROOT/pages/connectors/camel-aws2-cw-kafka-sink-connector.adoc b/docs/modules/ROOT/pages/connectors/camel-aws2-cw-kafka-sink-connector.adoc
new file mode 100644
index 0000000..b2e0034
--- /dev/null
+++ b/docs/modules/ROOT/pages/connectors/camel-aws2-cw-kafka-sink-connector.adoc
@@ -0,0 +1,44 @@
+// kafka-connector options: START
+== camel-aws2-cw-kafka-connector source configuration
+
+When using camel-aws2-cw-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-aws2-cw-kafka-connector</artifactId>
+ <version>x.x.x</version>
+ <!-- use the same version as your Camel Kafka connector version -->
+</dependency>
+----
+
+
+[width="100%",cols="2,5,^1,2",options="header"]
+|===
+| Name | Description | Default | Priority
+| *camel.sink.path.namespace* | The metric namespace | null | ConfigDef.Importance.HIGH
+| *camel.sink.endpoint.amazonCwClient* | To use the AmazonCloudWatch as the client | null | ConfigDef.Importance.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 cre [...]
+| *camel.sink.endpoint.name* | The metric name | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.proxyHost* | To define a proxy host when instantiating the CW client | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.proxyPort* | To define a proxy port when instantiating the CW client | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.proxyProtocol* | To define a proxy protocol when instantiating the CW client One of: [HTTP] [HTTPS] | "HTTPS" | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.region* | The region in which EKS client needs to work. When using this parameter, the configuration will expect the lowercase name of the region (for example ap-east-1) You'll need to use the name Region.EU_WEST_1.id() | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.timestamp* | The metric timestamp | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.unit* | The metric unit | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.value* | The metric value | null | ConfigDef.Importance.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 | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.synchronous* | Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). | false | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.accessKey* | Amazon AWS Access Key | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.secretKey* | Amazon AWS Secret Key | null | ConfigDef.Importance.MEDIUM
+| *camel.component.aws2-cw.accessKey* | Amazon AWS Access Key | null | ConfigDef.Importance.MEDIUM
+| *camel.component.aws2-cw.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 [...]
+| *camel.component.aws2-cw.region* | The region in which CW client needs to work | null | ConfigDef.Importance.MEDIUM
+| *camel.component.aws2-cw.secretKey* | Amazon AWS Secret Key | null | ConfigDef.Importance.MEDIUM
+| *camel.component.aws2-cw.basicPropertyBinding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+| *camel.component.aws2-cw.configuration* | The AWS CW default configuration | null | ConfigDef.Importance.MEDIUM
+|===
+
+
+// kafka-connector options: END
diff --git a/docs/modules/ROOT/pages/connectors/camel-aws2-ddb-kafka-sink-connector.adoc b/docs/modules/ROOT/pages/connectors/camel-aws2-ddb-kafka-sink-connector.adoc
new file mode 100644
index 0000000..5ea9122
--- /dev/null
+++ b/docs/modules/ROOT/pages/connectors/camel-aws2-ddb-kafka-sink-connector.adoc
@@ -0,0 +1,46 @@
+// kafka-connector options: START
+== camel-aws2-ddb-kafka-connector source configuration
+
+When using camel-aws2-ddb-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-aws2-ddb-kafka-connector</artifactId>
+ <version>x.x.x</version>
+ <!-- use the same version as your Camel Kafka connector version -->
+</dependency>
+----
+
+
+[width="100%",cols="2,5,^1,2",options="header"]
+|===
+| Name | Description | Default | Priority
+| *camel.sink.path.tableName* | The name of the table currently worked with. | null | ConfigDef.Importance.HIGH
+| *camel.sink.endpoint.amazonDDBClient* | To use the AmazonDynamoDB as the client | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.consistentRead* | Determines whether or not strong consistency should be enforced when data is read. | false | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.keyAttributeName* | Attribute name when creating table | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.keyAttributeType* | Attribute type when creating table | null | ConfigDef.Importance.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 cre [...]
+| *camel.sink.endpoint.operation* | What operation to perform One of: [BatchGetItems] [DeleteItem] [DeleteTable] [DescribeTable] [GetItem] [PutItem] [Query] [Scan] [UpdateItem] [UpdateTable] | "PutItem" | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.proxyHost* | To define a proxy host when instantiating the DDB client | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.proxyPort* | The region in which DynamoDB client needs to work. When using this parameter, the configuration will expect the lowercase name of the region (for example ap-east-1) You'll need to use the name Region.EU_WEST_1.id() | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.proxyProtocol* | To define a proxy protocol when instantiating the DDB client One of: [HTTP] [HTTPS] | "HTTPS" | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.readCapacity* | The provisioned throughput to reserve for reading resources from your table | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.region* | The region in which DDB client needs to work | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.writeCapacity* | The provisioned throughput to reserved for writing resources to your table | null | ConfigDef.Importance.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 | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.synchronous* | Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). | false | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.accessKey* | Amazon AWS Access Key | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.secretKey* | Amazon AWS Secret Key | null | ConfigDef.Importance.MEDIUM
+| *camel.component.aws2-ddb.accessKey* | Amazon AWS Access Key | null | ConfigDef.Importance.MEDIUM
+| *camel.component.aws2-ddb.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 the [...]
+| *camel.component.aws2-ddb.region* | The region in which DDB client needs to work | null | ConfigDef.Importance.MEDIUM
+| *camel.component.aws2-ddb.secretKey* | Amazon AWS Secret Key | null | ConfigDef.Importance.MEDIUM
+| *camel.component.aws2-ddb.basicPropertyBinding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+| *camel.component.aws2-ddb.configuration* | The AWS DDB default configuration | null | ConfigDef.Importance.MEDIUM
+|===
+
+
+// kafka-connector options: END
diff --git a/docs/modules/ROOT/pages/connectors/camel-aws2-ddbstream-kafka-source-connector.adoc b/docs/modules/ROOT/pages/connectors/camel-aws2-ddbstream-kafka-source-connector.adoc
new file mode 100644
index 0000000..1a5faea
--- /dev/null
+++ b/docs/modules/ROOT/pages/connectors/camel-aws2-ddbstream-kafka-source-connector.adoc
@@ -0,0 +1,61 @@
+// kafka-connector options: START
+== camel-aws2-ddbstream-kafka-connector source configuration
+
+When using camel-aws2-ddbstream-kafka-connector as source 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-aws2-ddbstream-kafka-connector</artifactId>
+ <version>x.x.x</version>
+ <!-- use the same version as your Camel Kafka connector version -->
+</dependency>
+----
+
+
+[width="100%",cols="2,5,^1,2",options="header"]
+|===
+| Name | Description | Default | Priority
+| *camel.source.path.tableName* | Name of the dynamodb table | null | ConfigDef.Importance.HIGH
+| *camel.source.endpoint.amazonDynamoDbStreamsClient* | Amazon DynamoDB client to use for all requests for this endpoint | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.bridgeErrorHandler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.iteratorType* | Defines where in the DynaboDB stream to start getting records. Note that using TRIM_HORIZON can cause a significant delay before the stream has caught up to real-time. if {AT,AFTER}_SEQUENCE_NUMBER are used, then a sequenceNumberProvider MUST be supplied. One of: [TRIM_HORIZON] [LATEST] [AT_SEQUENCE_NUMBER] [AFTER_SEQUENCE_NUMBER] [null] | "LATEST" | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.maxResultsPerRequest* | Maximum number of records that will be fetched in each poll | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.proxyHost* | To define a proxy host when instantiating the DDBStreams client | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.proxyPort* | To define a proxy port when instantiating the DDBStreams client | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.proxyProtocol* | To define a proxy protocol when instantiating the DDBStreams client One of: [HTTP] [HTTPS] | "HTTPS" | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.region* | The region in which DDBStreams client needs to work | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.sendEmptyMessageWhenIdle* | If the polling consumer did not poll any files, you can enable this option to send an empty message (no body) instead. | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.sequenceNumberProvider* | Provider for the sequence number when using one of the two ShardIteratorType.{AT,AFTER}_SEQUENCE_NUMBER iterator types. Can be a registry reference or a literal sequence number. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.exceptionHandler* | To let the consumer use a custom ExceptionHandler. Notice if the option bridgeErrorHandler is enabled then this option is not in use. By default the consumer will deal with exceptions, that will be logged at WARN or ERROR level and ignored. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.exchangePattern* | Sets the exchange pattern when the consumer creates an exchange. One of: [InOnly] [InOut] [InOptionalOut] | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.pollStrategy* | A pluggable org.apache.camel.PollingConsumerPollingStrategy allowing you to provide your custom implementation to control error handling usually occurred during the poll operation before an Exchange have been created and being routed in Camel. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.basicPropertyBinding* | Whether the endpoint should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.synchronous* | Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.backoffErrorThreshold* | The number of subsequent error polls (failed due some error) that should happen before the backoffMultipler should kick-in. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.backoffIdleThreshold* | The number of subsequent idle polls that should happen before the backoffMultipler should kick-in. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.backoffMultiplier* | To let the scheduled polling consumer backoff if there has been a number of subsequent idles/errors in a row. The multiplier is then the number of polls that will be skipped before the next actual attempt is happening again. When this option is in use then backoffIdleThreshold and/or backoffErrorThreshold must also be configured. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.delay* | Milliseconds before the next poll. You can also specify time values using units, such as 60s (60 seconds), 5m30s (5 minutes and 30 seconds), and 1h (1 hour). | 500L | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.greedy* | If greedy is enabled, then the ScheduledPollConsumer will run immediately again, if the previous run polled 1 or more messages. | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.initialDelay* | Milliseconds before the first poll starts. You can also specify time values using units, such as 60s (60 seconds), 5m30s (5 minutes and 30 seconds), and 1h (1 hour). | 1000L | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.repeatCount* | Specifies a maximum limit of number of fires. So if you set it to 1, the scheduler will only fire once. If you set it to 5, it will only fire five times. A value of zero or negative means fire forever. | 0L | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.runLoggingLevel* | The consumer logs a start/complete log line when it polls. This option allows you to configure the logging level for that. One of: [TRACE] [DEBUG] [INFO] [WARN] [ERROR] [OFF] | "TRACE" | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.scheduledExecutorService* | Allows for configuring a custom/shared thread pool to use for the consumer. By default each consumer has its own single threaded thread pool. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.scheduler* | To use a cron scheduler from either camel-spring or camel-quartz component One of: [none] [spring] [quartz] | "none" | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.schedulerProperties* | To configure additional properties when using a custom scheduler or any of the Quartz, Spring based scheduler. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.startScheduler* | Whether the scheduler should be auto started. | true | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.timeUnit* | Time unit for initialDelay and delay options. One of: [NANOSECONDS] [MICROSECONDS] [MILLISECONDS] [SECONDS] [MINUTES] [HOURS] [DAYS] | "MILLISECONDS" | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.useFixedDelay* | Controls if fixed delay or fixed rate is used. See ScheduledExecutorService in JDK for details. | true | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.accessKey* | Amazon AWS Access Key | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.secretKey* | Amazon AWS Secret Key | null | ConfigDef.Importance.MEDIUM
+| *camel.component.aws2-ddbstream.accessKey* | Amazon AWS Access Key | null | ConfigDef.Importance.MEDIUM
+| *camel.component.aws2-ddbstream.bridgeErrorHandler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | ConfigDef.Importa [...]
+| *camel.component.aws2-ddbstream.region* | Amazon AWS Region | null | ConfigDef.Importance.MEDIUM
+| *camel.component.aws2-ddbstream.secretKey* | Amazon AWS Secret Key | null | ConfigDef.Importance.MEDIUM
+| *camel.component.aws2-ddbstream.basicPropertyBinding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+| *camel.component.aws2-ddbstream.configuration* | The AWS DDB stream default configuration | null | ConfigDef.Importance.MEDIUM
+|===
+
+
+// kafka-connector options: END
diff --git a/docs/modules/ROOT/pages/connectors/camel-aws2-ec2-kafka-sink-connector.adoc b/docs/modules/ROOT/pages/connectors/camel-aws2-ec2-kafka-sink-connector.adoc
new file mode 100644
index 0000000..cc5173f
--- /dev/null
+++ b/docs/modules/ROOT/pages/connectors/camel-aws2-ec2-kafka-sink-connector.adoc
@@ -0,0 +1,41 @@
+// kafka-connector options: START
+== camel-aws2-ec2-kafka-connector source configuration
+
+When using camel-aws2-ec2-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-aws2-ec2-kafka-connector</artifactId>
+ <version>x.x.x</version>
+ <!-- use the same version as your Camel Kafka connector version -->
+</dependency>
+----
+
+
+[width="100%",cols="2,5,^1,2",options="header"]
+|===
+| Name | Description | Default | Priority
+| *camel.sink.path.label* | Logical name | null | ConfigDef.Importance.HIGH
+| *camel.sink.endpoint.accessKey* | Amazon AWS Access Key | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.amazonEc2Client* | To use a existing configured AmazonEC2Client as client | null | ConfigDef.Importance.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 cre [...]
+| *camel.sink.endpoint.operation* | The operation to perform. It can be createAndRunInstances, startInstances, stopInstances, terminateInstances, describeInstances, describeInstancesStatus, rebootInstances, monitorInstances, unmonitorInstances, createTags or deleteTags One of: [createAndRunInstances] [startInstances] [stopInstances] [terminateInstances] [describeInstances] [describeInstancesStatus] [rebootInstances] [monitorInstances] [unmonitorInstances] [createTags] [deleteTags] | null [...]
+| *camel.sink.endpoint.proxyHost* | To define a proxy host when instantiating the EC2 client | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.proxyPort* | To define a proxy port when instantiating the EC2 client | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.proxyProtocol* | To define a proxy protocol when instantiating the EC2 client One of: [HTTP] [HTTPS] | "HTTPS" | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.region* | The region in which EC2 client needs to work. When using this parameter, the configuration will expect the capitalized name of the region (for example AP_EAST_1) You'll need to use the name Regions.EU_WEST_1.name() | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.secretKey* | Amazon AWS Secret Key | null | ConfigDef.Importance.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 | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.synchronous* | Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). | false | ConfigDef.Importance.MEDIUM
+| *camel.component.aws2-ec2.accessKey* | Amazon AWS Access Key | null | ConfigDef.Importance.MEDIUM
+| *camel.component.aws2-ec2.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 the [...]
+| *camel.component.aws2-ec2.region* | The region in which EC2 client needs to work | null | ConfigDef.Importance.MEDIUM
+| *camel.component.aws2-ec2.secretKey* | Amazon AWS Secret Key | null | ConfigDef.Importance.MEDIUM
+| *camel.component.aws2-ec2.basicPropertyBinding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+| *camel.component.aws2-ec2.configuration* | The AWS EC2 default configuration | null | ConfigDef.Importance.MEDIUM
+|===
+
+
+// kafka-connector options: END
diff --git a/docs/modules/ROOT/pages/connectors/camel-aws2-ecs-kafka-sink-connector.adoc b/docs/modules/ROOT/pages/connectors/camel-aws2-ecs-kafka-sink-connector.adoc
new file mode 100644
index 0000000..39cf1a7
--- /dev/null
+++ b/docs/modules/ROOT/pages/connectors/camel-aws2-ecs-kafka-sink-connector.adoc
@@ -0,0 +1,41 @@
+// kafka-connector options: START
+== camel-aws2-ecs-kafka-connector source configuration
+
+When using camel-aws2-ecs-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-aws2-ecs-kafka-connector</artifactId>
+ <version>x.x.x</version>
+ <!-- use the same version as your Camel Kafka connector version -->
+</dependency>
+----
+
+
+[width="100%",cols="2,5,^1,2",options="header"]
+|===
+| Name | Description | Default | Priority
+| *camel.sink.path.label* | Logical name | null | ConfigDef.Importance.HIGH
+| *camel.sink.endpoint.accessKey* | Amazon AWS Access Key | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.ecsClient* | To use a existing configured AWS ECS as client | null | ConfigDef.Importance.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 cre [...]
+| *camel.sink.endpoint.operation* | The operation to perform One of: [listClusters] [describeCluster] [createCluster] [deleteCluster] | null | ConfigDef.Importance.HIGH
+| *camel.sink.endpoint.proxyHost* | To define a proxy host when instantiating the ECS client | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.proxyPort* | To define a proxy port when instantiating the ECS client | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.proxyProtocol* | To define a proxy protocol when instantiating the ECS client One of: [HTTP] [HTTPS] | "HTTPS" | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.region* | The region in which ECS client needs to work. When using this parameter, the configuration will expect the lowercase name of the region (for example ap-east-1) You'll need to use the name Region.EU_WEST_1.id() | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.secretKey* | Amazon AWS Secret Key | null | ConfigDef.Importance.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 | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.synchronous* | Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). | false | ConfigDef.Importance.MEDIUM
+| *camel.component.aws2-ecs.accessKey* | Amazon AWS Access Key | null | ConfigDef.Importance.MEDIUM
+| *camel.component.aws2-ecs.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 the [...]
+| *camel.component.aws2-ecs.region* | The region in which ECS client needs to work | null | ConfigDef.Importance.MEDIUM
+| *camel.component.aws2-ecs.secretKey* | Amazon AWS Secret Key | null | ConfigDef.Importance.MEDIUM
+| *camel.component.aws2-ecs.basicPropertyBinding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+| *camel.component.aws2-ecs.configuration* | The AWS ECS default configuration | null | ConfigDef.Importance.MEDIUM
+|===
+
+
+// kafka-connector options: END
diff --git a/docs/modules/ROOT/pages/connectors/camel-aws2-eks-kafka-sink-connector.adoc b/docs/modules/ROOT/pages/connectors/camel-aws2-eks-kafka-sink-connector.adoc
new file mode 100644
index 0000000..4c3965c
--- /dev/null
+++ b/docs/modules/ROOT/pages/connectors/camel-aws2-eks-kafka-sink-connector.adoc
@@ -0,0 +1,41 @@
+// kafka-connector options: START
+== camel-aws2-eks-kafka-connector source configuration
+
+When using camel-aws2-eks-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-aws2-eks-kafka-connector</artifactId>
+ <version>x.x.x</version>
+ <!-- use the same version as your Camel Kafka connector version -->
+</dependency>
+----
+
+
+[width="100%",cols="2,5,^1,2",options="header"]
+|===
+| Name | Description | Default | Priority
+| *camel.sink.path.label* | Logical name | null | ConfigDef.Importance.HIGH
+| *camel.sink.endpoint.accessKey* | Amazon AWS Access Key | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.eksClient* | To use a existing configured AWS EKS as client | null | ConfigDef.Importance.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 cre [...]
+| *camel.sink.endpoint.operation* | The operation to perform One of: [listClusters] [describeCluster] [createCluster] [deleteCluster] | null | ConfigDef.Importance.HIGH
+| *camel.sink.endpoint.proxyHost* | To define a proxy host when instantiating the EKS client | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.proxyPort* | To define a proxy port when instantiating the EKS client | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.proxyProtocol* | To define a proxy protocol when instantiating the EKS client One of: [HTTP] [HTTPS] | "HTTPS" | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.region* | The region in which EKS client needs to work. When using this parameter, the configuration will expect the lowercase name of the region (for example ap-east-1) You'll need to use the name Region.EU_WEST_1.id() | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.secretKey* | Amazon AWS Secret Key | null | ConfigDef.Importance.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 | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.synchronous* | Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). | false | ConfigDef.Importance.MEDIUM
+| *camel.component.aws2-eks.accessKey* | Amazon AWS Access Key | null | ConfigDef.Importance.MEDIUM
+| *camel.component.aws2-eks.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 the [...]
+| *camel.component.aws2-eks.region* | The region in which EKS client needs to work | null | ConfigDef.Importance.MEDIUM
+| *camel.component.aws2-eks.secretKey* | Amazon AWS Secret Key | null | ConfigDef.Importance.MEDIUM
+| *camel.component.aws2-eks.basicPropertyBinding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+| *camel.component.aws2-eks.configuration* | The AWS EKS default configuration | null | ConfigDef.Importance.MEDIUM
+|===
+
+
+// kafka-connector options: END
diff --git a/docs/modules/ROOT/pages/connectors/camel-aws2-iam-kafka-sink-connector.adoc b/docs/modules/ROOT/pages/connectors/camel-aws2-iam-kafka-sink-connector.adoc
new file mode 100644
index 0000000..3c324d6
--- /dev/null
+++ b/docs/modules/ROOT/pages/connectors/camel-aws2-iam-kafka-sink-connector.adoc
@@ -0,0 +1,41 @@
+// kafka-connector options: START
+== camel-aws2-iam-kafka-connector source configuration
+
+When using camel-aws2-iam-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-aws2-iam-kafka-connector</artifactId>
+ <version>x.x.x</version>
+ <!-- use the same version as your Camel Kafka connector version -->
+</dependency>
+----
+
+
+[width="100%",cols="2,5,^1,2",options="header"]
+|===
+| Name | Description | Default | Priority
+| *camel.sink.path.label* | Logical name | null | ConfigDef.Importance.HIGH
+| *camel.sink.endpoint.accessKey* | Amazon AWS Access Key | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.iamClient* | To use a existing configured AWS IAM as client | null | ConfigDef.Importance.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 cre [...]
+| *camel.sink.endpoint.operation* | The operation to perform One of: [listAccessKeys] [createUser] [deleteUser] [getUser] [listUsers] [createAccessKey] [deleteAccessKey] [updateAccessKey] [createGroup] [deleteGroup] [listGroups] [addUserToGroup] [removeUserFromGroup] | null | ConfigDef.Importance.HIGH
+| *camel.sink.endpoint.proxyHost* | To define a proxy host when instantiating the IAM client | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.proxyPort* | To define a proxy port when instantiating the IAM client | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.proxyProtocol* | To define a proxy protocol when instantiating the IAM client One of: [HTTP] [HTTPS] | "HTTPS" | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.region* | The region in which IAM client needs to work. When using this parameter, the configuration will expect the lowercase name of the region (for example ap-east-1) You'll need to use the name Region.EU_WEST_1.id() | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.secretKey* | Amazon AWS Secret Key | null | ConfigDef.Importance.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 | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.synchronous* | Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). | false | ConfigDef.Importance.MEDIUM
+| *camel.component.aws2-iam.accessKey* | Amazon AWS Access Key | null | ConfigDef.Importance.MEDIUM
+| *camel.component.aws2-iam.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 the [...]
+| *camel.component.aws2-iam.region* | The region in which IAM client needs to work | null | ConfigDef.Importance.MEDIUM
+| *camel.component.aws2-iam.secretKey* | Amazon AWS Secret Key | null | ConfigDef.Importance.MEDIUM
+| *camel.component.aws2-iam.basicPropertyBinding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+| *camel.component.aws2-iam.configuration* | The AWS IAM default configuration | null | ConfigDef.Importance.MEDIUM
+|===
+
+
+// kafka-connector options: END
diff --git a/docs/modules/ROOT/pages/connectors/camel-aws2-kms-kafka-sink-connector.adoc b/docs/modules/ROOT/pages/connectors/camel-aws2-kms-kafka-sink-connector.adoc
new file mode 100644
index 0000000..bc63e2e
--- /dev/null
+++ b/docs/modules/ROOT/pages/connectors/camel-aws2-kms-kafka-sink-connector.adoc
@@ -0,0 +1,41 @@
+// kafka-connector options: START
+== camel-aws2-kms-kafka-connector source configuration
+
+When using camel-aws2-kms-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-aws2-kms-kafka-connector</artifactId>
+ <version>x.x.x</version>
+ <!-- use the same version as your Camel Kafka connector version -->
+</dependency>
+----
+
+
+[width="100%",cols="2,5,^1,2",options="header"]
+|===
+| Name | Description | Default | Priority
+| *camel.sink.path.label* | Logical name | null | ConfigDef.Importance.HIGH
+| *camel.sink.endpoint.accessKey* | Amazon AWS Access Key | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.kmsClient* | To use a existing configured AWS KMS as client | null | ConfigDef.Importance.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 cre [...]
+| *camel.sink.endpoint.operation* | The operation to perform One of: [listKeys] [createKey] [disableKey] [scheduleKeyDeletion] [describeKey] [enableKey] | null | ConfigDef.Importance.HIGH
+| *camel.sink.endpoint.proxyHost* | To define a proxy host when instantiating the KMS client | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.proxyPort* | To define a proxy port when instantiating the KMS client | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.proxyProtocol* | To define a proxy protocol when instantiating the KMS client One of: [HTTP] [HTTPS] | "HTTPS" | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.region* | The region in which EKS client needs to work. When using this parameter, the configuration will expect the lowercase name of the region (for example ap-east-1) You'll need to use the name Region.EU_WEST_1.id() | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.secretKey* | Amazon AWS Secret Key | null | ConfigDef.Importance.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 | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.synchronous* | Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). | false | ConfigDef.Importance.MEDIUM
+| *camel.component.aws2-kms.accessKey* | Amazon AWS Access Key | null | ConfigDef.Importance.MEDIUM
+| *camel.component.aws2-kms.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 the [...]
+| *camel.component.aws2-kms.region* | The region in which KMS client needs to work | null | ConfigDef.Importance.MEDIUM
+| *camel.component.aws2-kms.secretKey* | Amazon AWS Secret Key | null | ConfigDef.Importance.MEDIUM
+| *camel.component.aws2-kms.basicPropertyBinding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+| *camel.component.aws2-kms.configuration* | The AWS KMS default configuration | null | ConfigDef.Importance.MEDIUM
+|===
+
+
+// kafka-connector options: END
diff --git a/docs/modules/ROOT/pages/connectors/camel-aws2-mq-kafka-sink-connector.adoc b/docs/modules/ROOT/pages/connectors/camel-aws2-mq-kafka-sink-connector.adoc
new file mode 100644
index 0000000..ca83cef
--- /dev/null
+++ b/docs/modules/ROOT/pages/connectors/camel-aws2-mq-kafka-sink-connector.adoc
@@ -0,0 +1,41 @@
+// kafka-connector options: START
+== camel-aws2-mq-kafka-connector source configuration
+
+When using camel-aws2-mq-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-aws2-mq-kafka-connector</artifactId>
+ <version>x.x.x</version>
+ <!-- use the same version as your Camel Kafka connector version -->
+</dependency>
+----
+
+
+[width="100%",cols="2,5,^1,2",options="header"]
+|===
+| Name | Description | Default | Priority
+| *camel.sink.path.label* | Logical name | null | ConfigDef.Importance.HIGH
+| *camel.sink.endpoint.accessKey* | Amazon AWS Access Key | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.amazonMqClient* | To use a existing configured AmazonMQClient as client | null | ConfigDef.Importance.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 cre [...]
+| *camel.sink.endpoint.operation* | The operation to perform. It can be listBrokers,createBroker,deleteBroker One of: [listBrokers] [createBroker] [deleteBroker] [rebootBroker] [updateBroker] [describeBroker] | null | ConfigDef.Importance.HIGH
+| *camel.sink.endpoint.proxyHost* | To define a proxy host when instantiating the MQ client | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.proxyPort* | To define a proxy port when instantiating the MQ client | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.proxyProtocol* | To define a proxy protocol when instantiating the MQ client One of: [HTTP] [HTTPS] | "HTTPS" | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.region* | The region in which MQ client needs to work. When using this parameter, the configuration will expect the lowercase name of the region (for example ap-east-1) You'll need to use the name Region.EU_WEST_1.id() | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.secretKey* | Amazon AWS Secret Key | null | ConfigDef.Importance.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 | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.synchronous* | Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). | false | ConfigDef.Importance.MEDIUM
+| *camel.component.aws2-mq.accessKey* | Amazon AWS Access Key | null | ConfigDef.Importance.MEDIUM
+| *camel.component.aws2-mq.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 [...]
+| *camel.component.aws2-mq.region* | The region in which MQ client needs to work | null | ConfigDef.Importance.MEDIUM
+| *camel.component.aws2-mq.secretKey* | Amazon AWS Secret Key | null | ConfigDef.Importance.MEDIUM
+| *camel.component.aws2-mq.basicPropertyBinding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+| *camel.component.aws2-mq.configuration* | The AWS MQ default configuration | null | ConfigDef.Importance.MEDIUM
+|===
+
+
+// kafka-connector options: END
diff --git a/docs/modules/ROOT/pages/connectors/camel-aws2-msk-kafka-sink-connector.adoc b/docs/modules/ROOT/pages/connectors/camel-aws2-msk-kafka-sink-connector.adoc
new file mode 100644
index 0000000..582d11f
--- /dev/null
+++ b/docs/modules/ROOT/pages/connectors/camel-aws2-msk-kafka-sink-connector.adoc
@@ -0,0 +1,41 @@
+// kafka-connector options: START
+== camel-aws2-msk-kafka-connector source configuration
+
+When using camel-aws2-msk-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-aws2-msk-kafka-connector</artifactId>
+ <version>x.x.x</version>
+ <!-- use the same version as your Camel Kafka connector version -->
+</dependency>
+----
+
+
+[width="100%",cols="2,5,^1,2",options="header"]
+|===
+| Name | Description | Default | Priority
+| *camel.sink.path.label* | Logical name | null | ConfigDef.Importance.HIGH
+| *camel.sink.endpoint.accessKey* | Amazon AWS Access Key | null | ConfigDef.Importance.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 cre [...]
+| *camel.sink.endpoint.mskClient* | To use a existing configured AWS MSK as client | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.operation* | The operation to perform One of: [listClusters] [createCluster] [deleteCluster] [describeCluster] | null | ConfigDef.Importance.HIGH
+| *camel.sink.endpoint.proxyHost* | To define a proxy host when instantiating the MSK client | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.proxyPort* | To define a proxy port when instantiating the MSK client | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.proxyProtocol* | To define a proxy protocol when instantiating the MSK client One of: [HTTP] [HTTPS] | "HTTPS" | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.region* | The region in which MSK client needs to work. When using this parameter, the configuration will expect the lowercase name of the region (for example ap-east-1) You'll need to use the name Region.EU_WEST_1.id() | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.secretKey* | Amazon AWS Secret Key | null | ConfigDef.Importance.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 | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.synchronous* | Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). | false | ConfigDef.Importance.MEDIUM
+| *camel.component.aws2-msk.accessKey* | Amazon AWS Access Key | null | ConfigDef.Importance.MEDIUM
+| *camel.component.aws2-msk.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 the [...]
+| *camel.component.aws2-msk.region* | The region in which MSK client needs to work | null | ConfigDef.Importance.MEDIUM
+| *camel.component.aws2-msk.secretKey* | Amazon AWS Secret Key | null | ConfigDef.Importance.MEDIUM
+| *camel.component.aws2-msk.basicPropertyBinding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+| *camel.component.aws2-msk.configuration* | The AWS MSK default configuration | null | ConfigDef.Importance.MEDIUM
+|===
+
+
+// kafka-connector options: END
diff --git a/docs/modules/ROOT/pages/connectors/camel-aws2-ses-kafka-sink-connector.adoc b/docs/modules/ROOT/pages/connectors/camel-aws2-ses-kafka-sink-connector.adoc
new file mode 100644
index 0000000..e90851a
--- /dev/null
+++ b/docs/modules/ROOT/pages/connectors/camel-aws2-ses-kafka-sink-connector.adoc
@@ -0,0 +1,44 @@
+// kafka-connector options: START
+== camel-aws2-ses-kafka-connector source configuration
+
+When using camel-aws2-ses-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-aws2-ses-kafka-connector</artifactId>
+ <version>x.x.x</version>
+ <!-- use the same version as your Camel Kafka connector version -->
+</dependency>
+----
+
+
+[width="100%",cols="2,5,^1,2",options="header"]
+|===
+| Name | Description | Default | Priority
+| *camel.sink.path.from* | The sender's email address. | null | ConfigDef.Importance.HIGH
+| *camel.sink.endpoint.amazonSESClient* | To use the AmazonSimpleEmailService as the client | null | ConfigDef.Importance.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 cre [...]
+| *camel.sink.endpoint.proxyHost* | To define a proxy host when instantiating the SES client | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.proxyPort* | To define a proxy port when instantiating the SES client | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.proxyProtocol* | To define a proxy protocol when instantiating the SES client One of: [HTTP] [HTTPS] | "HTTPS" | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.region* | The region in which SES client needs to work. When using this parameter, the configuration will expect the lowercase name of the region (for example ap-east-1) You'll need to use the name Region.EU_WEST_1.id() | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.replyToAddresses* | List of reply-to email address(es) for the message, override it using 'CamelAwsSesReplyToAddresses' header. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.returnPath* | The email address to which bounce notifications are to be forwarded, override it using 'CamelAwsSesReturnPath' header. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.subject* | The subject which is used if the message header 'CamelAwsSesSubject' is not present. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.to* | List of destination email address. Can be overriden with 'CamelAwsSesTo' header. | null | ConfigDef.Importance.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 | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.synchronous* | Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). | false | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.accessKey* | Amazon AWS Access Key | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.secretKey* | Amazon AWS Secret Key | null | ConfigDef.Importance.MEDIUM
+| *camel.component.aws2-ses.accessKey* | Amazon AWS Access Key | null | ConfigDef.Importance.MEDIUM
+| *camel.component.aws2-ses.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 the [...]
+| *camel.component.aws2-ses.region* | The region in which SES client needs to work | null | ConfigDef.Importance.MEDIUM
+| *camel.component.aws2-ses.secretKey* | Amazon AWS Secret Key | null | ConfigDef.Importance.MEDIUM
+| *camel.component.aws2-ses.basicPropertyBinding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+| *camel.component.aws2-ses.configuration* | The AWS SES default configuration | null | ConfigDef.Importance.MEDIUM
+|===
+
+
+// kafka-connector options: END
diff --git a/docs/modules/ROOT/pages/connectors/camel-aws2-sns-kafka-sink-connector.adoc b/docs/modules/ROOT/pages/connectors/camel-aws2-sns-kafka-sink-connector.adoc
new file mode 100644
index 0000000..09fafb8
--- /dev/null
+++ b/docs/modules/ROOT/pages/connectors/camel-aws2-sns-kafka-sink-connector.adoc
@@ -0,0 +1,49 @@
+// kafka-connector options: START
+== camel-aws2-sns-kafka-connector source configuration
+
+When using camel-aws2-sns-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-aws2-sns-kafka-connector</artifactId>
+ <version>x.x.x</version>
+ <!-- use the same version as your Camel Kafka connector version -->
+</dependency>
+----
+
+
+[width="100%",cols="2,5,^1,2",options="header"]
+|===
+| Name | Description | Default | Priority
+| *camel.sink.path.topicNameOrArn* | Topic name or ARN | null | ConfigDef.Importance.HIGH
+| *camel.sink.endpoint.amazonSNSClient* | To use the AmazonSNS as the client | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.autoCreateTopic* | Setting the autocreation of the topic | true | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.headerFilterStrategy* | To use a custom HeaderFilterStrategy to map headers to/from Camel. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.kmsMasterKeyId* | The ID of an AWS-managed customer master key (CMK) for Amazon SNS or a custom CMK. | null | ConfigDef.Importance.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 cre [...]
+| *camel.sink.endpoint.messageStructure* | The message structure to use such as json | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.policy* | The policy for this queue | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.proxyHost* | To define a proxy host when instantiating the SNS client | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.proxyPort* | To define a proxy port when instantiating the SNS client | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.proxyProtocol* | To define a proxy protocol when instantiating the SNS client One of: [HTTP] [HTTPS] | "HTTPS" | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.queueUrl* | The queueUrl to subscribe to | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.region* | The region in which SNS client needs to work. When using this parameter, the configuration will expect the lowercase name of the region (for example ap-east-1) You'll need to use the name Region.EU_WEST_1.id() | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.serverSideEncryptionEnabled* | Define if Server Side Encryption is enabled or not on the topic | false | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.subject* | The subject which is used if the message header 'CamelAwsSnsSubject' is not present. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.subscribeSNStoSQS* | Define if the subscription between SNS Topic and SQS must be done or not | false | ConfigDef.Importance.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 | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.synchronous* | Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). | false | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.accessKey* | Amazon AWS Access Key | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.secretKey* | Amazon AWS Secret Key | null | ConfigDef.Importance.MEDIUM
+| *camel.component.aws2-sns.accessKey* | Amazon AWS Access Key | null | ConfigDef.Importance.MEDIUM
+| *camel.component.aws2-sns.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 the [...]
+| *camel.component.aws2-sns.region* | The region in which SNS client needs to work | null | ConfigDef.Importance.MEDIUM
+| *camel.component.aws2-sns.secretKey* | Amazon AWS Secret Key | null | ConfigDef.Importance.MEDIUM
+| *camel.component.aws2-sns.basicPropertyBinding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+| *camel.component.aws2-sns.configuration* | The AWS SNS default configuration | null | ConfigDef.Importance.MEDIUM
+|===
+
+
+// kafka-connector options: END
diff --git a/docs/modules/ROOT/pages/connectors/camel-aws2-sqs-kafka-sink-connector.adoc b/docs/modules/ROOT/pages/connectors/camel-aws2-sqs-kafka-sink-connector.adoc
new file mode 100644
index 0000000..98f4102
--- /dev/null
+++ b/docs/modules/ROOT/pages/connectors/camel-aws2-sqs-kafka-sink-connector.adoc
@@ -0,0 +1,56 @@
+// kafka-connector options: START
+== camel-aws2-sqs-kafka-connector source configuration
+
+When using camel-aws2-sqs-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-aws2-sqs-kafka-connector</artifactId>
+ <version>x.x.x</version>
+ <!-- use the same version as your Camel Kafka connector version -->
+</dependency>
+----
+
+
+[width="100%",cols="2,5,^1,2",options="header"]
+|===
+| Name | Description | Default | Priority
+| *camel.sink.path.queueNameOrArn* | Queue name or ARN | null | ConfigDef.Importance.HIGH
+| *camel.sink.endpoint.amazonAWSHost* | The hostname of the Amazon AWS cloud. | "amazonaws.com" | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.amazonSQSClient* | To use the AmazonSQS as client | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.autoCreateQueue* | Setting the autocreation of the queue | true | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.headerFilterStrategy* | To use a custom HeaderFilterStrategy to map headers to/from Camel. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.protocol* | The underlying protocol used to communicate with SQS | "https" | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.proxyProtocol* | To define a proxy protocol when instantiating the SQS client One of: [HTTP] [HTTPS] | "HTTPS" | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.queueOwnerAWSAccountId* | Specify the queue owner aws account id when you need to connect the queue with different account owner. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.region* | The region in which ECS client needs to work. When using this parameter, the configuration will expect the lowercase name of the region (for example ap-east-1) You'll need to use the name Region.EU_WEST_1.id() | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.delaySeconds* | Delay sending messages for a number of seconds. | null | ConfigDef.Importance.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 cre [...]
+| *camel.sink.endpoint.messageDeduplicationIdStrategy* | Only for FIFO queues. Strategy for setting the messageDeduplicationId on the message. Can be one of the following options: useExchangeId, useContentBasedDeduplication. For the useContentBasedDeduplication option, no messageDeduplicationId will be set on the message. One of: [useExchangeId] [useContentBasedDeduplication] | "useExchangeId" | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.messageGroupIdStrategy* | Only for FIFO queues. Strategy for setting the messageGroupId on the message. Can be one of the following options: useConstant, useExchangeId, usePropertyValue. For the usePropertyValue option, the value of property CamelAwsMessageGroupId will be used. One of: [useConstant] [useExchangeId] [usePropertyValue] | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.operation* | The operation to do in case the user don't want to send only a message One of: [sendBatchMessage] [deleteMessage] [listQueues] | null | ConfigDef.Importance.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 | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.delayQueue* | Define if you want to apply delaySeconds option to the queue or on single messages | false | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.queueUrl* | To define the queueUrl explicitly. All other parameters, which would influence the queueUrl, are ignored. This parameter is intended to be used, to connect to a mock implementation of SQS, for testing purposes. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.synchronous* | Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). | false | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.proxyHost* | To define a proxy host when instantiating the SQS client | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.proxyPort* | To define a proxy port when instantiating the SQS client | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.maximumMessageSize* | The maximumMessageSize (in bytes) an SQS message can contain for this queue. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.messageRetentionPeriod* | The messageRetentionPeriod (in seconds) a message will be retained by SQS for this queue. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.policy* | The policy for this queue | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.receiveMessageWaitTimeSeconds* | If you do not specify WaitTimeSeconds in the request, the queue attribute ReceiveMessageWaitTimeSeconds is used to determine how long to wait. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.redrivePolicy* | Specify the policy that send message to DeadLetter queue. See detail at Amazon docs. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.accessKey* | Amazon AWS Access Key | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.secretKey* | Amazon AWS Secret Key | null | ConfigDef.Importance.MEDIUM
+| *camel.component.aws2-sqs.accessKey* | Amazon AWS Access Key | null | ConfigDef.Importance.MEDIUM
+| *camel.component.aws2-sqs.region* | Specify the queue region which could be used with queueOwnerAWSAccountId to build the service URL. | null | ConfigDef.Importance.MEDIUM
+| *camel.component.aws2-sqs.secretKey* | Amazon AWS Secret Key | null | ConfigDef.Importance.MEDIUM
+| *camel.component.aws2-sqs.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 the [...]
+| *camel.component.aws2-sqs.basicPropertyBinding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+| *camel.component.aws2-sqs.configuration* | The AWS SQS default configuration | null | ConfigDef.Importance.MEDIUM
+|===
+
+
+// kafka-connector options: END
diff --git a/docs/modules/ROOT/pages/connectors/camel-aws2-sqs-kafka-source-connector.adoc b/docs/modules/ROOT/pages/connectors/camel-aws2-sqs-kafka-source-connector.adoc
new file mode 100644
index 0000000..0da578f
--- /dev/null
+++ b/docs/modules/ROOT/pages/connectors/camel-aws2-sqs-kafka-source-connector.adoc
@@ -0,0 +1,83 @@
+// kafka-connector options: START
+== camel-aws2-sqs-kafka-connector source configuration
+
+When using camel-aws2-sqs-kafka-connector as source 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-aws2-sqs-kafka-connector</artifactId>
+ <version>x.x.x</version>
+ <!-- use the same version as your Camel Kafka connector version -->
+</dependency>
+----
+
+
+[width="100%",cols="2,5,^1,2",options="header"]
+|===
+| Name | Description | Default | Priority
+| *camel.source.path.queueNameOrArn* | Queue name or ARN | null | ConfigDef.Importance.HIGH
+| *camel.source.endpoint.amazonAWSHost* | The hostname of the Amazon AWS cloud. | "amazonaws.com" | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.amazonSQSClient* | To use the AmazonSQS as client | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.autoCreateQueue* | Setting the autocreation of the queue | true | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.headerFilterStrategy* | To use a custom HeaderFilterStrategy to map headers to/from Camel. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.protocol* | The underlying protocol used to communicate with SQS | "https" | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.proxyProtocol* | To define a proxy protocol when instantiating the SQS client One of: [HTTP] [HTTPS] | "HTTPS" | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.queueOwnerAWSAccountId* | Specify the queue owner aws account id when you need to connect the queue with different account owner. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.region* | The region in which ECS client needs to work. When using this parameter, the configuration will expect the lowercase name of the region (for example ap-east-1) You'll need to use the name Region.EU_WEST_1.id() | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.attributeNames* | A list of attribute names to receive when consuming. Multiple names can be separated by comma. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.bridgeErrorHandler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.concurrentConsumers* | Allows you to use multiple threads to poll the sqs queue to increase throughput | 1 | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.defaultVisibilityTimeout* | The default visibility timeout (in seconds) | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.deleteAfterRead* | Delete message from SQS after it has been read | true | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.deleteIfFiltered* | Whether or not to send the DeleteMessage to the SQS queue if an exchange fails to get through a filter. If 'false' and exchange does not make it through a Camel filter upstream in the route, then don't send DeleteMessage. | true | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.extendMessageVisibility* | If enabled then a scheduled background task will keep extending the message visibility on SQS. This is needed if it takes a long time to process the message. If set to true defaultVisibilityTimeout must be set. See details at Amazon docs. | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.kmsDataKeyReusePeriodSeconds* | The length of time, in seconds, for which Amazon SQS can reuse a data key to encrypt or decrypt messages before calling AWS KMS again. An integer representing seconds, between 60 seconds (1 minute) and 86,400 seconds (24 hours). Default: 300 (5 minutes). | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.kmsMasterKeyId* | The ID of an AWS-managed customer master key (CMK) for Amazon SQS or a custom CMK. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.maxMessagesPerPoll* | Gets the maximum number of messages as a limit to poll at each polling. Is default unlimited, but use 0 or negative number to disable it as unlimited. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.messageAttributeNames* | A list of message attribute names to receive when consuming. Multiple names can be separated by comma. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.sendEmptyMessageWhenIdle* | If the polling consumer did not poll any files, you can enable this option to send an empty message (no body) instead. | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.serverSideEncryptionEnabled* | Define if Server Side Encryption is enabled or not on the queue | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.visibilityTimeout* | The duration (in seconds) that the received messages are hidden from subsequent retrieve requests after being retrieved by a ReceiveMessage request to set in the com.amazonaws.services.sqs.model.SetQueueAttributesRequest. This only make sense if its different from defaultVisibilityTimeout. It changes the queue visibility timeout attribute permanently. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.waitTimeSeconds* | Duration in seconds (0 to 20) that the ReceiveMessage action call will wait until a message is in the queue to include in the response. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.exceptionHandler* | To let the consumer use a custom ExceptionHandler. Notice if the option bridgeErrorHandler is enabled then this option is not in use. By default the consumer will deal with exceptions, that will be logged at WARN or ERROR level and ignored. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.exchangePattern* | Sets the exchange pattern when the consumer creates an exchange. One of: [InOnly] [InOut] [InOptionalOut] | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.pollStrategy* | A pluggable org.apache.camel.PollingConsumerPollingStrategy allowing you to provide your custom implementation to control error handling usually occurred during the poll operation before an Exchange have been created and being routed in Camel. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.basicPropertyBinding* | Whether the endpoint should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.delayQueue* | Define if you want to apply delaySeconds option to the queue or on single messages | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.queueUrl* | To define the queueUrl explicitly. All other parameters, which would influence the queueUrl, are ignored. This parameter is intended to be used, to connect to a mock implementation of SQS, for testing purposes. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.synchronous* | Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.backoffErrorThreshold* | The number of subsequent error polls (failed due some error) that should happen before the backoffMultipler should kick-in. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.backoffIdleThreshold* | The number of subsequent idle polls that should happen before the backoffMultipler should kick-in. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.backoffMultiplier* | To let the scheduled polling consumer backoff if there has been a number of subsequent idles/errors in a row. The multiplier is then the number of polls that will be skipped before the next actual attempt is happening again. When this option is in use then backoffIdleThreshold and/or backoffErrorThreshold must also be configured. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.delay* | Milliseconds before the next poll. You can also specify time values using units, such as 60s (60 seconds), 5m30s (5 minutes and 30 seconds), and 1h (1 hour). | 500L | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.greedy* | If greedy is enabled, then the ScheduledPollConsumer will run immediately again, if the previous run polled 1 or more messages. | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.initialDelay* | Milliseconds before the first poll starts. You can also specify time values using units, such as 60s (60 seconds), 5m30s (5 minutes and 30 seconds), and 1h (1 hour). | 1000L | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.repeatCount* | Specifies a maximum limit of number of fires. So if you set it to 1, the scheduler will only fire once. If you set it to 5, it will only fire five times. A value of zero or negative means fire forever. | 0L | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.runLoggingLevel* | The consumer logs a start/complete log line when it polls. This option allows you to configure the logging level for that. One of: [TRACE] [DEBUG] [INFO] [WARN] [ERROR] [OFF] | "TRACE" | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.scheduledExecutorService* | Allows for configuring a custom/shared thread pool to use for the consumer. By default each consumer has its own single threaded thread pool. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.scheduler* | To use a cron scheduler from either camel-spring or camel-quartz component One of: [none] [spring] [quartz] | "none" | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.schedulerProperties* | To configure additional properties when using a custom scheduler or any of the Quartz, Spring based scheduler. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.startScheduler* | Whether the scheduler should be auto started. | true | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.timeUnit* | Time unit for initialDelay and delay options. One of: [NANOSECONDS] [MICROSECONDS] [MILLISECONDS] [SECONDS] [MINUTES] [HOURS] [DAYS] | "MILLISECONDS" | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.useFixedDelay* | Controls if fixed delay or fixed rate is used. See ScheduledExecutorService in JDK for details. | true | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.proxyHost* | To define a proxy host when instantiating the SQS client | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.proxyPort* | To define a proxy port when instantiating the SQS client | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.maximumMessageSize* | The maximumMessageSize (in bytes) an SQS message can contain for this queue. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.messageRetentionPeriod* | The messageRetentionPeriod (in seconds) a message will be retained by SQS for this queue. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.policy* | The policy for this queue | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.receiveMessageWaitTimeSeconds* | If you do not specify WaitTimeSeconds in the request, the queue attribute ReceiveMessageWaitTimeSeconds is used to determine how long to wait. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.redrivePolicy* | Specify the policy that send message to DeadLetter queue. See detail at Amazon docs. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.accessKey* | Amazon AWS Access Key | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.secretKey* | Amazon AWS Secret Key | null | ConfigDef.Importance.MEDIUM
+| *camel.component.aws2-sqs.accessKey* | Amazon AWS Access Key | null | ConfigDef.Importance.MEDIUM
+| *camel.component.aws2-sqs.region* | Specify the queue region which could be used with queueOwnerAWSAccountId to build the service URL. | null | ConfigDef.Importance.MEDIUM
+| *camel.component.aws2-sqs.secretKey* | Amazon AWS Secret Key | null | ConfigDef.Importance.MEDIUM
+| *camel.component.aws2-sqs.bridgeErrorHandler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | ConfigDef.Importance.MEDIUM
+| *camel.component.aws2-sqs.basicPropertyBinding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+| *camel.component.aws2-sqs.configuration* | The AWS SQS default configuration | null | ConfigDef.Importance.MEDIUM
+|===
+
+
+// kafka-connector options: END
diff --git a/docs/modules/ROOT/pages/connectors/camel-aws2-translate-kafka-sink-connector.adoc b/docs/modules/ROOT/pages/connectors/camel-aws2-translate-kafka-sink-connector.adoc
new file mode 100644
index 0000000..c97b2c5
--- /dev/null
+++ b/docs/modules/ROOT/pages/connectors/camel-aws2-translate-kafka-sink-connector.adoc
@@ -0,0 +1,44 @@
+// kafka-connector options: START
+== camel-aws2-translate-kafka-connector source configuration
+
+When using camel-aws2-translate-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-aws2-translate-kafka-connector</artifactId>
+ <version>x.x.x</version>
+ <!-- use the same version as your Camel Kafka connector version -->
+</dependency>
+----
+
+
+[width="100%",cols="2,5,^1,2",options="header"]
+|===
+| Name | Description | Default | Priority
+| *camel.sink.path.label* | Logical name | null | ConfigDef.Importance.HIGH
+| *camel.sink.endpoint.accessKey* | Amazon AWS Access Key | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.autodetectSourceLanguage* | Being able to autodetect the source language | false | ConfigDef.Importance.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 cre [...]
+| *camel.sink.endpoint.operation* | The operation to perform One of: [translateText] | "translateText" | ConfigDef.Importance.HIGH
+| *camel.sink.endpoint.proxyHost* | To define a proxy host when instantiating the Translate client | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.proxyPort* | To define a proxy port when instantiating the Translate client | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.proxyProtocol* | To define a proxy protocol when instantiating the Translate client One of: [HTTP] [HTTPS] | "HTTPS" | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.region* | The region in which Translate client needs to work. When using this parameter, the configuration will expect the lowercase name of the region (for example ap-east-1) You'll need to use the name Region.EU_WEST_1.id() | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.secretKey* | Amazon AWS Secret Key | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.sourceLanguage* | Source language to use | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.targetLanguage* | Target language to use | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.translateClient* | To use a existing configured AWS Translate as client | null | ConfigDef.Importance.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 | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.synchronous* | Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). | false | ConfigDef.Importance.MEDIUM
+| *camel.component.aws2-translate.accessKey* | Amazon AWS Access Key | null | ConfigDef.Importance.MEDIUM
+| *camel.component.aws2-translate.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 process [...]
+| *camel.component.aws2-translate.region* | The region in which Translate client needs to work | null | ConfigDef.Importance.MEDIUM
+| *camel.component.aws2-translate.secretKey* | Amazon AWS Secret Key | null | ConfigDef.Importance.MEDIUM
+| *camel.component.aws2-translate.basicPropertyBinding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+| *camel.component.aws2-translate.configuration* | The AWS Translate default configuration | null | ConfigDef.Importance.MEDIUM
+|===
+
+
+// kafka-connector options: END
diff --git a/docs/modules/ROOT/pages/connectors/camel-azure-blob-kafka-sink-connector.adoc b/docs/modules/ROOT/pages/connectors/camel-azure-blob-kafka-sink-connector.adoc
new file mode 100644
index 0000000..e4c0940
--- /dev/null
+++ b/docs/modules/ROOT/pages/connectors/camel-azure-blob-kafka-sink-connector.adoc
@@ -0,0 +1,45 @@
+// kafka-connector options: START
+== camel-azure-blob-kafka-connector source configuration
+
+When using camel-azure-blob-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-azure-blob-kafka-connector</artifactId>
+ <version>x.x.x</version>
+ <!-- use the same version as your Camel Kafka connector version -->
+</dependency>
+----
+
+
+[width="100%",cols="2,5,^1,2",options="header"]
+|===
+| Name | Description | Default | Priority
+| *camel.sink.path.containerOrBlobUri* | Container or Blob compact Uri | null | ConfigDef.Importance.HIGH
+| *camel.sink.endpoint.azureBlobClient* | The blob service client | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.blobOffset* | Set the blob offset for the upload or download operations, default is 0 | "0" | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.blobType* | Set a blob type, 'blockblob' is default One of: [blockblob] [appendblob] [pageblob] | "blockblob" | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.closeStreamAfterRead* | Close the stream after read or keep it open, default is true | true | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.credentials* | Set the storage credentials, required in most cases | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.dataLength* | Set the data length for the download or page blob upload operations | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.fileDir* | Set the file directory where the downloaded blobs will be saved to | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.publicForRead* | Storage resources can be public for reading their content, if this property is enabled then the credentials do not have to be set | false | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.streamReadSize* | Set the minimum read size in bytes when reading the blob content | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.blobMetadata* | Set the blob meta-data | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.blobPrefix* | Set a prefix which can be used for listing the blobs | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.closeStreamAfterWrite* | Close the stream after write or keep it open, default is true | true | ConfigDef.Importance.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 cre [...]
+| *camel.sink.endpoint.operation* | Blob service operation hint to the producer One of: [getBlob] [deleteBlob] [listBlobs] [updateBlockBlob] [uploadBlobBlocks] [commitBlobBlockList] [getBlobBlockList] [createAppendBlob] [updateAppendBlob] [createPageBlob] [updatePageBlob] [resizePageBlob] [clearPageBlob] [getPageBlobRanges] | "listBlobs" | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.streamWriteSize* | Set the size of the buffer for writing block and page blocks | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.useFlatListing* | Specify if the flat or hierarchical blob listing should be used | true | ConfigDef.Importance.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 | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.synchronous* | Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). | false | ConfigDef.Importance.MEDIUM
+| *camel.component.azure-blob.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 t [...]
+| *camel.component.azure-blob.basicPropertyBinding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+| *camel.component.azure-blob.configuration* | The Blob Service configuration | null | ConfigDef.Importance.MEDIUM
+|===
+
+
+// kafka-connector options: END
diff --git a/docs/modules/ROOT/pages/connectors/camel-azure-blob-kafka-source-connector.adoc b/docs/modules/ROOT/pages/connectors/camel-azure-blob-kafka-source-connector.adoc
new file mode 100644
index 0000000..ecb4b9f
--- /dev/null
+++ b/docs/modules/ROOT/pages/connectors/camel-azure-blob-kafka-source-connector.adoc
@@ -0,0 +1,41 @@
+// kafka-connector options: START
+== camel-azure-blob-kafka-connector source configuration
+
+When using camel-azure-blob-kafka-connector as source 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-azure-blob-kafka-connector</artifactId>
+ <version>x.x.x</version>
+ <!-- use the same version as your Camel Kafka connector version -->
+</dependency>
+----
+
+
+[width="100%",cols="2,5,^1,2",options="header"]
+|===
+| Name | Description | Default | Priority
+| *camel.source.path.containerOrBlobUri* | Container or Blob compact Uri | null | ConfigDef.Importance.HIGH
+| *camel.source.endpoint.azureBlobClient* | The blob service client | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.blobOffset* | Set the blob offset for the upload or download operations, default is 0 | "0" | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.blobType* | Set a blob type, 'blockblob' is default One of: [blockblob] [appendblob] [pageblob] | "blockblob" | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.closeStreamAfterRead* | Close the stream after read or keep it open, default is true | true | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.credentials* | Set the storage credentials, required in most cases | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.dataLength* | Set the data length for the download or page blob upload operations | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.fileDir* | Set the file directory where the downloaded blobs will be saved to | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.publicForRead* | Storage resources can be public for reading their content, if this property is enabled then the credentials do not have to be set | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.streamReadSize* | Set the minimum read size in bytes when reading the blob content | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.bridgeErrorHandler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.exceptionHandler* | To let the consumer use a custom ExceptionHandler. Notice if the option bridgeErrorHandler is enabled then this option is not in use. By default the consumer will deal with exceptions, that will be logged at WARN or ERROR level and ignored. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.exchangePattern* | Sets the exchange pattern when the consumer creates an exchange. One of: [InOnly] [InOut] [InOptionalOut] | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.basicPropertyBinding* | Whether the endpoint should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.synchronous* | Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). | false | ConfigDef.Importance.MEDIUM
+| *camel.component.azure-blob.bridgeErrorHandler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | ConfigDef.Importance.MEDIUM
+| *camel.component.azure-blob.basicPropertyBinding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+| *camel.component.azure-blob.configuration* | The Blob Service configuration | null | ConfigDef.Importance.MEDIUM
+|===
+
+
+// kafka-connector options: END
diff --git a/docs/modules/ROOT/pages/connectors/camel-azure-queue-kafka-sink-connector.adoc b/docs/modules/ROOT/pages/connectors/camel-azure-queue-kafka-sink-connector.adoc
new file mode 100644
index 0000000..026e206
--- /dev/null
+++ b/docs/modules/ROOT/pages/connectors/camel-azure-queue-kafka-sink-connector.adoc
@@ -0,0 +1,36 @@
+// kafka-connector options: START
+== camel-azure-queue-kafka-connector source configuration
+
+When using camel-azure-queue-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-azure-queue-kafka-connector</artifactId>
+ <version>x.x.x</version>
+ <!-- use the same version as your Camel Kafka connector version -->
+</dependency>
+----
+
+
+[width="100%",cols="2,5,^1,2",options="header"]
+|===
+| Name | Description | Default | Priority
+| *camel.sink.path.containerAndQueueUri* | Container Queue compact Uri | null | ConfigDef.Importance.HIGH
+| *camel.sink.endpoint.azureQueueClient* | The queue service client | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.credentials* | Set the storage credentials, required in most cases | null | ConfigDef.Importance.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 cre [...]
+| *camel.sink.endpoint.messageTimeToLive* | Message Time To Live in seconds | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.messageVisibilityDelay* | Message Visibility Delay in seconds | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.operation* | Queue service operation hint to the producer One of: [listQueues] [createQueue] [deleteQueue] [addMessage] [retrieveMessage] [peekMessage] [updateMessage] [deleteMessage] | "listQueues" | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.queuePrefix* | Set a prefix which can be used for listing the queues | null | ConfigDef.Importance.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 | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.synchronous* | Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). | false | ConfigDef.Importance.MEDIUM
+| *camel.component.azure-queue.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 [...]
+| *camel.component.azure-queue.basicPropertyBinding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+| *camel.component.azure-queue.configuration* | The Queue Service configuration | null | ConfigDef.Importance.MEDIUM
+|===
+
+
+// kafka-connector options: END
diff --git a/docs/modules/ROOT/pages/connectors/camel-azure-queue-kafka-source-connector.adoc b/docs/modules/ROOT/pages/connectors/camel-azure-queue-kafka-source-connector.adoc
new file mode 100644
index 0000000..3f34a74
--- /dev/null
+++ b/docs/modules/ROOT/pages/connectors/camel-azure-queue-kafka-source-connector.adoc
@@ -0,0 +1,34 @@
+// kafka-connector options: START
+== camel-azure-queue-kafka-connector source configuration
+
+When using camel-azure-queue-kafka-connector as source 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-azure-queue-kafka-connector</artifactId>
+ <version>x.x.x</version>
+ <!-- use the same version as your Camel Kafka connector version -->
+</dependency>
+----
+
+
+[width="100%",cols="2,5,^1,2",options="header"]
+|===
+| Name | Description | Default | Priority
+| *camel.source.path.containerAndQueueUri* | Container Queue compact Uri | null | ConfigDef.Importance.HIGH
+| *camel.source.endpoint.azureQueueClient* | The queue service client | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.credentials* | Set the storage credentials, required in most cases | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.bridgeErrorHandler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.exceptionHandler* | To let the consumer use a custom ExceptionHandler. Notice if the option bridgeErrorHandler is enabled then this option is not in use. By default the consumer will deal with exceptions, that will be logged at WARN or ERROR level and ignored. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.exchangePattern* | Sets the exchange pattern when the consumer creates an exchange. One of: [InOnly] [InOut] [InOptionalOut] | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.basicPropertyBinding* | Whether the endpoint should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.synchronous* | Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). | false | ConfigDef.Importance.MEDIUM
+| *camel.component.azure-queue.bridgeErrorHandler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | ConfigDef.Importance.MEDIUM
+| *camel.component.azure-queue.basicPropertyBinding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+| *camel.component.azure-queue.configuration* | The Queue Service configuration | null | ConfigDef.Importance.MEDIUM
+|===
+
+
+// kafka-connector options: END
diff --git a/docs/modules/ROOT/pages/connectors/camel-bean-kafka-sink-connector.adoc b/docs/modules/ROOT/pages/connectors/camel-bean-kafka-sink-connector.adoc
new file mode 100644
index 0000000..45a8358
--- /dev/null
+++ b/docs/modules/ROOT/pages/connectors/camel-bean-kafka-sink-connector.adoc
@@ -0,0 +1,35 @@
+// kafka-connector options: START
+== camel-bean-kafka-connector source configuration
+
+When using camel-bean-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-bean-kafka-connector</artifactId>
+ <version>x.x.x</version>
+ <!-- use the same version as your Camel Kafka connector version -->
+</dependency>
+----
+
+
+[width="100%",cols="2,5,^1,2",options="header"]
+|===
+| Name | Description | Default | Priority
+| *camel.sink.path.beanName* | Sets the name of the bean to invoke | null | ConfigDef.Importance.HIGH
+| *camel.sink.endpoint.cache* | Use scope option instead. | null | ConfigDef.Importance.LOW
+| *camel.sink.endpoint.method* | Sets the name of the method to invoke on the bean | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.scope* | Scope of bean. When using singleton scope (default) the bean is created or looked up only once and reused for the lifetime of the endpoint. The bean should be thread-safe in case concurrent threads is calling the bean at the same time. When using request scope the bean is created or looked up once per request (exchange). This can be used if you want to store state on a bean while processing a request and you want to call the same bean instance multiple tim [...]
+| *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 cre [...]
+| *camel.sink.endpoint.basicPropertyBinding* | Whether the endpoint should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.parameters* | Used for configuring additional properties on the bean | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.synchronous* | Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). | false | ConfigDef.Importance.MEDIUM
+| *camel.component.bean.cache* | Use singleton option instead. | "true" | ConfigDef.Importance.LOW
+| *camel.component.bean.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 cr [...]
+| *camel.component.bean.scope* | Scope of bean. When using singleton scope (default) the bean is created or looked up only once and reused for the lifetime of the endpoint. The bean should be thread-safe in case concurrent threads is calling the bean at the same time. When using request scope the bean is created or looked up once per request (exchange). This can be used if you want to store state on a bean while processing a request and you want to call the same bean instance multiple ti [...]
+| *camel.component.bean.basicPropertyBinding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+|===
+
+
+// kafka-connector options: END
diff --git a/docs/modules/ROOT/pages/connectors/camel-bean-validator-kafka-sink-connector.adoc b/docs/modules/ROOT/pages/connectors/camel-bean-validator-kafka-sink-connector.adoc
new file mode 100644
index 0000000..020be4f
--- /dev/null
+++ b/docs/modules/ROOT/pages/connectors/camel-bean-validator-kafka-sink-connector.adoc
@@ -0,0 +1,41 @@
+// kafka-connector options: START
+== camel-bean-validator-kafka-connector source configuration
+
+When using camel-bean-validator-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-bean-validator-kafka-connector</artifactId>
+ <version>x.x.x</version>
+ <!-- use the same version as your Camel Kafka connector version -->
+</dependency>
+----
+
+
+[width="100%",cols="2,5,^1,2",options="header"]
+|===
+| Name | Description | Default | Priority
+| *camel.sink.path.label* | Where label is an arbitrary text value describing the endpoint | null | ConfigDef.Importance.HIGH
+| *camel.sink.endpoint.group* | To use a custom validation group | "javax.validation.groups.Default" | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.ignoreXmlConfiguration* | Whether to ignore data from the META-INF/validation.xml file. | false | ConfigDef.Importance.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 cre [...]
+| *camel.sink.endpoint.basicPropertyBinding* | Whether the endpoint should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.constraintValidatorFactory* | To use a custom ConstraintValidatorFactory | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.messageInterpolator* | To use a custom MessageInterpolator | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.synchronous* | Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). | false | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.traversableResolver* | To use a custom TraversableResolver | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.validationProviderResolver* | To use a a custom ValidationProviderResolver | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.validatorFactory* | To use a custom ValidatorFactory | null | ConfigDef.Importance.MEDIUM
+| *camel.component.bean-validator.ignoreXmlConfiguration* | Whether to ignore data from the META-INF/validation.xml file. | false | ConfigDef.Importance.MEDIUM
+| *camel.component.bean-validator.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 process [...]
+| *camel.component.bean-validator.basicPropertyBinding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+| *camel.component.bean-validator.constraintValidatorFactory* | To use a custom ConstraintValidatorFactory | null | ConfigDef.Importance.MEDIUM
+| *camel.component.bean-validator.messageInterpolator* | To use a custom MessageInterpolator | null | ConfigDef.Importance.MEDIUM
+| *camel.component.bean-validator.traversableResolver* | To use a custom TraversableResolver | null | ConfigDef.Importance.MEDIUM
+| *camel.component.bean-validator.validationProviderResolver* | To use a a custom ValidationProviderResolver | null | ConfigDef.Importance.MEDIUM
+|===
+
+
+// kafka-connector options: END
diff --git a/docs/modules/ROOT/pages/connectors/camel-beanstalk-kafka-sink-connector.adoc b/docs/modules/ROOT/pages/connectors/camel-beanstalk-kafka-sink-connector.adoc
new file mode 100644
index 0000000..dd4be8f
--- /dev/null
+++ b/docs/modules/ROOT/pages/connectors/camel-beanstalk-kafka-sink-connector.adoc
@@ -0,0 +1,34 @@
+// kafka-connector options: START
+== camel-beanstalk-kafka-connector source configuration
+
+When using camel-beanstalk-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-beanstalk-kafka-connector</artifactId>
+ <version>x.x.x</version>
+ <!-- use the same version as your Camel Kafka connector version -->
+</dependency>
+----
+
+
+[width="100%",cols="2,5,^1,2",options="header"]
+|===
+| Name | Description | Default | Priority
+| *camel.sink.path.connectionSettings* | Connection settings host:port/tube | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.command* | put means to put the job into Beanstalk. Job body is specified in the Camel message body. Job ID will be returned in beanstalk.jobId message header. delete, release, touch or bury expect Job ID in the message header beanstalk.jobId. Result of the operation is returned in beanstalk.result message header kick expects the number of jobs to kick in the message body and returns the number of jobs actually kicked out in the message header beanstalk.result. One [...]
+| *camel.sink.endpoint.jobDelay* | Job delay in seconds. | 0 | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.jobPriority* | Job priority. (0 is the highest, see Beanstalk protocol) | 1000L | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.jobTimeToRun* | Job time to run in seconds. (when 0, the beanstalkd daemon raises it to 1 automatically, see Beanstalk protocol) | 60 | ConfigDef.Importance.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 cre [...]
+| *camel.sink.endpoint.basicPropertyBinding* | Whether the endpoint should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.synchronous* | Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). | false | ConfigDef.Importance.MEDIUM
+| *camel.component.beanstalk.connectionSettingsFactory* | Custom ConnectionSettingsFactory. Specify which ConnectionSettingsFactory to use to make connections to Beanstalkd. Especially useful for unit testing without beanstalkd daemon (you can mock ConnectionSettings) | null | ConfigDef.Importance.MEDIUM
+| *camel.component.beanstalk.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 th [...]
+| *camel.component.beanstalk.basicPropertyBinding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+|===
+
+
+// kafka-connector options: END
diff --git a/docs/modules/ROOT/pages/connectors/camel-beanstalk-kafka-source-connector.adoc b/docs/modules/ROOT/pages/connectors/camel-beanstalk-kafka-source-connector.adoc
new file mode 100644
index 0000000..57013dc
--- /dev/null
+++ b/docs/modules/ROOT/pages/connectors/camel-beanstalk-kafka-source-connector.adoc
@@ -0,0 +1,55 @@
+// kafka-connector options: START
+== camel-beanstalk-kafka-connector source configuration
+
+When using camel-beanstalk-kafka-connector as source 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-beanstalk-kafka-connector</artifactId>
+ <version>x.x.x</version>
+ <!-- use the same version as your Camel Kafka connector version -->
+</dependency>
+----
+
+
+[width="100%",cols="2,5,^1,2",options="header"]
+|===
+| Name | Description | Default | Priority
+| *camel.source.path.connectionSettings* | Connection settings host:port/tube | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.command* | put means to put the job into Beanstalk. Job body is specified in the Camel message body. Job ID will be returned in beanstalk.jobId message header. delete, release, touch or bury expect Job ID in the message header beanstalk.jobId. Result of the operation is returned in beanstalk.result message header kick expects the number of jobs to kick in the message body and returns the number of jobs actually kicked out in the message header beanstalk.result. O [...]
+| *camel.source.endpoint.jobDelay* | Job delay in seconds. | 0 | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.jobPriority* | Job priority. (0 is the highest, see Beanstalk protocol) | 1000L | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.jobTimeToRun* | Job time to run in seconds. (when 0, the beanstalkd daemon raises it to 1 automatically, see Beanstalk protocol) | 60 | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.awaitJob* | Whether to wait for job to complete before ack the job from beanstalk | true | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.bridgeErrorHandler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.onFailure* | Command to use when processing failed. One of: [bury] [release] [put] [touch] [delete] [kick] | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.sendEmptyMessageWhenIdle* | If the polling consumer did not poll any files, you can enable this option to send an empty message (no body) instead. | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.useBlockIO* | Whether to use blockIO. | true | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.exceptionHandler* | To let the consumer use a custom ExceptionHandler. Notice if the option bridgeErrorHandler is enabled then this option is not in use. By default the consumer will deal with exceptions, that will be logged at WARN or ERROR level and ignored. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.exchangePattern* | Sets the exchange pattern when the consumer creates an exchange. One of: [InOnly] [InOut] [InOptionalOut] | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.pollStrategy* | A pluggable org.apache.camel.PollingConsumerPollingStrategy allowing you to provide your custom implementation to control error handling usually occurred during the poll operation before an Exchange have been created and being routed in Camel. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.basicPropertyBinding* | Whether the endpoint should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.synchronous* | Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.backoffErrorThreshold* | The number of subsequent error polls (failed due some error) that should happen before the backoffMultipler should kick-in. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.backoffIdleThreshold* | The number of subsequent idle polls that should happen before the backoffMultipler should kick-in. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.backoffMultiplier* | To let the scheduled polling consumer backoff if there has been a number of subsequent idles/errors in a row. The multiplier is then the number of polls that will be skipped before the next actual attempt is happening again. When this option is in use then backoffIdleThreshold and/or backoffErrorThreshold must also be configured. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.delay* | Milliseconds before the next poll. You can also specify time values using units, such as 60s (60 seconds), 5m30s (5 minutes and 30 seconds), and 1h (1 hour). | 500L | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.greedy* | If greedy is enabled, then the ScheduledPollConsumer will run immediately again, if the previous run polled 1 or more messages. | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.initialDelay* | Milliseconds before the first poll starts. You can also specify time values using units, such as 60s (60 seconds), 5m30s (5 minutes and 30 seconds), and 1h (1 hour). | 1000L | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.repeatCount* | Specifies a maximum limit of number of fires. So if you set it to 1, the scheduler will only fire once. If you set it to 5, it will only fire five times. A value of zero or negative means fire forever. | 0L | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.runLoggingLevel* | The consumer logs a start/complete log line when it polls. This option allows you to configure the logging level for that. One of: [TRACE] [DEBUG] [INFO] [WARN] [ERROR] [OFF] | "TRACE" | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.scheduledExecutorService* | Allows for configuring a custom/shared thread pool to use for the consumer. By default each consumer has its own single threaded thread pool. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.scheduler* | To use a cron scheduler from either camel-spring or camel-quartz component One of: [none] [spring] [quartz] | "none" | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.schedulerProperties* | To configure additional properties when using a custom scheduler or any of the Quartz, Spring based scheduler. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.startScheduler* | Whether the scheduler should be auto started. | true | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.timeUnit* | Time unit for initialDelay and delay options. One of: [NANOSECONDS] [MICROSECONDS] [MILLISECONDS] [SECONDS] [MINUTES] [HOURS] [DAYS] | "MILLISECONDS" | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.useFixedDelay* | Controls if fixed delay or fixed rate is used. See ScheduledExecutorService in JDK for details. | true | ConfigDef.Importance.MEDIUM
+| *camel.component.beanstalk.connectionSettingsFactory* | Custom ConnectionSettingsFactory. Specify which ConnectionSettingsFactory to use to make connections to Beanstalkd. Especially useful for unit testing without beanstalkd daemon (you can mock ConnectionSettings) | null | ConfigDef.Importance.MEDIUM
+| *camel.component.beanstalk.bridgeErrorHandler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | ConfigDef.Importance.MEDIUM
+| *camel.component.beanstalk.basicPropertyBinding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+|===
+
+
+// kafka-connector options: END
diff --git a/docs/modules/ROOT/pages/connectors/camel-bonita-kafka-sink-connector.adoc b/docs/modules/ROOT/pages/connectors/camel-bonita-kafka-sink-connector.adoc
new file mode 100644
index 0000000..a60dc90
--- /dev/null
+++ b/docs/modules/ROOT/pages/connectors/camel-bonita-kafka-sink-connector.adoc
@@ -0,0 +1,34 @@
+// kafka-connector options: START
+== camel-bonita-kafka-connector source configuration
+
+When using camel-bonita-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-bonita-kafka-connector</artifactId>
+ <version>x.x.x</version>
+ <!-- use the same version as your Camel Kafka connector version -->
+</dependency>
+----
+
+
+[width="100%",cols="2,5,^1,2",options="header"]
+|===
+| Name | Description | Default | Priority
+| *camel.sink.path.operation* | Operation to use One of: [startCase] | null | ConfigDef.Importance.HIGH
+| *camel.sink.endpoint.hostname* | Hostname where Bonita engine runs | "localhost" | ConfigDef.Importance.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 cre [...]
+| *camel.sink.endpoint.port* | Port of the server hosting Bonita engine | "8080" | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.processName* | Name of the process involved in the operation | null | ConfigDef.Importance.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 | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.synchronous* | Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). | false | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.password* | Password to authenticate to Bonita engine. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.username* | Username to authenticate to Bonita engine. | null | ConfigDef.Importance.MEDIUM
+| *camel.component.bonita.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 [...]
+| *camel.component.bonita.basicPropertyBinding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+|===
+
+
+// kafka-connector options: END
diff --git a/docs/modules/ROOT/pages/connectors/camel-box-kafka-sink-connector.adoc b/docs/modules/ROOT/pages/connectors/camel-box-kafka-sink-connector.adoc
new file mode 100644
index 0000000..df63f61
--- /dev/null
+++ b/docs/modules/ROOT/pages/connectors/camel-box-kafka-sink-connector.adoc
@@ -0,0 +1,47 @@
+// kafka-connector options: START
+== camel-box-kafka-connector source configuration
+
+When using camel-box-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-box-kafka-connector</artifactId>
+ <version>x.x.x</version>
+ <!-- use the same version as your Camel Kafka connector version -->
+</dependency>
+----
+
+
+[width="100%",cols="2,5,^1,2",options="header"]
+|===
+| Name | Description | Default | Priority
+| *camel.sink.path.apiName* | What kind of operation to perform One of: [COLLABORATIONS] [COMMENTS] [EVENT_LOGS] [FILES] [FOLDERS] [GROUPS] [EVENTS] [SEARCH] [TASKS] [USERS] | null | ConfigDef.Importance.HIGH
+| *camel.sink.path.methodName* | What sub operation to use for the selected operation | null | ConfigDef.Importance.HIGH
+| *camel.sink.endpoint.clientId* | Box application client ID | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.enterpriseId* | The enterprise ID to use for an App Enterprise. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.inBody* | Sets the name of a parameter to be passed in the exchange In Body | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.userId* | The user ID to use for an App User. | null | ConfigDef.Importance.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 cre [...]
+| *camel.sink.endpoint.basicPropertyBinding* | Whether the endpoint should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.httpParams* | Custom HTTP params for settings like proxy host | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.synchronous* | Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). | false | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.accessTokenCache* | Custom Access Token Cache for storing and retrieving access tokens. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.clientSecret* | Box application client secret | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.encryptionAlgorithm* | The type of encryption algorithm for JWT. Supported Algorithms: RSA_SHA_256 RSA_SHA_384 RSA_SHA_512 One of: [RSA_SHA_256] [RSA_SHA_384] [RSA_SHA_512] | "RSA_SHA_256" | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.maxCacheEntries* | The maximum number of access tokens in cache. | 100 | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.authenticationType* | The type of authentication for connection. Types of Authentication: STANDARD_AUTHENTICATION - OAuth 2.0 (3-legged) SERVER_AUTHENTICATION - OAuth 2.0 with JSON Web Tokens | "APP_USER_AUTHENTICATION" | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.privateKeyFile* | The private key for generating the JWT signature. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.privateKeyPassword* | The password for the private key. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.publicKeyId* | The ID for public key for validating the JWT signature. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.sslContextParameters* | To configure security using SSLContextParameters. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.userName* | Box user name, MUST be provided | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.userPassword* | Box user password, MUST be provided if authSecureStorage is not set, or returns null on first call | null | ConfigDef.Importance.MEDIUM
+| *camel.component.box.configuration* | To use the shared configuration | null | ConfigDef.Importance.MEDIUM
+| *camel.component.box.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 cre [...]
+| *camel.component.box.basicPropertyBinding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+|===
+
+
+// kafka-connector options: END
diff --git a/docs/modules/ROOT/pages/connectors/camel-box-kafka-source-connector.adoc b/docs/modules/ROOT/pages/connectors/camel-box-kafka-source-connector.adoc
new file mode 100644
index 0000000..8a694b4
--- /dev/null
+++ b/docs/modules/ROOT/pages/connectors/camel-box-kafka-source-connector.adoc
@@ -0,0 +1,65 @@
+// kafka-connector options: START
+== camel-box-kafka-connector source configuration
+
+When using camel-box-kafka-connector as source 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-box-kafka-connector</artifactId>
+ <version>x.x.x</version>
+ <!-- use the same version as your Camel Kafka connector version -->
+</dependency>
+----
+
+
+[width="100%",cols="2,5,^1,2",options="header"]
+|===
+| Name | Description | Default | Priority
+| *camel.source.path.apiName* | What kind of operation to perform One of: [COLLABORATIONS] [COMMENTS] [EVENT_LOGS] [FILES] [FOLDERS] [GROUPS] [EVENTS] [SEARCH] [TASKS] [USERS] | null | ConfigDef.Importance.HIGH
+| *camel.source.path.methodName* | What sub operation to use for the selected operation | null | ConfigDef.Importance.HIGH
+| *camel.source.endpoint.clientId* | Box application client ID | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.enterpriseId* | The enterprise ID to use for an App Enterprise. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.inBody* | Sets the name of a parameter to be passed in the exchange In Body | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.userId* | The user ID to use for an App User. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.bridgeErrorHandler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.sendEmptyMessageWhenIdle* | If the polling consumer did not poll any files, you can enable this option to send an empty message (no body) instead. | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.exceptionHandler* | To let the consumer use a custom ExceptionHandler. Notice if the option bridgeErrorHandler is enabled then this option is not in use. By default the consumer will deal with exceptions, that will be logged at WARN or ERROR level and ignored. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.exchangePattern* | Sets the exchange pattern when the consumer creates an exchange. One of: [InOnly] [InOut] [InOptionalOut] | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.pollStrategy* | A pluggable org.apache.camel.PollingConsumerPollingStrategy allowing you to provide your custom implementation to control error handling usually occurred during the poll operation before an Exchange have been created and being routed in Camel. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.basicPropertyBinding* | Whether the endpoint should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.httpParams* | Custom HTTP params for settings like proxy host | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.synchronous* | Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.accessTokenCache* | Custom Access Token Cache for storing and retrieving access tokens. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.backoffErrorThreshold* | The number of subsequent error polls (failed due some error) that should happen before the backoffMultipler should kick-in. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.backoffIdleThreshold* | The number of subsequent idle polls that should happen before the backoffMultipler should kick-in. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.backoffMultiplier* | To let the scheduled polling consumer backoff if there has been a number of subsequent idles/errors in a row. The multiplier is then the number of polls that will be skipped before the next actual attempt is happening again. When this option is in use then backoffIdleThreshold and/or backoffErrorThreshold must also be configured. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.delay* | Milliseconds before the next poll. You can also specify time values using units, such as 60s (60 seconds), 5m30s (5 minutes and 30 seconds), and 1h (1 hour). | 500L | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.greedy* | If greedy is enabled, then the ScheduledPollConsumer will run immediately again, if the previous run polled 1 or more messages. | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.repeatCount* | Specifies a maximum limit of number of fires. So if you set it to 1, the scheduler will only fire once. If you set it to 5, it will only fire five times. A value of zero or negative means fire forever. | 0L | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.runLoggingLevel* | The consumer logs a start/complete log line when it polls. This option allows you to configure the logging level for that. One of: [TRACE] [DEBUG] [INFO] [WARN] [ERROR] [OFF] | "TRACE" | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.scheduledExecutorService* | Allows for configuring a custom/shared thread pool to use for the consumer. By default each consumer has its own single threaded thread pool. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.scheduler* | To use a cron scheduler from either camel-spring or camel-quartz component One of: [none] [spring] [quartz] | "none" | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.schedulerProperties* | To configure additional properties when using a custom scheduler or any of the Quartz, Spring based scheduler. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.timeUnit* | Time unit for initialDelay and delay options. One of: [NANOSECONDS] [MICROSECONDS] [MILLISECONDS] [SECONDS] [MINUTES] [HOURS] [DAYS] | "MILLISECONDS" | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.useFixedDelay* | Controls if fixed delay or fixed rate is used. See ScheduledExecutorService in JDK for details. | true | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.clientSecret* | Box application client secret | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.encryptionAlgorithm* | The type of encryption algorithm for JWT. Supported Algorithms: RSA_SHA_256 RSA_SHA_384 RSA_SHA_512 One of: [RSA_SHA_256] [RSA_SHA_384] [RSA_SHA_512] | "RSA_SHA_256" | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.maxCacheEntries* | The maximum number of access tokens in cache. | 100 | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.authenticationType* | The type of authentication for connection. Types of Authentication: STANDARD_AUTHENTICATION - OAuth 2.0 (3-legged) SERVER_AUTHENTICATION - OAuth 2.0 with JSON Web Tokens | "APP_USER_AUTHENTICATION" | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.initialDelay* | Milliseconds before the first poll starts. You can also specify time values using units, such as 60s (60 seconds), 5m30s (5 minutes and 30 seconds), and 1h (1 hour). | 1000L | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.startScheduler* | Whether the scheduler should be auto started. | true | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.privateKeyFile* | The private key for generating the JWT signature. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.privateKeyPassword* | The password for the private key. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.publicKeyId* | The ID for public key for validating the JWT signature. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.sslContextParameters* | To configure security using SSLContextParameters. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.userName* | Box user name, MUST be provided | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.userPassword* | Box user password, MUST be provided if authSecureStorage is not set, or returns null on first call | null | ConfigDef.Importance.MEDIUM
+| *camel.component.box.configuration* | To use the shared configuration | null | ConfigDef.Importance.MEDIUM
+| *camel.component.box.bridgeErrorHandler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | ConfigDef.Importance.MEDIUM
+| *camel.component.box.basicPropertyBinding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+|===
+
+
+// kafka-connector options: END
diff --git a/docs/modules/ROOT/pages/connectors/camel-braintree-kafka-sink-connector.adoc b/docs/modules/ROOT/pages/connectors/camel-braintree-kafka-sink-connector.adoc
new file mode 100644
index 0000000..8e40a87
--- /dev/null
+++ b/docs/modules/ROOT/pages/connectors/camel-braintree-kafka-sink-connector.adoc
@@ -0,0 +1,44 @@
+// kafka-connector options: START
+== camel-braintree-kafka-connector source configuration
+
+When using camel-braintree-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-braintree-kafka-connector</artifactId>
+ <version>x.x.x</version>
+ <!-- use the same version as your Camel Kafka connector version -->
+</dependency>
+----
+
+
+[width="100%",cols="2,5,^1,2",options="header"]
+|===
+| Name | Description | Default | Priority
+| *camel.sink.path.apiName* | What kind of operation to perform One of: [ADDON] [ADDRESS] [CLIENTTOKEN] [CREDITCARDVERIFICATION] [CUSTOMER] [DISCOUNT] [DISPUTE] [DOCUMENTUPLOAD] [MERCHANTACCOUNT] [PAYMENTMETHOD] [PAYMENTMETHODNONCE] [PLAN] [REPORT] [SETTLEMENTBATCHSUMMARY] [SUBSCRIPTION] [TRANSACTION] [WEBHOOKNOTIFICATION] | null | ConfigDef.Importance.HIGH
+| *camel.sink.path.methodName* | What sub operation to use for the selected operation | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.environment* | The environment Either SANDBOX or PRODUCTION | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.inBody* | Sets the name of a parameter to be passed in the exchange In Body | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.merchantId* | The merchant id provided by Braintree. | null | ConfigDef.Importance.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 cre [...]
+| *camel.sink.endpoint.basicPropertyBinding* | Whether the endpoint should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.httpReadTimeout* | Set read timeout for http calls. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.synchronous* | Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). | false | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.httpLogLevel* | Set logging level for http calls, see java.util.logging.Level | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.httpLogName* | Set log category to use to log http calls. | "Braintree" | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.logHandlerEnabled* | Sets whether to enable the BraintreeLogHandler. It may be desirable to set this to 'false' where an existing JUL - SLF4J logger bridge is on the classpath. This option can also be configured globally on the BraintreeComponent. | true | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.proxyHost* | The proxy host | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.proxyPort* | The proxy port | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.accessToken* | The access token granted by a merchant to another in order to process transactions on their behalf. Used in place of environment, merchant id, public key and private key fields. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.privateKey* | The private key provided by Braintree. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.publicKey* | The public key provided by Braintree. | null | ConfigDef.Importance.MEDIUM
+| *camel.component.braintree.configuration* | To use the shared configuration | null | ConfigDef.Importance.MEDIUM
+| *camel.component.braintree.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 th [...]
+| *camel.component.braintree.basicPropertyBinding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+| *camel.component.braintree.logHandlerEnabled* | Sets whether to enable the BraintreeLogHandler. It may be desirable to set this to false where an existing JUL - SLF4J logger bridge is on the classpath. | true | ConfigDef.Importance.MEDIUM
+|===
+
+
+// kafka-connector options: END
diff --git a/docs/modules/ROOT/pages/connectors/camel-braintree-kafka-source-connector.adoc b/docs/modules/ROOT/pages/connectors/camel-braintree-kafka-source-connector.adoc
new file mode 100644
index 0000000..7c2026d
--- /dev/null
+++ b/docs/modules/ROOT/pages/connectors/camel-braintree-kafka-source-connector.adoc
@@ -0,0 +1,62 @@
+// kafka-connector options: START
+== camel-braintree-kafka-connector source configuration
+
+When using camel-braintree-kafka-connector as source 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-braintree-kafka-connector</artifactId>
+ <version>x.x.x</version>
+ <!-- use the same version as your Camel Kafka connector version -->
+</dependency>
+----
+
+
+[width="100%",cols="2,5,^1,2",options="header"]
+|===
+| Name | Description | Default | Priority
+| *camel.source.path.apiName* | What kind of operation to perform One of: [ADDON] [ADDRESS] [CLIENTTOKEN] [CREDITCARDVERIFICATION] [CUSTOMER] [DISCOUNT] [DISPUTE] [DOCUMENTUPLOAD] [MERCHANTACCOUNT] [PAYMENTMETHOD] [PAYMENTMETHODNONCE] [PLAN] [REPORT] [SETTLEMENTBATCHSUMMARY] [SUBSCRIPTION] [TRANSACTION] [WEBHOOKNOTIFICATION] | null | ConfigDef.Importance.HIGH
+| *camel.source.path.methodName* | What sub operation to use for the selected operation | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.environment* | The environment Either SANDBOX or PRODUCTION | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.inBody* | Sets the name of a parameter to be passed in the exchange In Body | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.merchantId* | The merchant id provided by Braintree. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.bridgeErrorHandler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.sendEmptyMessageWhenIdle* | If the polling consumer did not poll any files, you can enable this option to send an empty message (no body) instead. | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.exceptionHandler* | To let the consumer use a custom ExceptionHandler. Notice if the option bridgeErrorHandler is enabled then this option is not in use. By default the consumer will deal with exceptions, that will be logged at WARN or ERROR level and ignored. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.exchangePattern* | Sets the exchange pattern when the consumer creates an exchange. One of: [InOnly] [InOut] [InOptionalOut] | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.pollStrategy* | A pluggable org.apache.camel.PollingConsumerPollingStrategy allowing you to provide your custom implementation to control error handling usually occurred during the poll operation before an Exchange have been created and being routed in Camel. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.basicPropertyBinding* | Whether the endpoint should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.httpReadTimeout* | Set read timeout for http calls. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.synchronous* | Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.backoffErrorThreshold* | The number of subsequent error polls (failed due some error) that should happen before the backoffMultipler should kick-in. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.backoffIdleThreshold* | The number of subsequent idle polls that should happen before the backoffMultipler should kick-in. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.backoffMultiplier* | To let the scheduled polling consumer backoff if there has been a number of subsequent idles/errors in a row. The multiplier is then the number of polls that will be skipped before the next actual attempt is happening again. When this option is in use then backoffIdleThreshold and/or backoffErrorThreshold must also be configured. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.delay* | Milliseconds before the next poll. You can also specify time values using units, such as 60s (60 seconds), 5m30s (5 minutes and 30 seconds), and 1h (1 hour). | 500L | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.greedy* | If greedy is enabled, then the ScheduledPollConsumer will run immediately again, if the previous run polled 1 or more messages. | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.initialDelay* | Milliseconds before the first poll starts. You can also specify time values using units, such as 60s (60 seconds), 5m30s (5 minutes and 30 seconds), and 1h (1 hour). | 1000L | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.repeatCount* | Specifies a maximum limit of number of fires. So if you set it to 1, the scheduler will only fire once. If you set it to 5, it will only fire five times. A value of zero or negative means fire forever. | 0L | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.runLoggingLevel* | The consumer logs a start/complete log line when it polls. This option allows you to configure the logging level for that. One of: [TRACE] [DEBUG] [INFO] [WARN] [ERROR] [OFF] | "TRACE" | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.scheduledExecutorService* | Allows for configuring a custom/shared thread pool to use for the consumer. By default each consumer has its own single threaded thread pool. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.scheduler* | To use a cron scheduler from either camel-spring or camel-quartz component One of: [none] [spring] [quartz] | "none" | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.schedulerProperties* | To configure additional properties when using a custom scheduler or any of the Quartz, Spring based scheduler. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.startScheduler* | Whether the scheduler should be auto started. | true | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.timeUnit* | Time unit for initialDelay and delay options. One of: [NANOSECONDS] [MICROSECONDS] [MILLISECONDS] [SECONDS] [MINUTES] [HOURS] [DAYS] | "MILLISECONDS" | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.useFixedDelay* | Controls if fixed delay or fixed rate is used. See ScheduledExecutorService in JDK for details. | true | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.httpLogLevel* | Set logging level for http calls, see java.util.logging.Level | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.httpLogName* | Set log category to use to log http calls. | "Braintree" | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.logHandlerEnabled* | Sets whether to enable the BraintreeLogHandler. It may be desirable to set this to 'false' where an existing JUL - SLF4J logger bridge is on the classpath. This option can also be configured globally on the BraintreeComponent. | true | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.proxyHost* | The proxy host | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.proxyPort* | The proxy port | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.accessToken* | The access token granted by a merchant to another in order to process transactions on their behalf. Used in place of environment, merchant id, public key and private key fields. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.privateKey* | The private key provided by Braintree. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.publicKey* | The public key provided by Braintree. | null | ConfigDef.Importance.MEDIUM
+| *camel.component.braintree.configuration* | To use the shared configuration | null | ConfigDef.Importance.MEDIUM
+| *camel.component.braintree.bridgeErrorHandler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | ConfigDef.Importance.MEDIUM
+| *camel.component.braintree.basicPropertyBinding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+| *camel.component.braintree.logHandlerEnabled* | Sets whether to enable the BraintreeLogHandler. It may be desirable to set this to false where an existing JUL - SLF4J logger bridge is on the classpath. | true | ConfigDef.Importance.MEDIUM
+|===
+
+
+// kafka-connector options: END
diff --git a/docs/modules/ROOT/pages/connectors/camel-browse-kafka-sink-connector.adoc b/docs/modules/ROOT/pages/connectors/camel-browse-kafka-sink-connector.adoc
new file mode 100644
index 0000000..6ab2514
--- /dev/null
+++ b/docs/modules/ROOT/pages/connectors/camel-browse-kafka-sink-connector.adoc
@@ -0,0 +1,29 @@
+// kafka-connector options: START
+== camel-browse-kafka-connector source configuration
+
+When using camel-browse-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-browse-kafka-connector</artifactId>
+ <version>x.x.x</version>
+ <!-- use the same version as your Camel Kafka connector version -->
+</dependency>
+----
+
+
+[width="100%",cols="2,5,^1,2",options="header"]
+|===
+| Name | Description | Default | Priority
+| *camel.sink.path.name* | A name which can be any string to uniquely identify the endpoint | null | ConfigDef.Importance.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 cre [...]
+| *camel.sink.endpoint.basicPropertyBinding* | Whether the endpoint should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.synchronous* | Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). | false | ConfigDef.Importance.MEDIUM
+| *camel.component.browse.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 [...]
+| *camel.component.browse.basicPropertyBinding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+|===
+
+
+// kafka-connector options: END
diff --git a/docs/modules/ROOT/pages/connectors/camel-browse-kafka-source-connector.adoc b/docs/modules/ROOT/pages/connectors/camel-browse-kafka-source-connector.adoc
new file mode 100644
index 0000000..e0f2e5f
--- /dev/null
+++ b/docs/modules/ROOT/pages/connectors/camel-browse-kafka-source-connector.adoc
@@ -0,0 +1,31 @@
+// kafka-connector options: START
+== camel-browse-kafka-connector source configuration
+
+When using camel-browse-kafka-connector as source 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-browse-kafka-connector</artifactId>
+ <version>x.x.x</version>
+ <!-- use the same version as your Camel Kafka connector version -->
+</dependency>
+----
+
+
+[width="100%",cols="2,5,^1,2",options="header"]
+|===
+| Name | Description | Default | Priority
+| *camel.source.path.name* | A name which can be any string to uniquely identify the endpoint | null | ConfigDef.Importance.HIGH
+| *camel.source.endpoint.bridgeErrorHandler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.exceptionHandler* | To let the consumer use a custom ExceptionHandler. Notice if the option bridgeErrorHandler is enabled then this option is not in use. By default the consumer will deal with exceptions, that will be logged at WARN or ERROR level and ignored. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.exchangePattern* | Sets the exchange pattern when the consumer creates an exchange. One of: [InOnly] [InOut] [InOptionalOut] | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.basicPropertyBinding* | Whether the endpoint should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.synchronous* | Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). | false | ConfigDef.Importance.MEDIUM
+| *camel.component.browse.bridgeErrorHandler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | ConfigDef.Importance.MEDIUM
+| *camel.component.browse.basicPropertyBinding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+|===
+
+
+// kafka-connector options: END
diff --git a/docs/modules/ROOT/pages/connectors/camel-caffeine-cache-kafka-sink-connector.adoc b/docs/modules/ROOT/pages/connectors/camel-caffeine-cache-kafka-sink-connector.adoc
new file mode 100644
index 0000000..07984ae
--- /dev/null
+++ b/docs/modules/ROOT/pages/connectors/camel-caffeine-cache-kafka-sink-connector.adoc
@@ -0,0 +1,45 @@
+// kafka-connector options: START
+== camel-caffeine-cache-kafka-connector source configuration
+
+When using camel-caffeine-cache-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-caffeine-cache-kafka-connector</artifactId>
+ <version>x.x.x</version>
+ <!-- use the same version as your Camel Kafka connector version -->
+</dependency>
+----
+
+
+[width="100%",cols="2,5,^1,2",options="header"]
+|===
+| Name | Description | Default | Priority
+| *camel.sink.path.cacheName* | the cache name | null | ConfigDef.Importance.HIGH
+| *camel.sink.endpoint.action* | To configure the default cache action. If an action is set in the message header, then the operation from the header takes precedence. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.cache* | To configure an already instantiated cache to be used | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.cacheLoader* | To configure a CacheLoader in case of a LoadCache use | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.createCacheIfNotExist* | Configure if a cache need to be created if it does exist or can't be pre-configured. | true | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.evictionType* | Set the eviction Type for this cache One of: [size_based] [time_based] | "SIZE_BASED" | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.expireAfterAccessTime* | Set the expire After Access Time in case of time based Eviction (in seconds) | 300 | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.expireAfterWriteTime* | Set the expire After Access Write in case of time based Eviction (in seconds) | 300 | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.initialCapacity* | Set the initial Capacity for the cache | 10000 | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.key* | To configure the default action key. If a key is set in the message header, then the key from the header takes precedence. | null | ConfigDef.Importance.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 cre [...]
+| *camel.sink.endpoint.maximumSize* | Set the maximum size for the cache | 10000 | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.removalListener* | Set a specific removal Listener for the cache | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.statsCounter* | Set a specific Stats Counter for the cache stats | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.statsEnabled* | To enable stats on the cache | false | ConfigDef.Importance.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 | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.keyType* | The cache key type, default java.lang.Object | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.synchronous* | Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). | false | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.valueType* | The cache value type, default java.lang.Object | null | ConfigDef.Importance.MEDIUM
+| *camel.component.caffeine-cache.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 process [...]
+| *camel.component.caffeine-cache.basicPropertyBinding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+| *camel.component.caffeine-cache.configuration* | Sets the global component configuration | null | ConfigDef.Importance.MEDIUM
+|===
+
+
+// kafka-connector options: END
diff --git a/docs/modules/ROOT/pages/connectors/camel-caffeine-loadcache-kafka-sink-connector.adoc b/docs/modules/ROOT/pages/connectors/camel-caffeine-loadcache-kafka-sink-connector.adoc
new file mode 100644
index 0000000..701490a
--- /dev/null
+++ b/docs/modules/ROOT/pages/connectors/camel-caffeine-loadcache-kafka-sink-connector.adoc
@@ -0,0 +1,45 @@
+// kafka-connector options: START
+== camel-caffeine-loadcache-kafka-connector source configuration
+
+When using camel-caffeine-loadcache-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-caffeine-loadcache-kafka-connector</artifactId>
+ <version>x.x.x</version>
+ <!-- use the same version as your Camel Kafka connector version -->
+</dependency>
+----
+
+
+[width="100%",cols="2,5,^1,2",options="header"]
+|===
+| Name | Description | Default | Priority
+| *camel.sink.path.cacheName* | the cache name | null | ConfigDef.Importance.HIGH
+| *camel.sink.endpoint.action* | To configure the default cache action. If an action is set in the message header, then the operation from the header takes precedence. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.cache* | To configure an already instantiated cache to be used | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.cacheLoader* | To configure a CacheLoader in case of a LoadCache use | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.createCacheIfNotExist* | Configure if a cache need to be created if it does exist or can't be pre-configured. | true | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.evictionType* | Set the eviction Type for this cache One of: [size_based] [time_based] | "SIZE_BASED" | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.expireAfterAccessTime* | Set the expire After Access Time in case of time based Eviction (in seconds) | 300 | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.expireAfterWriteTime* | Set the expire After Access Write in case of time based Eviction (in seconds) | 300 | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.initialCapacity* | Set the initial Capacity for the cache | 10000 | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.key* | To configure the default action key. If a key is set in the message header, then the key from the header takes precedence. | null | ConfigDef.Importance.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 cre [...]
+| *camel.sink.endpoint.maximumSize* | Set the maximum size for the cache | 10000 | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.removalListener* | Set a specific removal Listener for the cache | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.statsCounter* | Set a specific Stats Counter for the cache stats | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.statsEnabled* | To enable stats on the cache | false | ConfigDef.Importance.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 | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.keyType* | The cache key type, default java.lang.Object | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.synchronous* | Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). | false | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.valueType* | The cache value type, default java.lang.Object | null | ConfigDef.Importance.MEDIUM
+| *camel.component.caffeine-loadcache.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 pro [...]
+| *camel.component.caffeine-loadcache.basicPropertyBinding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+| *camel.component.caffeine-loadcache.configuration* | Sets the global component configuration | null | ConfigDef.Importance.MEDIUM
+|===
+
+
+// kafka-connector options: END
diff --git a/docs/modules/ROOT/pages/connectors/camel-chatscript-kafka-sink-connector.adoc b/docs/modules/ROOT/pages/connectors/camel-chatscript-kafka-sink-connector.adoc
new file mode 100644
index 0000000..e6ca997
--- /dev/null
+++ b/docs/modules/ROOT/pages/connectors/camel-chatscript-kafka-sink-connector.adoc
@@ -0,0 +1,33 @@
+// kafka-connector options: START
+== camel-chatscript-kafka-connector source configuration
+
+When using camel-chatscript-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-chatscript-kafka-connector</artifactId>
+ <version>x.x.x</version>
+ <!-- use the same version as your Camel Kafka connector version -->
+</dependency>
+----
+
+
+[width="100%",cols="2,5,^1,2",options="header"]
+|===
+| Name | Description | Default | Priority
+| *camel.sink.path.host* | Hostname or IP of the server on which CS server is running | null | ConfigDef.Importance.HIGH
+| *camel.sink.path.port* | Port on which ChatScript is listening to | 1024 | ConfigDef.Importance.MEDIUM
+| *camel.sink.path.botName* | Name of the Bot in CS to converse with | null | ConfigDef.Importance.HIGH
+| *camel.sink.endpoint.chatUserName* | Username who initializes the CS conversation. To be set when chat is initialized from camel route | null | ConfigDef.Importance.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 cre [...]
+| *camel.sink.endpoint.resetChat* | Issues :reset command to start a new conversation everytime | false | ConfigDef.Importance.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 | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.synchronous* | Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). | false | ConfigDef.Importance.MEDIUM
+| *camel.component.chatscript.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 t [...]
+| *camel.component.chatscript.basicPropertyBinding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+|===
+
+
+// kafka-connector options: END
diff --git a/docs/modules/ROOT/pages/connectors/camel-chunk-kafka-sink-connector.adoc b/docs/modules/ROOT/pages/connectors/camel-chunk-kafka-sink-connector.adoc
new file mode 100644
index 0000000..d0138e0
--- /dev/null
+++ b/docs/modules/ROOT/pages/connectors/camel-chunk-kafka-sink-connector.adoc
@@ -0,0 +1,35 @@
+// kafka-connector options: START
+== camel-chunk-kafka-connector source configuration
+
+When using camel-chunk-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-chunk-kafka-connector</artifactId>
+ <version>x.x.x</version>
+ <!-- use the same version as your Camel Kafka connector version -->
+</dependency>
+----
+
+
+[width="100%",cols="2,5,^1,2",options="header"]
+|===
+| Name | Description | Default | Priority
+| *camel.sink.path.resourceUri* | Path to the resource. You can prefix with: classpath, file, http, ref, or bean. classpath, file and http loads the resource using these protocols (classpath is default). ref will lookup the resource in the registry. bean will call a method on a bean to be used as the resource. For bean you can specify the method name after dot, eg bean:myBean.myMethod. | null | ConfigDef.Importance.HIGH
+| *camel.sink.endpoint.contentCache* | Sets whether to use resource content cache or not | false | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.encoding* | Define the encoding of the body | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.extension* | Define the file extension of the template | null | ConfigDef.Importance.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 cre [...]
+| *camel.sink.endpoint.themeFolder* | Define the themes folder to scan | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.themeLayer* | Define the theme layer to elaborate | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.themeSubfolder* | Define the themes subfolder to scan | null | ConfigDef.Importance.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 | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.synchronous* | Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). | false | ConfigDef.Importance.MEDIUM
+| *camel.component.chunk.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 c [...]
+| *camel.component.chunk.basicPropertyBinding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+|===
+
+
+// kafka-connector options: END
diff --git a/docs/modules/ROOT/pages/connectors/camel-class-kafka-sink-connector.adoc b/docs/modules/ROOT/pages/connectors/camel-class-kafka-sink-connector.adoc
new file mode 100644
index 0000000..4c93ea9
--- /dev/null
+++ b/docs/modules/ROOT/pages/connectors/camel-class-kafka-sink-connector.adoc
@@ -0,0 +1,35 @@
+// kafka-connector options: START
+== camel-class-kafka-connector source configuration
+
+When using camel-class-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-class-kafka-connector</artifactId>
+ <version>x.x.x</version>
+ <!-- use the same version as your Camel Kafka connector version -->
+</dependency>
+----
+
+
+[width="100%",cols="2,5,^1,2",options="header"]
+|===
+| Name | Description | Default | Priority
+| *camel.sink.path.beanName* | Sets the name of the bean to invoke | null | ConfigDef.Importance.HIGH
+| *camel.sink.endpoint.cache* | Use scope option instead. | null | ConfigDef.Importance.LOW
+| *camel.sink.endpoint.method* | Sets the name of the method to invoke on the bean | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.scope* | Scope of bean. When using singleton scope (default) the bean is created or looked up only once and reused for the lifetime of the endpoint. The bean should be thread-safe in case concurrent threads is calling the bean at the same time. When using request scope the bean is created or looked up once per request (exchange). This can be used if you want to store state on a bean while processing a request and you want to call the same bean instance multiple tim [...]
+| *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 cre [...]
+| *camel.sink.endpoint.basicPropertyBinding* | Whether the endpoint should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.parameters* | Used for configuring additional properties on the bean | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.synchronous* | Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). | false | ConfigDef.Importance.MEDIUM
+| *camel.component.class.cache* | Use singleton option instead. | "true" | ConfigDef.Importance.LOW
+| *camel.component.class.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 c [...]
+| *camel.component.class.scope* | Scope of bean. When using singleton scope (default) the bean is created or looked up only once and reused for the lifetime of the endpoint. The bean should be thread-safe in case concurrent threads is calling the bean at the same time. When using request scope the bean is created or looked up once per request (exchange). This can be used if you want to store state on a bean while processing a request and you want to call the same bean instance multiple t [...]
+| *camel.component.class.basicPropertyBinding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+|===
+
+
+// kafka-connector options: END
diff --git a/docs/modules/ROOT/pages/connectors/camel-cm-sms-kafka-sink-connector.adoc b/docs/modules/ROOT/pages/connectors/camel-cm-sms-kafka-sink-connector.adoc
new file mode 100644
index 0000000..1a1a82f
--- /dev/null
+++ b/docs/modules/ROOT/pages/connectors/camel-cm-sms-kafka-sink-connector.adoc
@@ -0,0 +1,33 @@
+// kafka-connector options: START
+== camel-cm-sms-kafka-connector source configuration
+
+When using camel-cm-sms-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-cm-sms-kafka-connector</artifactId>
+ <version>x.x.x</version>
+ <!-- use the same version as your Camel Kafka connector version -->
+</dependency>
+----
+
+
+[width="100%",cols="2,5,^1,2",options="header"]
+|===
+| Name | Description | Default | Priority
+| *camel.sink.path.host* | SMS Provider HOST with scheme | null | ConfigDef.Importance.HIGH
+| *camel.sink.endpoint.defaultFrom* | This is the sender name. The maximum length is 11 characters. | null | ConfigDef.Importance.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 | ConfigDef.Importance.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 cre [...]
+| *camel.sink.endpoint.productToken* | The unique token to use | null | ConfigDef.Importance.HIGH
+| *camel.sink.endpoint.testConnectionOnStartup* | Whether to test the connection to the SMS Gateway on startup | false | ConfigDef.Importance.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 | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.synchronous* | Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). | false | ConfigDef.Importance.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 [...]
+| *camel.component.cm-sms.basicPropertyBinding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+|===
+
+
+// kafka-connector options: END
diff --git a/docs/modules/ROOT/pages/connectors/camel-cmis-kafka-sink-connector.adoc b/docs/modules/ROOT/pages/connectors/camel-cmis-kafka-sink-connector.adoc
new file mode 100644
index 0000000..256c397
--- /dev/null
+++ b/docs/modules/ROOT/pages/connectors/camel-cmis-kafka-sink-connector.adoc
@@ -0,0 +1,38 @@
+// kafka-connector options: START
+== camel-cmis-kafka-connector source configuration
+
+When using camel-cmis-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-cmis-kafka-connector</artifactId>
+ <version>x.x.x</version>
+ <!-- use the same version as your Camel Kafka connector version -->
+</dependency>
+----
+
+
+[width="100%",cols="2,5,^1,2",options="header"]
+|===
+| Name | Description | Default | Priority
+| *camel.sink.path.cmsUrl* | URL to the cmis repository | null | ConfigDef.Importance.HIGH
+| *camel.sink.endpoint.pageSize* | Number of nodes to retrieve per page | 100 | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.readContent* | If set to true, the content of document node will be retrieved in addition to the properties | false | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.readCount* | Max number of nodes to read | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.repositoryId* | The Id of the repository to use. If not specified the first available repository is used | null | ConfigDef.Importance.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 cre [...]
+| *camel.sink.endpoint.queryMode* | If true, will execute the cmis query from the message body and return result, otherwise will create a node in the cmis repository | false | ConfigDef.Importance.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 | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.sessionFacadeFactory* | To use a custom CMISSessionFacadeFactory to create the CMISSessionFacade instances | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.synchronous* | Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). | false | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.password* | Password for the cmis repository | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.username* | Username for the cmis repository | null | ConfigDef.Importance.MEDIUM
+| *camel.component.cmis.sessionFacadeFactory* | To use a custom CMISSessionFacadeFactory to create the CMISSessionFacade instances | null | ConfigDef.Importance.MEDIUM
+| *camel.component.cmis.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 cr [...]
+| *camel.component.cmis.basicPropertyBinding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+|===
+
+
+// kafka-connector options: END
diff --git a/docs/modules/ROOT/pages/connectors/camel-cmis-kafka-source-connector.adoc b/docs/modules/ROOT/pages/connectors/camel-cmis-kafka-source-connector.adoc
new file mode 100644
index 0000000..6bcfcc6
--- /dev/null
+++ b/docs/modules/ROOT/pages/connectors/camel-cmis-kafka-source-connector.adoc
@@ -0,0 +1,40 @@
+// kafka-connector options: START
+== camel-cmis-kafka-connector source configuration
+
+When using camel-cmis-kafka-connector as source 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-cmis-kafka-connector</artifactId>
+ <version>x.x.x</version>
+ <!-- use the same version as your Camel Kafka connector version -->
+</dependency>
+----
+
+
+[width="100%",cols="2,5,^1,2",options="header"]
+|===
+| Name | Description | Default | Priority
+| *camel.source.path.cmsUrl* | URL to the cmis repository | null | ConfigDef.Importance.HIGH
+| *camel.source.endpoint.pageSize* | Number of nodes to retrieve per page | 100 | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.readContent* | If set to true, the content of document node will be retrieved in addition to the properties | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.readCount* | Max number of nodes to read | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.repositoryId* | The Id of the repository to use. If not specified the first available repository is used | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.bridgeErrorHandler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.query* | The cmis query to execute against the repository. If not specified, the consumer will retrieve every node from the content repository by iterating the content tree recursively | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.exceptionHandler* | To let the consumer use a custom ExceptionHandler. Notice if the option bridgeErrorHandler is enabled then this option is not in use. By default the consumer will deal with exceptions, that will be logged at WARN or ERROR level and ignored. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.exchangePattern* | Sets the exchange pattern when the consumer creates an exchange. One of: [InOnly] [InOut] [InOptionalOut] | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.basicPropertyBinding* | Whether the endpoint should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.sessionFacadeFactory* | To use a custom CMISSessionFacadeFactory to create the CMISSessionFacade instances | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.synchronous* | Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.password* | Password for the cmis repository | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.username* | Username for the cmis repository | null | ConfigDef.Importance.MEDIUM
+| *camel.component.cmis.sessionFacadeFactory* | To use a custom CMISSessionFacadeFactory to create the CMISSessionFacade instances | null | ConfigDef.Importance.MEDIUM
+| *camel.component.cmis.bridgeErrorHandler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | ConfigDef.Importance.MEDIUM
+| *camel.component.cmis.basicPropertyBinding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+|===
+
+
+// kafka-connector options: END
diff --git a/docs/modules/ROOT/pages/connectors/camel-coap+tcp-kafka-sink-connector.adoc b/docs/modules/ROOT/pages/connectors/camel-coap+tcp-kafka-sink-connector.adoc
new file mode 100644
index 0000000..6fdb430
--- /dev/null
+++ b/docs/modules/ROOT/pages/connectors/camel-coap+tcp-kafka-sink-connector.adoc
@@ -0,0 +1,38 @@
+// kafka-connector options: START
+== camel-coap+tcp-kafka-connector source configuration
+
+When using camel-coap+tcp-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-coap+tcp-kafka-connector</artifactId>
+ <version>x.x.x</version>
+ <!-- use the same version as your Camel Kafka connector version -->
+</dependency>
+----
+
+
+[width="100%",cols="2,5,^1,2",options="header"]
+|===
+| Name | Description | Default | Priority
+| *camel.sink.path.uri* | The URI for the CoAP endpoint | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.alias* | Sets the alias used to query the KeyStore for the private key and certificate. This parameter is used when we are enabling TLS with certificates on the service side, and similarly on the client side when TLS is used with certificates and client authentication. If the parameter is not specified then the default behavior is to use the first alias in the keystore that contains a key entry. This configuration parameter does not apply to configuring TLS via a R [...]
+| *camel.sink.endpoint.cipherSuites* | Sets the cipherSuites String. This is a comma separated String of ciphersuites to configure. If it is not specified, then it falls back to getting the ciphersuites from the sslContextParameters object. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.clientAuthentication* | Sets the configuration options for server-side client-authentication requirements. The value must be one of NONE, WANT, REQUIRE. If this value is not specified, then it falls back to checking the sslContextParameters.getServerParameters().getClientAuthentication() value. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.privateKey* | Set the configured private key for use with Raw Public Key. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.pskStore* | Set the PskStore to use for pre-shared key. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.publicKey* | Set the configured public key for use with Raw Public Key. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.recommendedCipherSuitesOnly* | The CBC cipher suites are not recommended. If you want to use them, you first need to set the recommendedCipherSuitesOnly option to false. | true | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.sslContextParameters* | Set the SSLContextParameters object for setting up TLS. This is required for coapstcp, and for coaps when we are using certificates for TLS (as opposed to RPK or PKS). | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.trustedRpkStore* | Set the TrustedRpkStore to use to determine trust in raw public keys. | null | ConfigDef.Importance.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 cre [...]
+| *camel.sink.endpoint.basicPropertyBinding* | Whether the endpoint should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.synchronous* | Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). | false | ConfigDef.Importance.MEDIUM
+| *camel.component.coap-tcp.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 the [...]
+| *camel.component.coap-tcp.basicPropertyBinding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+|===
+
+
+// kafka-connector options: END
diff --git a/docs/modules/ROOT/pages/connectors/camel-coap+tcp-kafka-source-connector.adoc b/docs/modules/ROOT/pages/connectors/camel-coap+tcp-kafka-source-connector.adoc
new file mode 100644
index 0000000..92b39d9
--- /dev/null
+++ b/docs/modules/ROOT/pages/connectors/camel-coap+tcp-kafka-source-connector.adoc
@@ -0,0 +1,41 @@
+// kafka-connector options: START
+== camel-coap+tcp-kafka-connector source configuration
+
+When using camel-coap+tcp-kafka-connector as source 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-coap+tcp-kafka-connector</artifactId>
+ <version>x.x.x</version>
+ <!-- use the same version as your Camel Kafka connector version -->
+</dependency>
+----
+
+
+[width="100%",cols="2,5,^1,2",options="header"]
+|===
+| Name | Description | Default | Priority
+| *camel.source.path.uri* | The URI for the CoAP endpoint | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.alias* | Sets the alias used to query the KeyStore for the private key and certificate. This parameter is used when we are enabling TLS with certificates on the service side, and similarly on the client side when TLS is used with certificates and client authentication. If the parameter is not specified then the default behavior is to use the first alias in the keystore that contains a key entry. This configuration parameter does not apply to configuring TLS via a [...]
+| *camel.source.endpoint.cipherSuites* | Sets the cipherSuites String. This is a comma separated String of ciphersuites to configure. If it is not specified, then it falls back to getting the ciphersuites from the sslContextParameters object. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.clientAuthentication* | Sets the configuration options for server-side client-authentication requirements. The value must be one of NONE, WANT, REQUIRE. If this value is not specified, then it falls back to checking the sslContextParameters.getServerParameters().getClientAuthentication() value. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.privateKey* | Set the configured private key for use with Raw Public Key. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.pskStore* | Set the PskStore to use for pre-shared key. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.publicKey* | Set the configured public key for use with Raw Public Key. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.recommendedCipherSuitesOnly* | The CBC cipher suites are not recommended. If you want to use them, you first need to set the recommendedCipherSuitesOnly option to false. | true | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.sslContextParameters* | Set the SSLContextParameters object for setting up TLS. This is required for coapstcp, and for coaps when we are using certificates for TLS (as opposed to RPK or PKS). | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.trustedRpkStore* | Set the TrustedRpkStore to use to determine trust in raw public keys. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.bridgeErrorHandler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.coapMethodRestrict* | Comma separated list of methods that the CoAP consumer will bind to. The default is to bind to all methods (DELETE, GET, POST, PUT). | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.exceptionHandler* | To let the consumer use a custom ExceptionHandler. Notice if the option bridgeErrorHandler is enabled then this option is not in use. By default the consumer will deal with exceptions, that will be logged at WARN or ERROR level and ignored. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.exchangePattern* | Sets the exchange pattern when the consumer creates an exchange. One of: [InOnly] [InOut] [InOptionalOut] | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.basicPropertyBinding* | Whether the endpoint should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.synchronous* | Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). | false | ConfigDef.Importance.MEDIUM
+| *camel.component.coap-tcp.bridgeErrorHandler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | ConfigDef.Importance.MEDIUM
+| *camel.component.coap-tcp.basicPropertyBinding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+|===
+
+
+// kafka-connector options: END
diff --git a/docs/modules/ROOT/pages/connectors/camel-coap-kafka-sink-connector.adoc b/docs/modules/ROOT/pages/connectors/camel-coap-kafka-sink-connector.adoc
new file mode 100644
index 0000000..dac0dd2
--- /dev/null
+++ b/docs/modules/ROOT/pages/connectors/camel-coap-kafka-sink-connector.adoc
@@ -0,0 +1,38 @@
+// kafka-connector options: START
+== camel-coap-kafka-connector source configuration
+
+When using camel-coap-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-coap-kafka-connector</artifactId>
+ <version>x.x.x</version>
+ <!-- use the same version as your Camel Kafka connector version -->
+</dependency>
+----
+
+
+[width="100%",cols="2,5,^1,2",options="header"]
+|===
+| Name | Description | Default | Priority
+| *camel.sink.path.uri* | The URI for the CoAP endpoint | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.alias* | Sets the alias used to query the KeyStore for the private key and certificate. This parameter is used when we are enabling TLS with certificates on the service side, and similarly on the client side when TLS is used with certificates and client authentication. If the parameter is not specified then the default behavior is to use the first alias in the keystore that contains a key entry. This configuration parameter does not apply to configuring TLS via a R [...]
+| *camel.sink.endpoint.cipherSuites* | Sets the cipherSuites String. This is a comma separated String of ciphersuites to configure. If it is not specified, then it falls back to getting the ciphersuites from the sslContextParameters object. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.clientAuthentication* | Sets the configuration options for server-side client-authentication requirements. The value must be one of NONE, WANT, REQUIRE. If this value is not specified, then it falls back to checking the sslContextParameters.getServerParameters().getClientAuthentication() value. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.privateKey* | Set the configured private key for use with Raw Public Key. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.pskStore* | Set the PskStore to use for pre-shared key. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.publicKey* | Set the configured public key for use with Raw Public Key. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.recommendedCipherSuitesOnly* | The CBC cipher suites are not recommended. If you want to use them, you first need to set the recommendedCipherSuitesOnly option to false. | true | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.sslContextParameters* | Set the SSLContextParameters object for setting up TLS. This is required for coapstcp, and for coaps when we are using certificates for TLS (as opposed to RPK or PKS). | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.trustedRpkStore* | Set the TrustedRpkStore to use to determine trust in raw public keys. | null | ConfigDef.Importance.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 cre [...]
+| *camel.sink.endpoint.basicPropertyBinding* | Whether the endpoint should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.synchronous* | Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). | false | ConfigDef.Importance.MEDIUM
+| *camel.component.coap.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 cr [...]
+| *camel.component.coap.basicPropertyBinding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+|===
+
+
+// kafka-connector options: END
diff --git a/docs/modules/ROOT/pages/connectors/camel-coap-kafka-source-connector.adoc b/docs/modules/ROOT/pages/connectors/camel-coap-kafka-source-connector.adoc
new file mode 100644
index 0000000..32f73dd
--- /dev/null
+++ b/docs/modules/ROOT/pages/connectors/camel-coap-kafka-source-connector.adoc
@@ -0,0 +1,41 @@
+// kafka-connector options: START
+== camel-coap-kafka-connector source configuration
+
+When using camel-coap-kafka-connector as source 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-coap-kafka-connector</artifactId>
+ <version>x.x.x</version>
+ <!-- use the same version as your Camel Kafka connector version -->
+</dependency>
+----
+
+
+[width="100%",cols="2,5,^1,2",options="header"]
+|===
+| Name | Description | Default | Priority
+| *camel.source.path.uri* | The URI for the CoAP endpoint | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.alias* | Sets the alias used to query the KeyStore for the private key and certificate. This parameter is used when we are enabling TLS with certificates on the service side, and similarly on the client side when TLS is used with certificates and client authentication. If the parameter is not specified then the default behavior is to use the first alias in the keystore that contains a key entry. This configuration parameter does not apply to configuring TLS via a [...]
+| *camel.source.endpoint.cipherSuites* | Sets the cipherSuites String. This is a comma separated String of ciphersuites to configure. If it is not specified, then it falls back to getting the ciphersuites from the sslContextParameters object. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.clientAuthentication* | Sets the configuration options for server-side client-authentication requirements. The value must be one of NONE, WANT, REQUIRE. If this value is not specified, then it falls back to checking the sslContextParameters.getServerParameters().getClientAuthentication() value. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.privateKey* | Set the configured private key for use with Raw Public Key. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.pskStore* | Set the PskStore to use for pre-shared key. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.publicKey* | Set the configured public key for use with Raw Public Key. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.recommendedCipherSuitesOnly* | The CBC cipher suites are not recommended. If you want to use them, you first need to set the recommendedCipherSuitesOnly option to false. | true | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.sslContextParameters* | Set the SSLContextParameters object for setting up TLS. This is required for coapstcp, and for coaps when we are using certificates for TLS (as opposed to RPK or PKS). | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.trustedRpkStore* | Set the TrustedRpkStore to use to determine trust in raw public keys. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.bridgeErrorHandler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.coapMethodRestrict* | Comma separated list of methods that the CoAP consumer will bind to. The default is to bind to all methods (DELETE, GET, POST, PUT). | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.exceptionHandler* | To let the consumer use a custom ExceptionHandler. Notice if the option bridgeErrorHandler is enabled then this option is not in use. By default the consumer will deal with exceptions, that will be logged at WARN or ERROR level and ignored. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.exchangePattern* | Sets the exchange pattern when the consumer creates an exchange. One of: [InOnly] [InOut] [InOptionalOut] | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.basicPropertyBinding* | Whether the endpoint should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.synchronous* | Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). | false | ConfigDef.Importance.MEDIUM
+| *camel.component.coap.bridgeErrorHandler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | ConfigDef.Importance.MEDIUM
+| *camel.component.coap.basicPropertyBinding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+|===
+
+
+// kafka-connector options: END
diff --git a/docs/modules/ROOT/pages/connectors/camel-coaps+tcp-kafka-sink-connector.adoc b/docs/modules/ROOT/pages/connectors/camel-coaps+tcp-kafka-sink-connector.adoc
new file mode 100644
index 0000000..5fc3fa6
--- /dev/null
+++ b/docs/modules/ROOT/pages/connectors/camel-coaps+tcp-kafka-sink-connector.adoc
@@ -0,0 +1,38 @@
+// kafka-connector options: START
+== camel-coaps+tcp-kafka-connector source configuration
+
+When using camel-coaps+tcp-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-coaps+tcp-kafka-connector</artifactId>
+ <version>x.x.x</version>
+ <!-- use the same version as your Camel Kafka connector version -->
+</dependency>
+----
+
+
+[width="100%",cols="2,5,^1,2",options="header"]
+|===
+| Name | Description | Default | Priority
+| *camel.sink.path.uri* | The URI for the CoAP endpoint | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.alias* | Sets the alias used to query the KeyStore for the private key and certificate. This parameter is used when we are enabling TLS with certificates on the service side, and similarly on the client side when TLS is used with certificates and client authentication. If the parameter is not specified then the default behavior is to use the first alias in the keystore that contains a key entry. This configuration parameter does not apply to configuring TLS via a R [...]
+| *camel.sink.endpoint.cipherSuites* | Sets the cipherSuites String. This is a comma separated String of ciphersuites to configure. If it is not specified, then it falls back to getting the ciphersuites from the sslContextParameters object. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.clientAuthentication* | Sets the configuration options for server-side client-authentication requirements. The value must be one of NONE, WANT, REQUIRE. If this value is not specified, then it falls back to checking the sslContextParameters.getServerParameters().getClientAuthentication() value. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.privateKey* | Set the configured private key for use with Raw Public Key. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.pskStore* | Set the PskStore to use for pre-shared key. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.publicKey* | Set the configured public key for use with Raw Public Key. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.recommendedCipherSuitesOnly* | The CBC cipher suites are not recommended. If you want to use them, you first need to set the recommendedCipherSuitesOnly option to false. | true | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.sslContextParameters* | Set the SSLContextParameters object for setting up TLS. This is required for coapstcp, and for coaps when we are using certificates for TLS (as opposed to RPK or PKS). | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.trustedRpkStore* | Set the TrustedRpkStore to use to determine trust in raw public keys. | null | ConfigDef.Importance.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 cre [...]
+| *camel.sink.endpoint.basicPropertyBinding* | Whether the endpoint should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.synchronous* | Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). | false | ConfigDef.Importance.MEDIUM
+| *camel.component.coaps-tcp.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 th [...]
+| *camel.component.coaps-tcp.basicPropertyBinding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+|===
+
+
+// kafka-connector options: END
diff --git a/docs/modules/ROOT/pages/connectors/camel-coaps+tcp-kafka-source-connector.adoc b/docs/modules/ROOT/pages/connectors/camel-coaps+tcp-kafka-source-connector.adoc
new file mode 100644
index 0000000..374ff77
--- /dev/null
+++ b/docs/modules/ROOT/pages/connectors/camel-coaps+tcp-kafka-source-connector.adoc
@@ -0,0 +1,41 @@
+// kafka-connector options: START
+== camel-coaps+tcp-kafka-connector source configuration
+
+When using camel-coaps+tcp-kafka-connector as source 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-coaps+tcp-kafka-connector</artifactId>
+ <version>x.x.x</version>
+ <!-- use the same version as your Camel Kafka connector version -->
+</dependency>
+----
+
+
+[width="100%",cols="2,5,^1,2",options="header"]
+|===
+| Name | Description | Default | Priority
+| *camel.source.path.uri* | The URI for the CoAP endpoint | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.alias* | Sets the alias used to query the KeyStore for the private key and certificate. This parameter is used when we are enabling TLS with certificates on the service side, and similarly on the client side when TLS is used with certificates and client authentication. If the parameter is not specified then the default behavior is to use the first alias in the keystore that contains a key entry. This configuration parameter does not apply to configuring TLS via a [...]
+| *camel.source.endpoint.cipherSuites* | Sets the cipherSuites String. This is a comma separated String of ciphersuites to configure. If it is not specified, then it falls back to getting the ciphersuites from the sslContextParameters object. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.clientAuthentication* | Sets the configuration options for server-side client-authentication requirements. The value must be one of NONE, WANT, REQUIRE. If this value is not specified, then it falls back to checking the sslContextParameters.getServerParameters().getClientAuthentication() value. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.privateKey* | Set the configured private key for use with Raw Public Key. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.pskStore* | Set the PskStore to use for pre-shared key. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.publicKey* | Set the configured public key for use with Raw Public Key. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.recommendedCipherSuitesOnly* | The CBC cipher suites are not recommended. If you want to use them, you first need to set the recommendedCipherSuitesOnly option to false. | true | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.sslContextParameters* | Set the SSLContextParameters object for setting up TLS. This is required for coapstcp, and for coaps when we are using certificates for TLS (as opposed to RPK or PKS). | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.trustedRpkStore* | Set the TrustedRpkStore to use to determine trust in raw public keys. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.bridgeErrorHandler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.coapMethodRestrict* | Comma separated list of methods that the CoAP consumer will bind to. The default is to bind to all methods (DELETE, GET, POST, PUT). | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.exceptionHandler* | To let the consumer use a custom ExceptionHandler. Notice if the option bridgeErrorHandler is enabled then this option is not in use. By default the consumer will deal with exceptions, that will be logged at WARN or ERROR level and ignored. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.exchangePattern* | Sets the exchange pattern when the consumer creates an exchange. One of: [InOnly] [InOut] [InOptionalOut] | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.basicPropertyBinding* | Whether the endpoint should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.synchronous* | Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). | false | ConfigDef.Importance.MEDIUM
+| *camel.component.coaps-tcp.bridgeErrorHandler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | ConfigDef.Importance.MEDIUM
+| *camel.component.coaps-tcp.basicPropertyBinding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+|===
+
+
+// kafka-connector options: END
diff --git a/docs/modules/ROOT/pages/connectors/camel-coaps-kafka-sink-connector.adoc b/docs/modules/ROOT/pages/connectors/camel-coaps-kafka-sink-connector.adoc
new file mode 100644
index 0000000..3dfc53f
--- /dev/null
+++ b/docs/modules/ROOT/pages/connectors/camel-coaps-kafka-sink-connector.adoc
@@ -0,0 +1,38 @@
+// kafka-connector options: START
+== camel-coaps-kafka-connector source configuration
+
+When using camel-coaps-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-coaps-kafka-connector</artifactId>
+ <version>x.x.x</version>
+ <!-- use the same version as your Camel Kafka connector version -->
+</dependency>
+----
+
+
+[width="100%",cols="2,5,^1,2",options="header"]
+|===
+| Name | Description | Default | Priority
+| *camel.sink.path.uri* | The URI for the CoAP endpoint | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.alias* | Sets the alias used to query the KeyStore for the private key and certificate. This parameter is used when we are enabling TLS with certificates on the service side, and similarly on the client side when TLS is used with certificates and client authentication. If the parameter is not specified then the default behavior is to use the first alias in the keystore that contains a key entry. This configuration parameter does not apply to configuring TLS via a R [...]
+| *camel.sink.endpoint.cipherSuites* | Sets the cipherSuites String. This is a comma separated String of ciphersuites to configure. If it is not specified, then it falls back to getting the ciphersuites from the sslContextParameters object. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.clientAuthentication* | Sets the configuration options for server-side client-authentication requirements. The value must be one of NONE, WANT, REQUIRE. If this value is not specified, then it falls back to checking the sslContextParameters.getServerParameters().getClientAuthentication() value. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.privateKey* | Set the configured private key for use with Raw Public Key. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.pskStore* | Set the PskStore to use for pre-shared key. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.publicKey* | Set the configured public key for use with Raw Public Key. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.recommendedCipherSuitesOnly* | The CBC cipher suites are not recommended. If you want to use them, you first need to set the recommendedCipherSuitesOnly option to false. | true | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.sslContextParameters* | Set the SSLContextParameters object for setting up TLS. This is required for coapstcp, and for coaps when we are using certificates for TLS (as opposed to RPK or PKS). | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.trustedRpkStore* | Set the TrustedRpkStore to use to determine trust in raw public keys. | null | ConfigDef.Importance.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 cre [...]
+| *camel.sink.endpoint.basicPropertyBinding* | Whether the endpoint should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.synchronous* | Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). | false | ConfigDef.Importance.MEDIUM
+| *camel.component.coaps.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 c [...]
+| *camel.component.coaps.basicPropertyBinding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+|===
+
+
+// kafka-connector options: END
diff --git a/docs/modules/ROOT/pages/connectors/camel-coaps-kafka-source-connector.adoc b/docs/modules/ROOT/pages/connectors/camel-coaps-kafka-source-connector.adoc
new file mode 100644
index 0000000..c472f75
--- /dev/null
+++ b/docs/modules/ROOT/pages/connectors/camel-coaps-kafka-source-connector.adoc
@@ -0,0 +1,41 @@
+// kafka-connector options: START
+== camel-coaps-kafka-connector source configuration
+
+When using camel-coaps-kafka-connector as source 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-coaps-kafka-connector</artifactId>
+ <version>x.x.x</version>
+ <!-- use the same version as your Camel Kafka connector version -->
+</dependency>
+----
+
+
+[width="100%",cols="2,5,^1,2",options="header"]
+|===
+| Name | Description | Default | Priority
+| *camel.source.path.uri* | The URI for the CoAP endpoint | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.alias* | Sets the alias used to query the KeyStore for the private key and certificate. This parameter is used when we are enabling TLS with certificates on the service side, and similarly on the client side when TLS is used with certificates and client authentication. If the parameter is not specified then the default behavior is to use the first alias in the keystore that contains a key entry. This configuration parameter does not apply to configuring TLS via a [...]
+| *camel.source.endpoint.cipherSuites* | Sets the cipherSuites String. This is a comma separated String of ciphersuites to configure. If it is not specified, then it falls back to getting the ciphersuites from the sslContextParameters object. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.clientAuthentication* | Sets the configuration options for server-side client-authentication requirements. The value must be one of NONE, WANT, REQUIRE. If this value is not specified, then it falls back to checking the sslContextParameters.getServerParameters().getClientAuthentication() value. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.privateKey* | Set the configured private key for use with Raw Public Key. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.pskStore* | Set the PskStore to use for pre-shared key. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.publicKey* | Set the configured public key for use with Raw Public Key. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.recommendedCipherSuitesOnly* | The CBC cipher suites are not recommended. If you want to use them, you first need to set the recommendedCipherSuitesOnly option to false. | true | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.sslContextParameters* | Set the SSLContextParameters object for setting up TLS. This is required for coapstcp, and for coaps when we are using certificates for TLS (as opposed to RPK or PKS). | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.trustedRpkStore* | Set the TrustedRpkStore to use to determine trust in raw public keys. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.bridgeErrorHandler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.coapMethodRestrict* | Comma separated list of methods that the CoAP consumer will bind to. The default is to bind to all methods (DELETE, GET, POST, PUT). | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.exceptionHandler* | To let the consumer use a custom ExceptionHandler. Notice if the option bridgeErrorHandler is enabled then this option is not in use. By default the consumer will deal with exceptions, that will be logged at WARN or ERROR level and ignored. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.exchangePattern* | Sets the exchange pattern when the consumer creates an exchange. One of: [InOnly] [InOut] [InOptionalOut] | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.basicPropertyBinding* | Whether the endpoint should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.synchronous* | Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). | false | ConfigDef.Importance.MEDIUM
+| *camel.component.coaps.bridgeErrorHandler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | ConfigDef.Importance.MEDIUM
+| *camel.component.coaps.basicPropertyBinding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+|===
+
+
+// kafka-connector options: END
diff --git a/docs/modules/ROOT/pages/connectors/camel-cometd-kafka-sink-connector.adoc b/docs/modules/ROOT/pages/connectors/camel-cometd-kafka-sink-connector.adoc
new file mode 100644
index 0000000..79da1d0
--- /dev/null
+++ b/docs/modules/ROOT/pages/connectors/camel-cometd-kafka-sink-connector.adoc
@@ -0,0 +1,49 @@
+// kafka-connector options: START
+== camel-cometd-kafka-connector source configuration
+
+When using camel-cometd-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-cometd-kafka-connector</artifactId>
+ <version>x.x.x</version>
+ <!-- use the same version as your Camel Kafka connector version -->
+</dependency>
+----
+
+
+[width="100%",cols="2,5,^1,2",options="header"]
+|===
+| Name | Description | Default | Priority
+| *camel.sink.path.host* | Hostname | null | ConfigDef.Importance.HIGH
+| *camel.sink.path.port* | Host port number | null | ConfigDef.Importance.HIGH
+| *camel.sink.path.channelName* | The channelName represents a topic that can be subscribed to by the Camel endpoints. | null | ConfigDef.Importance.HIGH
+| *camel.sink.endpoint.allowedOrigins* | The origins domain that support to cross, if the crosssOriginFilterOn is true | "*" | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.baseResource* | The root directory for the web resources or classpath. Use the protocol file: or classpath: depending if you want that the component loads the resource from file system or classpath. Classpath is required for OSGI deployment where the resources are packaged in the jar | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.crossOriginFilterOn* | If true, the server will support for cross-domain filtering | false | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.filterPath* | The filterPath will be used by the CrossOriginFilter, if the crosssOriginFilterOn is true | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.interval* | The client side poll timeout in milliseconds. How long a client will wait between reconnects | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.jsonCommented* | If true, the server will accept JSON wrapped in a comment and will generate JSON wrapped in a comment. This is a defence against Ajax Hijacking. | true | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.logLevel* | Logging level. 0=none, 1=info, 2=debug. One of: [0] [1] [2] | 1 | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.maxInterval* | The max client side poll timeout in milliseconds. A client will be removed if a connection is not received in this time. | 30000 | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.multiFrameInterval* | The client side poll timeout, if multiple connections are detected from the same browser. | 1500 | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.timeout* | The server side poll timeout in milliseconds. This is how long the server will hold a reconnect request before responding. | 240000 | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.disconnectLocalSession* | Whether to disconnect local sessions after publishing a message to its channel. Disconnecting local session is needed as they are not swept by default by CometD, and therefore you can run out of memory. | false | ConfigDef.Importance.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 cre [...]
+| *camel.sink.endpoint.basicPropertyBinding* | Whether the endpoint should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.synchronous* | Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). | false | ConfigDef.Importance.MEDIUM
+| *camel.component.cometd.extensions* | To use a list of custom BayeuxServer.Extension that allows modifying incoming and outgoing requests. | null | ConfigDef.Importance.MEDIUM
+| *camel.component.cometd.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 [...]
+| *camel.component.cometd.basicPropertyBinding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+| *camel.component.cometd.securityPolicy* | To use a custom configured SecurityPolicy to control authorization | null | ConfigDef.Importance.MEDIUM
+| *camel.component.cometd.sslContextParameters* | To configure security using SSLContextParameters | null | ConfigDef.Importance.MEDIUM
+| *camel.component.cometd.sslKeyPassword* | The password for the keystore when using SSL. | null | ConfigDef.Importance.MEDIUM
+| *camel.component.cometd.sslKeystore* | The path to the keystore. | null | ConfigDef.Importance.MEDIUM
+| *camel.component.cometd.sslPassword* | The password when using SSL. | null | ConfigDef.Importance.MEDIUM
+| *camel.component.cometd.useGlobalSslContextParameters* | Enable usage of global SSL context parameters. | false | ConfigDef.Importance.MEDIUM
+|===
+
+
+// kafka-connector options: END
diff --git a/docs/modules/ROOT/pages/connectors/camel-cometd-kafka-source-connector.adoc b/docs/modules/ROOT/pages/connectors/camel-cometd-kafka-source-connector.adoc
new file mode 100644
index 0000000..3b46b07
--- /dev/null
+++ b/docs/modules/ROOT/pages/connectors/camel-cometd-kafka-source-connector.adoc
@@ -0,0 +1,51 @@
+// kafka-connector options: START
+== camel-cometd-kafka-connector source configuration
+
+When using camel-cometd-kafka-connector as source 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-cometd-kafka-connector</artifactId>
+ <version>x.x.x</version>
+ <!-- use the same version as your Camel Kafka connector version -->
+</dependency>
+----
+
+
+[width="100%",cols="2,5,^1,2",options="header"]
+|===
+| Name | Description | Default | Priority
+| *camel.source.path.host* | Hostname | null | ConfigDef.Importance.HIGH
+| *camel.source.path.port* | Host port number | null | ConfigDef.Importance.HIGH
+| *camel.source.path.channelName* | The channelName represents a topic that can be subscribed to by the Camel endpoints. | null | ConfigDef.Importance.HIGH
+| *camel.source.endpoint.allowedOrigins* | The origins domain that support to cross, if the crosssOriginFilterOn is true | "*" | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.baseResource* | The root directory for the web resources or classpath. Use the protocol file: or classpath: depending if you want that the component loads the resource from file system or classpath. Classpath is required for OSGI deployment where the resources are packaged in the jar | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.crossOriginFilterOn* | If true, the server will support for cross-domain filtering | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.filterPath* | The filterPath will be used by the CrossOriginFilter, if the crosssOriginFilterOn is true | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.interval* | The client side poll timeout in milliseconds. How long a client will wait between reconnects | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.jsonCommented* | If true, the server will accept JSON wrapped in a comment and will generate JSON wrapped in a comment. This is a defence against Ajax Hijacking. | true | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.logLevel* | Logging level. 0=none, 1=info, 2=debug. One of: [0] [1] [2] | 1 | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.maxInterval* | The max client side poll timeout in milliseconds. A client will be removed if a connection is not received in this time. | 30000 | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.multiFrameInterval* | The client side poll timeout, if multiple connections are detected from the same browser. | 1500 | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.timeout* | The server side poll timeout in milliseconds. This is how long the server will hold a reconnect request before responding. | 240000 | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.bridgeErrorHandler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.sessionHeadersEnabled* | Whether to include the server session headers in the Camel message when creating a Camel Message for incoming requests. | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.exceptionHandler* | To let the consumer use a custom ExceptionHandler. Notice if the option bridgeErrorHandler is enabled then this option is not in use. By default the consumer will deal with exceptions, that will be logged at WARN or ERROR level and ignored. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.exchangePattern* | Sets the exchange pattern when the consumer creates an exchange. One of: [InOnly] [InOut] [InOptionalOut] | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.basicPropertyBinding* | Whether the endpoint should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.synchronous* | Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). | false | ConfigDef.Importance.MEDIUM
+| *camel.component.cometd.extensions* | To use a list of custom BayeuxServer.Extension that allows modifying incoming and outgoing requests. | null | ConfigDef.Importance.MEDIUM
+| *camel.component.cometd.bridgeErrorHandler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | ConfigDef.Importance.MEDIUM
+| *camel.component.cometd.basicPropertyBinding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+| *camel.component.cometd.securityPolicy* | To use a custom configured SecurityPolicy to control authorization | null | ConfigDef.Importance.MEDIUM
+| *camel.component.cometd.sslContextParameters* | To configure security using SSLContextParameters | null | ConfigDef.Importance.MEDIUM
+| *camel.component.cometd.sslKeyPassword* | The password for the keystore when using SSL. | null | ConfigDef.Importance.MEDIUM
+| *camel.component.cometd.sslKeystore* | The path to the keystore. | null | ConfigDef.Importance.MEDIUM
+| *camel.component.cometd.sslPassword* | The password when using SSL. | null | ConfigDef.Importance.MEDIUM
+| *camel.component.cometd.useGlobalSslContextParameters* | Enable usage of global SSL context parameters. | false | ConfigDef.Importance.MEDIUM
+|===
+
+
+// kafka-connector options: END
diff --git a/docs/modules/ROOT/pages/connectors/camel-cometds-kafka-sink-connector.adoc b/docs/modules/ROOT/pages/connectors/camel-cometds-kafka-sink-connector.adoc
new file mode 100644
index 0000000..db3aaea
--- /dev/null
+++ b/docs/modules/ROOT/pages/connectors/camel-cometds-kafka-sink-connector.adoc
@@ -0,0 +1,49 @@
+// kafka-connector options: START
+== camel-cometds-kafka-connector source configuration
+
+When using camel-cometds-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-cometds-kafka-connector</artifactId>
+ <version>x.x.x</version>
+ <!-- use the same version as your Camel Kafka connector version -->
+</dependency>
+----
+
+
+[width="100%",cols="2,5,^1,2",options="header"]
+|===
+| Name | Description | Default | Priority
+| *camel.sink.path.host* | Hostname | null | ConfigDef.Importance.HIGH
+| *camel.sink.path.port* | Host port number | null | ConfigDef.Importance.HIGH
+| *camel.sink.path.channelName* | The channelName represents a topic that can be subscribed to by the Camel endpoints. | null | ConfigDef.Importance.HIGH
+| *camel.sink.endpoint.allowedOrigins* | The origins domain that support to cross, if the crosssOriginFilterOn is true | "*" | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.baseResource* | The root directory for the web resources or classpath. Use the protocol file: or classpath: depending if you want that the component loads the resource from file system or classpath. Classpath is required for OSGI deployment where the resources are packaged in the jar | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.crossOriginFilterOn* | If true, the server will support for cross-domain filtering | false | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.filterPath* | The filterPath will be used by the CrossOriginFilter, if the crosssOriginFilterOn is true | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.interval* | The client side poll timeout in milliseconds. How long a client will wait between reconnects | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.jsonCommented* | If true, the server will accept JSON wrapped in a comment and will generate JSON wrapped in a comment. This is a defence against Ajax Hijacking. | true | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.logLevel* | Logging level. 0=none, 1=info, 2=debug. One of: [0] [1] [2] | 1 | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.maxInterval* | The max client side poll timeout in milliseconds. A client will be removed if a connection is not received in this time. | 30000 | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.multiFrameInterval* | The client side poll timeout, if multiple connections are detected from the same browser. | 1500 | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.timeout* | The server side poll timeout in milliseconds. This is how long the server will hold a reconnect request before responding. | 240000 | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.disconnectLocalSession* | Whether to disconnect local sessions after publishing a message to its channel. Disconnecting local session is needed as they are not swept by default by CometD, and therefore you can run out of memory. | false | ConfigDef.Importance.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 cre [...]
+| *camel.sink.endpoint.basicPropertyBinding* | Whether the endpoint should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.synchronous* | Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). | false | ConfigDef.Importance.MEDIUM
+| *camel.component.cometds.extensions* | To use a list of custom BayeuxServer.Extension that allows modifying incoming and outgoing requests. | null | ConfigDef.Importance.MEDIUM
+| *camel.component.cometds.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 [...]
+| *camel.component.cometds.basicPropertyBinding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+| *camel.component.cometds.securityPolicy* | To use a custom configured SecurityPolicy to control authorization | null | ConfigDef.Importance.MEDIUM
+| *camel.component.cometds.sslContextParameters* | To configure security using SSLContextParameters | null | ConfigDef.Importance.MEDIUM
+| *camel.component.cometds.sslKeyPassword* | The password for the keystore when using SSL. | null | ConfigDef.Importance.MEDIUM
+| *camel.component.cometds.sslKeystore* | The path to the keystore. | null | ConfigDef.Importance.MEDIUM
+| *camel.component.cometds.sslPassword* | The password when using SSL. | null | ConfigDef.Importance.MEDIUM
+| *camel.component.cometds.useGlobalSslContextParameters* | Enable usage of global SSL context parameters. | false | ConfigDef.Importance.MEDIUM
+|===
+
+
+// kafka-connector options: END
diff --git a/docs/modules/ROOT/pages/connectors/camel-cometds-kafka-source-connector.adoc b/docs/modules/ROOT/pages/connectors/camel-cometds-kafka-source-connector.adoc
new file mode 100644
index 0000000..1949c90
--- /dev/null
+++ b/docs/modules/ROOT/pages/connectors/camel-cometds-kafka-source-connector.adoc
@@ -0,0 +1,51 @@
+// kafka-connector options: START
+== camel-cometds-kafka-connector source configuration
+
+When using camel-cometds-kafka-connector as source 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-cometds-kafka-connector</artifactId>
+ <version>x.x.x</version>
+ <!-- use the same version as your Camel Kafka connector version -->
+</dependency>
+----
+
+
+[width="100%",cols="2,5,^1,2",options="header"]
+|===
+| Name | Description | Default | Priority
+| *camel.source.path.host* | Hostname | null | ConfigDef.Importance.HIGH
+| *camel.source.path.port* | Host port number | null | ConfigDef.Importance.HIGH
+| *camel.source.path.channelName* | The channelName represents a topic that can be subscribed to by the Camel endpoints. | null | ConfigDef.Importance.HIGH
+| *camel.source.endpoint.allowedOrigins* | The origins domain that support to cross, if the crosssOriginFilterOn is true | "*" | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.baseResource* | The root directory for the web resources or classpath. Use the protocol file: or classpath: depending if you want that the component loads the resource from file system or classpath. Classpath is required for OSGI deployment where the resources are packaged in the jar | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.crossOriginFilterOn* | If true, the server will support for cross-domain filtering | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.filterPath* | The filterPath will be used by the CrossOriginFilter, if the crosssOriginFilterOn is true | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.interval* | The client side poll timeout in milliseconds. How long a client will wait between reconnects | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.jsonCommented* | If true, the server will accept JSON wrapped in a comment and will generate JSON wrapped in a comment. This is a defence against Ajax Hijacking. | true | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.logLevel* | Logging level. 0=none, 1=info, 2=debug. One of: [0] [1] [2] | 1 | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.maxInterval* | The max client side poll timeout in milliseconds. A client will be removed if a connection is not received in this time. | 30000 | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.multiFrameInterval* | The client side poll timeout, if multiple connections are detected from the same browser. | 1500 | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.timeout* | The server side poll timeout in milliseconds. This is how long the server will hold a reconnect request before responding. | 240000 | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.bridgeErrorHandler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.sessionHeadersEnabled* | Whether to include the server session headers in the Camel message when creating a Camel Message for incoming requests. | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.exceptionHandler* | To let the consumer use a custom ExceptionHandler. Notice if the option bridgeErrorHandler is enabled then this option is not in use. By default the consumer will deal with exceptions, that will be logged at WARN or ERROR level and ignored. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.exchangePattern* | Sets the exchange pattern when the consumer creates an exchange. One of: [InOnly] [InOut] [InOptionalOut] | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.basicPropertyBinding* | Whether the endpoint should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.synchronous* | Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). | false | ConfigDef.Importance.MEDIUM
+| *camel.component.cometds.extensions* | To use a list of custom BayeuxServer.Extension that allows modifying incoming and outgoing requests. | null | ConfigDef.Importance.MEDIUM
+| *camel.component.cometds.bridgeErrorHandler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | ConfigDef.Importance.MEDIUM
+| *camel.component.cometds.basicPropertyBinding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+| *camel.component.cometds.securityPolicy* | To use a custom configured SecurityPolicy to control authorization | null | ConfigDef.Importance.MEDIUM
+| *camel.component.cometds.sslContextParameters* | To configure security using SSLContextParameters | null | ConfigDef.Importance.MEDIUM
+| *camel.component.cometds.sslKeyPassword* | The password for the keystore when using SSL. | null | ConfigDef.Importance.MEDIUM
+| *camel.component.cometds.sslKeystore* | The path to the keystore. | null | ConfigDef.Importance.MEDIUM
+| *camel.component.cometds.sslPassword* | The password when using SSL. | null | ConfigDef.Importance.MEDIUM
+| *camel.component.cometds.useGlobalSslContextParameters* | Enable usage of global SSL context parameters. | false | ConfigDef.Importance.MEDIUM
+|===
+
+
+// kafka-connector options: END
diff --git a/docs/modules/ROOT/pages/connectors/camel-consul-kafka-sink-connector.adoc b/docs/modules/ROOT/pages/connectors/camel-consul-kafka-sink-connector.adoc
new file mode 100644
index 0000000..1738be7
--- /dev/null
+++ b/docs/modules/ROOT/pages/connectors/camel-consul-kafka-sink-connector.adoc
@@ -0,0 +1,55 @@
+// kafka-connector options: START
+== camel-consul-kafka-connector source configuration
+
+When using camel-consul-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-consul-kafka-connector</artifactId>
+ <version>x.x.x</version>
+ <!-- use the same version as your Camel Kafka connector version -->
+</dependency>
+----
+
+
+[width="100%",cols="2,5,^1,2",options="header"]
+|===
+| Name | Description | Default | Priority
+| *camel.sink.path.apiEndpoint* | The API endpoint | null | ConfigDef.Importance.HIGH
+| *camel.sink.endpoint.connectTimeoutMillis* | Connect timeout for OkHttpClient | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.consulClient* | Reference to a com.orbitz.consul.Consul in the registry. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.key* | The default key. Can be overridden by CamelConsulKey | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.pingInstance* | Configure if the AgentClient should attempt a ping before returning the Consul instance | true | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.readTimeoutMillis* | Read timeout for OkHttpClient | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.tags* | Set tags. You can separate multiple tags by comma. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.url* | The Consul agent URL | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.writeTimeoutMillis* | Write timeout for OkHttpClient | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.action* | The default action. Can be overridden by CamelConsulAction | null | ConfigDef.Importance.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 cre [...]
+| *camel.sink.endpoint.valueAsString* | Default to transform values retrieved from Consul i.e. on KV endpoint to string. | false | ConfigDef.Importance.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 | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.consistencyMode* | The consistencyMode used for queries, default ConsistencyMode.DEFAULT One of: [DEFAULT] [STALE] [CONSISTENT] | "DEFAULT" | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.datacenter* | The data center | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.nearNode* | The near node to use for queries. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.nodeMeta* | The note meta-data to use for queries. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.synchronous* | Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). | false | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.aclToken* | Sets the ACL token to be used with Consul | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.password* | Sets the password to be used for basic authentication | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.sslContextParameters* | SSL configuration using an org.apache.camel.support.jsse.SSLContextParameters instance. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.userName* | Sets the username to be used for basic authentication | null | ConfigDef.Importance.MEDIUM
+| *camel.component.consul.aclToken* | Sets the ACL token to be used with Consul | null | ConfigDef.Importance.MEDIUM
+| *camel.component.consul.datacenter* | The data center | null | ConfigDef.Importance.MEDIUM
+| *camel.component.consul.password* | Sets the password to be used for basic authentication | null | ConfigDef.Importance.MEDIUM
+| *camel.component.consul.sslContextParameters* | SSL configuration using an org.apache.camel.support.jsse.SSLContextParameters instance. | null | ConfigDef.Importance.MEDIUM
+| *camel.component.consul.url* | The Consul agent URL | null | ConfigDef.Importance.MEDIUM
+| *camel.component.consul.userName* | Sets the username to be used for basic authentication | null | ConfigDef.Importance.MEDIUM
+| *camel.component.consul.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 [...]
+| *camel.component.consul.basicPropertyBinding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+| *camel.component.consul.configuration* | Sets the common configuration shared among endpoints | null | ConfigDef.Importance.MEDIUM
+| *camel.component.consul.useGlobalSslContextParameters* | Enable usage of global SSL context parameters. | false | ConfigDef.Importance.MEDIUM
+|===
+
+
+// kafka-connector options: END
diff --git a/docs/modules/ROOT/pages/connectors/camel-consul-kafka-source-connector.adoc b/docs/modules/ROOT/pages/connectors/camel-consul-kafka-source-connector.adoc
new file mode 100644
index 0000000..d6c9d16
--- /dev/null
+++ b/docs/modules/ROOT/pages/connectors/camel-consul-kafka-source-connector.adoc
@@ -0,0 +1,58 @@
+// kafka-connector options: START
+== camel-consul-kafka-connector source configuration
+
+When using camel-consul-kafka-connector as source 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-consul-kafka-connector</artifactId>
+ <version>x.x.x</version>
+ <!-- use the same version as your Camel Kafka connector version -->
+</dependency>
+----
+
+
+[width="100%",cols="2,5,^1,2",options="header"]
+|===
+| Name | Description | Default | Priority
+| *camel.source.path.apiEndpoint* | The API endpoint | null | ConfigDef.Importance.HIGH
+| *camel.source.endpoint.connectTimeoutMillis* | Connect timeout for OkHttpClient | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.consulClient* | Reference to a com.orbitz.consul.Consul in the registry. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.key* | The default key. Can be overridden by CamelConsulKey | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.pingInstance* | Configure if the AgentClient should attempt a ping before returning the Consul instance | true | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.readTimeoutMillis* | Read timeout for OkHttpClient | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.tags* | Set tags. You can separate multiple tags by comma. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.url* | The Consul agent URL | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.writeTimeoutMillis* | Write timeout for OkHttpClient | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.bridgeErrorHandler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.exceptionHandler* | To let the consumer use a custom ExceptionHandler. Notice if the option bridgeErrorHandler is enabled then this option is not in use. By default the consumer will deal with exceptions, that will be logged at WARN or ERROR level and ignored. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.exchangePattern* | Sets the exchange pattern when the consumer creates an exchange. One of: [InOnly] [InOut] [InOptionalOut] | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.basicPropertyBinding* | Whether the endpoint should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.consistencyMode* | The consistencyMode used for queries, default ConsistencyMode.DEFAULT One of: [DEFAULT] [STALE] [CONSISTENT] | "DEFAULT" | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.datacenter* | The data center | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.nearNode* | The near node to use for queries. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.nodeMeta* | The note meta-data to use for queries. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.synchronous* | Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.blockSeconds* | The second to wait for a watch event, default 10 seconds | "10" | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.firstIndex* | The first index for watch for, default 0 | "0" | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.recursive* | Recursively watch, default false | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.aclToken* | Sets the ACL token to be used with Consul | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.password* | Sets the password to be used for basic authentication | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.sslContextParameters* | SSL configuration using an org.apache.camel.support.jsse.SSLContextParameters instance. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.userName* | Sets the username to be used for basic authentication | null | ConfigDef.Importance.MEDIUM
+| *camel.component.consul.aclToken* | Sets the ACL token to be used with Consul | null | ConfigDef.Importance.MEDIUM
+| *camel.component.consul.datacenter* | The data center | null | ConfigDef.Importance.MEDIUM
+| *camel.component.consul.password* | Sets the password to be used for basic authentication | null | ConfigDef.Importance.MEDIUM
+| *camel.component.consul.sslContextParameters* | SSL configuration using an org.apache.camel.support.jsse.SSLContextParameters instance. | null | ConfigDef.Importance.MEDIUM
+| *camel.component.consul.url* | The Consul agent URL | null | ConfigDef.Importance.MEDIUM
+| *camel.component.consul.userName* | Sets the username to be used for basic authentication | null | ConfigDef.Importance.MEDIUM
+| *camel.component.consul.bridgeErrorHandler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | ConfigDef.Importance.MEDIUM
+| *camel.component.consul.basicPropertyBinding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+| *camel.component.consul.configuration* | Sets the common configuration shared among endpoints | null | ConfigDef.Importance.MEDIUM
+| *camel.component.consul.useGlobalSslContextParameters* | Enable usage of global SSL context parameters. | false | ConfigDef.Importance.MEDIUM
+|===
+
+
+// kafka-connector options: END
diff --git a/docs/modules/ROOT/pages/connectors/camel-controlbus-kafka-sink-connector.adoc b/docs/modules/ROOT/pages/connectors/camel-controlbus-kafka-sink-connector.adoc
new file mode 100644
index 0000000..c459ee9
--- /dev/null
+++ b/docs/modules/ROOT/pages/connectors/camel-controlbus-kafka-sink-connector.adoc
@@ -0,0 +1,35 @@
+// kafka-connector options: START
+== camel-controlbus-kafka-connector source configuration
+
+When using camel-controlbus-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-controlbus-kafka-connector</artifactId>
+ <version>x.x.x</version>
+ <!-- use the same version as your Camel Kafka connector version -->
+</dependency>
+----
+
+
+[width="100%",cols="2,5,^1,2",options="header"]
+|===
+| Name | Description | Default | Priority
+| *camel.sink.path.command* | Command can be either route or language One of: [route] [language] | null | ConfigDef.Importance.HIGH
+| *camel.sink.path.language* | Allows you to specify the name of a Language to use for evaluating the message body. If there is any result from the evaluation, then the result is put in the message body. One of: [bean] [constant] [el] [exchangeProperty] [file] [groovy] [header] [jsonpath] [mvel] [ognl] [ref] [simple] [spel] [sql] [terser] [tokenize] [xpath] [xquery] [xtokenize] | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.action* | To denote an action that can be either: start, stop, or status. To either start or stop a route, or to get the status of the route as output in the message body. You can use suspend and resume from Camel 2.11.1 onwards to either suspend or resume a route. And from Camel 2.11.1 onwards you can use stats to get performance statics returned in XML format; the routeId option can be used to define which route to get the performance stats for, if routeId is not [...]
+| *camel.sink.endpoint.async* | Whether to execute the control bus task asynchronously. Important: If this option is enabled, then any result from the task is not set on the Exchange. This is only possible if executing tasks synchronously. | false | ConfigDef.Importance.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 cre [...]
+| *camel.sink.endpoint.loggingLevel* | Logging level used for logging when task is done, or if any exceptions occurred during processing the task. One of: [TRACE] [DEBUG] [INFO] [WARN] [ERROR] [OFF] | "INFO" | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.restartDelay* | The delay in millis to use when restarting a route. | 1000 | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.routeId* | To specify a route by its id. The special keyword current indicates the current route. | null | ConfigDef.Importance.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 | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.synchronous* | Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). | false | ConfigDef.Importance.MEDIUM
+| *camel.component.controlbus.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 t [...]
+| *camel.component.controlbus.basicPropertyBinding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+|===
+
+
+// kafka-connector options: END
diff --git a/docs/modules/ROOT/pages/connectors/camel-corda-kafka-sink-connector.adoc b/docs/modules/ROOT/pages/connectors/camel-corda-kafka-sink-connector.adoc
new file mode 100644
index 0000000..a652cda
--- /dev/null
+++ b/docs/modules/ROOT/pages/connectors/camel-corda-kafka-sink-connector.adoc
@@ -0,0 +1,33 @@
+// kafka-connector options: START
+== camel-corda-kafka-connector source configuration
+
+When using camel-corda-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-corda-kafka-connector</artifactId>
+ <version>x.x.x</version>
+ <!-- use the same version as your Camel Kafka connector version -->
+</dependency>
+----
+
+
+[width="100%",cols="2,5,^1,2",options="header"]
+|===
+| Name | Description | Default | Priority
+| *camel.sink.path.node* | The url for the corda node | null | ConfigDef.Importance.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 cre [...]
+| *camel.sink.endpoint.operation* | Operation to use | null | ConfigDef.Importance.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 | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.synchronous* | Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). | false | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.password* | Password for login | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.username* | Username for login | null | ConfigDef.Importance.MEDIUM
+| *camel.component.corda.configuration* | To use a shared configuration. | null | ConfigDef.Importance.MEDIUM
+| *camel.component.corda.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 c [...]
+| *camel.component.corda.basicPropertyBinding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+|===
+
+
+// kafka-connector options: END
diff --git a/docs/modules/ROOT/pages/connectors/camel-corda-kafka-source-connector.adoc b/docs/modules/ROOT/pages/connectors/camel-corda-kafka-source-connector.adoc
new file mode 100644
index 0000000..dff1694
--- /dev/null
+++ b/docs/modules/ROOT/pages/connectors/camel-corda-kafka-source-connector.adoc
@@ -0,0 +1,41 @@
+// kafka-connector options: START
+== camel-corda-kafka-connector source configuration
+
+When using camel-corda-kafka-connector as source 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-corda-kafka-connector</artifactId>
+ <version>x.x.x</version>
+ <!-- use the same version as your Camel Kafka connector version -->
+</dependency>
+----
+
+
+[width="100%",cols="2,5,^1,2",options="header"]
+|===
+| Name | Description | Default | Priority
+| *camel.source.path.node* | The url for the corda node | null | ConfigDef.Importance.HIGH
+| *camel.source.endpoint.bridgeErrorHandler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.pageSpecification* | PageSpecification allows specification of a page number (starting from 1) and page size (defaulting to 200 with a maximum page size of (Integer.MAX_INT) Note: we default the page number to 200 to enable queries without requiring a page specification but enabling detection of large results sets that fall out of the 200 requirement. Max page size should be used with extreme caution as results may exceed your JVM memory footprint. | "200" | Conf [...]
+| *camel.source.endpoint.processSnapshot* | Whether to process snapshots or not | true | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.sort* | Sort allows specification of a set of entity attribute names and their associated directionality and null handling, to be applied upon processing a query specification. One of: [ASC] [DESC] | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.contractStateClass* | A contract state (or just state) contains opaque data used by a contract program. It can be thought of as a disk file that the program can use to persist data across transactions. States are immutable: once created they are never updated, instead, any changes must generate a new successor state. States can be updated (consumed) only once: the notary is responsible for ensuring there is no double spending by only signing a transaction if the [...]
+| *camel.source.endpoint.exceptionHandler* | To let the consumer use a custom ExceptionHandler. Notice if the option bridgeErrorHandler is enabled then this option is not in use. By default the consumer will deal with exceptions, that will be logged at WARN or ERROR level and ignored. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.exchangePattern* | Sets the exchange pattern when the consumer creates an exchange. One of: [InOnly] [InOut] [InOptionalOut] | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.flowLogicArguments* | Start the given flow with the given arguments, returning an Observable with a single observation of the result of running the flow. The flowLogicClass must be annotated with net.corda.core.flows.StartableByRPC. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.flowLogicClass* | Start the given flow with the given arguments, returning an Observable with a single observation of the result of running the flow. The flowLogicClass must be annotated with net.corda.core.flows.StartableByRPC. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.queryCriteria* | QueryCriteria assumes underlying schema tables are correctly indexed for performance. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.basicPropertyBinding* | Whether the endpoint should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.synchronous* | Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.password* | Password for login | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.username* | Username for login | null | ConfigDef.Importance.MEDIUM
+| *camel.component.corda.configuration* | To use a shared configuration. | null | ConfigDef.Importance.MEDIUM
+| *camel.component.corda.bridgeErrorHandler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | ConfigDef.Importance.MEDIUM
+| *camel.component.corda.basicPropertyBinding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+|===
+
+
+// kafka-connector options: END
diff --git a/docs/modules/ROOT/pages/connectors/camel-couchbase-kafka-sink-connector.adoc b/docs/modules/ROOT/pages/connectors/camel-couchbase-kafka-sink-connector.adoc
new file mode 100644
index 0000000..973d79c
--- /dev/null
+++ b/docs/modules/ROOT/pages/connectors/camel-couchbase-kafka-sink-connector.adoc
@@ -0,0 +1,51 @@
+// kafka-connector options: START
+== camel-couchbase-kafka-connector source configuration
+
+When using camel-couchbase-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-couchbase-kafka-connector</artifactId>
+ <version>x.x.x</version>
+ <!-- use the same version as your Camel Kafka connector version -->
+</dependency>
+----
+
+
+[width="100%",cols="2,5,^1,2",options="header"]
+|===
+| Name | Description | Default | Priority
+| *camel.sink.path.protocol* | The protocol to use | null | ConfigDef.Importance.HIGH
+| *camel.sink.path.hostname* | The hostname to use | null | ConfigDef.Importance.HIGH
+| *camel.sink.path.port* | The port number to use | 8091 | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.bucket* | The bucket to use | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.key* | The key to use | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.autoStartIdForInserts* | Define if we want an autostart Id when we are doing an insert operation | false | ConfigDef.Importance.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 cre [...]
+| *camel.sink.endpoint.operation* | The operation to do | "CCB_PUT" | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.persistTo* | Where to persist the data | 0 | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.producerRetryAttempts* | Define the number of retry attempts | 2 | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.producerRetryPause* | Define the retry pause between different attempts | 5000 | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.replicateTo* | Where to replicate the data | 0 | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.startingIdForInsertsFrom* | Define the starting Id where we are doing an insert operation | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.additionalHosts* | The additional hosts | null | ConfigDef.Importance.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 | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.maxReconnectDelay* | Define the max delay during a reconnection | 30000L | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.obsPollInterval* | Define the observation polling interval | 400L | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.obsTimeout* | Define the observation timeout | -1L | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.opQueueMaxBlockTime* | Define the max time an operation can be in queue blocked | 10000L | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.opTimeOut* | Define the operation timeout | 2500L | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.readBufferSize* | Define the buffer size | 16384 | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.shouldOptimize* | Define if we want to use optimization or not where possible | false | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.synchronous* | Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). | false | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.timeoutExceptionThreshold* | Define the threshold for throwing a timeout Exception | 998 | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.password* | The password to use | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.username* | The username to use | null | ConfigDef.Importance.MEDIUM
+| *camel.component.couchbase.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 th [...]
+| *camel.component.couchbase.basicPropertyBinding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+|===
+
+
+// kafka-connector options: END
diff --git a/docs/modules/ROOT/pages/connectors/camel-couchbase-kafka-source-connector.adoc b/docs/modules/ROOT/pages/connectors/camel-couchbase-kafka-source-connector.adoc
new file mode 100644
index 0000000..0952e9e
--- /dev/null
+++ b/docs/modules/ROOT/pages/connectors/camel-couchbase-kafka-source-connector.adoc
@@ -0,0 +1,70 @@
+// kafka-connector options: START
+== camel-couchbase-kafka-connector source configuration
+
+When using camel-couchbase-kafka-connector as source 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-couchbase-kafka-connector</artifactId>
+ <version>x.x.x</version>
+ <!-- use the same version as your Camel Kafka connector version -->
+</dependency>
+----
+
+
+[width="100%",cols="2,5,^1,2",options="header"]
+|===
+| Name | Description | Default | Priority
+| *camel.source.path.protocol* | The protocol to use | null | ConfigDef.Importance.HIGH
+| *camel.source.path.hostname* | The hostname to use | null | ConfigDef.Importance.HIGH
+| *camel.source.path.port* | The port number to use | 8091 | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.bucket* | The bucket to use | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.key* | The key to use | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.bridgeErrorHandler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.consumerProcessedStrategy* | Define the consumer Processed strategy to use | "none" | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.descending* | Define if this operation is descending or not | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.designDocumentName* | The design document name to use | "beer" | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.limit* | The output limit to use | -1 | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.rangeEndKey* | Define a range for the end key | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.rangeStartKey* | Define a range for the start key | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.sendEmptyMessageWhenIdle* | If the polling consumer did not poll any files, you can enable this option to send an empty message (no body) instead. | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.skip* | Define the skip to use | -1 | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.viewName* | The view name to use | "brewery_beers" | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.exceptionHandler* | To let the consumer use a custom ExceptionHandler. Notice if the option bridgeErrorHandler is enabled then this option is not in use. By default the consumer will deal with exceptions, that will be logged at WARN or ERROR level and ignored. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.exchangePattern* | Sets the exchange pattern when the consumer creates an exchange. One of: [InOnly] [InOut] [InOptionalOut] | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.pollStrategy* | A pluggable org.apache.camel.PollingConsumerPollingStrategy allowing you to provide your custom implementation to control error handling usually occurred during the poll operation before an Exchange have been created and being routed in Camel. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.additionalHosts* | The additional hosts | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.basicPropertyBinding* | Whether the endpoint should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.maxReconnectDelay* | Define the max delay during a reconnection | 30000L | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.obsPollInterval* | Define the observation polling interval | 400L | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.obsTimeout* | Define the observation timeout | -1L | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.opQueueMaxBlockTime* | Define the max time an operation can be in queue blocked | 10000L | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.opTimeOut* | Define the operation timeout | 2500L | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.readBufferSize* | Define the buffer size | 16384 | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.shouldOptimize* | Define if we want to use optimization or not where possible | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.synchronous* | Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.timeoutExceptionThreshold* | Define the threshold for throwing a timeout Exception | 998 | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.backoffErrorThreshold* | The number of subsequent error polls (failed due some error) that should happen before the backoffMultipler should kick-in. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.backoffIdleThreshold* | The number of subsequent idle polls that should happen before the backoffMultipler should kick-in. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.backoffMultiplier* | To let the scheduled polling consumer backoff if there has been a number of subsequent idles/errors in a row. The multiplier is then the number of polls that will be skipped before the next actual attempt is happening again. When this option is in use then backoffIdleThreshold and/or backoffErrorThreshold must also be configured. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.delay* | Milliseconds before the next poll. You can also specify time values using units, such as 60s (60 seconds), 5m30s (5 minutes and 30 seconds), and 1h (1 hour). | 500L | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.greedy* | If greedy is enabled, then the ScheduledPollConsumer will run immediately again, if the previous run polled 1 or more messages. | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.initialDelay* | Milliseconds before the first poll starts. You can also specify time values using units, such as 60s (60 seconds), 5m30s (5 minutes and 30 seconds), and 1h (1 hour). | 1000L | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.repeatCount* | Specifies a maximum limit of number of fires. So if you set it to 1, the scheduler will only fire once. If you set it to 5, it will only fire five times. A value of zero or negative means fire forever. | 0L | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.runLoggingLevel* | The consumer logs a start/complete log line when it polls. This option allows you to configure the logging level for that. One of: [TRACE] [DEBUG] [INFO] [WARN] [ERROR] [OFF] | "TRACE" | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.scheduledExecutorService* | Allows for configuring a custom/shared thread pool to use for the consumer. By default each consumer has its own single threaded thread pool. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.scheduler* | To use a cron scheduler from either camel-spring or camel-quartz component One of: [none] [spring] [quartz] | "none" | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.schedulerProperties* | To configure additional properties when using a custom scheduler or any of the Quartz, Spring based scheduler. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.startScheduler* | Whether the scheduler should be auto started. | true | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.timeUnit* | Time unit for initialDelay and delay options. One of: [NANOSECONDS] [MICROSECONDS] [MILLISECONDS] [SECONDS] [MINUTES] [HOURS] [DAYS] | "MILLISECONDS" | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.useFixedDelay* | Controls if fixed delay or fixed rate is used. See ScheduledExecutorService in JDK for details. | true | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.password* | The password to use | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.username* | The username to use | null | ConfigDef.Importance.MEDIUM
+| *camel.component.couchbase.bridgeErrorHandler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | ConfigDef.Importance.MEDIUM
+| *camel.component.couchbase.basicPropertyBinding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+|===
+
+
+// kafka-connector options: END
diff --git a/docs/modules/ROOT/pages/connectors/camel-couchdb-kafka-sink-connector.adoc b/docs/modules/ROOT/pages/connectors/camel-couchdb-kafka-sink-connector.adoc
new file mode 100644
index 0000000..415e6bc
--- /dev/null
+++ b/docs/modules/ROOT/pages/connectors/camel-couchdb-kafka-sink-connector.adoc
@@ -0,0 +1,35 @@
+// kafka-connector options: START
+== camel-couchdb-kafka-connector source configuration
+
+When using camel-couchdb-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-couchdb-kafka-connector</artifactId>
+ <version>x.x.x</version>
+ <!-- use the same version as your Camel Kafka connector version -->
+</dependency>
+----
+
+
+[width="100%",cols="2,5,^1,2",options="header"]
+|===
+| Name | Description | Default | Priority
+| *camel.sink.path.protocol* | The protocol to use for communicating with the database. One of: [http] [https] | null | ConfigDef.Importance.HIGH
+| *camel.sink.path.hostname* | Hostname of the running couchdb instance | null | ConfigDef.Importance.HIGH
+| *camel.sink.path.port* | Port number for the running couchdb instance | 5984 | ConfigDef.Importance.MEDIUM
+| *camel.sink.path.database* | Name of the database to use | null | ConfigDef.Importance.HIGH
+| *camel.sink.endpoint.createDatabase* | Creates the database if it does not already exist | false | ConfigDef.Importance.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 cre [...]
+| *camel.sink.endpoint.basicPropertyBinding* | Whether the endpoint should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.synchronous* | Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). | false | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.password* | Password for authenticated databases | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.username* | Username in case of authenticated databases | null | ConfigDef.Importance.MEDIUM
+| *camel.component.couchdb.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 [...]
+| *camel.component.couchdb.basicPropertyBinding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+|===
+
+
+// kafka-connector options: END
diff --git a/docs/modules/ROOT/pages/connectors/camel-couchdb-kafka-source-connector.adoc b/docs/modules/ROOT/pages/connectors/camel-couchdb-kafka-source-connector.adoc
new file mode 100644
index 0000000..713a3cc
--- /dev/null
+++ b/docs/modules/ROOT/pages/connectors/camel-couchdb-kafka-source-connector.adoc
@@ -0,0 +1,42 @@
+// kafka-connector options: START
+== camel-couchdb-kafka-connector source configuration
+
+When using camel-couchdb-kafka-connector as source 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-couchdb-kafka-connector</artifactId>
+ <version>x.x.x</version>
+ <!-- use the same version as your Camel Kafka connector version -->
+</dependency>
+----
+
+
+[width="100%",cols="2,5,^1,2",options="header"]
+|===
+| Name | Description | Default | Priority
+| *camel.source.path.protocol* | The protocol to use for communicating with the database. One of: [http] [https] | null | ConfigDef.Importance.HIGH
+| *camel.source.path.hostname* | Hostname of the running couchdb instance | null | ConfigDef.Importance.HIGH
+| *camel.source.path.port* | Port number for the running couchdb instance | 5984 | ConfigDef.Importance.MEDIUM
+| *camel.source.path.database* | Name of the database to use | null | ConfigDef.Importance.HIGH
+| *camel.source.endpoint.createDatabase* | Creates the database if it does not already exist | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.bridgeErrorHandler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.deletes* | Document deletes are published as events | true | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.heartbeat* | How often to send an empty message to keep socket alive in millis | 30000L | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.since* | Start tracking changes immediately after the given update sequence. The default, null, will start monitoring from the latest sequence. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.style* | Specifies how many revisions are returned in the changes array. The default, main_only, will only return the current winning revision; all_docs will return all leaf revisions (including conflicts and deleted former conflicts.) One of: [all_docs] [main_only] | "main_only" | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.updates* | Document inserts/updates are published as events | true | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.exceptionHandler* | To let the consumer use a custom ExceptionHandler. Notice if the option bridgeErrorHandler is enabled then this option is not in use. By default the consumer will deal with exceptions, that will be logged at WARN or ERROR level and ignored. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.exchangePattern* | Sets the exchange pattern when the consumer creates an exchange. One of: [InOnly] [InOut] [InOptionalOut] | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.basicPropertyBinding* | Whether the endpoint should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.synchronous* | Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.password* | Password for authenticated databases | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.username* | Username in case of authenticated databases | null | ConfigDef.Importance.MEDIUM
+| *camel.component.couchdb.bridgeErrorHandler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | ConfigDef.Importance.MEDIUM
+| *camel.component.couchdb.basicPropertyBinding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+|===
+
+
+// kafka-connector options: END
diff --git a/docs/modules/ROOT/pages/connectors/camel-cql-kafka-sink-connector.adoc b/docs/modules/ROOT/pages/connectors/camel-cql-kafka-sink-connector.adoc
new file mode 100644
index 0000000..249f35c
--- /dev/null
+++ b/docs/modules/ROOT/pages/connectors/camel-cql-kafka-sink-connector.adoc
@@ -0,0 +1,42 @@
+// kafka-connector options: START
+== camel-cql-kafka-connector source configuration
+
+When using camel-cql-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-cql-kafka-connector</artifactId>
+ <version>x.x.x</version>
+ <!-- use the same version as your Camel Kafka connector version -->
+</dependency>
+----
+
+
+[width="100%",cols="2,5,^1,2",options="header"]
+|===
+| Name | Description | Default | Priority
+| *camel.sink.path.beanRef* | beanRef is defined using bean:id | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.path.hosts* | Hostname(s) cassansdra server(s). Multiple hosts can be separated by comma. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.path.port* | Port number of cassansdra server(s) | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.path.keyspace* | Keyspace to use | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.cluster* | To use the Cluster instance (you would normally not use this option) | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.clusterName* | Cluster name | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.consistencyLevel* | Consistency level to use One of: [ANY] [ONE] [TWO] [THREE] [QUORUM] [ALL] [LOCAL_QUORUM] [EACH_QUORUM] [SERIAL] [LOCAL_SERIAL] [LOCAL_ONE] | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.cql* | CQL query to perform. Can be overridden with the message header with key CamelCqlQuery. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.loadBalancingPolicy* | To use a specific LoadBalancingPolicy | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.password* | Password for session authentication | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.prepareStatements* | Whether to use PreparedStatements or regular Statements | true | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.resultSetConversionStrategy* | To use a custom class that implements logic for converting ResultSet into message body ALL, ONE, LIMIT_10, LIMIT_100... | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.session* | To use the Session instance (you would normally not use this option) | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.username* | Username for session authentication | null | ConfigDef.Importance.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 cre [...]
+| *camel.sink.endpoint.basicPropertyBinding* | Whether the endpoint should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.synchronous* | Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). | false | ConfigDef.Importance.MEDIUM
+| *camel.component.cql.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 cre [...]
+| *camel.component.cql.basicPropertyBinding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+|===
+
+
+// kafka-connector options: END
diff --git a/docs/modules/ROOT/pages/connectors/camel-cql-kafka-source-connector.adoc b/docs/modules/ROOT/pages/connectors/camel-cql-kafka-source-connector.adoc
new file mode 100644
index 0000000..68f13b7
--- /dev/null
+++ b/docs/modules/ROOT/pages/connectors/camel-cql-kafka-source-connector.adoc
@@ -0,0 +1,60 @@
+// kafka-connector options: START
+== camel-cql-kafka-connector source configuration
+
+When using camel-cql-kafka-connector as source 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-cql-kafka-connector</artifactId>
+ <version>x.x.x</version>
+ <!-- use the same version as your Camel Kafka connector version -->
+</dependency>
+----
+
+
+[width="100%",cols="2,5,^1,2",options="header"]
+|===
+| Name | Description | Default | Priority
+| *camel.source.path.beanRef* | beanRef is defined using bean:id | null | ConfigDef.Importance.MEDIUM
+| *camel.source.path.hosts* | Hostname(s) cassansdra server(s). Multiple hosts can be separated by comma. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.path.port* | Port number of cassansdra server(s) | null | ConfigDef.Importance.MEDIUM
+| *camel.source.path.keyspace* | Keyspace to use | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.cluster* | To use the Cluster instance (you would normally not use this option) | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.clusterName* | Cluster name | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.consistencyLevel* | Consistency level to use One of: [ANY] [ONE] [TWO] [THREE] [QUORUM] [ALL] [LOCAL_QUORUM] [EACH_QUORUM] [SERIAL] [LOCAL_SERIAL] [LOCAL_ONE] | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.cql* | CQL query to perform. Can be overridden with the message header with key CamelCqlQuery. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.loadBalancingPolicy* | To use a specific LoadBalancingPolicy | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.password* | Password for session authentication | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.prepareStatements* | Whether to use PreparedStatements or regular Statements | true | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.resultSetConversionStrategy* | To use a custom class that implements logic for converting ResultSet into message body ALL, ONE, LIMIT_10, LIMIT_100... | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.session* | To use the Session instance (you would normally not use this option) | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.username* | Username for session authentication | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.bridgeErrorHandler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.sendEmptyMessageWhenIdle* | If the polling consumer did not poll any files, you can enable this option to send an empty message (no body) instead. | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.exceptionHandler* | To let the consumer use a custom ExceptionHandler. Notice if the option bridgeErrorHandler is enabled then this option is not in use. By default the consumer will deal with exceptions, that will be logged at WARN or ERROR level and ignored. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.exchangePattern* | Sets the exchange pattern when the consumer creates an exchange. One of: [InOnly] [InOut] [InOptionalOut] | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.pollStrategy* | A pluggable org.apache.camel.PollingConsumerPollingStrategy allowing you to provide your custom implementation to control error handling usually occurred during the poll operation before an Exchange have been created and being routed in Camel. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.basicPropertyBinding* | Whether the endpoint should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.synchronous* | Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.backoffErrorThreshold* | The number of subsequent error polls (failed due some error) that should happen before the backoffMultipler should kick-in. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.backoffIdleThreshold* | The number of subsequent idle polls that should happen before the backoffMultipler should kick-in. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.backoffMultiplier* | To let the scheduled polling consumer backoff if there has been a number of subsequent idles/errors in a row. The multiplier is then the number of polls that will be skipped before the next actual attempt is happening again. When this option is in use then backoffIdleThreshold and/or backoffErrorThreshold must also be configured. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.delay* | Milliseconds before the next poll. You can also specify time values using units, such as 60s (60 seconds), 5m30s (5 minutes and 30 seconds), and 1h (1 hour). | 500L | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.greedy* | If greedy is enabled, then the ScheduledPollConsumer will run immediately again, if the previous run polled 1 or more messages. | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.initialDelay* | Milliseconds before the first poll starts. You can also specify time values using units, such as 60s (60 seconds), 5m30s (5 minutes and 30 seconds), and 1h (1 hour). | 1000L | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.repeatCount* | Specifies a maximum limit of number of fires. So if you set it to 1, the scheduler will only fire once. If you set it to 5, it will only fire five times. A value of zero or negative means fire forever. | 0L | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.runLoggingLevel* | The consumer logs a start/complete log line when it polls. This option allows you to configure the logging level for that. One of: [TRACE] [DEBUG] [INFO] [WARN] [ERROR] [OFF] | "TRACE" | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.scheduledExecutorService* | Allows for configuring a custom/shared thread pool to use for the consumer. By default each consumer has its own single threaded thread pool. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.scheduler* | To use a cron scheduler from either camel-spring or camel-quartz component One of: [none] [spring] [quartz] | "none" | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.schedulerProperties* | To configure additional properties when using a custom scheduler or any of the Quartz, Spring based scheduler. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.startScheduler* | Whether the scheduler should be auto started. | true | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.timeUnit* | Time unit for initialDelay and delay options. One of: [NANOSECONDS] [MICROSECONDS] [MILLISECONDS] [SECONDS] [MINUTES] [HOURS] [DAYS] | "MILLISECONDS" | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.useFixedDelay* | Controls if fixed delay or fixed rate is used. See ScheduledExecutorService in JDK for details. | true | ConfigDef.Importance.MEDIUM
+| *camel.component.cql.bridgeErrorHandler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | ConfigDef.Importance.MEDIUM
+| *camel.component.cql.basicPropertyBinding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+|===
+
+
+// kafka-connector options: END
diff --git a/docs/modules/ROOT/pages/connectors/camel-cron-kafka-source-connector.adoc b/docs/modules/ROOT/pages/connectors/camel-cron-kafka-source-connector.adoc
new file mode 100644
index 0000000..2266f7f
--- /dev/null
+++ b/docs/modules/ROOT/pages/connectors/camel-cron-kafka-source-connector.adoc
@@ -0,0 +1,33 @@
+// kafka-connector options: START
+== camel-cron-kafka-connector source configuration
+
+When using camel-cron-kafka-connector as source 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-cron-kafka-connector</artifactId>
+ <version>x.x.x</version>
+ <!-- use the same version as your Camel Kafka connector version -->
+</dependency>
+----
+
+
+[width="100%",cols="2,5,^1,2",options="header"]
+|===
+| Name | Description | Default | Priority
+| *camel.source.path.name* | The name of the cron trigger | null | ConfigDef.Importance.HIGH
+| *camel.source.endpoint.bridgeErrorHandler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.schedule* | A cron expression that will be used to generate events | null | ConfigDef.Importance.HIGH
+| *camel.source.endpoint.exceptionHandler* | To let the consumer use a custom ExceptionHandler. Notice if the option bridgeErrorHandler is enabled then this option is not in use. By default the consumer will deal with exceptions, that will be logged at WARN or ERROR level and ignored. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.exchangePattern* | Sets the exchange pattern when the consumer creates an exchange. One of: [InOnly] [InOut] [InOptionalOut] | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.basicPropertyBinding* | Whether the endpoint should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.synchronous* | Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). | false | ConfigDef.Importance.MEDIUM
+| *camel.component.cron.bridgeErrorHandler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | ConfigDef.Importance.MEDIUM
+| *camel.component.cron.basicPropertyBinding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+| *camel.component.cron.cronService* | The id of the CamelCronService to use when multiple implementations are provided | null | ConfigDef.Importance.MEDIUM
+|===
+
+
+// kafka-connector options: END
diff --git a/docs/modules/ROOT/pages/connectors/camel-crypto-cms-kafka-sink-connector.adoc b/docs/modules/ROOT/pages/connectors/camel-crypto-cms-kafka-sink-connector.adoc
new file mode 100644
index 0000000..d27bd0b
--- /dev/null
+++ b/docs/modules/ROOT/pages/connectors/camel-crypto-cms-kafka-sink-connector.adoc
@@ -0,0 +1,46 @@
+// kafka-connector options: START
+== camel-crypto-cms-kafka-connector source configuration
+
+When using camel-crypto-cms-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-crypto-cms-kafka-connector</artifactId>
+ <version>x.x.x</version>
+ <!-- use the same version as your Camel Kafka connector version -->
+</dependency>
+----
+
+
+[width="100%",cols="2,5,^1,2",options="header"]
+|===
+| Name | Description | Default | Priority
+| *camel.sink.path.cryptoOperation* | Set the Crypto operation from that supplied after the crypto scheme in the endpoint uri e.g. crypto-cms:sign sets sign as the operation. Possible values: sign, verify, encrypt, or decrypt. One of: [sign] [verify] [encrypt] [decrypt] | null | ConfigDef.Importance.HIGH
+| *camel.sink.path.name* | The name part in the URI can be chosen by the user to distinguish between different signer/verifier/encryptor/decryptor endpoints within the camel context. | null | ConfigDef.Importance.HIGH
+| *camel.sink.endpoint.keyStore* | Keystore which contains signer private keys, verifier public keys, encryptor public keys, decryptor private keys depending on the operation. Use either this parameter or the parameter 'keyStoreParameters'. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.keyStoreParameters* | Keystore containing signer private keys, verifier public keys, encryptor public keys, decryptor private keys depending on the operation. Use either this parameter or the parameter 'keystore'. | null | ConfigDef.Importance.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 cre [...]
+| *camel.sink.endpoint.basicPropertyBinding* | Whether the endpoint should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.synchronous* | Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). | false | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.password* | Sets the password of the private keys. It is assumed that all private keys in the keystore have the same password. If not set then it is assumed that the password of the private keys is given by the keystore password given in the KeyStoreParameters. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.fromBase64* | If true then the CMS message is base 64 encoded and must be decoded during the processing. Default value is false. | false | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.contentEncryptionAlgorithm* | Encryption algorithm, for example DESede/CBC/PKCS5Padding. Further possible values: DESede/CBC/PKCS5Padding, AES/CBC/PKCS5Padding, Camellia/CBC/PKCS5Padding, CAST5/CBC/PKCS5Padding. One of: [AES/CBC/PKCS5Padding] [DESede/CBC/PKCS5Padding] [Camellia/CBC/PKCS5Padding] [CAST5/CBC/PKCS5Padding] | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.originatorInformationProvider* | Provider for the originator info. See \https://tools.ietf.org/html/rfc5652#section-6.1. The default value is null. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.recipient* | Recipient Info: reference to a bean which implements the interface org.apache.camel.component.crypto.cms.api.TransRecipientInfo | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.secretKeyLength* | Key length for the secret symmetric key used for the content encryption. Only used if the specified content-encryption algorithm allows keys of different sizes. If contentEncryptionAlgorithm=AES/CBC/PKCS5Padding or Camellia/CBC/PKCS5Padding then 128; if contentEncryptionAlgorithm=DESede/CBC/PKCS5Padding then 192, 128; if strong encryption is enabled then for AES/CBC/PKCS5Padding and Camellia/CBC/PKCS5Padding also the key lengths 192 and 256 are p [...]
+| *camel.sink.endpoint.unprotectedAttributesGeneratorProvider* | Provider of the generator for the unprotected attributes. The default value is null which means no unprotected attribute is added to the Enveloped Data object. See \https://tools.ietf.org/html/rfc5652#section-6.1. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.toBase64* | Indicates whether the Signed Data or Enveloped Data instance shall be base 64 encoded. Default value is false. | "false" | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.includeContent* | Indicates whether the signed content should be included into the Signed Data instance. If false then a detached Signed Data instance is created in the header CamelCryptoCmsSignedData. | "true" | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.signer* | Signer information: reference to bean(s) which implements org.apache.camel.component.crypto.cms.api.SignerInfo. Multiple values can be separated by comma | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.signedDataHeaderBase64* | Indicates whether the value in the header CamelCryptoCmsSignedData is base64 encoded. Default value is false. Only relevant for detached signatures. In the detached signature case, the header contains the Signed Data object. | false | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.verifySignaturesOfAllSigners* | If true then the signatures of all signers contained in the Signed Data object are verified. If false then only one signature whose signer info matches with one of the specified certificates is verified. Default value is true. | true | ConfigDef.Importance.MEDIUM
+| *camel.component.crypto-cms.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 t [...]
+| *camel.component.crypto-cms.basicPropertyBinding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+| *camel.component.crypto-cms.envelopedDataDecryptorConfiguration* | To configure the shared EnvelopedDataDecryptorConfiguration, which determines the uri parameters for the decrypt operation. | null | ConfigDef.Importance.MEDIUM
+| *camel.component.crypto-cms.signedDataVerifierConfiguration* | To configure the shared SignedDataVerifierConfiguration, which determines the uri parameters for the verify operation. | null | ConfigDef.Importance.MEDIUM
+|===
+
+
+// kafka-connector options: END
diff --git a/docs/modules/ROOT/pages/connectors/camel-crypto-kafka-sink-connector.adoc b/docs/modules/ROOT/pages/connectors/camel-crypto-kafka-sink-connector.adoc
new file mode 100644
index 0000000..5fa6d9f
--- /dev/null
+++ b/docs/modules/ROOT/pages/connectors/camel-crypto-kafka-sink-connector.adoc
@@ -0,0 +1,49 @@
+// kafka-connector options: START
+== camel-crypto-kafka-connector source configuration
+
+When using camel-crypto-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-crypto-kafka-connector</artifactId>
+ <version>x.x.x</version>
+ <!-- use the same version as your Camel Kafka connector version -->
+</dependency>
+----
+
+
+[width="100%",cols="2,5,^1,2",options="header"]
+|===
+| Name | Description | Default | Priority
+| *camel.sink.path.cryptoOperation* | Set the Crypto operation from that supplied after the crypto scheme in the endpoint uri e.g. crypto:sign sets sign as the operation. One of: [sign] [verify] | null | ConfigDef.Importance.HIGH
+| *camel.sink.path.name* | The logical name of this operation. | null | ConfigDef.Importance.HIGH
+| *camel.sink.endpoint.algorithm* | Sets the JCE name of the Algorithm that should be used for the signer. | "SHA256withRSA" | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.alias* | Sets the alias used to query the KeyStore for keys and {link java.security.cert.Certificate Certificates} to be used in signing and verifying exchanges. This value can be provided at runtime via the message header org.apache.camel.component.crypto.DigitalSignatureConstants#KEYSTORE_ALIAS | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.certificateName* | Sets the reference name for a PrivateKey that can be found in the registry. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.keystore* | Sets the KeyStore that can contain keys and Certficates for use in signing and verifying exchanges. A KeyStore is typically used with an alias, either one supplied in the Route definition or dynamically via the message header CamelSignatureKeyStoreAlias. If no alias is supplied and there is only a single entry in the Keystore, then this single entry will be used. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.keystoreName* | Sets the reference name for a Keystore that can be found in the registry. | null | ConfigDef.Importance.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 cre [...]
+| *camel.sink.endpoint.privateKey* | Set the PrivateKey that should be used to sign the exchange | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.privateKeyName* | Sets the reference name for a PrivateKey that can be found in the registry. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.provider* | Set the id of the security provider that provides the configured Signature algorithm. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.publicKeyName* | references that should be resolved when the context changes | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.secureRandomName* | Sets the reference name for a SecureRandom that can be found in the registry. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.signatureHeaderName* | Set the name of the message header that should be used to store the base64 encoded signature. This defaults to 'CamelDigitalSignature' | null | ConfigDef.Importance.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 | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.bufferSize* | Set the size of the buffer used to read in the Exchange payload data. | "2048" | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.certificate* | Set the Certificate that should be used to verify the signature in the exchange based on its payload. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.clearHeaders* | Determines if the Signature specific headers be cleared after signing and verification. Defaults to true, and should only be made otherwise at your extreme peril as vital private information such as Keys and passwords may escape if unset. | true | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.keyStoreParameters* | Sets the KeyStore that can contain keys and Certficates for use in signing and verifying exchanges based on the given KeyStoreParameters. A KeyStore is typically used with an alias, either one supplied in the Route definition or dynamically via the message header CamelSignatureKeyStoreAlias. If no alias is supplied and there is only a single entry in the Keystore, then this single entry will be used. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.publicKey* | Set the PublicKey that should be used to verify the signature in the exchange. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.secureRandom* | Set the SecureRandom used to initialize the Signature service | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.synchronous* | Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). | false | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.password* | Sets the password used to access an aliased PrivateKey in the KeyStore. | null | ConfigDef.Importance.MEDIUM
+| *camel.component.crypto.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 [...]
+| *camel.component.crypto.basicPropertyBinding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+| *camel.component.crypto.configuration* | To use the shared DigitalSignatureConfiguration as configuration | null | ConfigDef.Importance.MEDIUM
+|===
+
+
+// kafka-connector options: END
diff --git a/docs/modules/ROOT/pages/connectors/camel-cxf-kafka-sink-connector.adoc b/docs/modules/ROOT/pages/connectors/camel-cxf-kafka-sink-connector.adoc
new file mode 100644
index 0000000..3a0644a
--- /dev/null
+++ b/docs/modules/ROOT/pages/connectors/camel-cxf-kafka-sink-connector.adoc
@@ -0,0 +1,63 @@
+// kafka-connector options: START
+== camel-cxf-kafka-connector source configuration
+
+When using camel-cxf-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-cxf-kafka-connector</artifactId>
+ <version>x.x.x</version>
+ <!-- use the same version as your Camel Kafka connector version -->
+</dependency>
+----
+
+
+[width="100%",cols="2,5,^1,2",options="header"]
+|===
+| Name | Description | Default | Priority
+| *camel.sink.path.beanId* | To lookup an existing configured CxfEndpoint. Must used bean: as prefix. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.path.address* | The service publish address. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.dataFormat* | The data type messages supported by the CXF endpoint. One of: [PAYLOAD] [RAW] [MESSAGE] [CXF_MESSAGE] [POJO] | "POJO" | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.wrappedStyle* | The WSDL style that describes how parameters are represented in the SOAP body. If the value is false, CXF will chose the document-literal unwrapped style, If the value is true, CXF will chose the document-literal wrapped style | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.cookieHandler* | Configure a cookie handler to maintain a HTTP session | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.defaultOperationName* | This option will set the default operationName that will be used by the CxfProducer which invokes the remote service. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.defaultOperationNamespace* | This option will set the default operationNamespace that will be used by the CxfProducer which invokes the remote service. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.hostnameVerifier* | The hostname verifier to be used. Use the # notation to reference a HostnameVerifier from the registry. | null | ConfigDef.Importance.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 cre [...]
+| *camel.sink.endpoint.sslContextParameters* | The Camel SSL setting reference. Use the # notation to reference the SSL Context. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.wrapped* | Which kind of operation that CXF endpoint producer will invoke | false | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.allowStreaming* | This option controls whether the CXF component, when running in PAYLOAD mode, will DOM parse the incoming messages into DOM Elements or keep the payload as a javax.xml.transform.Source object that would allow streaming in some cases. | null | ConfigDef.Importance.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 | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.bus* | To use a custom configured CXF Bus. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.continuationTimeout* | This option is used to set the CXF continuation timeout which could be used in CxfConsumer by default when the CXF server is using Jetty or Servlet transport. | 30000L | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.cxfBinding* | To use a custom CxfBinding to control the binding between Camel Message and CXF Message. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.cxfConfigurer* | This option could apply the implementation of org.apache.camel.component.cxf.CxfEndpointConfigurer which supports to configure the CXF endpoint in programmatic way. User can configure the CXF server and client by implementing configure\{ServerClient\} method of CxfEndpointConfigurer. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.defaultBus* | Will set the default bus when CXF endpoint create a bus by itself | false | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.headerFilterStrategy* | To use a custom HeaderFilterStrategy to filter header to and from Camel message. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.mergeProtocolHeaders* | Whether to merge protocol headers. If enabled then propagating headers between Camel and CXF becomes more consistent and similar. For more details see CAMEL-6393. | false | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.mtomEnabled* | To enable MTOM (attachments). This requires to use POJO or PAYLOAD data format mode. | false | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.properties* | To set additional CXF options using the key/value pairs from the Map. For example to turn on stacktraces in SOAP faults, properties.faultStackTraceEnabled=true | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.skipPayloadMessagePartCheck* | Sets whether SOAP message validation should be disabled. | false | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.synchronous* | Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). | false | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.loggingFeatureEnabled* | This option enables CXF Logging Feature which writes inbound and outbound SOAP messages to log. | false | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.loggingSizeLimit* | To limit the total size of number of bytes the logger will output when logging feature has been enabled and -1 for no limit. | 49152 | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.skipFaultLogging* | This option controls whether the PhaseInterceptorChain skips logging the Fault that it catches. | false | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.password* | This option is used to set the basic authentication information of password for the CXF client. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.username* | This option is used to set the basic authentication information of username for the CXF client. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.bindingId* | The bindingId for the service model to use. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.portName* | The endpoint name this service is implementing, it maps to the wsdl:portname. In the format of ns:PORT_NAME where ns is a namespace prefix valid at this scope. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.publishedEndpointUrl* | This option can override the endpointUrl that published from the WSDL which can be accessed with service address url plus wsd | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.serviceClass* | The class name of the SEI (Service Endpoint Interface) class which could have JSR181 annotation or not. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.serviceName* | The service name this service is implementing, it maps to the wsdl:servicename. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.wsdlURL* | The location of the WSDL. Can be on the classpath, file system, or be hosted remotely. | null | ConfigDef.Importance.MEDIUM
+| *camel.component.cxf.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 cre [...]
+| *camel.component.cxf.allowStreaming* | This option controls whether the CXF component, when running in PAYLOAD mode, will DOM parse the incoming messages into DOM Elements or keep the payload as a javax.xml.transform.Source object that would allow streaming in some cases. | null | ConfigDef.Importance.MEDIUM
+| *camel.component.cxf.basicPropertyBinding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+| *camel.component.cxf.headerFilterStrategy* | To use a custom org.apache.camel.spi.HeaderFilterStrategy to filter header to and from Camel message. | null | ConfigDef.Importance.MEDIUM
+| *camel.component.cxf.useGlobalSslContextParameters* | Enable usage of global SSL context parameters. | false | ConfigDef.Importance.MEDIUM
+|===
+
+
+// kafka-connector options: END
diff --git a/docs/modules/ROOT/pages/connectors/camel-cxf-kafka-source-connector.adoc b/docs/modules/ROOT/pages/connectors/camel-cxf-kafka-source-connector.adoc
new file mode 100644
index 0000000..2a56a91
--- /dev/null
+++ b/docs/modules/ROOT/pages/connectors/camel-cxf-kafka-source-connector.adoc
@@ -0,0 +1,59 @@
+// kafka-connector options: START
+== camel-cxf-kafka-connector source configuration
+
+When using camel-cxf-kafka-connector as source 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-cxf-kafka-connector</artifactId>
+ <version>x.x.x</version>
+ <!-- use the same version as your Camel Kafka connector version -->
+</dependency>
+----
+
+
+[width="100%",cols="2,5,^1,2",options="header"]
+|===
+| Name | Description | Default | Priority
+| *camel.source.path.beanId* | To lookup an existing configured CxfEndpoint. Must used bean: as prefix. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.path.address* | The service publish address. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.dataFormat* | The data type messages supported by the CXF endpoint. One of: [PAYLOAD] [RAW] [MESSAGE] [CXF_MESSAGE] [POJO] | "POJO" | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.wrappedStyle* | The WSDL style that describes how parameters are represented in the SOAP body. If the value is false, CXF will chose the document-literal unwrapped style, If the value is true, CXF will chose the document-literal wrapped style | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.bridgeErrorHandler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.exceptionHandler* | To let the consumer use a custom ExceptionHandler. Notice if the option bridgeErrorHandler is enabled then this option is not in use. By default the consumer will deal with exceptions, that will be logged at WARN or ERROR level and ignored. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.exchangePattern* | Sets the exchange pattern when the consumer creates an exchange. One of: [InOnly] [InOut] [InOptionalOut] | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.allowStreaming* | This option controls whether the CXF component, when running in PAYLOAD mode, will DOM parse the incoming messages into DOM Elements or keep the payload as a javax.xml.transform.Source object that would allow streaming in some cases. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.basicPropertyBinding* | Whether the endpoint should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.bus* | To use a custom configured CXF Bus. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.continuationTimeout* | This option is used to set the CXF continuation timeout which could be used in CxfConsumer by default when the CXF server is using Jetty or Servlet transport. | 30000L | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.cxfBinding* | To use a custom CxfBinding to control the binding between Camel Message and CXF Message. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.cxfConfigurer* | This option could apply the implementation of org.apache.camel.component.cxf.CxfEndpointConfigurer which supports to configure the CXF endpoint in programmatic way. User can configure the CXF server and client by implementing configure\{ServerClient\} method of CxfEndpointConfigurer. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.defaultBus* | Will set the default bus when CXF endpoint create a bus by itself | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.headerFilterStrategy* | To use a custom HeaderFilterStrategy to filter header to and from Camel message. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.mergeProtocolHeaders* | Whether to merge protocol headers. If enabled then propagating headers between Camel and CXF becomes more consistent and similar. For more details see CAMEL-6393. | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.mtomEnabled* | To enable MTOM (attachments). This requires to use POJO or PAYLOAD data format mode. | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.properties* | To set additional CXF options using the key/value pairs from the Map. For example to turn on stacktraces in SOAP faults, properties.faultStackTraceEnabled=true | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.skipPayloadMessagePartCheck* | Sets whether SOAP message validation should be disabled. | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.synchronous* | Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.loggingFeatureEnabled* | This option enables CXF Logging Feature which writes inbound and outbound SOAP messages to log. | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.loggingSizeLimit* | To limit the total size of number of bytes the logger will output when logging feature has been enabled and -1 for no limit. | 49152 | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.skipFaultLogging* | This option controls whether the PhaseInterceptorChain skips logging the Fault that it catches. | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.password* | This option is used to set the basic authentication information of password for the CXF client. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.username* | This option is used to set the basic authentication information of username for the CXF client. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.bindingId* | The bindingId for the service model to use. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.portName* | The endpoint name this service is implementing, it maps to the wsdl:portname. In the format of ns:PORT_NAME where ns is a namespace prefix valid at this scope. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.publishedEndpointUrl* | This option can override the endpointUrl that published from the WSDL which can be accessed with service address url plus wsd | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.serviceClass* | The class name of the SEI (Service Endpoint Interface) class which could have JSR181 annotation or not. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.serviceName* | The service name this service is implementing, it maps to the wsdl:servicename. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.wsdlURL* | The location of the WSDL. Can be on the classpath, file system, or be hosted remotely. | null | ConfigDef.Importance.MEDIUM
+| *camel.component.cxf.bridgeErrorHandler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | ConfigDef.Importance.MEDIUM
+| *camel.component.cxf.allowStreaming* | This option controls whether the CXF component, when running in PAYLOAD mode, will DOM parse the incoming messages into DOM Elements or keep the payload as a javax.xml.transform.Source object that would allow streaming in some cases. | null | ConfigDef.Importance.MEDIUM
+| *camel.component.cxf.basicPropertyBinding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+| *camel.component.cxf.headerFilterStrategy* | To use a custom org.apache.camel.spi.HeaderFilterStrategy to filter header to and from Camel message. | null | ConfigDef.Importance.MEDIUM
+| *camel.component.cxf.useGlobalSslContextParameters* | Enable usage of global SSL context parameters. | false | ConfigDef.Importance.MEDIUM
+|===
+
+
+// kafka-connector options: END
diff --git a/docs/modules/ROOT/pages/connectors/camel-cxfrs-kafka-sink-connector.adoc b/docs/modules/ROOT/pages/connectors/camel-cxfrs-kafka-sink-connector.adoc
new file mode 100644
index 0000000..0b6cdc3
--- /dev/null
+++ b/docs/modules/ROOT/pages/connectors/camel-cxfrs-kafka-sink-connector.adoc
@@ -0,0 +1,55 @@
+// kafka-connector options: START
+== camel-cxfrs-kafka-connector source configuration
+
+When using camel-cxfrs-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-cxfrs-kafka-connector</artifactId>
+ <version>x.x.x</version>
+ <!-- use the same version as your Camel Kafka connector version -->
+</dependency>
+----
+
+
+[width="100%",cols="2,5,^1,2",options="header"]
+|===
+| Name | Description | Default | Priority
+| *camel.sink.path.beanId* | To lookup an existing configured CxfRsEndpoint. Must used bean: as prefix. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.path.address* | The service publish address. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.features* | Set the feature list to the CxfRs endpoint. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.loggingFeatureEnabled* | This option enables CXF Logging Feature which writes inbound and outbound REST messages to log. | false | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.loggingSizeLimit* | To limit the total size of number of bytes the logger will output when logging feature has been enabled. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.modelRef* | This option is used to specify the model file which is useful for the resource class without annotation. When using this option, then the service class can be omitted, to emulate document-only endpoints | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.providers* | Set custom JAX-RS provider(s) list to the CxfRs endpoint. You can specify a string with a list of providers to lookup in the registy separated by comma. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.resourceClasses* | The resource classes which you want to export as REST service. Multiple classes can be separated by comma. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.schemaLocations* | Sets the locations of the schema(s) which can be used to validate the incoming XML or JAXB-driven JSON. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.skipFaultLogging* | This option controls whether the PhaseInterceptorChain skips logging the Fault that it catches. | false | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.cookieHandler* | Configure a cookie handler to maintain a HTTP session | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.hostnameVerifier* | The hostname verifier to be used. Use the # notation to reference a HostnameVerifier from the registry. | null | ConfigDef.Importance.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 cre [...]
+| *camel.sink.endpoint.sslContextParameters* | The Camel SSL setting reference. Use the # notation to reference the SSL Context. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.throwExceptionOnFailure* | This option tells the CxfRsProducer to inspect return codes and will generate an Exception if the return code is larger than 207. | true | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.httpClientAPI* | If it is true, the CxfRsProducer will use the HttpClientAPI to invoke the service. If it is false, the CxfRsProducer will use the ProxyClientAPI to invoke the service | true | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.ignoreDeleteMethodMessageBody* | This option is used to tell CxfRsProducer to ignore the message body of the DELETE method when using HTTP API. | false | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.maxClientCacheSize* | This option allows you to configure the maximum size of the cache. The implementation caches CXF clients or ClientFactoryBean in CxfProvider and CxfRsProvider. | 10 | ConfigDef.Importance.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 | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.binding* | To use a custom CxfBinding to control the binding between Camel Message and CXF Message. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.bus* | To use a custom configured CXF Bus. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.continuationTimeout* | This option is used to set the CXF continuation timeout which could be used in CxfConsumer by default when the CXF server is using Jetty or Servlet transport. | 30000L | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.cxfRsConfigurer* | This option could apply the implementation of org.apache.camel.component.cxf.jaxrs.CxfRsEndpointConfigurer which supports to configure the CXF endpoint in programmatic way. User can configure the CXF server and client by implementing configure{Server/Client} method of CxfEndpointConfigurer. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.defaultBus* | Will set the default bus when CXF endpoint create a bus by itself | false | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.headerFilterStrategy* | To use a custom HeaderFilterStrategy to filter header to and from Camel message. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.performInvocation* | When the option is true, Camel will perform the invocation of the resource class instance and put the response object into the exchange for further processing. | false | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.propagateContexts* | When the option is true, JAXRS UriInfo, HttpHeaders, Request and SecurityContext contexts will be available to custom CXFRS processors as typed Camel exchange properties. These contexts can be used to analyze the current requests using JAX-RS API. | false | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.synchronous* | Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). | false | ConfigDef.Importance.MEDIUM
+| *camel.component.cxfrs.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 c [...]
+| *camel.component.cxfrs.basicPropertyBinding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+| *camel.component.cxfrs.headerFilterStrategy* | To use a custom org.apache.camel.spi.HeaderFilterStrategy to filter header to and from Camel message. | null | ConfigDef.Importance.MEDIUM
+| *camel.component.cxfrs.useGlobalSslContextParameters* | Enable usage of global SSL context parameters. | false | ConfigDef.Importance.MEDIUM
+|===
+
+
+// kafka-connector options: END
diff --git a/docs/modules/ROOT/pages/connectors/camel-cxfrs-kafka-source-connector.adoc b/docs/modules/ROOT/pages/connectors/camel-cxfrs-kafka-source-connector.adoc
new file mode 100644
index 0000000..a2ca07f
--- /dev/null
+++ b/docs/modules/ROOT/pages/connectors/camel-cxfrs-kafka-source-connector.adoc
@@ -0,0 +1,53 @@
+// kafka-connector options: START
+== camel-cxfrs-kafka-connector source configuration
+
+When using camel-cxfrs-kafka-connector as source 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-cxfrs-kafka-connector</artifactId>
+ <version>x.x.x</version>
+ <!-- use the same version as your Camel Kafka connector version -->
+</dependency>
+----
+
+
+[width="100%",cols="2,5,^1,2",options="header"]
+|===
+| Name | Description | Default | Priority
+| *camel.source.path.beanId* | To lookup an existing configured CxfRsEndpoint. Must used bean: as prefix. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.path.address* | The service publish address. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.features* | Set the feature list to the CxfRs endpoint. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.loggingFeatureEnabled* | This option enables CXF Logging Feature which writes inbound and outbound REST messages to log. | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.loggingSizeLimit* | To limit the total size of number of bytes the logger will output when logging feature has been enabled. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.modelRef* | This option is used to specify the model file which is useful for the resource class without annotation. When using this option, then the service class can be omitted, to emulate document-only endpoints | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.providers* | Set custom JAX-RS provider(s) list to the CxfRs endpoint. You can specify a string with a list of providers to lookup in the registy separated by comma. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.resourceClasses* | The resource classes which you want to export as REST service. Multiple classes can be separated by comma. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.schemaLocations* | Sets the locations of the schema(s) which can be used to validate the incoming XML or JAXB-driven JSON. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.skipFaultLogging* | This option controls whether the PhaseInterceptorChain skips logging the Fault that it catches. | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.bindingStyle* | Sets how requests and responses will be mapped to/from Camel. Two values are possible: SimpleConsumer: This binding style processes request parameters, multiparts, etc. and maps them to IN headers, IN attachments and to the message body. It aims to eliminate low-level processing of org.apache.cxf.message.MessageContentsList. It also also adds more flexibility and simplicity to the response mapping. Only available for consumers. Default: The defaul [...]
+| *camel.source.endpoint.bridgeErrorHandler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.publishedEndpointUrl* | This option can override the endpointUrl that published from the WADL which can be accessed with resource address url plus _wadl | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.exceptionHandler* | To let the consumer use a custom ExceptionHandler. Notice if the option bridgeErrorHandler is enabled then this option is not in use. By default the consumer will deal with exceptions, that will be logged at WARN or ERROR level and ignored. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.exchangePattern* | Sets the exchange pattern when the consumer creates an exchange. One of: [InOnly] [InOut] [InOptionalOut] | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.serviceBeans* | The service beans (the bean ids to lookup in the registry) which you want to export as REST service. Multiple beans can be separated by comma | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.basicPropertyBinding* | Whether the endpoint should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.binding* | To use a custom CxfBinding to control the binding between Camel Message and CXF Message. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.bus* | To use a custom configured CXF Bus. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.continuationTimeout* | This option is used to set the CXF continuation timeout which could be used in CxfConsumer by default when the CXF server is using Jetty or Servlet transport. | 30000L | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.cxfRsConfigurer* | This option could apply the implementation of org.apache.camel.component.cxf.jaxrs.CxfRsEndpointConfigurer which supports to configure the CXF endpoint in programmatic way. User can configure the CXF server and client by implementing configure{Server/Client} method of CxfEndpointConfigurer. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.defaultBus* | Will set the default bus when CXF endpoint create a bus by itself | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.headerFilterStrategy* | To use a custom HeaderFilterStrategy to filter header to and from Camel message. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.performInvocation* | When the option is true, Camel will perform the invocation of the resource class instance and put the response object into the exchange for further processing. | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.propagateContexts* | When the option is true, JAXRS UriInfo, HttpHeaders, Request and SecurityContext contexts will be available to custom CXFRS processors as typed Camel exchange properties. These contexts can be used to analyze the current requests using JAX-RS API. | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.synchronous* | Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). | false | ConfigDef.Importance.MEDIUM
+| *camel.component.cxfrs.bridgeErrorHandler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | ConfigDef.Importance.MEDIUM
+| *camel.component.cxfrs.basicPropertyBinding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+| *camel.component.cxfrs.headerFilterStrategy* | To use a custom org.apache.camel.spi.HeaderFilterStrategy to filter header to and from Camel message. | null | ConfigDef.Importance.MEDIUM
+| *camel.component.cxfrs.useGlobalSslContextParameters* | Enable usage of global SSL context parameters. | false | ConfigDef.Importance.MEDIUM
+|===
+
+
+// kafka-connector options: END
diff --git a/docs/modules/ROOT/pages/connectors/camel-dataformat-kafka-sink-connector.adoc b/docs/modules/ROOT/pages/connectors/camel-dataformat-kafka-sink-connector.adoc
new file mode 100644
index 0000000..e7bc98b
--- /dev/null
+++ b/docs/modules/ROOT/pages/connectors/camel-dataformat-kafka-sink-connector.adoc
@@ -0,0 +1,30 @@
+// kafka-connector options: START
+== camel-dataformat-kafka-connector source configuration
+
+When using camel-dataformat-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-dataformat-kafka-connector</artifactId>
+ <version>x.x.x</version>
+ <!-- use the same version as your Camel Kafka connector version -->
+</dependency>
+----
+
+
+[width="100%",cols="2,5,^1,2",options="header"]
+|===
+| Name | Description | Default | Priority
+| *camel.sink.path.name* | Name of data format | null | ConfigDef.Importance.HIGH
+| *camel.sink.path.operation* | Operation to use either marshal or unmarshal One of: [marshal] [unmarshal] | null | ConfigDef.Importance.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 cre [...]
+| *camel.sink.endpoint.basicPropertyBinding* | Whether the endpoint should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.synchronous* | Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). | false | ConfigDef.Importance.MEDIUM
+| *camel.component.dataformat.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 t [...]
+| *camel.component.dataformat.basicPropertyBinding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+|===
+
+
+// kafka-connector options: END
diff --git a/docs/modules/ROOT/pages/connectors/camel-dataset-kafka-sink-connector.adoc b/docs/modules/ROOT/pages/connectors/camel-dataset-kafka-sink-connector.adoc
new file mode 100644
index 0000000..88598c8
--- /dev/null
+++ b/docs/modules/ROOT/pages/connectors/camel-dataset-kafka-sink-connector.adoc
@@ -0,0 +1,41 @@
+// kafka-connector options: START
+== camel-dataset-kafka-connector source configuration
+
+When using camel-dataset-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-dataset-kafka-connector</artifactId>
+ <version>x.x.x</version>
+ <!-- use the same version as your Camel Kafka connector version -->
+</dependency>
+----
+
+
+[width="100%",cols="2,5,^1,2",options="header"]
+|===
+| Name | Description | Default | Priority
+| *camel.sink.path.name* | Name of DataSet to lookup in the registry | null | ConfigDef.Importance.HIGH
+| *camel.sink.endpoint.dataSetIndex* | Controls the behaviour of the CamelDataSetIndex header. For Consumers: - off = the header will not be set - strict/lenient = the header will be set For Producers: - off = the header value will not be verified, and will not be set if it is not present = strict = the header value must be present and will be verified = lenient = the header value will be verified if it is present, and will be set if it is not present One of: [strict] [lenient] [off] | " [...]
+| *camel.sink.endpoint.assertPeriod* | Sets a grace period after which the mock endpoint will re-assert to ensure the preliminary assertion is still valid. This is used for example to assert that exactly a number of messages arrives. For example if expectedMessageCount(int) was set to 5, then the assertion is satisfied when 5 or more message arrives. To ensure that exactly 5 messages arrives, then you would need to wait a little period to ensure no further message arrives. This is what y [...]
+| *camel.sink.endpoint.consumeDelay* | Allows a delay to be specified which causes a delay when a message is consumed by the producer (to simulate slow processing) | 0L | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.expectedCount* | Specifies the expected number of message exchanges that should be received by this endpoint. Beware: If you want to expect that 0 messages, then take extra care, as 0 matches when the tests starts, so you need to set a assert period time to let the test run for a while to make sure there are still no messages arrived; for that use setAssertPeriod(long). An alternative is to use NotifyBuilder, and use the notifier to know when Camel is done routing [...]
+| *camel.sink.endpoint.failFast* | Sets whether assertIsSatisfied() should fail fast at the first detected failed expectation while it may otherwise wait for all expected messages to arrive before performing expectations verifications. Is by default true. Set to false to use behavior as in Camel 2.x. | false | ConfigDef.Importance.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 cre [...]
+| *camel.sink.endpoint.reportGroup* | A number that is used to turn on throughput logging based on groups of the size. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.resultMinimumWaitTime* | Sets the minimum expected amount of time (in millis) the assertIsSatisfied() will wait on a latch until it is satisfied | 0L | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.resultWaitTime* | Sets the maximum amount of time (in millis) the assertIsSatisfied() will wait on a latch until it is satisfied | 0L | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.retainFirst* | Specifies to only retain the first n'th number of received Exchanges. This is used when testing with big data, to reduce memory consumption by not storing copies of every Exchange this mock endpoint receives. Important: When using this limitation, then the getReceivedCounter() will still return the actual number of received Exchanges. For example if we have received 5000 Exchanges, and have configured to only retain the first 10 Exchanges, then the g [...]
+| *camel.sink.endpoint.retainLast* | Specifies to only retain the last n'th number of received Exchanges. This is used when testing with big data, to reduce memory consumption by not storing copies of every Exchange this mock endpoint receives. Important: When using this limitation, then the getReceivedCounter() will still return the actual number of received Exchanges. For example if we have received 5000 Exchanges, and have configured to only retain the last 20 Exchanges, then the getR [...]
+| *camel.sink.endpoint.sleepForEmptyTest* | Allows a sleep to be specified to wait to check that this endpoint really is empty when expectedMessageCount(int) is called with zero | 0L | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.copyOnExchange* | Sets whether to make a deep copy of the incoming Exchange when received at this mock endpoint. Is by default true. | true | ConfigDef.Importance.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 | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.synchronous* | Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). | false | ConfigDef.Importance.MEDIUM
+| *camel.component.dataset.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 [...]
+| *camel.component.dataset.basicPropertyBinding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+|===
+
+
+// kafka-connector options: END
diff --git a/docs/modules/ROOT/pages/connectors/camel-dataset-kafka-source-connector.adoc b/docs/modules/ROOT/pages/connectors/camel-dataset-kafka-source-connector.adoc
new file mode 100644
index 0000000..1324e94
--- /dev/null
+++ b/docs/modules/ROOT/pages/connectors/camel-dataset-kafka-source-connector.adoc
@@ -0,0 +1,36 @@
+// kafka-connector options: START
+== camel-dataset-kafka-connector source configuration
+
+When using camel-dataset-kafka-connector as source 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-dataset-kafka-connector</artifactId>
+ <version>x.x.x</version>
+ <!-- use the same version as your Camel Kafka connector version -->
+</dependency>
+----
+
+
+[width="100%",cols="2,5,^1,2",options="header"]
+|===
+| Name | Description | Default | Priority
+| *camel.source.path.name* | Name of DataSet to lookup in the registry | null | ConfigDef.Importance.HIGH
+| *camel.source.endpoint.dataSetIndex* | Controls the behaviour of the CamelDataSetIndex header. For Consumers: - off = the header will not be set - strict/lenient = the header will be set For Producers: - off = the header value will not be verified, and will not be set if it is not present = strict = the header value must be present and will be verified = lenient = the header value will be verified if it is present, and will be set if it is not present One of: [strict] [lenient] [off] | [...]
+| *camel.source.endpoint.bridgeErrorHandler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.initialDelay* | Time period in millis to wait before starting sending messages. | 1000L | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.minRate* | Wait until the DataSet contains at least this number of messages | 0 | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.preloadSize* | Sets how many messages should be preloaded (sent) before the route completes its initialization | 0L | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.produceDelay* | Allows a delay to be specified which causes a delay when a message is sent by the consumer (to simulate slow processing) | 3L | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.exceptionHandler* | To let the consumer use a custom ExceptionHandler. Notice if the option bridgeErrorHandler is enabled then this option is not in use. By default the consumer will deal with exceptions, that will be logged at WARN or ERROR level and ignored. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.exchangePattern* | Sets the exchange pattern when the consumer creates an exchange. One of: [InOnly] [InOut] [InOptionalOut] | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.basicPropertyBinding* | Whether the endpoint should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.synchronous* | Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). | false | ConfigDef.Importance.MEDIUM
+| *camel.component.dataset.bridgeErrorHandler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | ConfigDef.Importance.MEDIUM
+| *camel.component.dataset.basicPropertyBinding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+|===
+
+
+// kafka-connector options: END
diff --git a/docs/modules/ROOT/pages/connectors/camel-dataset-test-kafka-sink-connector.adoc b/docs/modules/ROOT/pages/connectors/camel-dataset-test-kafka-sink-connector.adoc
new file mode 100644
index 0000000..04faae8
--- /dev/null
+++ b/docs/modules/ROOT/pages/connectors/camel-dataset-test-kafka-sink-connector.adoc
@@ -0,0 +1,43 @@
+// kafka-connector options: START
+== camel-dataset-test-kafka-connector source configuration
+
+When using camel-dataset-test-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-dataset-test-kafka-connector</artifactId>
+ <version>x.x.x</version>
+ <!-- use the same version as your Camel Kafka connector version -->
+</dependency>
+----
+
+
+[width="100%",cols="2,5,^1,2",options="header"]
+|===
+| Name | Description | Default | Priority
+| *camel.sink.path.name* | Name of endpoint to lookup in the registry to use for polling messages used for testing | null | ConfigDef.Importance.HIGH
+| *camel.sink.endpoint.anyOrder* | Whether the expected messages should arrive in the same order or can be in any order. | false | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.assertPeriod* | Sets a grace period after which the mock endpoint will re-assert to ensure the preliminary assertion is still valid. This is used for example to assert that exactly a number of messages arrives. For example if expectedMessageCount(int) was set to 5, then the assertion is satisfied when 5 or more message arrives. To ensure that exactly 5 messages arrives, then you would need to wait a little period to ensure no further message arrives. This is what y [...]
+| *camel.sink.endpoint.delimiter* | The split delimiter to use when split is enabled. By default the delimiter is new line based. The delimiter can be a regular expression. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.expectedCount* | Specifies the expected number of message exchanges that should be received by this endpoint. Beware: If you want to expect that 0 messages, then take extra care, as 0 matches when the tests starts, so you need to set a assert period time to let the test run for a while to make sure there are still no messages arrived; for that use setAssertPeriod(long). An alternative is to use NotifyBuilder, and use the notifier to know when Camel is done routing [...]
+| *camel.sink.endpoint.failFast* | Sets whether assertIsSatisfied() should fail fast at the first detected failed expectation while it may otherwise wait for all expected messages to arrive before performing expectations verifications. Is by default true. Set to false to use behavior as in Camel 2.x. | false | ConfigDef.Importance.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 cre [...]
+| *camel.sink.endpoint.reportGroup* | A number that is used to turn on throughput logging based on groups of the size. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.resultMinimumWaitTime* | Sets the minimum expected amount of time (in millis) the assertIsSatisfied() will wait on a latch until it is satisfied | 0L | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.resultWaitTime* | Sets the maximum amount of time (in millis) the assertIsSatisfied() will wait on a latch until it is satisfied | 0L | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.retainFirst* | Specifies to only retain the first n'th number of received Exchanges. This is used when testing with big data, to reduce memory consumption by not storing copies of every Exchange this mock endpoint receives. Important: When using this limitation, then the getReceivedCounter() will still return the actual number of received Exchanges. For example if we have received 5000 Exchanges, and have configured to only retain the first 10 Exchanges, then the g [...]
+| *camel.sink.endpoint.retainLast* | Specifies to only retain the last n'th number of received Exchanges. This is used when testing with big data, to reduce memory consumption by not storing copies of every Exchange this mock endpoint receives. Important: When using this limitation, then the getReceivedCounter() will still return the actual number of received Exchanges. For example if we have received 5000 Exchanges, and have configured to only retain the last 20 Exchanges, then the getR [...]
+| *camel.sink.endpoint.sleepForEmptyTest* | Allows a sleep to be specified to wait to check that this endpoint really is empty when expectedMessageCount(int) is called with zero | 0L | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.split* | If enabled the messages loaded from the test endpoint will be split using new line delimiters so each line is an expected message. For example to use a file endpoint to load a file where each line is an expected message. | false | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.timeout* | The timeout to use when polling for message bodies from the URI | 2000L | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.copyOnExchange* | Sets whether to make a deep copy of the incoming Exchange when received at this mock endpoint. Is by default true. | true | ConfigDef.Importance.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 | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.synchronous* | Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). | false | ConfigDef.Importance.MEDIUM
+| *camel.component.dataset-test.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 [...]
+| *camel.component.dataset-test.basicPropertyBinding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+|===
+
+
+// kafka-connector options: END
diff --git a/docs/modules/ROOT/pages/connectors/camel-debezium-mongodb-kafka-source-connector.adoc b/docs/modules/ROOT/pages/connectors/camel-debezium-mongodb-kafka-source-connector.adoc
new file mode 100644
index 0000000..13fa360
--- /dev/null
+++ b/docs/modules/ROOT/pages/connectors/camel-debezium-mongodb-kafka-source-connector.adoc
@@ -0,0 +1,71 @@
+// kafka-connector options: START
+== camel-debezium-mongodb-kafka-connector source configuration
+
+When using camel-debezium-mongodb-kafka-connector as source 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-debezium-mongodb-kafka-connector</artifactId>
+ <version>x.x.x</version>
+ <!-- use the same version as your Camel Kafka connector version -->
+</dependency>
+----
+
+
+[width="100%",cols="2,5,^1,2",options="header"]
+|===
+| Name | Description | Default | Priority
+| *camel.source.path.name* | Unique name for the connector. Attempting to register again with the same name will fail. | null | ConfigDef.Importance.HIGH
+| *camel.source.endpoint.additionalProperties* | Additional properties for debezium components in case they can't be set directly on the camel configurations (e.g: setting Kafka Connect properties needed by Debezium engine, for example setting KafkaOffsetBackingStore), the properties have to be prefixed with additionalProperties.. E.g: additionalProperties.transactional.id=12345&additionalProperties.schema.registry.url=\http://localhost:8811/avro | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.bridgeErrorHandler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.internalKeyConverter* | The Converter class that should be used to serialize and deserialize key data for offsets. The default is JSON converter. | "org.apache.kafka.connect.json.JsonConverter" | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.internalValueConverter* | The Converter class that should be used to serialize and deserialize value data for offsets. The default is JSON converter. | "org.apache.kafka.connect.json.JsonConverter" | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.offsetCommitPolicy* | The name of the Java class of the commit policy. It defines when offsets commit has to be triggered based on the number of events processed and the time elapsed since the last commit. This class must implement the interface 'OffsetCommitPolicy'. The default is a periodic commit policy based upon time intervals. | "io.debezium.embedded.spi.OffsetCommitPolicy.PeriodicCommitOffsetPolicy" | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.offsetCommitTimeoutMs* | Maximum number of milliseconds to wait for records to flush and partition offset data to be committed to offset storage before cancelling the process and restoring the offset data to be committed in a future attempt. The default is 5 seconds. | 5000L | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.offsetFlushIntervalMs* | Interval at which to try committing offsets. The default is 1 minute. | 60000L | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.offsetStorage* | The name of the Java class that is responsible for persistence of connector offsets. | "org.apache.kafka.connect.storage.FileOffsetBackingStore" | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.offsetStorageFileName* | Path to file where offsets are to be stored. Required when offset.storage is set to the FileOffsetBackingStore. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.offsetStoragePartitions* | The number of partitions used when creating the offset storage topic. Required when offset.storage is set to the 'KafkaOffsetBackingStore'. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.offsetStorageReplicationFactor* | Replication factor used when creating the offset storage topic. Required when offset.storage is set to the KafkaOffsetBackingStore | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.offsetStorageTopic* | The name of the Kafka topic where offsets are to be stored. Required when offset.storage is set to the KafkaOffsetBackingStore. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.exceptionHandler* | To let the consumer use a custom ExceptionHandler. Notice if the option bridgeErrorHandler is enabled then this option is not in use. By default the consumer will deal with exceptions, that will be logged at WARN or ERROR level and ignored. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.exchangePattern* | Sets the exchange pattern when the consumer creates an exchange. One of: [InOnly] [InOut] [InOptionalOut] | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.basicPropertyBinding* | Whether the endpoint should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.synchronous* | Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.collectionBlacklist* | Description is not available here, please check Debezium website for corresponding key 'collection.blacklist' description. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.collectionWhitelist* | The collections for which changes are to be captured | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.connectBackoffInitialDelayMs* | The initial delay when trying to reconnect to a primary after a connection cannot be made or when no primary is available. Defaults to 1 second (1000 ms). | 1000L | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.connectBackoffMaxDelayMs* | The maximum delay when trying to reconnect to a primary after a connection cannot be made or when no primary is available. Defaults to 120 second (120,000 ms). | 120000L | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.connectMaxAttempts* | Maximum number of failed connection attempts to a replica set primary before an exception occurs and task is aborted. Defaults to 16, which with the defaults for 'connect.backoff.initial.delay.ms' and 'connect.backoff.max.delay.ms' results in just over 20 minutes of attempts before failing. | 16 | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.databaseBlacklist* | The databases for which changes are to be excluded | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.databaseHistoryFileFilename* | The path to the file that will be used to record the database history | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.databaseWhitelist* | The databases for which changes are to be captured | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.fieldBlacklist* | Description is not available here, please check Debezium website for corresponding key 'field.blacklist' description. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.fieldRenames* | Description is not available here, please check Debezium website for corresponding key 'field.renames' description. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.heartbeatIntervalMs* | Length of an interval in milli-seconds in in which the connector periodically sends heartbeat messages to a heartbeat topic. Use 0 to disable heartbeat messages. Disabled by default. | 0 | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.heartbeatTopicsPrefix* | The prefix that is used to name heartbeat topics.Defaults to __debezium-heartbeat. | "__debezium-heartbeat" | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.initialSyncMaxThreads* | Maximum number of threads used to perform an intial sync of the collections in a replica set. Defaults to 1. | 1 | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.maxBatchSize* | Maximum size of each batch of source records. Defaults to 2048. | 2048 | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.maxQueueSize* | Maximum size of the queue for change events read from the database log but not yet recorded or forwarded. Defaults to 8192, and should always be larger than the maximum batch size. | 8192 | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.mongodbHosts* | The hostname and port pairs (in the form 'host' or 'host:port') of the MongoDB server(s) in the replica set. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.mongodbMembersAutoDiscover* | Specifies whether the addresses in 'hosts' are seeds that should be used to discover all members of the cluster or replica set ('true'), or whether the address(es) in 'hosts' should be used as is ('false'). The default is 'true'. | true | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.mongodbName* | Unique name that identifies the MongoDB replica set or cluster and all recorded offsets, andthat is used as a prefix for all schemas and topics. Each distinct MongoDB installation should have a separate namespace and monitored by at most one Debezium connector. | null | ConfigDef.Importance.HIGH
+| *camel.source.endpoint.mongodbPassword* | Password to be used when connecting to MongoDB, if necessary. | null | ConfigDef.Importance.HIGH
+| *camel.source.endpoint.mongodbSslEnabled* | Should connector use SSL to connect to MongoDB instances | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.mongodbSslInvalidHostnameAllowed* | Whether invalid host names are allowed when using SSL. If true the connection will not prevent man-in-the-middle attacks | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.mongodbUser* | Database user for connecting to MongoDB, if necessary. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.pollIntervalMs* | Frequency in milliseconds to wait for new change events to appear after receiving no events. Defaults to 500ms. | 500L | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.snapshotDelayMs* | The number of milliseconds to delay before a snapshot will begin. | 0L | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.snapshotFetchSize* | The maximum number of records that should be loaded into memory while performing a snapshot | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.snapshotMode* | The criteria for running a snapshot upon startup of the connector. Options include: 'initial' (the default) to specify the connector should always perform an initial sync when required; 'never' to specify the connector should never perform an initial sync | "initial" | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.sourceStructVersion* | A version of the format of the publicly visible source part in the message | "v2" | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.tombstonesOnDelete* | Whether delete operations should be represented by a delete event and a subsquenttombstone event (true) or only by a delete event (false). Emitting the tombstone event (the default behavior) allows Kafka to completely delete all events pertaining to the given key once the source record got deleted. | false | ConfigDef.Importance.MEDIUM
+| *camel.component.debezium-mongodb.bridgeErrorHandler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | ConfigDef.Impor [...]
+| *camel.component.debezium-mongodb.configuration* | Allow pre-configured Configurations to be set. | null | ConfigDef.Importance.MEDIUM
+| *camel.component.debezium-mongodb.basicPropertyBinding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+|===
+
+
+// kafka-connector options: END
diff --git a/docs/modules/ROOT/pages/connectors/camel-debezium-mysql-kafka-source-connector.adoc b/docs/modules/ROOT/pages/connectors/camel-debezium-mysql-kafka-source-connector.adoc
new file mode 100644
index 0000000..a7baac0
--- /dev/null
+++ b/docs/modules/ROOT/pages/connectors/camel-debezium-mysql-kafka-source-connector.adoc
@@ -0,0 +1,101 @@
+// kafka-connector options: START
+== camel-debezium-mysql-kafka-connector source configuration
+
+When using camel-debezium-mysql-kafka-connector as source 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-debezium-mysql-kafka-connector</artifactId>
+ <version>x.x.x</version>
+ <!-- use the same version as your Camel Kafka connector version -->
+</dependency>
+----
+
+
+[width="100%",cols="2,5,^1,2",options="header"]
+|===
+| Name | Description | Default | Priority
+| *camel.source.path.name* | Unique name for the connector. Attempting to register again with the same name will fail. | null | ConfigDef.Importance.HIGH
+| *camel.source.endpoint.additionalProperties* | Additional properties for debezium components in case they can't be set directly on the camel configurations (e.g: setting Kafka Connect properties needed by Debezium engine, for example setting KafkaOffsetBackingStore), the properties have to be prefixed with additionalProperties.. E.g: additionalProperties.transactional.id=12345&additionalProperties.schema.registry.url=\http://localhost:8811/avro | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.bridgeErrorHandler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.internalKeyConverter* | The Converter class that should be used to serialize and deserialize key data for offsets. The default is JSON converter. | "org.apache.kafka.connect.json.JsonConverter" | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.internalValueConverter* | The Converter class that should be used to serialize and deserialize value data for offsets. The default is JSON converter. | "org.apache.kafka.connect.json.JsonConverter" | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.offsetCommitPolicy* | The name of the Java class of the commit policy. It defines when offsets commit has to be triggered based on the number of events processed and the time elapsed since the last commit. This class must implement the interface 'OffsetCommitPolicy'. The default is a periodic commit policy based upon time intervals. | "io.debezium.embedded.spi.OffsetCommitPolicy.PeriodicCommitOffsetPolicy" | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.offsetCommitTimeoutMs* | Maximum number of milliseconds to wait for records to flush and partition offset data to be committed to offset storage before cancelling the process and restoring the offset data to be committed in a future attempt. The default is 5 seconds. | 5000L | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.offsetFlushIntervalMs* | Interval at which to try committing offsets. The default is 1 minute. | 60000L | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.offsetStorage* | The name of the Java class that is responsible for persistence of connector offsets. | "org.apache.kafka.connect.storage.FileOffsetBackingStore" | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.offsetStorageFileName* | Path to file where offsets are to be stored. Required when offset.storage is set to the FileOffsetBackingStore. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.offsetStoragePartitions* | The number of partitions used when creating the offset storage topic. Required when offset.storage is set to the 'KafkaOffsetBackingStore'. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.offsetStorageReplicationFactor* | Replication factor used when creating the offset storage topic. Required when offset.storage is set to the KafkaOffsetBackingStore | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.offsetStorageTopic* | The name of the Kafka topic where offsets are to be stored. Required when offset.storage is set to the KafkaOffsetBackingStore. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.exceptionHandler* | To let the consumer use a custom ExceptionHandler. Notice if the option bridgeErrorHandler is enabled then this option is not in use. By default the consumer will deal with exceptions, that will be logged at WARN or ERROR level and ignored. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.exchangePattern* | Sets the exchange pattern when the consumer creates an exchange. One of: [InOnly] [InOut] [InOptionalOut] | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.basicPropertyBinding* | Whether the endpoint should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.synchronous* | Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.bigintUnsignedHandlingMode* | Specify how BIGINT UNSIGNED columns should be represented in change events, including:'precise' uses java.math.BigDecimal to represent values, which are encoded in the change events using a binary representation and Kafka Connect's 'org.apache.kafka.connect.data.Decimal' type; 'long' (the default) represents values using Java's 'long', which may not offer the precision but will be far easier to use in consumers. | "long" | ConfigDef. [...]
+| *camel.source.endpoint.binlogBufferSize* | The size of a look-ahead buffer used by the binlog reader to decide whether the transaction in progress is going to be committed or rolled back. Use 0 to disable look-ahead buffering. Defaults to 0 (i.e. buffering is disabled). | 0 | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.columnBlacklist* | Description is not available here, please check Debezium website for corresponding key 'column.blacklist' description. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.connectKeepAlive* | Whether a separate thread should be used to ensure the connection is kept alive. | true | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.connectKeepAliveIntervalMs* | Interval in milliseconds to wait for connection checking if keep alive thread is used. | 60000L | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.connectTimeoutMs* | Maximum time in milliseconds to wait after trying to connect to the database before timing out. | 30000 | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.databaseBlacklist* | Description is not available here, please check Debezium website for corresponding key 'database.blacklist' description. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.databaseHistory* | The name of the DatabaseHistory class that should be used to store and recover database schema changes. The configuration properties for the history are prefixed with the 'database.history.' string. | "io.debezium.relational.history.FileDatabaseHistory" | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.databaseHistoryFileFilename* | The path to the file that will be used to record the database history | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.databaseHistoryKafkaBootstrapServers* | A list of host/port pairs that the connector will use for establishing the initial connection to the Kafka cluster for retrieving database schema history previously stored by the connector. This should point to the same Kafka cluster used by the Kafka Connect process. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.databaseHistoryKafkaRecoveryAttempts* | The number of attempts in a row that no data are returned from Kafka before recover completes. The maximum amount of time to wait after receiving no data is (recovery.attempts) x (recovery.poll.interval.ms). | 100 | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.databaseHistoryKafkaRecoveryPollIntervalMs* | The number of milliseconds to wait while polling for persisted data during recovery. | 100 | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.databaseHistoryKafkaTopic* | The name of the topic for the database schema history | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.databaseHistorySkipUnparseableDdl* | Controls the action Debezium will take when it meets a DDL statement in binlog, that it cannot parse.By default the connector will stop operating but by changing the setting it can ignore the statements which it cannot parse. If skipping is enabled then Debezium can miss metadata changes. | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.databaseHistoryStoreOnlyMonitoredTablesDdl* | Controls what DDL will Debezium store in database history.By default (false) Debezium will store all incoming DDL statements. If set to truethen only DDL that manipulates a monitored table will be stored. | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.databaseHostname* | Resolvable hostname or IP address of the MySQL database server. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.databaseInitialStatements* | A semicolon separated list of SQL statements to be executed when a JDBC connection (not binlog reading connection) to the database is established. Note that the connector may establish JDBC connections at its own discretion, so this should typically be used for configuration of session parameters only,but not for executing DML statements. Use doubled semicolon (';;') to use a semicolon as a character and not as a delimiter. | null | C [...]
+| *camel.source.endpoint.databaseJdbcDriver* | JDBC Driver class name used to connect to the MySQL database server. | "class com.mysql.cj.jdbc.Driver" | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.databasePassword* | Password of the MySQL database user to be used when connecting to the database. | null | ConfigDef.Importance.HIGH
+| *camel.source.endpoint.databasePort* | Port of the MySQL database server. | 3306 | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.databaseServerId* | A numeric ID of this database client, which must be unique across all currently-running database processes in the cluster. This connector joins the MySQL database cluster as another server (with this unique ID) so it can read the binlog. By default, a random number is generated between 5400 and 6400. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.databaseServerIdOffset* | Only relevant if parallel snapshotting is configured. During parallel snapshotting, multiple (4) connections open to the database client, and they each need their own unique connection ID. This offset is used to generate those IDs from the base configured cluster ID. | 10000L | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.databaseServerName* | Unique name that identifies the database server and all recorded offsets, and that is used as a prefix for all schemas and topics. Each distinct installation should have a separate namespace and be monitored by at most one Debezium connector. | null | ConfigDef.Importance.HIGH
+| *camel.source.endpoint.databaseSslKeystore* | Location of the Java keystore file containing an application process's own certificate and private key. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.databaseSslKeystorePassword* | Password to access the private key from the keystore file specified by 'ssl.keystore' configuration property or the 'javax.net.ssl.keyStore' system or JVM property. This password is used to unlock the keystore file (store password), and to decrypt the private key stored in the keystore (key password). | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.databaseSslMode* | Whether to use an encrypted connection to MySQL. Options include'disabled' (the default) to use an unencrypted connection; 'preferred' to establish a secure (encrypted) connection if the server supports secure connections, but fall back to an unencrypted connection otherwise; 'required' to use a secure (encrypted) connection, and fail if one cannot be established; 'verify_ca' like 'required' but additionally verify the server TLS certificate ag [...]
+| *camel.source.endpoint.databaseSslTruststore* | Location of the Java truststore file containing the collection of CA certificates trusted by this application process (trust store). | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.databaseSslTruststorePassword* | Password to unlock the keystore file (store password) specified by 'ssl.trustore' configuration property or the 'javax.net.ssl.trustStore' system or JVM property. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.databaseUser* | Name of the MySQL database user to be used when connecting to the database. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.databaseWhitelist* | The databases for which changes are to be captured | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.decimalHandlingMode* | Specify how DECIMAL and NUMERIC columns should be represented in change events, including:'precise' (the default) uses java.math.BigDecimal to represent values, which are encoded in the change events using a binary representation and Kafka Connect's 'org.apache.kafka.connect.data.Decimal' type; 'string' uses string to represent values; 'double' represents values using Java's 'double', which may not offer the precision but will be far easier [...]
+| *camel.source.endpoint.enableTimeAdjuster* | MySQL allows user to insert year value as either 2-digit or 4-digit. In case of two digit the value is automatically mapped into 1970 - 2069.false - delegates the implicit conversion to the databasetrue - (the default) Debezium makes the conversion | true | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.eventDeserializationFailureHandlingMode* | Specify how failures during deserialization of binlog events (i.e. when encountering a corrupted event) should be handled, including:'fail' (the default) an exception indicating the problematic event and its binlog position is raised, causing the connector to be stopped; 'warn' the problematic event and its binlog position will be logged and the event will be skipped;'ignore' the problematic event will be skipped. | "fai [...]
+| *camel.source.endpoint.gtidNewChannelPosition* | If set to 'latest', when connector sees new GTID, it will start consuming gtid channel from the server latest executed gtid position. If 'earliest' connector starts reading channel from first available (not purged) gtid position on the server. | "latest" | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.gtidSourceExcludes* | The source UUIDs used to exclude GTID ranges when determine the starting position in the MySQL server's binlog. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.gtidSourceFilterDmlEvents* | If set to true, we will only produce DML events into Kafka for transactions that were written on mysql servers with UUIDs matching the filters defined by the gtid.source.includes or gtid.source.excludes configuration options, if they are specified. | true | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.gtidSourceIncludes* | The source UUIDs used to include GTID ranges when determine the starting position in the MySQL server's binlog. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.heartbeatIntervalMs* | Length of an interval in milli-seconds in in which the connector periodically sends heartbeat messages to a heartbeat topic. Use 0 to disable heartbeat messages. Disabled by default. | 0 | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.heartbeatTopicsPrefix* | The prefix that is used to name heartbeat topics.Defaults to __debezium-heartbeat. | "__debezium-heartbeat" | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.includeQuery* | Whether the connector should include the original SQL query that generated the change event. Note: This option requires MySQL be configured with the binlog_rows_query_log_events option set to ON. Query will not be present for events generated from snapshot. WARNING: Enabling this option may expose tables or fields explicitly blacklisted or masked by including the original SQL statement in the change event. For this reason the default value is 'fal [...]
+| *camel.source.endpoint.includeSchemaChanges* | Whether the connector should publish changes in the database schema to a Kafka topic with the same name as the database server ID. Each schema change will be recorded using a key that contains the database name and whose value includes the DDL statement(s).The default is 'true'. This is independent of how the connector internally records database history. | true | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.inconsistentSchemaHandlingMode* | Specify how binlog events that belong to a table missing from internal schema representation (i.e. internal representation is not consistent with database) should be handled, including:'fail' (the default) an exception indicating the problematic event and its binlog position is raised, causing the connector to be stopped; 'warn' the problematic event and its binlog position will be logged and the event will be skipped;'ignore' th [...]
+| *camel.source.endpoint.maxBatchSize* | Maximum size of each batch of source records. Defaults to 2048. | 2048 | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.maxQueueSize* | Maximum size of the queue for change events read from the database log but not yet recorded or forwarded. Defaults to 8192, and should always be larger than the maximum batch size. | 8192 | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.messageKeyColumns* | A semicolon-separated list of expressions that match fully-qualified tables and column(s) to be used as message key. Each expression must match the pattern ':',where the table names could be defined as (DB_NAME.TABLE_NAME) or (SCHEMA_NAME.TABLE_NAME), depending on the specific connector,and the key columns are a comma-separated list of columns representing the custom key. For any table without an explicit key configuration the table's primary [...]
+| *camel.source.endpoint.pollIntervalMs* | Frequency in milliseconds to wait for new change events to appear after receiving no events. Defaults to 500ms. | 500L | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.snapshotDelayMs* | The number of milliseconds to delay before a snapshot will begin. | 0L | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.snapshotFetchSize* | The maximum number of records that should be loaded into memory while performing a snapshot | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.snapshotLockingMode* | Controls how long the connector holds onto the global read lock while it is performing a snapshot. The default is 'minimal', which means the connector holds the global read lock (and thus prevents any updates) for just the initial portion of the snapshot while the database schemas and other metadata are being read. The remaining work in a snapshot involves selecting all rows from each table, and this can be done using the snapshot process' [...]
+| *camel.source.endpoint.snapshotMode* | The criteria for running a snapshot upon startup of the connector. Options include: 'when_needed' to specify that the connector run a snapshot upon startup whenever it deems it necessary; 'initial' (the default) to specify the connector can run a snapshot only when no offsets are available for the logical server name; 'initial_only' same as 'initial' except the connector should stop after completing the snapshot and before it would normally read t [...]
+| *camel.source.endpoint.snapshotNewTables* | BETA FEATURE: On connector restart, the connector will check if there have been any new tables added to the configuration, and snapshot them. There is presently only two options:'off': Default behavior. Do not snapshot new tables.'parallel': The snapshot of the new tables will occur in parallel to the continued binlog reading of the old tables. When the snapshot completes, an independent binlog reader will begin reading the events for the new [...]
+| *camel.source.endpoint.snapshotSelectStatementOverrides* | This property contains a comma-separated list of fully-qualified tables (DB_NAME.TABLE_NAME) or (SCHEMA_NAME.TABLE_NAME), depending on thespecific connectors . Select statements for the individual tables are specified in further configuration properties, one for each table, identified by the id 'snapshot.select.statement.overrides.DB_NAME.TABLE_NAME' or 'snapshot.select.statement.overrides.SCHEMA_NAME.TABLE_NAME', respectively. [...]
+| *camel.source.endpoint.sourceStructVersion* | A version of the format of the publicly visible source part in the message | "v2" | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.tableBlacklist* | Description is not available here, please check Debezium website for corresponding key 'table.blacklist' description. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.tableIgnoreBuiltin* | Flag specifying whether built-in tables should be ignored. | true | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.tableWhitelist* | The tables for which changes are to be captured | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.timePrecisionMode* | Time, date and timestamps can be represented with different kinds of precisions, including:'adaptive_time_microseconds': the precision of date and timestamp values is based the database column's precision; but time fields always use microseconds precision;'connect': always represents time, date and timestamp values using Kafka Connect's built-in representations for Time, Date, and Timestamp, which uses millisecond precision regardless of the [...]
+| *camel.source.endpoint.tombstonesOnDelete* | Whether delete operations should be represented by a delete event and a subsquenttombstone event (true) or only by a delete event (false). Emitting the tombstone event (the default behavior) allows Kafka to completely delete all events pertaining to the given key once the source record got deleted. | false | ConfigDef.Importance.MEDIUM
+| *camel.component.debezium-mysql.bridgeErrorHandler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | ConfigDef.Importa [...]
+| *camel.component.debezium-mysql.configuration* | Allow pre-configured Configurations to be set. | null | ConfigDef.Importance.MEDIUM
+| *camel.component.debezium-mysql.basicPropertyBinding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+|===
+
+
+// kafka-connector options: END
diff --git a/docs/modules/ROOT/pages/connectors/camel-debezium-postgres-kafka-source-connector.adoc b/docs/modules/ROOT/pages/connectors/camel-debezium-postgres-kafka-source-connector.adoc
new file mode 100644
index 0000000..21e26aa
--- /dev/null
+++ b/docs/modules/ROOT/pages/connectors/camel-debezium-postgres-kafka-source-connector.adoc
@@ -0,0 +1,93 @@
+// kafka-connector options: START
+== camel-debezium-postgres-kafka-connector source configuration
+
+When using camel-debezium-postgres-kafka-connector as source 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-debezium-postgres-kafka-connector</artifactId>
+ <version>x.x.x</version>
+ <!-- use the same version as your Camel Kafka connector version -->
+</dependency>
+----
+
+
+[width="100%",cols="2,5,^1,2",options="header"]
+|===
+| Name | Description | Default | Priority
+| *camel.source.path.name* | Unique name for the connector. Attempting to register again with the same name will fail. | null | ConfigDef.Importance.HIGH
+| *camel.source.endpoint.additionalProperties* | Additional properties for debezium components in case they can't be set directly on the camel configurations (e.g: setting Kafka Connect properties needed by Debezium engine, for example setting KafkaOffsetBackingStore), the properties have to be prefixed with additionalProperties.. E.g: additionalProperties.transactional.id=12345&additionalProperties.schema.registry.url=\http://localhost:8811/avro | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.bridgeErrorHandler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.internalKeyConverter* | The Converter class that should be used to serialize and deserialize key data for offsets. The default is JSON converter. | "org.apache.kafka.connect.json.JsonConverter" | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.internalValueConverter* | The Converter class that should be used to serialize and deserialize value data for offsets. The default is JSON converter. | "org.apache.kafka.connect.json.JsonConverter" | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.offsetCommitPolicy* | The name of the Java class of the commit policy. It defines when offsets commit has to be triggered based on the number of events processed and the time elapsed since the last commit. This class must implement the interface 'OffsetCommitPolicy'. The default is a periodic commit policy based upon time intervals. | "io.debezium.embedded.spi.OffsetCommitPolicy.PeriodicCommitOffsetPolicy" | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.offsetCommitTimeoutMs* | Maximum number of milliseconds to wait for records to flush and partition offset data to be committed to offset storage before cancelling the process and restoring the offset data to be committed in a future attempt. The default is 5 seconds. | 5000L | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.offsetFlushIntervalMs* | Interval at which to try committing offsets. The default is 1 minute. | 60000L | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.offsetStorage* | The name of the Java class that is responsible for persistence of connector offsets. | "org.apache.kafka.connect.storage.FileOffsetBackingStore" | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.offsetStorageFileName* | Path to file where offsets are to be stored. Required when offset.storage is set to the FileOffsetBackingStore. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.offsetStoragePartitions* | The number of partitions used when creating the offset storage topic. Required when offset.storage is set to the 'KafkaOffsetBackingStore'. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.offsetStorageReplicationFactor* | Replication factor used when creating the offset storage topic. Required when offset.storage is set to the KafkaOffsetBackingStore | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.offsetStorageTopic* | The name of the Kafka topic where offsets are to be stored. Required when offset.storage is set to the KafkaOffsetBackingStore. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.exceptionHandler* | To let the consumer use a custom ExceptionHandler. Notice if the option bridgeErrorHandler is enabled then this option is not in use. By default the consumer will deal with exceptions, that will be logged at WARN or ERROR level and ignored. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.exchangePattern* | Sets the exchange pattern when the consumer creates an exchange. One of: [InOnly] [InOut] [InOptionalOut] | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.basicPropertyBinding* | Whether the endpoint should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.synchronous* | Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.columnBlacklist* | Description is not available here, please check Debezium website for corresponding key 'column.blacklist' description. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.databaseDbname* | The name of the database the connector should be monitoring | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.databaseHistoryFileFilename* | The path to the file that will be used to record the database history | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.databaseHostname* | Resolvable hostname or IP address of the Postgres database server. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.databaseInitialStatements* | A semicolon separated list of SQL statements to be executed when a JDBC connection to the database is established. Note that the connector may establish JDBC connections at its own discretion, so this should typically be used for configurationof session parameters only, but not for executing DML statements. Use doubled semicolon (';;') to use a semicolon as a character and not as a delimiter. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.databasePassword* | Password of the Postgres database user to be used when connecting to the database. | null | ConfigDef.Importance.HIGH
+| *camel.source.endpoint.databasePort* | Port of the Postgres database server. | 5432 | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.databaseServerName* | Unique name that identifies the database server and all recorded offsets, and that is used as a prefix for all schemas and topics. Each distinct installation should have a separate namespace and be monitored by at most one Debezium connector. | null | ConfigDef.Importance.HIGH
+| *camel.source.endpoint.databaseSslcert* | File containing the SSL Certificate for the client. See the Postgres SSL docs for further information | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.databaseSslfactory* | A name of class to that creates SSL Sockets. Use org.postgresql.ssl.NonValidatingFactory to disable SSL validation in development environments | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.databaseSslkey* | File containing the SSL private key for the client. See the Postgres SSL docs for further information | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.databaseSslmode* | Whether to use an encrypted connection to Postgres. Options include'disable' (the default) to use an unencrypted connection; 'require' to use a secure (encrypted) connection, and fail if one cannot be established; 'verify-ca' like 'required' but additionally verify the server TLS certificate against the configured Certificate Authority (CA) certificates, or fail if no valid matching CA certificates are found; or'verify-full' like 'verify-ca' bu [...]
+| *camel.source.endpoint.databaseSslpassword* | Password to access the client private key from the file specified by 'database.sslkey'. See the Postgres SSL docs for further information | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.databaseSslrootcert* | File containing the root certificate(s) against which the server is validated. See the Postgres JDBC SSL docs for further information | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.databaseTcpkeepalive* | Enable or disable TCP keep-alive probe to avoid dropping TCP connection | true | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.databaseUser* | Name of the Postgres database user to be used when connecting to the database. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.decimalHandlingMode* | Specify how DECIMAL and NUMERIC columns should be represented in change events, including:'precise' (the default) uses java.math.BigDecimal to represent values, which are encoded in the change events using a binary representation and Kafka Connect's 'org.apache.kafka.connect.data.Decimal' type; 'string' uses string to represent values; 'double' represents values using Java's 'double', which may not offer the precision but will be far easier [...]
+| *camel.source.endpoint.heartbeatIntervalMs* | Length of an interval in milli-seconds in in which the connector periodically sends heartbeat messages to a heartbeat topic. Use 0 to disable heartbeat messages. Disabled by default. | 0 | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.heartbeatTopicsPrefix* | The prefix that is used to name heartbeat topics.Defaults to __debezium-heartbeat. | "__debezium-heartbeat" | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.hstoreHandlingMode* | Specify how HSTORE columns should be represented in change events, including:'json' represents values as json string'map' (default) represents values using java.util.Map | "json" | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.includeUnknownDatatypes* | Specify whether the fields of data type not supported by Debezium should be processed:'false' (the default) omits the fields; 'true' converts the field into an implementation dependent binary representation. | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.intervalHandlingMode* | Specify how INTERVAL columns should be represented in change events, including:'string' represents values as an exact ISO formatted string'numeric' (default) represents values using the inexact conversion into microseconds | "numeric" | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.maxBatchSize* | Maximum size of each batch of source records. Defaults to 2048. | 2048 | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.maxQueueSize* | Maximum size of the queue for change events read from the database log but not yet recorded or forwarded. Defaults to 8192, and should always be larger than the maximum batch size. | 8192 | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.messageKeyColumns* | A semicolon-separated list of expressions that match fully-qualified tables and column(s) to be used as message key. Each expression must match the pattern ':',where the table names could be defined as (DB_NAME.TABLE_NAME) or (SCHEMA_NAME.TABLE_NAME), depending on the specific connector,and the key columns are a comma-separated list of columns representing the custom key. For any table without an explicit key configuration the table's primary [...]
+| *camel.source.endpoint.pluginName* | The name of the Postgres logical decoding plugin installed on the server. Supported values are 'decoderbufs' and 'wal2json'. Defaults to 'decoderbufs'. | "decoderbufs" | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.pollIntervalMs* | Frequency in milliseconds to wait for new change events to appear after receiving no events. Defaults to 500ms. | 500L | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.publicationName* | The name of the Postgres 10 publication used for streaming changes from a plugin.Defaults to 'dbz_publication' | "dbz_publication" | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.schemaBlacklist* | The schemas for which events must not be captured | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.schemaRefreshMode* | Specify the conditions that trigger a refresh of the in-memory schema for a table. 'columns_diff' (the default) is the safest mode, ensuring the in-memory schema stays in-sync with the database table's schema at all times. 'columns_diff_exclude_unchanged_toast' instructs the connector to refresh the in-memory schema cache if there is a discrepancy between it and the schema derived from the incoming message, unless unchanged TOASTable data ful [...]
+| *camel.source.endpoint.schemaWhitelist* | The schemas for which events should be captured | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.slotDropOnStop* | Whether or not to drop the logical replication slot when the connector finishes orderlyBy default the replication is kept so that on restart progress can resume from the last recorded location | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.slotMaxRetries* | How many times to retry connecting to a replication slot when an attempt fails. | 6 | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.slotName* | The name of the Postgres logical decoding slot created for streaming changes from a plugin.Defaults to 'debezium | "debezium" | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.slotRetryDelayMs* | The number of milli-seconds to wait between retry attempts when the connector fails to connect to a replication slot. | 10000L | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.slotStreamParams* | Any optional parameters used by logical decoding plugin. Semi-colon separated. E.g. 'add-tables=public.table,public.table2;include-lsn=true' | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.snapshotCustomClass* | When 'snapshot.mode' is set as custom, this setting must be set to specify a fully qualified class name to load (via the default class loader).This class must implement the 'Snapshotter' interface and is called on each app boot to determine whether to do a snapshot and how to build queries. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.snapshotDelayMs* | The number of milliseconds to delay before a snapshot will begin. | 0L | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.snapshotFetchSize* | The maximum number of records that should be loaded into memory while performing a snapshot | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.snapshotLockTimeoutMs* | The maximum number of millis to wait for table locks at the beginning of a snapshot. If locks cannot be acquired in this time frame, the snapshot will be aborted. Defaults to 10 seconds | 10000L | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.snapshotMode* | The criteria for running a snapshot upon startup of the connector. Options include: 'always' to specify that the connector run a snapshot each time it starts up; 'initial' (the default) to specify the connector can run a snapshot only when no offsets are available for the logical server name; 'initial_only' same as 'initial' except the connector should stop after completing the snapshot and before it would normally start emitting changes;'never' t [...]
+| *camel.source.endpoint.snapshotSelectStatementOverrides* | This property contains a comma-separated list of fully-qualified tables (DB_NAME.TABLE_NAME) or (SCHEMA_NAME.TABLE_NAME), depending on thespecific connectors . Select statements for the individual tables are specified in further configuration properties, one for each table, identified by the id 'snapshot.select.statement.overrides.DB_NAME.TABLE_NAME' or 'snapshot.select.statement.overrides.SCHEMA_NAME.TABLE_NAME', respectively. [...]
+| *camel.source.endpoint.sourceStructVersion* | A version of the format of the publicly visible source part in the message | "v2" | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.statusUpdateIntervalMs* | Frequency in milliseconds for sending replication connection status updates to the server. Defaults to 10 seconds (10000 ms). | 10000 | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.tableBlacklist* | Description is not available here, please check Debezium website for corresponding key 'table.blacklist' description. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.tableWhitelist* | The tables for which changes are to be captured | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.timePrecisionMode* | Time, date, and timestamps can be represented with different kinds of precisions, including:'adaptive' (the default) bases the precision of time, date, and timestamp values on the database column's precision; 'adaptive_time_microseconds' like 'adaptive' mode, but TIME fields always use microseconds precision;'connect' always represents time, date, and timestamp values using Kafka Connect's built-in representations for Time, Date, and Timestam [...]
+| *camel.source.endpoint.toastedValuePlaceholder* | Specify the constant that will be provided by Debezium to indicate that the original value is a toasted value not provided by the database.If starts with 'hex:' prefix it is expected that the rest of the string repesents hexadecimally encoded octets. | "__debezium_unavailable_value" | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.tombstonesOnDelete* | Whether delete operations should be represented by a delete event and a subsquenttombstone event (true) or only by a delete event (false). Emitting the tombstone event (the default behavior) allows Kafka to completely delete all events pertaining to the given key once the source record got deleted. | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.xminFetchIntervalMs* | Specify how often (in ms) the xmin will be fetched from the replication slot. This xmin value is exposed by the slot which gives a lower bound of where a new replication slot could start from. The lower the value, the more likely this value is to be the current 'true' value, but the bigger the performance cost. The bigger the value, the less likely this value is to be the current 'true' value, but the lower the performance penalty. The defa [...]
+| *camel.component.debezium-postgres.bridgeErrorHandler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | ConfigDef.Impo [...]
+| *camel.component.debezium-postgres.configuration* | Allow pre-configured Configurations to be set. | null | ConfigDef.Importance.MEDIUM
+| *camel.component.debezium-postgres.basicPropertyBinding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+|===
+
+
+// kafka-connector options: END
diff --git a/docs/modules/ROOT/pages/connectors/camel-debezium-sqlserver-kafka-source-connector.adoc b/docs/modules/ROOT/pages/connectors/camel-debezium-sqlserver-kafka-source-connector.adoc
new file mode 100644
index 0000000..e867de0
--- /dev/null
+++ b/docs/modules/ROOT/pages/connectors/camel-debezium-sqlserver-kafka-source-connector.adoc
@@ -0,0 +1,75 @@
+// kafka-connector options: START
+== camel-debezium-sqlserver-kafka-connector source configuration
+
+When using camel-debezium-sqlserver-kafka-connector as source 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-debezium-sqlserver-kafka-connector</artifactId>
+ <version>x.x.x</version>
+ <!-- use the same version as your Camel Kafka connector version -->
+</dependency>
+----
+
+
+[width="100%",cols="2,5,^1,2",options="header"]
+|===
+| Name | Description | Default | Priority
+| *camel.source.path.name* | Unique name for the connector. Attempting to register again with the same name will fail. | null | ConfigDef.Importance.HIGH
+| *camel.source.endpoint.additionalProperties* | Additional properties for debezium components in case they can't be set directly on the camel configurations (e.g: setting Kafka Connect properties needed by Debezium engine, for example setting KafkaOffsetBackingStore), the properties have to be prefixed with additionalProperties.. E.g: additionalProperties.transactional.id=12345&additionalProperties.schema.registry.url=\http://localhost:8811/avro | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.bridgeErrorHandler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.internalKeyConverter* | The Converter class that should be used to serialize and deserialize key data for offsets. The default is JSON converter. | "org.apache.kafka.connect.json.JsonConverter" | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.internalValueConverter* | The Converter class that should be used to serialize and deserialize value data for offsets. The default is JSON converter. | "org.apache.kafka.connect.json.JsonConverter" | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.offsetCommitPolicy* | The name of the Java class of the commit policy. It defines when offsets commit has to be triggered based on the number of events processed and the time elapsed since the last commit. This class must implement the interface 'OffsetCommitPolicy'. The default is a periodic commit policy based upon time intervals. | "io.debezium.embedded.spi.OffsetCommitPolicy.PeriodicCommitOffsetPolicy" | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.offsetCommitTimeoutMs* | Maximum number of milliseconds to wait for records to flush and partition offset data to be committed to offset storage before cancelling the process and restoring the offset data to be committed in a future attempt. The default is 5 seconds. | 5000L | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.offsetFlushIntervalMs* | Interval at which to try committing offsets. The default is 1 minute. | 60000L | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.offsetStorage* | The name of the Java class that is responsible for persistence of connector offsets. | "org.apache.kafka.connect.storage.FileOffsetBackingStore" | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.offsetStorageFileName* | Path to file where offsets are to be stored. Required when offset.storage is set to the FileOffsetBackingStore. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.offsetStoragePartitions* | The number of partitions used when creating the offset storage topic. Required when offset.storage is set to the 'KafkaOffsetBackingStore'. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.offsetStorageReplicationFactor* | Replication factor used when creating the offset storage topic. Required when offset.storage is set to the KafkaOffsetBackingStore | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.offsetStorageTopic* | The name of the Kafka topic where offsets are to be stored. Required when offset.storage is set to the KafkaOffsetBackingStore. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.exceptionHandler* | To let the consumer use a custom ExceptionHandler. Notice if the option bridgeErrorHandler is enabled then this option is not in use. By default the consumer will deal with exceptions, that will be logged at WARN or ERROR level and ignored. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.exchangePattern* | Sets the exchange pattern when the consumer creates an exchange. One of: [InOnly] [InOut] [InOptionalOut] | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.basicPropertyBinding* | Whether the endpoint should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.synchronous* | Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.columnBlacklist* | Description is not available here, please check Debezium website for corresponding key 'column.blacklist' description. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.databaseDbname* | The name of the database the connector should be monitoring. When working with a multi-tenant set-up, must be set to the CDB name. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.databaseHistory* | The name of the DatabaseHistory class that should be used to store and recover database schema changes. The configuration properties for the history are prefixed with the 'database.history.' string. | "io.debezium.relational.history.FileDatabaseHistory" | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.databaseHistoryFileFilename* | The path to the file that will be used to record the database history | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.databaseHistoryKafkaBootstrapServers* | A list of host/port pairs that the connector will use for establishing the initial connection to the Kafka cluster for retrieving database schema history previously stored by the connector. This should point to the same Kafka cluster used by the Kafka Connect process. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.databaseHistoryKafkaRecoveryAttempts* | The number of attempts in a row that no data are returned from Kafka before recover completes. The maximum amount of time to wait after receiving no data is (recovery.attempts) x (recovery.poll.interval.ms). | 100 | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.databaseHistoryKafkaRecoveryPollIntervalMs* | The number of milliseconds to wait while polling for persisted data during recovery. | 100 | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.databaseHistoryKafkaTopic* | The name of the topic for the database schema history | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.databaseHostname* | Resolvable hostname or IP address of the SQL Server database server. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.databasePassword* | Password of the SQL Server database user to be used when connecting to the database. | null | ConfigDef.Importance.HIGH
+| *camel.source.endpoint.databasePort* | Port of the SQL Server database server. | 1433 | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.databaseServerName* | Unique name that identifies the database server and all recorded offsets, and that is used as a prefix for all schemas and topics. Each distinct installation should have a separate namespace and be monitored by at most one Debezium connector. | null | ConfigDef.Importance.HIGH
+| *camel.source.endpoint.databaseServerTimezone* | The timezone of the server used to correctly shift the commit transaction timestamp on the client sideOptions include: Any valid Java ZoneId | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.databaseUser* | Name of the SQL Server database user to be used when connecting to the database. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.decimalHandlingMode* | Specify how DECIMAL and NUMERIC columns should be represented in change events, including:'precise' (the default) uses java.math.BigDecimal to represent values, which are encoded in the change events using a binary representation and Kafka Connect's 'org.apache.kafka.connect.data.Decimal' type; 'string' uses string to represent values; 'double' represents values using Java's 'double', which may not offer the precision but will be far easier [...]
+| *camel.source.endpoint.heartbeatIntervalMs* | Length of an interval in milli-seconds in in which the connector periodically sends heartbeat messages to a heartbeat topic. Use 0 to disable heartbeat messages. Disabled by default. | 0 | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.heartbeatTopicsPrefix* | The prefix that is used to name heartbeat topics.Defaults to __debezium-heartbeat. | "__debezium-heartbeat" | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.maxBatchSize* | Maximum size of each batch of source records. Defaults to 2048. | 2048 | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.maxQueueSize* | Maximum size of the queue for change events read from the database log but not yet recorded or forwarded. Defaults to 8192, and should always be larger than the maximum batch size. | 8192 | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.messageKeyColumns* | A semicolon-separated list of expressions that match fully-qualified tables and column(s) to be used as message key. Each expression must match the pattern ':',where the table names could be defined as (DB_NAME.TABLE_NAME) or (SCHEMA_NAME.TABLE_NAME), depending on the specific connector,and the key columns are a comma-separated list of columns representing the custom key. For any table without an explicit key configuration the table's primary [...]
+| *camel.source.endpoint.pollIntervalMs* | Frequency in milliseconds to wait for new change events to appear after receiving no events. Defaults to 500ms. | 500L | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.snapshotDelayMs* | The number of milliseconds to delay before a snapshot will begin. | 0L | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.snapshotFetchSize* | The maximum number of records that should be loaded into memory while performing a snapshot | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.snapshotLockTimeoutMs* | The maximum number of millis to wait for table locks at the beginning of a snapshot. If locks cannot be acquired in this time frame, the snapshot will be aborted. Defaults to 10 seconds | 10000L | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.snapshotMode* | The criteria for running a snapshot upon startup of the connector. Options include: 'initial' (the default) to specify the connector should run a snapshot only when no offsets are available for the logical server name; 'schema_only' to specify the connector should run a snapshot of the schema when no offsets are available for the logical server name. | "initial" | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.snapshotSelectStatementOverrides* | This property contains a comma-separated list of fully-qualified tables (DB_NAME.TABLE_NAME) or (SCHEMA_NAME.TABLE_NAME), depending on thespecific connectors . Select statements for the individual tables are specified in further configuration properties, one for each table, identified by the id 'snapshot.select.statement.overrides.DB_NAME.TABLE_NAME' or 'snapshot.select.statement.overrides.SCHEMA_NAME.TABLE_NAME', respectively. [...]
+| *camel.source.endpoint.sourceStructVersion* | A version of the format of the publicly visible source part in the message | "v2" | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.tableBlacklist* | Description is not available here, please check Debezium website for corresponding key 'table.blacklist' description. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.tableIgnoreBuiltin* | Flag specifying whether built-in tables should be ignored. | true | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.tableWhitelist* | The tables for which changes are to be captured | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.timePrecisionMode* | Time, date, and timestamps can be represented with different kinds of precisions, including:'adaptive' (the default) bases the precision of time, date, and timestamp values on the database column's precision; 'adaptive_time_microseconds' like 'adaptive' mode, but TIME fields always use microseconds precision;'connect' always represents time, date, and timestamp values using Kafka Connect's built-in representations for Time, Date, and Timestam [...]
+| *camel.source.endpoint.tombstonesOnDelete* | Whether delete operations should be represented by a delete event and a subsquenttombstone event (true) or only by a delete event (false). Emitting the tombstone event (the default behavior) allows Kafka to completely delete all events pertaining to the given key once the source record got deleted. | false | ConfigDef.Importance.MEDIUM
+| *camel.component.debezium-sqlserver.bridgeErrorHandler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | ConfigDef.Imp [...]
+| *camel.component.debezium-sqlserver.configuration* | Allow pre-configured Configurations to be set. | null | ConfigDef.Importance.MEDIUM
+| *camel.component.debezium-sqlserver.basicPropertyBinding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+|===
+
+
+// kafka-connector options: END
diff --git a/docs/modules/ROOT/pages/connectors/camel-digitalocean-kafka-sink-connector.adoc b/docs/modules/ROOT/pages/connectors/camel-digitalocean-kafka-sink-connector.adoc
new file mode 100644
index 0000000..c7b97e3
--- /dev/null
+++ b/docs/modules/ROOT/pages/connectors/camel-digitalocean-kafka-sink-connector.adoc
@@ -0,0 +1,38 @@
+// kafka-connector options: START
+== camel-digitalocean-kafka-connector source configuration
+
+When using camel-digitalocean-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-digitalocean-kafka-connector</artifactId>
+ <version>x.x.x</version>
+ <!-- use the same version as your Camel Kafka connector version -->
+</dependency>
+----
+
+
+[width="100%",cols="2,5,^1,2",options="header"]
+|===
+| Name | Description | Default | Priority
+| *camel.sink.path.operation* | The operation to perform to the given resource. One of: [create] [update] [delete] [list] [ownList] [get] [listBackups] [listActions] [listNeighbors] [listSnapshots] [listKernels] [listAllNeighbors] [enableBackups] [disableBackups] [reboot] [powerCycle] [shutdown] [powerOn] [powerOff] [restore] [resetPassword] [resize] [rebuild] [rename] [changeKernel] [enableIpv6] [enablePrivateNetworking] [takeSnapshot] [transfer] [convert] [attach] [detach] [assign] [un [...]
+| *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 cre [...]
+| *camel.sink.endpoint.page* | Use for pagination. Force the page number. | "1" | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.perPage* | Use for pagination. Set the number of item per request. The maximum number of results per page is 200. | "25" | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.resource* | The DigitalOcean resource type on which perform the operation. One of: [account] [actions] [blockStorages] [droplets] [mages] [snapshots] [keys] [regions] [sizes] [floatingIPs] [tags] | null | ConfigDef.Importance.HIGH
+| *camel.sink.endpoint.basicPropertyBinding* | Whether the endpoint should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.digitalOceanClient* | To use a existing configured DigitalOceanClient as client | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.synchronous* | Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). | false | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.httpProxyHost* | Set a proxy host if needed | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.httpProxyPassword* | Set a proxy password if needed | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.httpProxyPort* | Set a proxy port if needed | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.httpProxyUser* | Set a proxy host if needed | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.oAuthToken* | DigitalOcean OAuth Token | null | ConfigDef.Importance.MEDIUM
+| *camel.component.digitalocean.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 [...]
+| *camel.component.digitalocean.basicPropertyBinding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+|===
+
+
+// kafka-connector options: END
diff --git a/docs/modules/ROOT/pages/connectors/camel-direct-kafka-sink-connector.adoc b/docs/modules/ROOT/pages/connectors/camel-direct-kafka-sink-connector.adoc
new file mode 100644
index 0000000..7d0def9
--- /dev/null
+++ b/docs/modules/ROOT/pages/connectors/camel-direct-kafka-sink-connector.adoc
@@ -0,0 +1,34 @@
+// kafka-connector options: START
+== camel-direct-kafka-connector source configuration
+
+When using camel-direct-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-direct-kafka-connector</artifactId>
+ <version>x.x.x</version>
+ <!-- use the same version as your Camel Kafka connector version -->
+</dependency>
+----
+
+
+[width="100%",cols="2,5,^1,2",options="header"]
+|===
+| Name | Description | Default | Priority
+| *camel.sink.path.name* | Name of direct endpoint | null | ConfigDef.Importance.HIGH
+| *camel.sink.endpoint.block* | If sending a message to a direct endpoint which has no active consumer, then we can tell the producer to block and wait for the consumer to become active. | true | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.failIfNoConsumers* | Whether the producer should fail by throwing an exception, when sending to a DIRECT endpoint with no active consumers. | false | ConfigDef.Importance.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 cre [...]
+| *camel.sink.endpoint.timeout* | The timeout value to use if block is enabled. | 30000L | ConfigDef.Importance.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 | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.synchronous* | Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). | false | ConfigDef.Importance.MEDIUM
+| *camel.component.direct.block* | If sending a message to a direct endpoint which has no active consumer, then we can tell the producer to block and wait for the consumer to become active. | true | ConfigDef.Importance.MEDIUM
+| *camel.component.direct.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 [...]
+| *camel.component.direct.timeout* | The timeout value to use if block is enabled. | 30000L | ConfigDef.Importance.MEDIUM
+| *camel.component.direct.basicPropertyBinding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+|===
+
+
+// kafka-connector options: END
diff --git a/docs/modules/ROOT/pages/connectors/camel-direct-kafka-source-connector.adoc b/docs/modules/ROOT/pages/connectors/camel-direct-kafka-source-connector.adoc
new file mode 100644
index 0000000..6797ed8
--- /dev/null
+++ b/docs/modules/ROOT/pages/connectors/camel-direct-kafka-source-connector.adoc
@@ -0,0 +1,31 @@
+// kafka-connector options: START
+== camel-direct-kafka-connector source configuration
+
+When using camel-direct-kafka-connector as source 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-direct-kafka-connector</artifactId>
+ <version>x.x.x</version>
+ <!-- use the same version as your Camel Kafka connector version -->
+</dependency>
+----
+
+
+[width="100%",cols="2,5,^1,2",options="header"]
+|===
+| Name | Description | Default | Priority
+| *camel.source.path.name* | Name of direct endpoint | null | ConfigDef.Importance.HIGH
+| *camel.source.endpoint.bridgeErrorHandler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.exceptionHandler* | To let the consumer use a custom ExceptionHandler. Notice if the option bridgeErrorHandler is enabled then this option is not in use. By default the consumer will deal with exceptions, that will be logged at WARN or ERROR level and ignored. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.exchangePattern* | Sets the exchange pattern when the consumer creates an exchange. One of: [InOnly] [InOut] [InOptionalOut] | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.basicPropertyBinding* | Whether the endpoint should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.synchronous* | Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). | false | ConfigDef.Importance.MEDIUM
+| *camel.component.direct.bridgeErrorHandler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | ConfigDef.Importance.MEDIUM
+| *camel.component.direct.basicPropertyBinding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+|===
+
+
+// kafka-connector options: END
diff --git a/docs/modules/ROOT/pages/connectors/camel-direct-vm-kafka-sink-connector.adoc b/docs/modules/ROOT/pages/connectors/camel-direct-vm-kafka-sink-connector.adoc
new file mode 100644
index 0000000..2dce8c8
--- /dev/null
+++ b/docs/modules/ROOT/pages/connectors/camel-direct-vm-kafka-sink-connector.adoc
@@ -0,0 +1,38 @@
+// kafka-connector options: START
+== camel-direct-vm-kafka-connector source configuration
+
+When using camel-direct-vm-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-direct-vm-kafka-connector</artifactId>
+ <version>x.x.x</version>
+ <!-- use the same version as your Camel Kafka connector version -->
+</dependency>
+----
+
+
+[width="100%",cols="2,5,^1,2",options="header"]
+|===
+| Name | Description | Default | Priority
+| *camel.sink.path.name* | Name of direct-vm endpoint | null | ConfigDef.Importance.HIGH
+| *camel.sink.endpoint.block* | If sending a message to a direct endpoint which has no active consumer, then we can tell the producer to block and wait for the consumer to become active. | true | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.failIfNoConsumers* | Whether the producer should fail by throwing an exception, when sending to a Direct-VM endpoint with no active consumers. | false | ConfigDef.Importance.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 cre [...]
+| *camel.sink.endpoint.timeout* | The timeout value to use if block is enabled. | 30000L | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.headerFilterStrategy* | Sets a HeaderFilterStrategy that will only be applied on producer endpoints (on both directions: request and response). Default value: none. | null | ConfigDef.Importance.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 | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.propagateProperties* | Whether to propagate or not properties from the producer side to the consumer side, and vice versa. Default value: true. | true | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.synchronous* | Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). | false | ConfigDef.Importance.MEDIUM
+| *camel.component.direct-vm.block* | If sending a message to a direct endpoint which has no active consumer, then we can tell the producer to block and wait for the consumer to become active. | true | ConfigDef.Importance.MEDIUM
+| *camel.component.direct-vm.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 th [...]
+| *camel.component.direct-vm.timeout* | The timeout value to use if block is enabled. | 30000L | ConfigDef.Importance.MEDIUM
+| *camel.component.direct-vm.basicPropertyBinding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+| *camel.component.direct-vm.headerFilterStrategy* | Sets a HeaderFilterStrategy that will only be applied on producer endpoints (on both directions: request and response). Default value: none. | null | ConfigDef.Importance.MEDIUM
+| *camel.component.direct-vm.propagateProperties* | Whether to propagate or not properties from the producer side to the consumer side, and vice versa. Default value: true. | true | ConfigDef.Importance.MEDIUM
+|===
+
+
+// kafka-connector options: END
diff --git a/docs/modules/ROOT/pages/connectors/camel-direct-vm-kafka-source-connector.adoc b/docs/modules/ROOT/pages/connectors/camel-direct-vm-kafka-source-connector.adoc
new file mode 100644
index 0000000..88061a7
--- /dev/null
+++ b/docs/modules/ROOT/pages/connectors/camel-direct-vm-kafka-source-connector.adoc
@@ -0,0 +1,34 @@
+// kafka-connector options: START
+== camel-direct-vm-kafka-connector source configuration
+
+When using camel-direct-vm-kafka-connector as source 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-direct-vm-kafka-connector</artifactId>
+ <version>x.x.x</version>
+ <!-- use the same version as your Camel Kafka connector version -->
+</dependency>
+----
+
+
+[width="100%",cols="2,5,^1,2",options="header"]
+|===
+| Name | Description | Default | Priority
+| *camel.source.path.name* | Name of direct-vm endpoint | null | ConfigDef.Importance.HIGH
+| *camel.source.endpoint.bridgeErrorHandler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.exceptionHandler* | To let the consumer use a custom ExceptionHandler. Notice if the option bridgeErrorHandler is enabled then this option is not in use. By default the consumer will deal with exceptions, that will be logged at WARN or ERROR level and ignored. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.exchangePattern* | Sets the exchange pattern when the consumer creates an exchange. One of: [InOnly] [InOut] [InOptionalOut] | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.basicPropertyBinding* | Whether the endpoint should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.propagateProperties* | Whether to propagate or not properties from the producer side to the consumer side, and vice versa. Default value: true. | true | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.synchronous* | Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). | false | ConfigDef.Importance.MEDIUM
+| *camel.component.direct-vm.bridgeErrorHandler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | ConfigDef.Importance.MEDIUM
+| *camel.component.direct-vm.basicPropertyBinding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+| *camel.component.direct-vm.headerFilterStrategy* | Sets a HeaderFilterStrategy that will only be applied on producer endpoints (on both directions: request and response). Default value: none. | null | ConfigDef.Importance.MEDIUM
+| *camel.component.direct-vm.propagateProperties* | Whether to propagate or not properties from the producer side to the consumer side, and vice versa. Default value: true. | true | ConfigDef.Importance.MEDIUM
+|===
+
+
+// kafka-connector options: END
diff --git a/docs/modules/ROOT/pages/connectors/camel-disruptor-kafka-sink-connector.adoc b/docs/modules/ROOT/pages/connectors/camel-disruptor-kafka-sink-connector.adoc
new file mode 100644
index 0000000..c01f0f7
--- /dev/null
+++ b/docs/modules/ROOT/pages/connectors/camel-disruptor-kafka-sink-connector.adoc
@@ -0,0 +1,38 @@
+// kafka-connector options: START
+== camel-disruptor-kafka-connector source configuration
+
+When using camel-disruptor-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-disruptor-kafka-connector</artifactId>
+ <version>x.x.x</version>
+ <!-- use the same version as your Camel Kafka connector version -->
+</dependency>
+----
+
+
+[width="100%",cols="2,5,^1,2",options="header"]
+|===
+| Name | Description | Default | Priority
+| *camel.sink.path.name* | Name of queue | null | ConfigDef.Importance.HIGH
+| *camel.sink.endpoint.size* | The maximum capacity of the Disruptors ringbuffer Will be effectively increased to the nearest power of two. Notice: Mind if you use this option, then its the first endpoint being created with the queue name, that determines the size. To make sure all endpoints use same size, then configure the size option on all of them, or the first endpoint being created. | 1024 | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.blockWhenFull* | Whether a thread that sends messages to a full Disruptor will block until the ringbuffer's capacity is no longer exhausted. By default, the calling thread will block and wait until the message can be accepted. By disabling this option, an exception will be thrown stating that the queue is full. | false | ConfigDef.Importance.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 cre [...]
+| *camel.sink.endpoint.producerType* | Defines the producers allowed on the Disruptor. The options allowed are: Multi to allow multiple producers and Single to enable certain optimizations only allowed when one concurrent producer (on one thread or otherwise synchronized) is active. One of: [Single] [Multi] | "Multi" | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.timeout* | Timeout (in milliseconds) before a producer will stop waiting for an asynchronous task to complete. You can disable timeout by using 0 or a negative value. | 30000L | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.waitForTaskToComplete* | Option to specify whether the caller should wait for the async task to complete or not before continuing. The following three options are supported: Always, Never or IfReplyExpected. The first two values are self-explanatory. The last value, IfReplyExpected, will only wait if the message is Request Reply based. One of: [Never] [IfReplyExpected] [Always] | "IfReplyExpected" | ConfigDef.Importance.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 | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.synchronous* | Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). | false | ConfigDef.Importance.MEDIUM
+| *camel.component.disruptor.bufferSize* | To configure the ring buffer size | 1024 | ConfigDef.Importance.MEDIUM
+| *camel.component.disruptor.queueSize* | To configure the ring buffer size | null | ConfigDef.Importance.LOW
+| *camel.component.disruptor.defaultBlockWhenFull* | To configure the default value for block when full The default value is true. | true | ConfigDef.Importance.MEDIUM
+| *camel.component.disruptor.defaultProducerType* | To configure the default value for DisruptorProducerType The default value is Multi. One of: [Single] [Multi] | "Multi" | ConfigDef.Importance.MEDIUM
+| *camel.component.disruptor.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 th [...]
+| *camel.component.disruptor.basicPropertyBinding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+|===
+
+
+// kafka-connector options: END
diff --git a/docs/modules/ROOT/pages/connectors/camel-disruptor-kafka-source-connector.adoc b/docs/modules/ROOT/pages/connectors/camel-disruptor-kafka-source-connector.adoc
new file mode 100644
index 0000000..b93d5ec
--- /dev/null
+++ b/docs/modules/ROOT/pages/connectors/camel-disruptor-kafka-source-connector.adoc
@@ -0,0 +1,40 @@
+// kafka-connector options: START
+== camel-disruptor-kafka-connector source configuration
+
+When using camel-disruptor-kafka-connector as source 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-disruptor-kafka-connector</artifactId>
+ <version>x.x.x</version>
+ <!-- use the same version as your Camel Kafka connector version -->
+</dependency>
+----
+
+
+[width="100%",cols="2,5,^1,2",options="header"]
+|===
+| Name | Description | Default | Priority
+| *camel.source.path.name* | Name of queue | null | ConfigDef.Importance.HIGH
+| *camel.source.endpoint.size* | The maximum capacity of the Disruptors ringbuffer Will be effectively increased to the nearest power of two. Notice: Mind if you use this option, then its the first endpoint being created with the queue name, that determines the size. To make sure all endpoints use same size, then configure the size option on all of them, or the first endpoint being created. | 1024 | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.bridgeErrorHandler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.concurrentConsumers* | Number of concurrent threads processing exchanges. | 1 | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.multipleConsumers* | Specifies whether multiple consumers are allowed. If enabled, you can use Disruptor for Publish-Subscribe messaging. That is, you can send a message to the queue and have each consumer receive a copy of the message. When enabled, this option should be specified on every consumer endpoint. | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.waitStrategy* | Defines the strategy used by consumer threads to wait on new exchanges to be published. The options allowed are:Blocking, Sleeping, BusySpin and Yielding. One of: [Blocking] [Sleeping] [BusySpin] [Yielding] | "Blocking" | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.exceptionHandler* | To let the consumer use a custom ExceptionHandler. Notice if the option bridgeErrorHandler is enabled then this option is not in use. By default the consumer will deal with exceptions, that will be logged at WARN or ERROR level and ignored. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.exchangePattern* | Sets the exchange pattern when the consumer creates an exchange. One of: [InOnly] [InOut] [InOptionalOut] | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.basicPropertyBinding* | Whether the endpoint should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.synchronous* | Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). | false | ConfigDef.Importance.MEDIUM
+| *camel.component.disruptor.bufferSize* | To configure the ring buffer size | 1024 | ConfigDef.Importance.MEDIUM
+| *camel.component.disruptor.queueSize* | To configure the ring buffer size | null | ConfigDef.Importance.LOW
+| *camel.component.disruptor.bridgeErrorHandler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | ConfigDef.Importance.MEDIUM
+| *camel.component.disruptor.defaultConcurrentConsumers* | To configure the default number of concurrent consumers | 1 | ConfigDef.Importance.MEDIUM
+| *camel.component.disruptor.defaultMultipleConsumers* | To configure the default value for multiple consumers | false | ConfigDef.Importance.MEDIUM
+| *camel.component.disruptor.defaultWaitStrategy* | To configure the default value for DisruptorWaitStrategy The default value is Blocking. One of: [Blocking] [Sleeping] [BusySpin] [Yielding] | "Blocking" | ConfigDef.Importance.MEDIUM
+| *camel.component.disruptor.basicPropertyBinding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+|===
+
+
+// kafka-connector options: END
diff --git a/docs/modules/ROOT/pages/connectors/camel-disruptor-vm-kafka-sink-connector.adoc b/docs/modules/ROOT/pages/connectors/camel-disruptor-vm-kafka-sink-connector.adoc
new file mode 100644
index 0000000..4267c09
--- /dev/null
+++ b/docs/modules/ROOT/pages/connectors/camel-disruptor-vm-kafka-sink-connector.adoc
@@ -0,0 +1,38 @@
+// kafka-connector options: START
+== camel-disruptor-vm-kafka-connector source configuration
+
+When using camel-disruptor-vm-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-disruptor-vm-kafka-connector</artifactId>
+ <version>x.x.x</version>
+ <!-- use the same version as your Camel Kafka connector version -->
+</dependency>
+----
+
+
+[width="100%",cols="2,5,^1,2",options="header"]
+|===
+| Name | Description | Default | Priority
+| *camel.sink.path.name* | Name of queue | null | ConfigDef.Importance.HIGH
+| *camel.sink.endpoint.size* | The maximum capacity of the Disruptors ringbuffer Will be effectively increased to the nearest power of two. Notice: Mind if you use this option, then its the first endpoint being created with the queue name, that determines the size. To make sure all endpoints use same size, then configure the size option on all of them, or the first endpoint being created. | 1024 | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.blockWhenFull* | Whether a thread that sends messages to a full Disruptor will block until the ringbuffer's capacity is no longer exhausted. By default, the calling thread will block and wait until the message can be accepted. By disabling this option, an exception will be thrown stating that the queue is full. | false | ConfigDef.Importance.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 cre [...]
+| *camel.sink.endpoint.producerType* | Defines the producers allowed on the Disruptor. The options allowed are: Multi to allow multiple producers and Single to enable certain optimizations only allowed when one concurrent producer (on one thread or otherwise synchronized) is active. One of: [Single] [Multi] | "Multi" | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.timeout* | Timeout (in milliseconds) before a producer will stop waiting for an asynchronous task to complete. You can disable timeout by using 0 or a negative value. | 30000L | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.waitForTaskToComplete* | Option to specify whether the caller should wait for the async task to complete or not before continuing. The following three options are supported: Always, Never or IfReplyExpected. The first two values are self-explanatory. The last value, IfReplyExpected, will only wait if the message is Request Reply based. One of: [Never] [IfReplyExpected] [Always] | "IfReplyExpected" | ConfigDef.Importance.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 | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.synchronous* | Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). | false | ConfigDef.Importance.MEDIUM
+| *camel.component.disruptor-vm.bufferSize* | To configure the ring buffer size | 1024 | ConfigDef.Importance.MEDIUM
+| *camel.component.disruptor-vm.queueSize* | To configure the ring buffer size | null | ConfigDef.Importance.LOW
+| *camel.component.disruptor-vm.defaultBlockWhenFull* | To configure the default value for block when full The default value is true. | true | ConfigDef.Importance.MEDIUM
+| *camel.component.disruptor-vm.defaultProducerType* | To configure the default value for DisruptorProducerType The default value is Multi. One of: [Single] [Multi] | "Multi" | ConfigDef.Importance.MEDIUM
+| *camel.component.disruptor-vm.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 [...]
+| *camel.component.disruptor-vm.basicPropertyBinding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+|===
+
+
+// kafka-connector options: END
diff --git a/docs/modules/ROOT/pages/connectors/camel-disruptor-vm-kafka-source-connector.adoc b/docs/modules/ROOT/pages/connectors/camel-disruptor-vm-kafka-source-connector.adoc
new file mode 100644
index 0000000..8f1512b
--- /dev/null
+++ b/docs/modules/ROOT/pages/connectors/camel-disruptor-vm-kafka-source-connector.adoc
@@ -0,0 +1,40 @@
+// kafka-connector options: START
+== camel-disruptor-vm-kafka-connector source configuration
+
+When using camel-disruptor-vm-kafka-connector as source 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-disruptor-vm-kafka-connector</artifactId>
+ <version>x.x.x</version>
+ <!-- use the same version as your Camel Kafka connector version -->
+</dependency>
+----
+
+
+[width="100%",cols="2,5,^1,2",options="header"]
+|===
+| Name | Description | Default | Priority
+| *camel.source.path.name* | Name of queue | null | ConfigDef.Importance.HIGH
+| *camel.source.endpoint.size* | The maximum capacity of the Disruptors ringbuffer Will be effectively increased to the nearest power of two. Notice: Mind if you use this option, then its the first endpoint being created with the queue name, that determines the size. To make sure all endpoints use same size, then configure the size option on all of them, or the first endpoint being created. | 1024 | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.bridgeErrorHandler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.concurrentConsumers* | Number of concurrent threads processing exchanges. | 1 | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.multipleConsumers* | Specifies whether multiple consumers are allowed. If enabled, you can use Disruptor for Publish-Subscribe messaging. That is, you can send a message to the queue and have each consumer receive a copy of the message. When enabled, this option should be specified on every consumer endpoint. | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.waitStrategy* | Defines the strategy used by consumer threads to wait on new exchanges to be published. The options allowed are:Blocking, Sleeping, BusySpin and Yielding. One of: [Blocking] [Sleeping] [BusySpin] [Yielding] | "Blocking" | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.exceptionHandler* | To let the consumer use a custom ExceptionHandler. Notice if the option bridgeErrorHandler is enabled then this option is not in use. By default the consumer will deal with exceptions, that will be logged at WARN or ERROR level and ignored. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.exchangePattern* | Sets the exchange pattern when the consumer creates an exchange. One of: [InOnly] [InOut] [InOptionalOut] | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.basicPropertyBinding* | Whether the endpoint should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.synchronous* | Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). | false | ConfigDef.Importance.MEDIUM
+| *camel.component.disruptor-vm.bufferSize* | To configure the ring buffer size | 1024 | ConfigDef.Importance.MEDIUM
+| *camel.component.disruptor-vm.queueSize* | To configure the ring buffer size | null | ConfigDef.Importance.LOW
+| *camel.component.disruptor-vm.bridgeErrorHandler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | ConfigDef.Importanc [...]
+| *camel.component.disruptor-vm.defaultConcurrentConsumers* | To configure the default number of concurrent consumers | 1 | ConfigDef.Importance.MEDIUM
+| *camel.component.disruptor-vm.defaultMultipleConsumers* | To configure the default value for multiple consumers | false | ConfigDef.Importance.MEDIUM
+| *camel.component.disruptor-vm.defaultWaitStrategy* | To configure the default value for DisruptorWaitStrategy The default value is Blocking. One of: [Blocking] [Sleeping] [BusySpin] [Yielding] | "Blocking" | ConfigDef.Importance.MEDIUM
+| *camel.component.disruptor-vm.basicPropertyBinding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+|===
+
+
+// kafka-connector options: END
diff --git a/docs/modules/ROOT/pages/connectors/camel-dns-kafka-sink-connector.adoc b/docs/modules/ROOT/pages/connectors/camel-dns-kafka-sink-connector.adoc
new file mode 100644
index 0000000..1d0b7b3
--- /dev/null
+++ b/docs/modules/ROOT/pages/connectors/camel-dns-kafka-sink-connector.adoc
@@ -0,0 +1,29 @@
+// kafka-connector options: START
+== camel-dns-kafka-connector source configuration
+
+When using camel-dns-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-dns-kafka-connector</artifactId>
+ <version>x.x.x</version>
+ <!-- use the same version as your Camel Kafka connector version -->
+</dependency>
+----
+
+
+[width="100%",cols="2,5,^1,2",options="header"]
+|===
+| Name | Description | Default | Priority
+| *camel.sink.path.dnsType* | The type of the lookup. One of: [dig] [ip] [lookup] [wikipedia] | null | ConfigDef.Importance.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 cre [...]
+| *camel.sink.endpoint.basicPropertyBinding* | Whether the endpoint should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.synchronous* | Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). | false | ConfigDef.Importance.MEDIUM
+| *camel.component.dns.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 cre [...]
+| *camel.component.dns.basicPropertyBinding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+|===
+
+
+// kafka-connector options: END
diff --git a/docs/modules/ROOT/pages/connectors/camel-docker-kafka-sink-connector.adoc b/docs/modules/ROOT/pages/connectors/camel-docker-kafka-sink-connector.adoc
new file mode 100644
index 0000000..0939ada
--- /dev/null
+++ b/docs/modules/ROOT/pages/connectors/camel-docker-kafka-sink-connector.adoc
@@ -0,0 +1,47 @@
+// kafka-connector options: START
+== camel-docker-kafka-connector source configuration
+
+When using camel-docker-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-docker-kafka-connector</artifactId>
+ <version>x.x.x</version>
+ <!-- use the same version as your Camel Kafka connector version -->
+</dependency>
+----
+
+
+[width="100%",cols="2,5,^1,2",options="header"]
+|===
+| Name | Description | Default | Priority
+| *camel.sink.path.operation* | Which operation to use One of: [events] [stats] [auth] [info] [ping] [version] [imagebuild] [imagecreate] [imageinspect] [imagelist] [imagepull] [imagepushimageremove] [imagesearch] [imagetag] [containerattach] [containercommit] [containercopyfile] [containercreate] [containerdiffinspectcontainer] [containerkill] [containerlist] [containerlog] [containerpause] [containerrestart] [containerremove] [containerstartcontainerstop] [containertop] [containerunpau [...]
+| *camel.sink.endpoint.email* | Email address associated with the user | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.host* | Docker host | "localhost" | ConfigDef.Importance.HIGH
+| *camel.sink.endpoint.port* | Docker port | "2375" | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.requestTimeout* | Request timeout for response (in seconds) | null | ConfigDef.Importance.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 cre [...]
+| *camel.sink.endpoint.basicPropertyBinding* | Whether the endpoint should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.cmdExecFactory* | The fully qualified class name of the DockerCmdExecFactory implementation to use | "com.github.dockerjava.netty.NettyDockerCmdExecFactory" | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.followRedirectFilter* | Whether to follow redirect filter | false | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.loggingFilter* | Whether to use logging filter | false | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.maxPerRouteConnections* | Maximum route connections | "100" | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.maxTotalConnections* | Maximum total connections | "100" | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.parameters* | Additional configuration parameters as key/value pairs | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.serverAddress* | Server address for docker registry. | "https://index.docker.io/v1/" | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.socket* | Socket connection mode | true | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.synchronous* | Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). | false | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.certPath* | Location containing the SSL certificate chain | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.password* | Password to authenticate with | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.secure* | Use HTTPS communication | false | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.tlsVerify* | Check TLS | false | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.username* | User name to authenticate with | null | ConfigDef.Importance.MEDIUM
+| *camel.component.docker.configuration* | To use the shared docker configuration | null | ConfigDef.Importance.MEDIUM
+| *camel.component.docker.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 [...]
+| *camel.component.docker.basicPropertyBinding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+|===
+
+
+// kafka-connector options: END
diff --git a/docs/modules/ROOT/pages/connectors/camel-docker-kafka-source-connector.adoc b/docs/modules/ROOT/pages/connectors/camel-docker-kafka-source-connector.adoc
new file mode 100644
index 0000000..fdde0d9
--- /dev/null
+++ b/docs/modules/ROOT/pages/connectors/camel-docker-kafka-source-connector.adoc
@@ -0,0 +1,49 @@
+// kafka-connector options: START
+== camel-docker-kafka-connector source configuration
+
+When using camel-docker-kafka-connector as source 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-docker-kafka-connector</artifactId>
+ <version>x.x.x</version>
+ <!-- use the same version as your Camel Kafka connector version -->
+</dependency>
+----
+
+
+[width="100%",cols="2,5,^1,2",options="header"]
+|===
+| Name | Description | Default | Priority
+| *camel.source.path.operation* | Which operation to use One of: [events] [stats] [auth] [info] [ping] [version] [imagebuild] [imagecreate] [imageinspect] [imagelist] [imagepull] [imagepushimageremove] [imagesearch] [imagetag] [containerattach] [containercommit] [containercopyfile] [containercreate] [containerdiffinspectcontainer] [containerkill] [containerlist] [containerlog] [containerpause] [containerrestart] [containerremove] [containerstartcontainerstop] [containertop] [containerunp [...]
+| *camel.source.endpoint.email* | Email address associated with the user | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.host* | Docker host | "localhost" | ConfigDef.Importance.HIGH
+| *camel.source.endpoint.port* | Docker port | "2375" | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.requestTimeout* | Request timeout for response (in seconds) | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.bridgeErrorHandler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.exceptionHandler* | To let the consumer use a custom ExceptionHandler. Notice if the option bridgeErrorHandler is enabled then this option is not in use. By default the consumer will deal with exceptions, that will be logged at WARN or ERROR level and ignored. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.exchangePattern* | Sets the exchange pattern when the consumer creates an exchange. One of: [InOnly] [InOut] [InOptionalOut] | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.basicPropertyBinding* | Whether the endpoint should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.cmdExecFactory* | The fully qualified class name of the DockerCmdExecFactory implementation to use | "com.github.dockerjava.netty.NettyDockerCmdExecFactory" | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.followRedirectFilter* | Whether to follow redirect filter | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.loggingFilter* | Whether to use logging filter | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.maxPerRouteConnections* | Maximum route connections | "100" | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.maxTotalConnections* | Maximum total connections | "100" | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.parameters* | Additional configuration parameters as key/value pairs | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.serverAddress* | Server address for docker registry. | "https://index.docker.io/v1/" | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.socket* | Socket connection mode | true | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.synchronous* | Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.certPath* | Location containing the SSL certificate chain | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.password* | Password to authenticate with | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.secure* | Use HTTPS communication | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.tlsVerify* | Check TLS | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.username* | User name to authenticate with | null | ConfigDef.Importance.MEDIUM
+| *camel.component.docker.configuration* | To use the shared docker configuration | null | ConfigDef.Importance.MEDIUM
+| *camel.component.docker.bridgeErrorHandler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | ConfigDef.Importance.MEDIUM
+| *camel.component.docker.basicPropertyBinding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+|===
+
+
+// kafka-connector options: END
diff --git a/docs/modules/ROOT/pages/connectors/camel-dozer-kafka-sink-connector.adoc b/docs/modules/ROOT/pages/connectors/camel-dozer-kafka-sink-connector.adoc
new file mode 100644
index 0000000..7d97d58
--- /dev/null
+++ b/docs/modules/ROOT/pages/connectors/camel-dozer-kafka-sink-connector.adoc
@@ -0,0 +1,35 @@
+// kafka-connector options: START
+== camel-dozer-kafka-connector source configuration
+
+When using camel-dozer-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-dozer-kafka-connector</artifactId>
+ <version>x.x.x</version>
+ <!-- use the same version as your Camel Kafka connector version -->
+</dependency>
+----
+
+
+[width="100%",cols="2,5,^1,2",options="header"]
+|===
+| Name | Description | Default | Priority
+| *camel.sink.path.name* | A human readable name of the mapping. | null | ConfigDef.Importance.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 cre [...]
+| *camel.sink.endpoint.mappingConfiguration* | The name of a DozerBeanMapperConfiguration bean in the Camel registry which should be used for configuring the Dozer mapping. This is an alternative to the mappingFile option that can be used for fine-grained control over how Dozer is configured. Remember to use a # prefix in the value to indicate that the bean is in the Camel registry (e.g. #myDozerConfig). | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.mappingFile* | The location of a Dozer configuration file. The file is loaded from the classpath by default, but you can use file:, classpath:, or http: to load the configuration from a specific location. | "dozerBeanMapping.xml" | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.marshalId* | The id of a dataFormat defined within the Camel Context to use for marshalling the mapping output to a non-Java type. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.sourceModel* | Fully-qualified class name for the source type used in the mapping. If specified, the input to the mapping is converted to the specified type before being mapped with Dozer. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.targetModel* | Fully-qualified class name for the target type used in the mapping. | null | ConfigDef.Importance.HIGH
+| *camel.sink.endpoint.unmarshalId* | The id of a dataFormat defined within the Camel Context to use for unmarshalling the mapping input from a non-Java type. | null | ConfigDef.Importance.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 | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.synchronous* | Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). | false | ConfigDef.Importance.MEDIUM
+| *camel.component.dozer.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 c [...]
+| *camel.component.dozer.basicPropertyBinding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+|===
+
+
+// kafka-connector options: END
diff --git a/docs/modules/ROOT/pages/connectors/camel-drill-kafka-sink-connector.adoc b/docs/modules/ROOT/pages/connectors/camel-drill-kafka-sink-connector.adoc
new file mode 100644
index 0000000..8e12aae
--- /dev/null
+++ b/docs/modules/ROOT/pages/connectors/camel-drill-kafka-sink-connector.adoc
@@ -0,0 +1,33 @@
+// kafka-connector options: START
+== camel-drill-kafka-connector source configuration
+
+When using camel-drill-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-drill-kafka-connector</artifactId>
+ <version>x.x.x</version>
+ <!-- use the same version as your Camel Kafka connector version -->
+</dependency>
+----
+
+
+[width="100%",cols="2,5,^1,2",options="header"]
+|===
+| Name | Description | Default | Priority
+| *camel.sink.path.host* | Host name or IP address | null | ConfigDef.Importance.HIGH
+| *camel.sink.endpoint.clusterId* | Cluster ID \https://drill.apache.org/docs/using-the-jdbc-driver/#determining-the-cluster-id | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.directory* | Drill directory | null | ConfigDef.Importance.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 cre [...]
+| *camel.sink.endpoint.mode* | Connection mode: zk: Zookeeper drillbit: Drillbit direct connection \https://drill.apache.org/docs/using-the-jdbc-driver/ One of: [ZK] [DRILLBIT] | "ZK" | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.port* | Port number | "2181" | ConfigDef.Importance.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 | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.synchronous* | Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). | false | ConfigDef.Importance.MEDIUM
+| *camel.component.drill.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 c [...]
+| *camel.component.drill.basicPropertyBinding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+|===
+
+
+// kafka-connector options: END
diff --git a/docs/modules/ROOT/pages/connectors/camel-dropbox-kafka-sink-connector.adoc b/docs/modules/ROOT/pages/connectors/camel-dropbox-kafka-sink-connector.adoc
new file mode 100644
index 0000000..f40de51
--- /dev/null
+++ b/docs/modules/ROOT/pages/connectors/camel-dropbox-kafka-sink-connector.adoc
@@ -0,0 +1,37 @@
+// kafka-connector options: START
+== camel-dropbox-kafka-connector source configuration
+
+When using camel-dropbox-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-dropbox-kafka-connector</artifactId>
+ <version>x.x.x</version>
+ <!-- use the same version as your Camel Kafka connector version -->
+</dependency>
+----
+
+
+[width="100%",cols="2,5,^1,2",options="header"]
+|===
+| Name | Description | Default | Priority
+| *camel.sink.path.operation* | The specific action (typically is a CRUD action) to perform on Dropbox remote folder. One of: [put] [del] [search] [get] [move] | null | ConfigDef.Importance.HIGH
+| *camel.sink.endpoint.accessToken* | The access token to make API requests for a specific Dropbox user | null | ConfigDef.Importance.HIGH
+| *camel.sink.endpoint.client* | To use an existing DbxClient instance as DropBox client. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.clientIdentifier* | Name of the app registered to make API requests | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.localPath* | Optional folder or file to upload on Dropbox from the local filesystem. If this option has not been configured then the message body is used as the content to upload. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.newRemotePath* | Destination file or folder | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.query* | A space-separated list of sub-strings to search for. A file matches only if it contains all the sub-strings. If this option is not set, all files will be matched. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.remotePath* | Original file or folder to move | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.uploadMode* | Which mode to upload. in case of add the new file will be renamed if a file with the same name already exists on dropbox. in case of force if a file with the same name already exists on dropbox, this will be overwritten. One of: [add] [force] | null | ConfigDef.Importance.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 cre [...]
+| *camel.sink.endpoint.basicPropertyBinding* | Whether the endpoint should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.synchronous* | Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). | false | ConfigDef.Importance.MEDIUM
+| *camel.component.dropbox.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 [...]
+| *camel.component.dropbox.basicPropertyBinding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+|===
+
+
+// kafka-connector options: END
diff --git a/docs/modules/ROOT/pages/connectors/camel-dropbox-kafka-source-connector.adoc b/docs/modules/ROOT/pages/connectors/camel-dropbox-kafka-source-connector.adoc
new file mode 100644
index 0000000..9c0fc50
--- /dev/null
+++ b/docs/modules/ROOT/pages/connectors/camel-dropbox-kafka-source-connector.adoc
@@ -0,0 +1,39 @@
+// kafka-connector options: START
+== camel-dropbox-kafka-connector source configuration
+
+When using camel-dropbox-kafka-connector as source 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-dropbox-kafka-connector</artifactId>
+ <version>x.x.x</version>
+ <!-- use the same version as your Camel Kafka connector version -->
+</dependency>
+----
+
+
+[width="100%",cols="2,5,^1,2",options="header"]
+|===
+| Name | Description | Default | Priority
+| *camel.source.path.operation* | The specific action (typically is a CRUD action) to perform on Dropbox remote folder. One of: [put] [del] [search] [get] [move] | null | ConfigDef.Importance.HIGH
+| *camel.source.endpoint.accessToken* | The access token to make API requests for a specific Dropbox user | null | ConfigDef.Importance.HIGH
+| *camel.source.endpoint.client* | To use an existing DbxClient instance as DropBox client. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.clientIdentifier* | Name of the app registered to make API requests | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.localPath* | Optional folder or file to upload on Dropbox from the local filesystem. If this option has not been configured then the message body is used as the content to upload. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.newRemotePath* | Destination file or folder | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.query* | A space-separated list of sub-strings to search for. A file matches only if it contains all the sub-strings. If this option is not set, all files will be matched. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.remotePath* | Original file or folder to move | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.uploadMode* | Which mode to upload. in case of add the new file will be renamed if a file with the same name already exists on dropbox. in case of force if a file with the same name already exists on dropbox, this will be overwritten. One of: [add] [force] | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.bridgeErrorHandler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.exceptionHandler* | To let the consumer use a custom ExceptionHandler. Notice if the option bridgeErrorHandler is enabled then this option is not in use. By default the consumer will deal with exceptions, that will be logged at WARN or ERROR level and ignored. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.exchangePattern* | Sets the exchange pattern when the consumer creates an exchange. One of: [InOnly] [InOut] [InOptionalOut] | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.basicPropertyBinding* | Whether the endpoint should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.synchronous* | Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). | false | ConfigDef.Importance.MEDIUM
+| *camel.component.dropbox.bridgeErrorHandler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | ConfigDef.Importance.MEDIUM
+| *camel.component.dropbox.basicPropertyBinding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+|===
+
+
+// kafka-connector options: END
diff --git a/docs/modules/ROOT/pages/connectors/camel-ehcache-kafka-sink-connector.adoc b/docs/modules/ROOT/pages/connectors/camel-ehcache-kafka-sink-connector.adoc
new file mode 100644
index 0000000..762a264
--- /dev/null
+++ b/docs/modules/ROOT/pages/connectors/camel-ehcache-kafka-sink-connector.adoc
@@ -0,0 +1,45 @@
+// kafka-connector options: START
+== camel-ehcache-kafka-connector source configuration
+
+When using camel-ehcache-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-ehcache-kafka-connector</artifactId>
+ <version>x.x.x</version>
+ <!-- use the same version as your Camel Kafka connector version -->
+</dependency>
+----
+
+
+[width="100%",cols="2,5,^1,2",options="header"]
+|===
+| Name | Description | Default | Priority
+| *camel.sink.path.cacheName* | the cache name | null | ConfigDef.Importance.HIGH
+| *camel.sink.endpoint.cacheManager* | The cache manager | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.cacheManagerConfiguration* | The cache manager configuration | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.configurationUri* | URI pointing to the Ehcache XML configuration file's location | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.createCacheIfNotExist* | Configure if a cache need to be created if it does exist or can't be pre-configured. | true | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.action* | To configure the default cache action. If an action is set in the message header, then the operation from the header takes precedence. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.key* | To configure the default action key. If a key is set in the message header, then the key from the header takes precedence. | null | ConfigDef.Importance.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 cre [...]
+| *camel.sink.endpoint.basicPropertyBinding* | Whether the endpoint should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.configuration* | The default cache configuration to be used to create caches. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.configurations* | A map of cache configuration to be used to create caches. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.keyType* | The cache key type, default java.lang.Object | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.synchronous* | Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). | false | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.valueType* | The cache value type, default java.lang.Object | null | ConfigDef.Importance.MEDIUM
+| *camel.component.ehcache.cacheConfiguration* | The default cache configuration to be used to create caches. | null | ConfigDef.Importance.MEDIUM
+| *camel.component.ehcache.cacheConfigurationUri* | URI pointing to the Ehcache XML configuration file's location | null | ConfigDef.Importance.MEDIUM
+| *camel.component.ehcache.cacheManager* | The cache manager | null | ConfigDef.Importance.MEDIUM
+| *camel.component.ehcache.cacheManagerConfiguration* | The cache manager configuration | null | ConfigDef.Importance.MEDIUM
+| *camel.component.ehcache.cachesConfigurations* | A map of caches configurations to be used to create caches. | null | ConfigDef.Importance.MEDIUM
+| *camel.component.ehcache.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 [...]
+| *camel.component.ehcache.basicPropertyBinding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+| *camel.component.ehcache.configuration* | Sets the global component configuration | null | ConfigDef.Importance.MEDIUM
+|===
+
+
+// kafka-connector options: END
diff --git a/docs/modules/ROOT/pages/connectors/camel-ehcache-kafka-source-connector.adoc b/docs/modules/ROOT/pages/connectors/camel-ehcache-kafka-source-connector.adoc
new file mode 100644
index 0000000..5f9402b
--- /dev/null
+++ b/docs/modules/ROOT/pages/connectors/camel-ehcache-kafka-source-connector.adoc
@@ -0,0 +1,48 @@
+// kafka-connector options: START
+== camel-ehcache-kafka-connector source configuration
+
+When using camel-ehcache-kafka-connector as source 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-ehcache-kafka-connector</artifactId>
+ <version>x.x.x</version>
+ <!-- use the same version as your Camel Kafka connector version -->
+</dependency>
+----
+
+
+[width="100%",cols="2,5,^1,2",options="header"]
+|===
+| Name | Description | Default | Priority
+| *camel.source.path.cacheName* | the cache name | null | ConfigDef.Importance.HIGH
+| *camel.source.endpoint.cacheManager* | The cache manager | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.cacheManagerConfiguration* | The cache manager configuration | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.configurationUri* | URI pointing to the Ehcache XML configuration file's location | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.createCacheIfNotExist* | Configure if a cache need to be created if it does exist or can't be pre-configured. | true | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.bridgeErrorHandler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.eventFiring* | Set the delivery mode (synchronous, asynchronous) One of: [ASYNCHRONOUS] [SYNCHRONOUS] | "ASYNCHRONOUS" | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.eventOrdering* | Set the delivery mode (ordered, unordered) One of: [UNORDERED] [ORDERED] | "ORDERED" | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.eventTypes* | Set the type of events to listen for (EVICTED,EXPIRED,REMOVED,CREATED,UPDATED). You can specify multiple entries separated by comma. One of: [EVICTED] [EXPIRED] [REMOVED] [CREATED] [UPDATED] | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.exceptionHandler* | To let the consumer use a custom ExceptionHandler. Notice if the option bridgeErrorHandler is enabled then this option is not in use. By default the consumer will deal with exceptions, that will be logged at WARN or ERROR level and ignored. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.exchangePattern* | Sets the exchange pattern when the consumer creates an exchange. One of: [InOnly] [InOut] [InOptionalOut] | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.basicPropertyBinding* | Whether the endpoint should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.configuration* | The default cache configuration to be used to create caches. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.configurations* | A map of cache configuration to be used to create caches. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.keyType* | The cache key type, default java.lang.Object | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.synchronous* | Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.valueType* | The cache value type, default java.lang.Object | null | ConfigDef.Importance.MEDIUM
+| *camel.component.ehcache.cacheConfiguration* | The default cache configuration to be used to create caches. | null | ConfigDef.Importance.MEDIUM
+| *camel.component.ehcache.cacheConfigurationUri* | URI pointing to the Ehcache XML configuration file's location | null | ConfigDef.Importance.MEDIUM
+| *camel.component.ehcache.cacheManager* | The cache manager | null | ConfigDef.Importance.MEDIUM
+| *camel.component.ehcache.cacheManagerConfiguration* | The cache manager configuration | null | ConfigDef.Importance.MEDIUM
+| *camel.component.ehcache.cachesConfigurations* | A map of caches configurations to be used to create caches. | null | ConfigDef.Importance.MEDIUM
+| *camel.component.ehcache.bridgeErrorHandler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | ConfigDef.Importance.MEDIUM
+| *camel.component.ehcache.basicPropertyBinding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+| *camel.component.ehcache.configuration* | Sets the global component configuration | null | ConfigDef.Importance.MEDIUM
+|===
+
+
+// kafka-connector options: END
diff --git a/docs/modules/ROOT/pages/connectors/camel-elasticsearch-rest-kafka-sink-connector.adoc b/docs/modules/ROOT/pages/connectors/camel-elasticsearch-rest-kafka-sink-connector.adoc
new file mode 100644
index 0000000..f26c621
--- /dev/null
+++ b/docs/modules/ROOT/pages/connectors/camel-elasticsearch-rest-kafka-sink-connector.adoc
@@ -0,0 +1,56 @@
+// kafka-connector options: START
+== camel-elasticsearch-rest-kafka-connector source configuration
+
+When using camel-elasticsearch-rest-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-elasticsearch-rest-kafka-connector</artifactId>
+ <version>x.x.x</version>
+ <!-- use the same version as your Camel Kafka connector version -->
+</dependency>
+----
+
+
+[width="100%",cols="2,5,^1,2",options="header"]
+|===
+| Name | Description | Default | Priority
+| *camel.sink.path.clusterName* | Name of the cluster | null | ConfigDef.Importance.HIGH
+| *camel.sink.endpoint.connectionTimeout* | The time in ms to wait before connection will timeout. | 30000 | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.disconnect* | Disconnect after it finish calling the producer | false | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.enableSniffer* | Enable automatically discover nodes from a running Elasticsearch cluster | false | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.enableSSL* | Enable SSL | false | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.from* | Starting index of the response. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.hostAddresses* | Comma separated list with ip:port formatted remote transport addresses to use. | null | ConfigDef.Importance.HIGH
+| *camel.sink.endpoint.indexName* | The name of the index to act against | null | ConfigDef.Importance.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 cre [...]
+| *camel.sink.endpoint.maxRetryTimeout* | The time in ms before retry | 30000 | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.operation* | What operation to perform One of: [Index] [Update] [Bulk] [BulkIndex] [GetById] [MultiGet] [MultiSearch] [Delete] [DeleteIndex] [Search] [Exists] [Ping] | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.scrollKeepAliveMs* | Time in ms during which elasticsearch will keep search context alive | 60000 | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.size* | Size of the response. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.sniffAfterFailureDelay* | The delay of a sniff execution scheduled after a failure (in milliseconds) | 60000 | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.snifferInterval* | The interval between consecutive ordinary sniff executions in milliseconds. Will be honoured when sniffOnFailure is disabled or when there are no failures between consecutive sniff executions | 300000 | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.socketTimeout* | The timeout in ms to wait before the socket will timeout. | 30000 | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.useScroll* | Enable scroll usage | false | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.waitForActiveShards* | Index creation waits for the write consistency number of shards to be available | 1 | ConfigDef.Importance.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 | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.synchronous* | Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). | false | ConfigDef.Importance.MEDIUM
+| *camel.component.elasticsearch-rest.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 pro [...]
+| *camel.component.elasticsearch-rest.basicPropertyBinding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+| *camel.component.elasticsearch-rest.client* | To use an existing configured Elasticsearch client, instead of creating a client per endpoint. This allow to customize the client with specific settings. | null | ConfigDef.Importance.MEDIUM
+| *camel.component.elasticsearch-rest.connectionTimeout* | The time in ms to wait before connection will timeout. | 30000 | ConfigDef.Importance.MEDIUM
+| *camel.component.elasticsearch-rest.enableSniffer* | Enable automatically discover nodes from a running Elasticsearch cluster | "false" | ConfigDef.Importance.MEDIUM
+| *camel.component.elasticsearch-rest.hostAddresses* | Comma separated list with ip:port formatted remote transport addresses to use. The ip and port options must be left blank for hostAddresses to be considered instead. | null | ConfigDef.Importance.MEDIUM
+| *camel.component.elasticsearch-rest.maxRetryTimeout* | The time in ms before retry | 30000 | ConfigDef.Importance.MEDIUM
+| *camel.component.elasticsearch-rest.sniffAfterFailureDelay* | The delay of a sniff execution scheduled after a failure (in milliseconds) | 60000 | ConfigDef.Importance.MEDIUM
+| *camel.component.elasticsearch-rest.snifferInterval* | The interval between consecutive ordinary sniff executions in milliseconds. Will be honoured when sniffOnFailure is disabled or when there are no failures between consecutive sniff executions | 300000 | ConfigDef.Importance.MEDIUM
+| *camel.component.elasticsearch-rest.socketTimeout* | The timeout in ms to wait before the socket will timeout. | 30000 | ConfigDef.Importance.MEDIUM
+| *camel.component.elasticsearch-rest.enableSSL* | Enable SSL | "false" | ConfigDef.Importance.MEDIUM
+| *camel.component.elasticsearch-rest.password* | Password for authenticate | null | ConfigDef.Importance.MEDIUM
+| *camel.component.elasticsearch-rest.user* | Basic authenticate user | null | ConfigDef.Importance.MEDIUM
+|===
+
+
+// kafka-connector options: END
diff --git a/docs/modules/ROOT/pages/connectors/camel-elsql-kafka-sink-connector.adoc b/docs/modules/ROOT/pages/connectors/camel-elsql-kafka-sink-connector.adoc
new file mode 100644
index 0000000..4c3cb4f
--- /dev/null
+++ b/docs/modules/ROOT/pages/connectors/camel-elsql-kafka-sink-connector.adoc
@@ -0,0 +1,52 @@
+// kafka-connector options: START
+== camel-elsql-kafka-connector source configuration
+
+When using camel-elsql-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-elsql-kafka-connector</artifactId>
+ <version>x.x.x</version>
+ <!-- use the same version as your Camel Kafka connector version -->
+</dependency>
+----
+
+
+[width="100%",cols="2,5,^1,2",options="header"]
+|===
+| Name | Description | Default | Priority
+| *camel.sink.path.elsqlName* | The name of the elsql to use (is NAMED in the elsql file) | null | ConfigDef.Importance.HIGH
+| *camel.sink.path.resourceUri* | The resource file which contains the elsql SQL statements to use. You can specify multiple resources separated by comma. The resources are loaded on the classpath by default, you can prefix with file: to load from file system. Notice you can set this option on the component and then you do not have to configure this on the endpoint. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.allowNamedParameters* | Whether to allow using named parameters in the queries. | true | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.databaseVendor* | To use a vendor specific com.opengamma.elsql.ElSqlConfig One of: [Default] [Postgres] [HSql] [MySql] [Oracle] [SqlServer2008] [Veritca] | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.dataSource* | Sets the DataSource to use to communicate with the database. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.dataSourceRef* | Sets the reference to a DataSource to lookup from the registry, to use for communicating with the database. | null | ConfigDef.Importance.LOW
+| *camel.sink.endpoint.outputClass* | Specify the full package and class name to use as conversion when outputType=SelectOne. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.outputHeader* | Store the query result in a header instead of the message body. By default, outputHeader == null and the query result is stored in the message body, any existing content in the message body is discarded. If outputHeader is set, the value is used as the name of the header to store the query result and the original message body is preserved. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.outputType* | Make the output of consumer or producer to SelectList as List of Map, or SelectOne as single Java object in the following way: a) If the query has only single column, then that JDBC Column object is returned. (such as SELECT COUNT( ) FROM PROJECT will return a Long object. b) If the query has more than one column, then it will return a Map of that result. c) If the outputClass is set, then it will convert the query result into an Java bean object by c [...]
+| *camel.sink.endpoint.separator* | The separator to use when parameter values is taken from message body (if the body is a String type), to be inserted at # placeholders. Notice if you use named parameters, then a Map type is used instead. The default value is comma | "," | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.batch* | Enables or disables batch mode | false | ConfigDef.Importance.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 cre [...]
+| *camel.sink.endpoint.noop* | If set, will ignore the results of the SQL query and use the existing IN message as the OUT message for the continuation of processing | false | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.useMessageBodyForSql* | Whether to use the message body as the SQL and then headers for parameters. If this option is enabled then the SQL in the uri is not used. | false | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.alwaysPopulateStatement* | If enabled then the populateStatement method from org.apache.camel.component.sql.SqlPrepareStatementStrategy is always invoked, also if there is no expected parameters to be prepared. When this is false then the populateStatement is only invoked if there is 1 or more expected parameters to be set; for example this avoids reading the message body/headers for SQL queries with no parameters. | false | ConfigDef.Importance.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 | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.elSqlConfig* | To use a specific configured ElSqlConfig. It may be better to use the databaseVendor option instead. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.parametersCount* | If set greater than zero, then Camel will use this count value of parameters to replace instead of querying via JDBC metadata API. This is useful if the JDBC vendor could not return correct parameters count, then user may override instead. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.placeholder* | Specifies a character that will be replaced to in SQL query. Notice, that it is simple String.replaceAll() operation and no SQL parsing is involved (quoted strings will also change). | "#" | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.prepareStatementStrategy* | Allows to plugin to use a custom org.apache.camel.component.sql.SqlPrepareStatementStrategy to control preparation of the query and prepared statement. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.synchronous* | Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). | false | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.templateOptions* | Configures the Spring JdbcTemplate with the key/values from the Map | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.usePlaceholder* | Sets whether to use placeholder and replace all placeholder characters with sign in the SQL queries. | true | ConfigDef.Importance.MEDIUM
+| *camel.component.elsql.databaseVendor* | To use a vendor specific com.opengamma.elsql.ElSqlConfig One of: [Default] [Postgres] [HSql] [MySql] [Oracle] [SqlServer2008] [Veritca] | null | ConfigDef.Importance.MEDIUM
+| *camel.component.elsql.dataSource* | Sets the DataSource to use to communicate with the database. | null | ConfigDef.Importance.MEDIUM
+| *camel.component.elsql.resourceUri* | The resource file which contains the elsql SQL statements to use. You can specify multiple resources separated by comma. The resources are loaded on the classpath by default, you can prefix with file: to load from file system. Notice you can set this option on the component and then you do not have to configure this on the endpoint. | null | ConfigDef.Importance.MEDIUM
+| *camel.component.elsql.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 c [...]
+| *camel.component.elsql.basicPropertyBinding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+| *camel.component.elsql.elSqlConfig* | To use a specific configured ElSqlConfig. It may be better to use the databaseVendor option instead. | null | ConfigDef.Importance.MEDIUM
+|===
+
+
+// kafka-connector options: END
diff --git a/docs/modules/ROOT/pages/connectors/camel-elsql-kafka-source-connector.adoc b/docs/modules/ROOT/pages/connectors/camel-elsql-kafka-source-connector.adoc
new file mode 100644
index 0000000..9b6557f
--- /dev/null
+++ b/docs/modules/ROOT/pages/connectors/camel-elsql-kafka-source-connector.adoc
@@ -0,0 +1,77 @@
+// kafka-connector options: START
+== camel-elsql-kafka-connector source configuration
+
+When using camel-elsql-kafka-connector as source 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-elsql-kafka-connector</artifactId>
+ <version>x.x.x</version>
+ <!-- use the same version as your Camel Kafka connector version -->
+</dependency>
+----
+
+
+[width="100%",cols="2,5,^1,2",options="header"]
+|===
+| Name | Description | Default | Priority
+| *camel.source.path.elsqlName* | The name of the elsql to use (is NAMED in the elsql file) | null | ConfigDef.Importance.HIGH
+| *camel.source.path.resourceUri* | The resource file which contains the elsql SQL statements to use. You can specify multiple resources separated by comma. The resources are loaded on the classpath by default, you can prefix with file: to load from file system. Notice you can set this option on the component and then you do not have to configure this on the endpoint. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.allowNamedParameters* | Whether to allow using named parameters in the queries. | true | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.databaseVendor* | To use a vendor specific com.opengamma.elsql.ElSqlConfig One of: [Default] [Postgres] [HSql] [MySql] [Oracle] [SqlServer2008] [Veritca] | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.dataSource* | Sets the DataSource to use to communicate with the database. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.dataSourceRef* | Sets the reference to a DataSource to lookup from the registry, to use for communicating with the database. | null | ConfigDef.Importance.LOW
+| *camel.source.endpoint.outputClass* | Specify the full package and class name to use as conversion when outputType=SelectOne. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.outputHeader* | Store the query result in a header instead of the message body. By default, outputHeader == null and the query result is stored in the message body, any existing content in the message body is discarded. If outputHeader is set, the value is used as the name of the header to store the query result and the original message body is preserved. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.outputType* | Make the output of consumer or producer to SelectList as List of Map, or SelectOne as single Java object in the following way: a) If the query has only single column, then that JDBC Column object is returned. (such as SELECT COUNT( ) FROM PROJECT will return a Long object. b) If the query has more than one column, then it will return a Map of that result. c) If the outputClass is set, then it will convert the query result into an Java bean object by [...]
+| *camel.source.endpoint.separator* | The separator to use when parameter values is taken from message body (if the body is a String type), to be inserted at # placeholders. Notice if you use named parameters, then a Map type is used instead. The default value is comma | "," | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.breakBatchOnConsumeFail* | Sets whether to break batch if onConsume failed. | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.bridgeErrorHandler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.expectedUpdateCount* | Sets an expected update count to validate when using onConsume. | -1 | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.maxMessagesPerPoll* | Sets the maximum number of messages to poll | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.onConsume* | After processing each row then this query can be executed, if the Exchange was processed successfully, for example to mark the row as processed. The query can have parameter. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.onConsumeBatchComplete* | After processing the entire batch, this query can be executed to bulk update rows etc. The query cannot have parameters. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.onConsumeFailed* | After processing each row then this query can be executed, if the Exchange failed, for example to mark the row as failed. The query can have parameter. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.routeEmptyResultSet* | Sets whether empty resultset should be allowed to be sent to the next hop. Defaults to false. So the empty resultset will be filtered out. | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.sendEmptyMessageWhenIdle* | If the polling consumer did not poll any files, you can enable this option to send an empty message (no body) instead. | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.transacted* | Enables or disables transaction. If enabled then if processing an exchange failed then the consumer breaks out processing any further exchanges to cause a rollback eager. | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.useIterator* | Sets how resultset should be delivered to route. Indicates delivery as either a list or individual object. defaults to true. | true | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.exceptionHandler* | To let the consumer use a custom ExceptionHandler. Notice if the option bridgeErrorHandler is enabled then this option is not in use. By default the consumer will deal with exceptions, that will be logged at WARN or ERROR level and ignored. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.exchangePattern* | Sets the exchange pattern when the consumer creates an exchange. One of: [InOnly] [InOut] [InOptionalOut] | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.pollStrategy* | A pluggable org.apache.camel.PollingConsumerPollingStrategy allowing you to provide your custom implementation to control error handling usually occurred during the poll operation before an Exchange have been created and being routed in Camel. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.processingStrategy* | Allows to plugin to use a custom org.apache.camel.component.sql.SqlProcessingStrategy to execute queries when the consumer has processed the rows/batch. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.alwaysPopulateStatement* | If enabled then the populateStatement method from org.apache.camel.component.sql.SqlPrepareStatementStrategy is always invoked, also if there is no expected parameters to be prepared. When this is false then the populateStatement is only invoked if there is 1 or more expected parameters to be set; for example this avoids reading the message body/headers for SQL queries with no parameters. | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.basicPropertyBinding* | Whether the endpoint should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.elSqlConfig* | To use a specific configured ElSqlConfig. It may be better to use the databaseVendor option instead. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.parametersCount* | If set greater than zero, then Camel will use this count value of parameters to replace instead of querying via JDBC metadata API. This is useful if the JDBC vendor could not return correct parameters count, then user may override instead. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.placeholder* | Specifies a character that will be replaced to in SQL query. Notice, that it is simple String.replaceAll() operation and no SQL parsing is involved (quoted strings will also change). | "#" | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.prepareStatementStrategy* | Allows to plugin to use a custom org.apache.camel.component.sql.SqlPrepareStatementStrategy to control preparation of the query and prepared statement. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.synchronous* | Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.templateOptions* | Configures the Spring JdbcTemplate with the key/values from the Map | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.usePlaceholder* | Sets whether to use placeholder and replace all placeholder characters with sign in the SQL queries. | true | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.backoffErrorThreshold* | The number of subsequent error polls (failed due some error) that should happen before the backoffMultipler should kick-in. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.backoffIdleThreshold* | The number of subsequent idle polls that should happen before the backoffMultipler should kick-in. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.backoffMultiplier* | To let the scheduled polling consumer backoff if there has been a number of subsequent idles/errors in a row. The multiplier is then the number of polls that will be skipped before the next actual attempt is happening again. When this option is in use then backoffIdleThreshold and/or backoffErrorThreshold must also be configured. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.delay* | Milliseconds before the next poll. You can also specify time values using units, such as 60s (60 seconds), 5m30s (5 minutes and 30 seconds), and 1h (1 hour). | 500L | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.greedy* | If greedy is enabled, then the ScheduledPollConsumer will run immediately again, if the previous run polled 1 or more messages. | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.initialDelay* | Milliseconds before the first poll starts. You can also specify time values using units, such as 60s (60 seconds), 5m30s (5 minutes and 30 seconds), and 1h (1 hour). | 1000L | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.repeatCount* | Specifies a maximum limit of number of fires. So if you set it to 1, the scheduler will only fire once. If you set it to 5, it will only fire five times. A value of zero or negative means fire forever. | 0L | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.runLoggingLevel* | The consumer logs a start/complete log line when it polls. This option allows you to configure the logging level for that. One of: [TRACE] [DEBUG] [INFO] [WARN] [ERROR] [OFF] | "TRACE" | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.scheduledExecutorService* | Allows for configuring a custom/shared thread pool to use for the consumer. By default each consumer has its own single threaded thread pool. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.scheduler* | To use a cron scheduler from either camel-spring or camel-quartz component One of: [none] [spring] [quartz] | "none" | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.schedulerProperties* | To configure additional properties when using a custom scheduler or any of the Quartz, Spring based scheduler. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.startScheduler* | Whether the scheduler should be auto started. | true | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.timeUnit* | Time unit for initialDelay and delay options. One of: [NANOSECONDS] [MICROSECONDS] [MILLISECONDS] [SECONDS] [MINUTES] [HOURS] [DAYS] | "MILLISECONDS" | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.useFixedDelay* | Controls if fixed delay or fixed rate is used. See ScheduledExecutorService in JDK for details. | true | ConfigDef.Importance.MEDIUM
+| *camel.component.elsql.databaseVendor* | To use a vendor specific com.opengamma.elsql.ElSqlConfig One of: [Default] [Postgres] [HSql] [MySql] [Oracle] [SqlServer2008] [Veritca] | null | ConfigDef.Importance.MEDIUM
+| *camel.component.elsql.dataSource* | Sets the DataSource to use to communicate with the database. | null | ConfigDef.Importance.MEDIUM
+| *camel.component.elsql.resourceUri* | The resource file which contains the elsql SQL statements to use. You can specify multiple resources separated by comma. The resources are loaded on the classpath by default, you can prefix with file: to load from file system. Notice you can set this option on the component and then you do not have to configure this on the endpoint. | null | ConfigDef.Importance.MEDIUM
+| *camel.component.elsql.bridgeErrorHandler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | ConfigDef.Importance.MEDIUM
+| *camel.component.elsql.basicPropertyBinding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+| *camel.component.elsql.elSqlConfig* | To use a specific configured ElSqlConfig. It may be better to use the databaseVendor option instead. | null | ConfigDef.Importance.MEDIUM
+|===
+
+
+// kafka-connector options: END
diff --git a/docs/modules/ROOT/pages/connectors/camel-elytron-kafka-sink-connector.adoc b/docs/modules/ROOT/pages/connectors/camel-elytron-kafka-sink-connector.adoc
new file mode 100644
index 0000000..32b4bad
--- /dev/null
+++ b/docs/modules/ROOT/pages/connectors/camel-elytron-kafka-sink-connector.adoc
@@ -0,0 +1,52 @@
+// kafka-connector options: START
+== camel-elytron-kafka-connector source configuration
+
+When using camel-elytron-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-elytron-kafka-connector</artifactId>
+ <version>x.x.x</version>
+ <!-- use the same version as your Camel Kafka connector version -->
+</dependency>
+----
+
+
+[width="100%",cols="2,5,^1,2",options="header"]
+|===
+| Name | Description | Default | Priority
+| *camel.sink.path.httpURI* | The url of the HTTP endpoint to use. | null | ConfigDef.Importance.HIGH
+| *camel.sink.endpoint.allowedRoles* | Comma separated list of allowed roles. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.useStreaming* | For HTTP endpoint: if true, text and binary messages will be wrapped as java.io.InputStream before they are passed to an Exchange; otherwise they will be passed as byte. For WebSocket endpoint: if true, text and binary messages will be wrapped as java.io.Reader and java.io.InputStream respectively before they are passed to an Exchange; otherwise they will be passed as String and byte respectively. | false | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.cookieHandler* | Configure a cookie handler to maintain a HTTP session | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.keepAlive* | Setting to ensure socket is not closed due to inactivity | "true" | ConfigDef.Importance.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 cre [...]
+| *camel.sink.endpoint.options* | Sets additional channel options. The options that can be used are defined in org.xnio.Options. To configure from endpoint uri, then prefix each option with option., such as option.close-abort=true&option.send-buffer=8192 | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.preserveHostHeader* | If the option is true, UndertowProducer will set the Host header to the value contained in the current exchange Host header, useful in reverse proxy applications where you want the Host header received by the downstream server to reflect the URL called by the upstream client, this allows applications which use the Host header to generate accurate URL's for a proxied service. | true | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.reuseAddresses* | Setting to facilitate socket multiplexing | "true" | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.tcpNoDelay* | Setting to improve TCP protocol performance | "true" | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.throwExceptionOnFailure* | Option to disable throwing the HttpOperationFailedException in case of failed responses from the remote server. This allows you to get all responses regardless of the HTTP status code. | "true" | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.transferException* | If enabled and an Exchange failed processing on the consumer side and if the caused Exception was send back serialized in the response as a application/x-java-serialized-object content type. On the producer side the exception will be deserialized and thrown as is instead of the HttpOperationFailedException. The caused exception is required to be serialized. This is by default turned off. If you enable this then be aware that Java will deseriali [...]
+| *camel.sink.endpoint.accessLogReceiver* | Which Undertow AccessLogReciever should be used Will use JBossLoggingAccessLogReceiver if not specifid | null | ConfigDef.Importance.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 | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.headerFilterStrategy* | To use a custom HeaderFilterStrategy to filter header to and from Camel message. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.synchronous* | Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). | false | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.undertowHttpBinding* | To use a custom UndertowHttpBinding to control the mapping between Camel message and undertow. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.sendTimeout* | Timeout in milliseconds when sending to a websocket channel. The default timeout is 30000 (30 seconds). | "30000" | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.sendToAll* | To send to all websocket subscribers. Can be used to configure on endpoint level, instead of having to use the UndertowConstants.SEND_TO_ALL header on the message. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.sslContextParameters* | To configure security using SSLContextParameters | null | ConfigDef.Importance.MEDIUM
+| *camel.component.elytron.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 [...]
+| *camel.component.elytron.basicPropertyBinding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+| *camel.component.elytron.elytronProvider* | Elytron security provider, has to support mechanism from parameter mechanismName. | "instance of WildFlyElytronHttpBearerProvider" | ConfigDef.Importance.MEDIUM
+| *camel.component.elytron.hostOptions* | To configure common options, such as thread pools | null | ConfigDef.Importance.MEDIUM
+| *camel.component.elytron.mechanismName* | Name of the mechanism, which will be used for selection of authentication mechanism. | "BEARER_TOKEN" | ConfigDef.Importance.MEDIUM
+| *camel.component.elytron.securityDomainBuilder* | Definition of Builder, which will be used for creation of security domain. | null | ConfigDef.Importance.HIGH
+| *camel.component.elytron.undertowHttpBinding* | To use a custom HttpBinding to control the mapping between Camel message and HttpClient. | null | ConfigDef.Importance.MEDIUM
+| *camel.component.elytron.sslContextParameters* | To configure security using SSLContextParameters | null | ConfigDef.Importance.MEDIUM
+| *camel.component.elytron.useGlobalSslContextParameters* | Enable usage of global SSL context parameters. | false | ConfigDef.Importance.MEDIUM
+|===
+
+
+// kafka-connector options: END
diff --git a/docs/modules/ROOT/pages/connectors/camel-elytron-kafka-source-connector.adoc b/docs/modules/ROOT/pages/connectors/camel-elytron-kafka-source-connector.adoc
new file mode 100644
index 0000000..efb826f
--- /dev/null
+++ b/docs/modules/ROOT/pages/connectors/camel-elytron-kafka-source-connector.adoc
@@ -0,0 +1,52 @@
+// kafka-connector options: START
+== camel-elytron-kafka-connector source configuration
+
+When using camel-elytron-kafka-connector as source 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-elytron-kafka-connector</artifactId>
+ <version>x.x.x</version>
+ <!-- use the same version as your Camel Kafka connector version -->
+</dependency>
+----
+
+
+[width="100%",cols="2,5,^1,2",options="header"]
+|===
+| Name | Description | Default | Priority
+| *camel.source.path.httpURI* | The url of the HTTP endpoint to use. | null | ConfigDef.Importance.HIGH
+| *camel.source.endpoint.allowedRoles* | Comma separated list of allowed roles. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.useStreaming* | For HTTP endpoint: if true, text and binary messages will be wrapped as java.io.InputStream before they are passed to an Exchange; otherwise they will be passed as byte. For WebSocket endpoint: if true, text and binary messages will be wrapped as java.io.Reader and java.io.InputStream respectively before they are passed to an Exchange; otherwise they will be passed as String and byte respectively. | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.accessLog* | Whether or not the consumer should write access log | "false" | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.bridgeErrorHandler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.httpMethodRestrict* | Used to only allow consuming if the HttpMethod matches, such as GET/POST/PUT etc. Multiple methods can be specified separated by comma. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.matchOnUriPrefix* | Whether or not the consumer should try to find a target consumer by matching the URI prefix if no exact match is found. | "false" | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.muteException* | If enabled and an Exchange failed processing on the consumer side the response's body won't contain the exception's stack trace. | "false" | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.optionsEnabled* | Specifies whether to enable HTTP OPTIONS for this Servlet consumer. By default OPTIONS is turned off. | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.exceptionHandler* | To let the consumer use a custom ExceptionHandler. Notice if the option bridgeErrorHandler is enabled then this option is not in use. By default the consumer will deal with exceptions, that will be logged at WARN or ERROR level and ignored. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.exchangePattern* | Sets the exchange pattern when the consumer creates an exchange. One of: [InOnly] [InOut] [InOptionalOut] | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.handlers* | Specifies a comma-delimited set of io.undertow.server.HttpHandler instances to lookup in your Registry. These handlers are added to the Undertow handler chain (for example, to add security). Important: You can not use different handlers with different Undertow endpoints using the same port number. The handlers is associated to the port number. If you need different handlers, then use different port numbers. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.accessLogReceiver* | Which Undertow AccessLogReciever should be used Will use JBossLoggingAccessLogReceiver if not specifid | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.basicPropertyBinding* | Whether the endpoint should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.headerFilterStrategy* | To use a custom HeaderFilterStrategy to filter header to and from Camel message. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.synchronous* | Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.undertowHttpBinding* | To use a custom UndertowHttpBinding to control the mapping between Camel message and undertow. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.fireWebSocketChannelEvents* | if true, the consumer will post notifications to the route when a new WebSocket peer connects, disconnects, etc. See UndertowConstants.EVENT_TYPE and EventType. | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.sslContextParameters* | To configure security using SSLContextParameters | null | ConfigDef.Importance.MEDIUM
+| *camel.component.elytron.bridgeErrorHandler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | ConfigDef.Importance.MEDIUM
+| *camel.component.elytron.muteException* | If enabled and an Exchange failed processing on the consumer side the response's body won't contain the exception's stack trace. | false | ConfigDef.Importance.MEDIUM
+| *camel.component.elytron.basicPropertyBinding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+| *camel.component.elytron.elytronProvider* | Elytron security provider, has to support mechanism from parameter mechanismName. | "instance of WildFlyElytronHttpBearerProvider" | ConfigDef.Importance.MEDIUM
+| *camel.component.elytron.hostOptions* | To configure common options, such as thread pools | null | ConfigDef.Importance.MEDIUM
+| *camel.component.elytron.mechanismName* | Name of the mechanism, which will be used for selection of authentication mechanism. | "BEARER_TOKEN" | ConfigDef.Importance.MEDIUM
+| *camel.component.elytron.securityDomainBuilder* | Definition of Builder, which will be used for creation of security domain. | null | ConfigDef.Importance.HIGH
+| *camel.component.elytron.undertowHttpBinding* | To use a custom HttpBinding to control the mapping between Camel message and HttpClient. | null | ConfigDef.Importance.MEDIUM
+| *camel.component.elytron.sslContextParameters* | To configure security using SSLContextParameters | null | ConfigDef.Importance.MEDIUM
+| *camel.component.elytron.useGlobalSslContextParameters* | Enable usage of global SSL context parameters. | false | ConfigDef.Importance.MEDIUM
+|===
+
+
+// kafka-connector options: END
diff --git a/docs/modules/ROOT/pages/connectors/camel-etcd-keys-kafka-sink-connector.adoc b/docs/modules/ROOT/pages/connectors/camel-etcd-keys-kafka-sink-connector.adoc
new file mode 100644
index 0000000..197e702
--- /dev/null
+++ b/docs/modules/ROOT/pages/connectors/camel-etcd-keys-kafka-sink-connector.adoc
@@ -0,0 +1,43 @@
+// kafka-connector options: START
+== camel-etcd-keys-kafka-connector source configuration
+
+When using camel-etcd-keys-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-etcd-keys-kafka-connector</artifactId>
+ <version>x.x.x</version>
+ <!-- use the same version as your Camel Kafka connector version -->
+</dependency>
+----
+
+
+[width="100%",cols="2,5,^1,2",options="header"]
+|===
+| Name | Description | Default | Priority
+| *camel.sink.path.path* | The path the endpoint refers to | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.recursive* | To apply an action recursively. | false | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.servicePath* | The path to look for for service discovery | "/services/" | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.timeout* | To set the maximum time an action could take to complete. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.uris* | To set the URIs the client connects. | "http://localhost:2379,http://localhost:4001" | ConfigDef.Importance.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 cre [...]
+| *camel.sink.endpoint.timeToLive* | To set the lifespan of a key in milliseconds. | null | ConfigDef.Importance.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 | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.synchronous* | Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). | false | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.password* | The password to use for basic authentication. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.sslContextParameters* | To configure security using SSLContextParameters. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.userName* | The user name to use for basic authentication. | null | ConfigDef.Importance.MEDIUM
+| *camel.component.etcd-keys.configuration* | Sets the common configuration shared among endpoints | null | ConfigDef.Importance.MEDIUM
+| *camel.component.etcd-keys.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 th [...]
+| *camel.component.etcd-keys.password* | The password to use for basic authentication. | null | ConfigDef.Importance.MEDIUM
+| *camel.component.etcd-keys.sslContextParameters* | To configure security using SSLContextParameters. | null | ConfigDef.Importance.MEDIUM
+| *camel.component.etcd-keys.uris* | To set the URIs the client connects. | null | ConfigDef.Importance.MEDIUM
+| *camel.component.etcd-keys.userName* | The user name to use for basic authentication. | null | ConfigDef.Importance.MEDIUM
+| *camel.component.etcd-keys.basicPropertyBinding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+| *camel.component.etcd-keys.useGlobalSslContextParameters* | Enable usage of global SSL context parameters. | false | ConfigDef.Importance.MEDIUM
+|===
+
+
+// kafka-connector options: END
diff --git a/docs/modules/ROOT/pages/connectors/camel-etcd-stats-kafka-sink-connector.adoc b/docs/modules/ROOT/pages/connectors/camel-etcd-stats-kafka-sink-connector.adoc
new file mode 100644
index 0000000..13a328a
--- /dev/null
+++ b/docs/modules/ROOT/pages/connectors/camel-etcd-stats-kafka-sink-connector.adoc
@@ -0,0 +1,43 @@
+// kafka-connector options: START
+== camel-etcd-stats-kafka-connector source configuration
+
+When using camel-etcd-stats-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-etcd-stats-kafka-connector</artifactId>
+ <version>x.x.x</version>
+ <!-- use the same version as your Camel Kafka connector version -->
+</dependency>
+----
+
+
+[width="100%",cols="2,5,^1,2",options="header"]
+|===
+| Name | Description | Default | Priority
+| *camel.sink.path.path* | The path the endpoint refers to | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.recursive* | To apply an action recursively. | false | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.servicePath* | The path to look for for service discovery | "/services/" | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.timeout* | To set the maximum time an action could take to complete. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.uris* | To set the URIs the client connects. | "http://localhost:2379,http://localhost:4001" | ConfigDef.Importance.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 cre [...]
+| *camel.sink.endpoint.timeToLive* | To set the lifespan of a key in milliseconds. | null | ConfigDef.Importance.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 | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.synchronous* | Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). | false | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.password* | The password to use for basic authentication. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.sslContextParameters* | To configure security using SSLContextParameters. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.userName* | The user name to use for basic authentication. | null | ConfigDef.Importance.MEDIUM
+| *camel.component.etcd-stats.configuration* | Sets the common configuration shared among endpoints | null | ConfigDef.Importance.MEDIUM
+| *camel.component.etcd-stats.password* | The password to use for basic authentication. | null | ConfigDef.Importance.MEDIUM
+| *camel.component.etcd-stats.sslContextParameters* | To configure security using SSLContextParameters. | null | ConfigDef.Importance.MEDIUM
+| *camel.component.etcd-stats.uris* | To set the URIs the client connects. | null | ConfigDef.Importance.MEDIUM
+| *camel.component.etcd-stats.userName* | The user name to use for basic authentication. | null | ConfigDef.Importance.MEDIUM
+| *camel.component.etcd-stats.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 t [...]
+| *camel.component.etcd-stats.basicPropertyBinding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+| *camel.component.etcd-stats.useGlobalSslContextParameters* | Enable usage of global SSL context parameters. | false | ConfigDef.Importance.MEDIUM
+|===
+
+
+// kafka-connector options: END
diff --git a/docs/modules/ROOT/pages/connectors/camel-etcd-stats-kafka-source-connector.adoc b/docs/modules/ROOT/pages/connectors/camel-etcd-stats-kafka-source-connector.adoc
new file mode 100644
index 0000000..2730f0c
--- /dev/null
+++ b/docs/modules/ROOT/pages/connectors/camel-etcd-stats-kafka-source-connector.adoc
@@ -0,0 +1,62 @@
+// kafka-connector options: START
+== camel-etcd-stats-kafka-connector source configuration
+
+When using camel-etcd-stats-kafka-connector as source 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-etcd-stats-kafka-connector</artifactId>
+ <version>x.x.x</version>
+ <!-- use the same version as your Camel Kafka connector version -->
+</dependency>
+----
+
+
+[width="100%",cols="2,5,^1,2",options="header"]
+|===
+| Name | Description | Default | Priority
+| *camel.source.path.path* | The path the endpoint refers to | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.recursive* | To apply an action recursively. | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.servicePath* | The path to look for for service discovery | "/services/" | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.timeout* | To set the maximum time an action could take to complete. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.uris* | To set the URIs the client connects. | "http://localhost:2379,http://localhost:4001" | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.bridgeErrorHandler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.sendEmptyExchangeOnTimeout* | To send an empty message in case of timeout watching for a key. | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.sendEmptyMessageWhenIdle* | If the polling consumer did not poll any files, you can enable this option to send an empty message (no body) instead. | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.exceptionHandler* | To let the consumer use a custom ExceptionHandler. Notice if the option bridgeErrorHandler is enabled then this option is not in use. By default the consumer will deal with exceptions, that will be logged at WARN or ERROR level and ignored. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.exchangePattern* | Sets the exchange pattern when the consumer creates an exchange. One of: [InOnly] [InOut] [InOptionalOut] | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.fromIndex* | The index to watch from | 0L | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.pollStrategy* | A pluggable org.apache.camel.PollingConsumerPollingStrategy allowing you to provide your custom implementation to control error handling usually occurred during the poll operation before an Exchange have been created and being routed in Camel. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.basicPropertyBinding* | Whether the endpoint should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.synchronous* | Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.backoffErrorThreshold* | The number of subsequent error polls (failed due some error) that should happen before the backoffMultipler should kick-in. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.backoffIdleThreshold* | The number of subsequent idle polls that should happen before the backoffMultipler should kick-in. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.backoffMultiplier* | To let the scheduled polling consumer backoff if there has been a number of subsequent idles/errors in a row. The multiplier is then the number of polls that will be skipped before the next actual attempt is happening again. When this option is in use then backoffIdleThreshold and/or backoffErrorThreshold must also be configured. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.delay* | Milliseconds before the next poll. You can also specify time values using units, such as 60s (60 seconds), 5m30s (5 minutes and 30 seconds), and 1h (1 hour). | 500L | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.greedy* | If greedy is enabled, then the ScheduledPollConsumer will run immediately again, if the previous run polled 1 or more messages. | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.initialDelay* | Milliseconds before the first poll starts. You can also specify time values using units, such as 60s (60 seconds), 5m30s (5 minutes and 30 seconds), and 1h (1 hour). | 1000L | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.repeatCount* | Specifies a maximum limit of number of fires. So if you set it to 1, the scheduler will only fire once. If you set it to 5, it will only fire five times. A value of zero or negative means fire forever. | 0L | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.runLoggingLevel* | The consumer logs a start/complete log line when it polls. This option allows you to configure the logging level for that. One of: [TRACE] [DEBUG] [INFO] [WARN] [ERROR] [OFF] | "TRACE" | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.scheduledExecutorService* | Allows for configuring a custom/shared thread pool to use for the consumer. By default each consumer has its own single threaded thread pool. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.scheduler* | To use a cron scheduler from either camel-spring or camel-quartz component One of: [none] [spring] [quartz] | "none" | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.schedulerProperties* | To configure additional properties when using a custom scheduler or any of the Quartz, Spring based scheduler. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.startScheduler* | Whether the scheduler should be auto started. | true | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.timeUnit* | Time unit for initialDelay and delay options. One of: [NANOSECONDS] [MICROSECONDS] [MILLISECONDS] [SECONDS] [MINUTES] [HOURS] [DAYS] | "MILLISECONDS" | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.useFixedDelay* | Controls if fixed delay or fixed rate is used. See ScheduledExecutorService in JDK for details. | true | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.password* | The password to use for basic authentication. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.sslContextParameters* | To configure security using SSLContextParameters. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.userName* | The user name to use for basic authentication. | null | ConfigDef.Importance.MEDIUM
+| *camel.component.etcd-stats.configuration* | Sets the common configuration shared among endpoints | null | ConfigDef.Importance.MEDIUM
+| *camel.component.etcd-stats.password* | The password to use for basic authentication. | null | ConfigDef.Importance.MEDIUM
+| *camel.component.etcd-stats.sslContextParameters* | To configure security using SSLContextParameters. | null | ConfigDef.Importance.MEDIUM
+| *camel.component.etcd-stats.uris* | To set the URIs the client connects. | null | ConfigDef.Importance.MEDIUM
+| *camel.component.etcd-stats.userName* | The user name to use for basic authentication. | null | ConfigDef.Importance.MEDIUM
+| *camel.component.etcd-stats.bridgeErrorHandler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | ConfigDef.Importance.MEDIUM
+| *camel.component.etcd-stats.basicPropertyBinding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+| *camel.component.etcd-stats.useGlobalSslContextParameters* | Enable usage of global SSL context parameters. | false | ConfigDef.Importance.MEDIUM
+|===
+
+
+// kafka-connector options: END
diff --git a/docs/modules/ROOT/pages/connectors/camel-etcd-watch-kafka-source-connector.adoc b/docs/modules/ROOT/pages/connectors/camel-etcd-watch-kafka-source-connector.adoc
new file mode 100644
index 0000000..f3dd598
--- /dev/null
+++ b/docs/modules/ROOT/pages/connectors/camel-etcd-watch-kafka-source-connector.adoc
@@ -0,0 +1,46 @@
+// kafka-connector options: START
+== camel-etcd-watch-kafka-connector source configuration
+
+When using camel-etcd-watch-kafka-connector as source 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-etcd-watch-kafka-connector</artifactId>
+ <version>x.x.x</version>
+ <!-- use the same version as your Camel Kafka connector version -->
+</dependency>
+----
+
+
+[width="100%",cols="2,5,^1,2",options="header"]
+|===
+| Name | Description | Default | Priority
+| *camel.source.path.path* | The path the endpoint refers to | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.bridgeErrorHandler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.recursive* | To apply an action recursively. | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.servicePath* | The path to look for for service discovery | "/services/" | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.uris* | To set the URIs the client connects. | "http://localhost:2379,http://localhost:4001" | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.sendEmptyExchangeOnTimeout* | To send an empty message in case of timeout watching for a key. | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.timeout* | To set the maximum time an action could take to complete. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.exceptionHandler* | To let the consumer use a custom ExceptionHandler. Notice if the option bridgeErrorHandler is enabled then this option is not in use. By default the consumer will deal with exceptions, that will be logged at WARN or ERROR level and ignored. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.exchangePattern* | Sets the exchange pattern when the consumer creates an exchange. One of: [InOnly] [InOut] [InOptionalOut] | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.fromIndex* | The index to watch from | 0L | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.basicPropertyBinding* | Whether the endpoint should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.synchronous* | Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.password* | The password to use for basic authentication. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.sslContextParameters* | To configure security using SSLContextParameters. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.userName* | The user name to use for basic authentication. | null | ConfigDef.Importance.MEDIUM
+| *camel.component.etcd-watch.bridgeErrorHandler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | ConfigDef.Importance.MEDIUM
+| *camel.component.etcd-watch.configuration* | Sets the common configuration shared among endpoints | null | ConfigDef.Importance.MEDIUM
+| *camel.component.etcd-watch.password* | The password to use for basic authentication. | null | ConfigDef.Importance.MEDIUM
+| *camel.component.etcd-watch.sslContextParameters* | To configure security using SSLContextParameters. | null | ConfigDef.Importance.MEDIUM
+| *camel.component.etcd-watch.uris* | To set the URIs the client connects. | null | ConfigDef.Importance.MEDIUM
+| *camel.component.etcd-watch.userName* | The user name to use for basic authentication. | null | ConfigDef.Importance.MEDIUM
+| *camel.component.etcd-watch.basicPropertyBinding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+| *camel.component.etcd-watch.useGlobalSslContextParameters* | Enable usage of global SSL context parameters. | false | ConfigDef.Importance.MEDIUM
+|===
+
+
+// kafka-connector options: END
diff --git a/docs/modules/ROOT/pages/connectors/camel-eventadmin-kafka-sink-connector.adoc b/docs/modules/ROOT/pages/connectors/camel-eventadmin-kafka-sink-connector.adoc
new file mode 100644
index 0000000..9ed86e7
--- /dev/null
+++ b/docs/modules/ROOT/pages/connectors/camel-eventadmin-kafka-sink-connector.adoc
@@ -0,0 +1,31 @@
+// kafka-connector options: START
+== camel-eventadmin-kafka-connector source configuration
+
+When using camel-eventadmin-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-eventadmin-kafka-connector</artifactId>
+ <version>x.x.x</version>
+ <!-- use the same version as your Camel Kafka connector version -->
+</dependency>
+----
+
+
+[width="100%",cols="2,5,^1,2",options="header"]
+|===
+| Name | Description | Default | Priority
+| *camel.sink.path.topic* | Name of topic to listen or send to | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.send* | Whether to use 'send' or 'synchronous' deliver. Default false (async delivery) | false | ConfigDef.Importance.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 cre [...]
+| *camel.sink.endpoint.basicPropertyBinding* | Whether the endpoint should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.synchronous* | Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). | false | ConfigDef.Importance.MEDIUM
+| *camel.component.eventadmin.bundleContext* | The OSGi BundleContext is automatic injected by Camel | null | ConfigDef.Importance.MEDIUM
+| *camel.component.eventadmin.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 t [...]
+| *camel.component.eventadmin.basicPropertyBinding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+|===
+
+
+// kafka-connector options: END
diff --git a/docs/modules/ROOT/pages/connectors/camel-eventadmin-kafka-source-connector.adoc b/docs/modules/ROOT/pages/connectors/camel-eventadmin-kafka-source-connector.adoc
new file mode 100644
index 0000000..c19d5d7
--- /dev/null
+++ b/docs/modules/ROOT/pages/connectors/camel-eventadmin-kafka-source-connector.adoc
@@ -0,0 +1,33 @@
+// kafka-connector options: START
+== camel-eventadmin-kafka-connector source configuration
+
+When using camel-eventadmin-kafka-connector as source 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-eventadmin-kafka-connector</artifactId>
+ <version>x.x.x</version>
+ <!-- use the same version as your Camel Kafka connector version -->
+</dependency>
+----
+
+
+[width="100%",cols="2,5,^1,2",options="header"]
+|===
+| Name | Description | Default | Priority
+| *camel.source.path.topic* | Name of topic to listen or send to | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.send* | Whether to use 'send' or 'synchronous' deliver. Default false (async delivery) | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.bridgeErrorHandler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.exceptionHandler* | To let the consumer use a custom ExceptionHandler. Notice if the option bridgeErrorHandler is enabled then this option is not in use. By default the consumer will deal with exceptions, that will be logged at WARN or ERROR level and ignored. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.exchangePattern* | Sets the exchange pattern when the consumer creates an exchange. One of: [InOnly] [InOut] [InOptionalOut] | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.basicPropertyBinding* | Whether the endpoint should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.synchronous* | Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). | false | ConfigDef.Importance.MEDIUM
+| *camel.component.eventadmin.bundleContext* | The OSGi BundleContext is automatic injected by Camel | null | ConfigDef.Importance.MEDIUM
+| *camel.component.eventadmin.bridgeErrorHandler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | ConfigDef.Importance.MEDIUM
+| *camel.component.eventadmin.basicPropertyBinding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+|===
+
+
+// kafka-connector options: END
diff --git a/docs/modules/ROOT/pages/connectors/camel-exec-kafka-sink-connector.adoc b/docs/modules/ROOT/pages/connectors/camel-exec-kafka-sink-connector.adoc
new file mode 100644
index 0000000..e07670c
--- /dev/null
+++ b/docs/modules/ROOT/pages/connectors/camel-exec-kafka-sink-connector.adoc
@@ -0,0 +1,37 @@
+// kafka-connector options: START
+== camel-exec-kafka-connector source configuration
+
+When using camel-exec-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-exec-kafka-connector</artifactId>
+ <version>x.x.x</version>
+ <!-- use the same version as your Camel Kafka connector version -->
+</dependency>
+----
+
+
+[width="100%",cols="2,5,^1,2",options="header"]
+|===
+| Name | Description | Default | Priority
+| *camel.sink.path.executable* | Sets the executable to be executed. The executable must not be empty or null. | null | ConfigDef.Importance.HIGH
+| *camel.sink.endpoint.args* | The arguments may be one or many whitespace-separated tokens. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.binding* | A reference to a org.apache.commons.exec.ExecBinding in the Registry. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.commandExecutor* | A reference to a org.apache.commons.exec.ExecCommandExecutor in the Registry that customizes the command execution. The default command executor utilizes the commons-exec library, which adds a shutdown hook for every executed command. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.commandLogLevel* | Logging level to be used for commands during execution. The default value is DEBUG. Possible values are TRACE, DEBUG, INFO, WARN, ERROR or OFF. (Values of ExecCommandLogLevelType enum) One of: [TRACE] [DEBUG] [INFO] [WARN] [ERROR] [OFF] | "DEBUG" | ConfigDef.Importance.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 cre [...]
+| *camel.sink.endpoint.outFile* | The name of a file, created by the executable, that should be considered as its output. If no outFile is set, the standard output (stdout) of the executable will be used instead. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.timeout* | The timeout, in milliseconds, after which the executable should be terminated. If execution has not completed within the timeout, the component will send a termination request. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.useStderrOnEmptyStdout* | A boolean indicating that when stdout is empty, this component will populate the Camel Message Body with stderr. This behavior is disabled (false) by default. | false | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.workingDir* | The directory in which the command should be executed. If null, the working directory of the current process will be used. | null | ConfigDef.Importance.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 | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.synchronous* | Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). | false | ConfigDef.Importance.MEDIUM
+| *camel.component.exec.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 cr [...]
+| *camel.component.exec.basicPropertyBinding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+|===
+
+
+// kafka-connector options: END
diff --git a/docs/modules/ROOT/pages/connectors/camel-facebook-kafka-sink-connector.adoc b/docs/modules/ROOT/pages/connectors/camel-facebook-kafka-sink-connector.adoc
new file mode 100644
index 0000000..73098ff
--- /dev/null
+++ b/docs/modules/ROOT/pages/connectors/camel-facebook-kafka-sink-connector.adoc
@@ -0,0 +1,128 @@
+// kafka-connector options: START
+== camel-facebook-kafka-connector source configuration
+
+When using camel-facebook-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-facebook-kafka-connector</artifactId>
+ <version>x.x.x</version>
+ <!-- use the same version as your Camel Kafka connector version -->
+</dependency>
+----
+
+
+[width="100%",cols="2,5,^1,2",options="header"]
+|===
+| Name | Description | Default | Priority
+| *camel.sink.path.methodName* | What operation to perform | null | ConfigDef.Importance.HIGH
+| *camel.sink.endpoint.achievementURL* | The unique URL of the achievement | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.albumId* | The album ID | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.albumUpdate* | The facebook Album to be created or updated | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.appId* | The ID of the Facebook Application | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.center* | Location latitude and longitude | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.checkinId* | The checkin ID | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.checkinUpdate* | The checkin to be created. Deprecated, instead create a Post with an attached location | null | ConfigDef.Importance.LOW
+| *camel.sink.endpoint.clientURL* | Facebook4J API client URL | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.clientVersion* | Facebook4J client API version | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.commentId* | The comment ID | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.commentUpdate* | The facebook Comment to be created or updated | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.debugEnabled* | Enables deubg output. Effective only with the embedded logger | "false" | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.description* | The description text | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.distance* | Distance in meters | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.domainId* | The domain ID | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.domainName* | The domain name | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.domainNames* | The domain names | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.eventId* | The event ID | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.eventUpdate* | The event to be created or updated | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.friendId* | The friend ID | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.friendlistId* | The friend list ID | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.friendlistName* | The friend list Name | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.friendUserId* | The friend user ID | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.groupId* | The group ID | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.gzipEnabled* | Use Facebook GZIP encoding | "true" | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.httpConnectionTimeout* | Http connection timeout in milliseconds | "20000" | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.httpDefaultMaxPerRoute* | HTTP maximum connections per route | "2" | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.httpMaxTotalConnections* | HTTP maximum total connections | "20" | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.httpReadTimeout* | Http read timeout in milliseconds | "120000" | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.httpRetryCount* | Number of HTTP retries | "0" | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.httpRetryIntervalSeconds* | HTTP retry interval in seconds | "5" | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.httpStreamingReadTimeout* | HTTP streaming read timeout in milliseconds | "40000" | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.ids* | The ids of users | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.inBody* | Sets the name of a parameter to be passed in the exchange In Body | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.includeRead* | Enables notifications that the user has already read in addition to unread ones | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.isHidden* | Whether hidden | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.jsonStoreEnabled* | If set to true, raw JSON forms will be stored in DataObjectFactory | "false" | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.link* | Link URL | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.linkId* | Link ID | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.locale* | Desired FQL locale | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.mbeanEnabled* | If set to true, Facebook4J mbean will be registerd | "false" | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.message* | The message text | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.messageId* | The message ID | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.metric* | The metric name | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.milestoneId* | The milestone id | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.name* | Test user name, must be of the form 'first last' | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.noteId* | The note ID | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.notificationId* | The notification ID | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.objectId* | The insight object ID | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.offerId* | The offer id | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.optionDescription* | The question's answer option description | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.pageId* | The page id | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.permissionName* | The permission name | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.permissions* | Test user permissions in the format perm1,perm2,... | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.photoId* | The photo ID | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.pictureId* | The picture id | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.pictureId2* | The picture2 id | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.pictureSize* | The picture size One of: [square] [small] [normal] [large] [thumbnail] [album] | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.placeId* | The place ID | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.postId* | The post ID | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.postUpdate* | The post to create or update | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.prettyDebugEnabled* | Prettify JSON debug output if set to true | "false" | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.queries* | FQL queries | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.query* | FQL query or search terms for search endpoints | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.questionId* | The question id | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.reading* | Optional reading parameters. See Reading Options(#reading) | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.readingOptions* | To configure Reading using key/value pairs from the Map. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.restBaseURL* | API base URL | "https://graph.facebook.com/" | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.scoreValue* | The numeric score with value | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.size* | The picture size, one of large, normal, small or square One of: [square] [small] [normal] [large] [thumbnail] [album] | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.source* | The media content from either a java.io.File or java.io.Inputstream | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.subject* | The note of the subject | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.tabId* | The tab id | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.tagUpdate* | Photo tag information | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.testUser1* | Test user 1 | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.testUser2* | Test user 2 | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.testUserId* | The ID of the test user | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.title* | The title text | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.toUserId* | The ID of the user to tag | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.toUserIds* | The IDs of the users to tag | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.userId* | The Facebook user ID | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.userId1* | The ID of a user 1 | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.userId2* | The ID of a user 2 | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.userIds* | The IDs of users to invite to event | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.userLocale* | The test user locale | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.useSSL* | Use SSL | "true" | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.videoBaseURL* | Video API base URL | "https://graph-video.facebook.com/" | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.videoId* | The video ID | null | ConfigDef.Importance.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 cre [...]
+| *camel.sink.endpoint.basicPropertyBinding* | Whether the endpoint should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.synchronous* | Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). | false | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.httpProxyHost* | HTTP proxy server host name | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.httpProxyPassword* | HTTP proxy server password | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.httpProxyPort* | HTTP proxy server port | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.httpProxyUser* | HTTP proxy server user name | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.oAuthAccessToken* | The user access token | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.oAuthAccessTokenURL* | OAuth access token URL | "https://graph.facebook.com/oauth/access_token" | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.oAuthAppId* | The application Id | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.oAuthAppSecret* | The application Secret | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.oAuthAuthorizationURL* | OAuth authorization URL | "https://www.facebook.com/dialog/oauth" | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.oAuthPermissions* | Default OAuth permissions. Comma separated permission names. See \https://developers.facebook.com/docs/reference/login/#permissions for the detail | null | ConfigDef.Importance.MEDIUM
+| *camel.component.facebook.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 the [...]
+| *camel.component.facebook.basicPropertyBinding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+| *camel.component.facebook.configuration* | To use the shared configuration | null | ConfigDef.Importance.MEDIUM
+|===
+
+
+// kafka-connector options: END
diff --git a/docs/modules/ROOT/pages/connectors/camel-facebook-kafka-source-connector.adoc b/docs/modules/ROOT/pages/connectors/camel-facebook-kafka-source-connector.adoc
new file mode 100644
index 0000000..4a8b527
--- /dev/null
+++ b/docs/modules/ROOT/pages/connectors/camel-facebook-kafka-source-connector.adoc
@@ -0,0 +1,130 @@
+// kafka-connector options: START
+== camel-facebook-kafka-connector source configuration
+
+When using camel-facebook-kafka-connector as source 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-facebook-kafka-connector</artifactId>
+ <version>x.x.x</version>
+ <!-- use the same version as your Camel Kafka connector version -->
+</dependency>
+----
+
+
+[width="100%",cols="2,5,^1,2",options="header"]
+|===
+| Name | Description | Default | Priority
+| *camel.source.path.methodName* | What operation to perform | null | ConfigDef.Importance.HIGH
+| *camel.source.endpoint.achievementURL* | The unique URL of the achievement | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.albumId* | The album ID | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.albumUpdate* | The facebook Album to be created or updated | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.appId* | The ID of the Facebook Application | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.center* | Location latitude and longitude | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.checkinId* | The checkin ID | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.checkinUpdate* | The checkin to be created. Deprecated, instead create a Post with an attached location | null | ConfigDef.Importance.LOW
+| *camel.source.endpoint.clientURL* | Facebook4J API client URL | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.clientVersion* | Facebook4J client API version | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.commentId* | The comment ID | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.commentUpdate* | The facebook Comment to be created or updated | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.debugEnabled* | Enables deubg output. Effective only with the embedded logger | "false" | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.description* | The description text | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.distance* | Distance in meters | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.domainId* | The domain ID | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.domainName* | The domain name | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.domainNames* | The domain names | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.eventId* | The event ID | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.eventUpdate* | The event to be created or updated | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.friendId* | The friend ID | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.friendlistId* | The friend list ID | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.friendlistName* | The friend list Name | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.friendUserId* | The friend user ID | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.groupId* | The group ID | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.gzipEnabled* | Use Facebook GZIP encoding | "true" | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.httpConnectionTimeout* | Http connection timeout in milliseconds | "20000" | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.httpDefaultMaxPerRoute* | HTTP maximum connections per route | "2" | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.httpMaxTotalConnections* | HTTP maximum total connections | "20" | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.httpReadTimeout* | Http read timeout in milliseconds | "120000" | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.httpRetryCount* | Number of HTTP retries | "0" | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.httpRetryIntervalSeconds* | HTTP retry interval in seconds | "5" | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.httpStreamingReadTimeout* | HTTP streaming read timeout in milliseconds | "40000" | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.ids* | The ids of users | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.inBody* | Sets the name of a parameter to be passed in the exchange In Body | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.includeRead* | Enables notifications that the user has already read in addition to unread ones | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.isHidden* | Whether hidden | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.jsonStoreEnabled* | If set to true, raw JSON forms will be stored in DataObjectFactory | "false" | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.link* | Link URL | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.linkId* | Link ID | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.locale* | Desired FQL locale | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.mbeanEnabled* | If set to true, Facebook4J mbean will be registerd | "false" | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.message* | The message text | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.messageId* | The message ID | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.metric* | The metric name | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.milestoneId* | The milestone id | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.name* | Test user name, must be of the form 'first last' | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.noteId* | The note ID | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.notificationId* | The notification ID | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.objectId* | The insight object ID | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.offerId* | The offer id | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.optionDescription* | The question's answer option description | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.pageId* | The page id | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.permissionName* | The permission name | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.permissions* | Test user permissions in the format perm1,perm2,... | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.photoId* | The photo ID | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.pictureId* | The picture id | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.pictureId2* | The picture2 id | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.pictureSize* | The picture size One of: [square] [small] [normal] [large] [thumbnail] [album] | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.placeId* | The place ID | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.postId* | The post ID | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.postUpdate* | The post to create or update | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.prettyDebugEnabled* | Prettify JSON debug output if set to true | "false" | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.queries* | FQL queries | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.query* | FQL query or search terms for search endpoints | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.questionId* | The question id | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.reading* | Optional reading parameters. See Reading Options(#reading) | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.readingOptions* | To configure Reading using key/value pairs from the Map. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.restBaseURL* | API base URL | "https://graph.facebook.com/" | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.scoreValue* | The numeric score with value | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.size* | The picture size, one of large, normal, small or square One of: [square] [small] [normal] [large] [thumbnail] [album] | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.source* | The media content from either a java.io.File or java.io.Inputstream | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.subject* | The note of the subject | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.tabId* | The tab id | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.tagUpdate* | Photo tag information | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.testUser1* | Test user 1 | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.testUser2* | Test user 2 | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.testUserId* | The ID of the test user | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.title* | The title text | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.toUserId* | The ID of the user to tag | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.toUserIds* | The IDs of the users to tag | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.userId* | The Facebook user ID | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.userId1* | The ID of a user 1 | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.userId2* | The ID of a user 2 | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.userIds* | The IDs of users to invite to event | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.userLocale* | The test user locale | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.useSSL* | Use SSL | "true" | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.videoBaseURL* | Video API base URL | "https://graph-video.facebook.com/" | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.videoId* | The video ID | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.bridgeErrorHandler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.exceptionHandler* | To let the consumer use a custom ExceptionHandler. Notice if the option bridgeErrorHandler is enabled then this option is not in use. By default the consumer will deal with exceptions, that will be logged at WARN or ERROR level and ignored. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.exchangePattern* | Sets the exchange pattern when the consumer creates an exchange. One of: [InOnly] [InOut] [InOptionalOut] | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.basicPropertyBinding* | Whether the endpoint should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.synchronous* | Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.httpProxyHost* | HTTP proxy server host name | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.httpProxyPassword* | HTTP proxy server password | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.httpProxyPort* | HTTP proxy server port | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.httpProxyUser* | HTTP proxy server user name | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.oAuthAccessToken* | The user access token | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.oAuthAccessTokenURL* | OAuth access token URL | "https://graph.facebook.com/oauth/access_token" | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.oAuthAppId* | The application Id | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.oAuthAppSecret* | The application Secret | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.oAuthAuthorizationURL* | OAuth authorization URL | "https://www.facebook.com/dialog/oauth" | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.oAuthPermissions* | Default OAuth permissions. Comma separated permission names. See \https://developers.facebook.com/docs/reference/login/#permissions for the detail | null | ConfigDef.Importance.MEDIUM
+| *camel.component.facebook.bridgeErrorHandler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | ConfigDef.Importance.MEDIUM
+| *camel.component.facebook.basicPropertyBinding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+| *camel.component.facebook.configuration* | To use the shared configuration | null | ConfigDef.Importance.MEDIUM
+|===
+
+
+// kafka-connector options: END
diff --git a/docs/modules/ROOT/pages/connectors/camel-fhir-kafka-sink-connector.adoc b/docs/modules/ROOT/pages/connectors/camel-fhir-kafka-sink-connector.adoc
new file mode 100644
index 0000000..00cfeec
--- /dev/null
+++ b/docs/modules/ROOT/pages/connectors/camel-fhir-kafka-sink-connector.adoc
@@ -0,0 +1,55 @@
+// kafka-connector options: START
+== camel-fhir-kafka-connector source configuration
+
+When using camel-fhir-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-fhir-kafka-connector</artifactId>
+ <version>x.x.x</version>
+ <!-- use the same version as your Camel Kafka connector version -->
+</dependency>
+----
+
+
+[width="100%",cols="2,5,^1,2",options="header"]
+|===
+| Name | Description | Default | Priority
+| *camel.sink.path.apiName* | What kind of operation to perform One of: [capabilities] [create] [delete] [history] [load-page] [meta] [patch] [read] [search] [transaction] [update] [validate] | null | ConfigDef.Importance.HIGH
+| *camel.sink.path.methodName* | What sub operation to use for the selected operation | null | ConfigDef.Importance.HIGH
+| *camel.sink.endpoint.encoding* | Encoding to use for all request One of: [JSON] [XML] | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.fhirVersion* | The FHIR Version to use One of: [DSTU2] [DSTU2_HL7ORG] [DSTU2_1] [DSTU3] [R4] [R5] | "R4" | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.inBody* | Sets the name of a parameter to be passed in the exchange In Body | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.log* | Will log every requests and responses | false | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.prettyPrint* | Pretty print all request | false | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.serverUrl* | The FHIR server base URL | null | ConfigDef.Importance.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 cre [...]
+| *camel.sink.endpoint.basicPropertyBinding* | Whether the endpoint should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.client* | To use the custom client | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.clientFactory* | To use the custom client factory | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.compress* | Compresses outgoing (POST/PUT) contents to the GZIP format | false | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.connectionTimeout* | How long to try and establish the initial TCP connection (in ms) | "10000" | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.deferModelScanning* | When this option is set, model classes will not be scanned for children until the child list for the given type is actually accessed. | false | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.fhirContext* | FhirContext is an expensive object to create. To avoid creating multiple instances, it can be set directly. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.forceConformanceCheck* | Force conformance check | false | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.sessionCookie* | HTTP session cookie to add to every request | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.socketTimeout* | How long to block for individual read/write operations (in ms) | "10000" | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.summary* | Request that the server modify the response using the _summary param One of: [COUNT] [TEXT] [DATA] [TRUE] [FALSE] | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.synchronous* | Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). | false | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.validationMode* | When should Camel validate the FHIR Server's conformance statement One of: [NEVER] [ONCE] | "ONCE" | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.proxyHost* | The proxy host | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.proxyPassword* | The proxy password | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.proxyPort* | The proxy port | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.proxyUser* | The proxy username | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.accessToken* | OAuth access token | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.password* | Username to use for basic authentication | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.username* | Username to use for basic authentication | null | ConfigDef.Importance.MEDIUM
+| *camel.component.fhir.configuration* | To use the shared configuration | null | ConfigDef.Importance.MEDIUM
+| *camel.component.fhir.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 cr [...]
+| *camel.component.fhir.basicPropertyBinding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+|===
+
+
+// kafka-connector options: END
diff --git a/docs/modules/ROOT/pages/connectors/camel-fhir-kafka-source-connector.adoc b/docs/modules/ROOT/pages/connectors/camel-fhir-kafka-source-connector.adoc
new file mode 100644
index 0000000..a03eafe
--- /dev/null
+++ b/docs/modules/ROOT/pages/connectors/camel-fhir-kafka-source-connector.adoc
@@ -0,0 +1,73 @@
+// kafka-connector options: START
+== camel-fhir-kafka-connector source configuration
+
+When using camel-fhir-kafka-connector as source 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-fhir-kafka-connector</artifactId>
+ <version>x.x.x</version>
+ <!-- use the same version as your Camel Kafka connector version -->
+</dependency>
+----
+
+
+[width="100%",cols="2,5,^1,2",options="header"]
+|===
+| Name | Description | Default | Priority
+| *camel.source.path.apiName* | What kind of operation to perform One of: [capabilities] [create] [delete] [history] [load-page] [meta] [patch] [read] [search] [transaction] [update] [validate] | null | ConfigDef.Importance.HIGH
+| *camel.source.path.methodName* | What sub operation to use for the selected operation | null | ConfigDef.Importance.HIGH
+| *camel.source.endpoint.encoding* | Encoding to use for all request One of: [JSON] [XML] | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.fhirVersion* | The FHIR Version to use One of: [DSTU2] [DSTU2_HL7ORG] [DSTU2_1] [DSTU3] [R4] [R5] | "R4" | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.inBody* | Sets the name of a parameter to be passed in the exchange In Body | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.log* | Will log every requests and responses | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.prettyPrint* | Pretty print all request | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.serverUrl* | The FHIR server base URL | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.bridgeErrorHandler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.sendEmptyMessageWhenIdle* | If the polling consumer did not poll any files, you can enable this option to send an empty message (no body) instead. | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.exceptionHandler* | To let the consumer use a custom ExceptionHandler. Notice if the option bridgeErrorHandler is enabled then this option is not in use. By default the consumer will deal with exceptions, that will be logged at WARN or ERROR level and ignored. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.exchangePattern* | Sets the exchange pattern when the consumer creates an exchange. One of: [InOnly] [InOut] [InOptionalOut] | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.pollStrategy* | A pluggable org.apache.camel.PollingConsumerPollingStrategy allowing you to provide your custom implementation to control error handling usually occurred during the poll operation before an Exchange have been created and being routed in Camel. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.basicPropertyBinding* | Whether the endpoint should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.client* | To use the custom client | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.clientFactory* | To use the custom client factory | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.compress* | Compresses outgoing (POST/PUT) contents to the GZIP format | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.connectionTimeout* | How long to try and establish the initial TCP connection (in ms) | "10000" | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.deferModelScanning* | When this option is set, model classes will not be scanned for children until the child list for the given type is actually accessed. | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.fhirContext* | FhirContext is an expensive object to create. To avoid creating multiple instances, it can be set directly. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.forceConformanceCheck* | Force conformance check | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.sessionCookie* | HTTP session cookie to add to every request | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.socketTimeout* | How long to block for individual read/write operations (in ms) | "10000" | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.summary* | Request that the server modify the response using the _summary param One of: [COUNT] [TEXT] [DATA] [TRUE] [FALSE] | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.synchronous* | Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.validationMode* | When should Camel validate the FHIR Server's conformance statement One of: [NEVER] [ONCE] | "ONCE" | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.backoffErrorThreshold* | The number of subsequent error polls (failed due some error) that should happen before the backoffMultipler should kick-in. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.backoffIdleThreshold* | The number of subsequent idle polls that should happen before the backoffMultipler should kick-in. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.backoffMultiplier* | To let the scheduled polling consumer backoff if there has been a number of subsequent idles/errors in a row. The multiplier is then the number of polls that will be skipped before the next actual attempt is happening again. When this option is in use then backoffIdleThreshold and/or backoffErrorThreshold must also be configured. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.delay* | Milliseconds before the next poll. You can also specify time values using units, such as 60s (60 seconds), 5m30s (5 minutes and 30 seconds), and 1h (1 hour). | 500L | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.greedy* | If greedy is enabled, then the ScheduledPollConsumer will run immediately again, if the previous run polled 1 or more messages. | false | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.initialDelay* | Milliseconds before the first poll starts. You can also specify time values using units, such as 60s (60 seconds), 5m30s (5 minutes and 30 seconds), and 1h (1 hour). | 1000L | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.repeatCount* | Specifies a maximum limit of number of fires. So if you set it to 1, the scheduler will only fire once. If you set it to 5, it will only fire five times. A value of zero or negative means fire forever. | 0L | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.runLoggingLevel* | The consumer logs a start/complete log line when it polls. This option allows you to configure the logging level for that. One of: [TRACE] [DEBUG] [INFO] [WARN] [ERROR] [OFF] | "TRACE" | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.scheduledExecutorService* | Allows for configuring a custom/shared thread pool to use for the consumer. By default each consumer has its own single threaded thread pool. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.scheduler* | To use a cron scheduler from either camel-spring or camel-quartz component One of: [none] [spring] [quartz] | "none" | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.schedulerProperties* | To configure additional properties when using a custom scheduler or any of the Quartz, Spring based scheduler. | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.startScheduler* | Whether the scheduler should be auto started. | true | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.timeUnit* | Time unit for initialDelay and delay options. One of: [NANOSECONDS] [MICROSECONDS] [MILLISECONDS] [SECONDS] [MINUTES] [HOURS] [DAYS] | "MILLISECONDS" | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.useFixedDelay* | Controls if fixed delay or fixed rate is used. See ScheduledExecutorService in JDK for details. | true | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.proxyHost* | The proxy host | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.proxyPassword* | The proxy password | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.proxyPort* | The proxy port | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.proxyUser* | The proxy username | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.accessToken* | OAuth access token | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.password* | Username to use for basic authentication | null | ConfigDef.Importance.MEDIUM
+| *camel.source.endpoint.username* | Username to use for basic authentication | null | ConfigDef.Importance.MEDIUM
+| *camel.component.fhir.configuration* | To use the shared configuration | null | ConfigDef.Importance.MEDIUM
+| *camel.component.fhir.bridgeErrorHandler* | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | ConfigDef.Importance.MEDIUM
+| *camel.component.fhir.basicPropertyBinding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+|===
+
+
+// kafka-connector options: END
diff --git a/docs/modules/ROOT/pages/connectors/camel-file-kafka-sink-connector.adoc b/docs/modules/ROOT/pages/connectors/camel-file-kafka-sink-connector.adoc
new file mode 100644
index 0000000..97e474b
--- /dev/null
+++ b/docs/modules/ROOT/pages/connectors/camel-file-kafka-sink-connector.adoc
@@ -0,0 +1,50 @@
+// kafka-connector options: START
+== camel-file-kafka-connector source configuration
+
+When using camel-file-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-file-kafka-connector</artifactId>
+ <version>x.x.x</version>
+ <!-- use the same version as your Camel Kafka connector version -->
+</dependency>
+----
+
+
+[width="100%",cols="2,5,^1,2",options="header"]
+|===
+| Name | Description | Default | Priority
+| *camel.sink.path.directoryName* | The starting directory | null | ConfigDef.Importance.HIGH
+| *camel.sink.endpoint.charset* | This option is used to specify the encoding of the file. You can use this on the consumer, to specify the encodings of the files, which allow Camel to know the charset it should load the file content in case the file content is being accessed. Likewise when writing a file, you can use this option to specify which charset to write the file as well. Do mind that when writing the file Camel may have to read the message content into memory to be able to conv [...]
+| *camel.sink.endpoint.doneFileName* | Producer: If provided, then Camel will write a 2nd done file when the original file has been written. The done file will be empty. This option configures what file name to use. Either you can specify a fixed name. Or you can use dynamic placeholders. The done file will always be written in the same folder as the original file. Consumer: If provided, Camel will only consume files if a done file exists. This option configures what file name to use. Ei [...]
+| *camel.sink.endpoint.fileName* | Use Expression such as File Language to dynamically set the filename. For consumers, it's used as a filename filter. For producers, it's used to evaluate the filename to write. If an expression is set, it take precedence over the CamelFileName header. (Note: The header itself can also be an Expression). The expression options support both String and Expression types. If the expression is a String type, it is always evaluated using the File Language. If [...]
+| *camel.sink.endpoint.appendChars* | Used to append characters (text) after writing files. This can for example be used to add new lines or other separators when writing and appending to existing files. To specify new-line (slash-n or slash-r) or tab (slash-t) characters then escape with an extra slash, eg slash-slash-n. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.fileExist* | What to do if a file already exists with the same name. Override, which is the default, replaces the existing file. - Append - adds content to the existing file. - Fail - throws a GenericFileOperationException, indicating that there is already an existing file. - Ignore - silently ignores the problem and does not override the existing file, but assumes everything is okay. - Move - option requires to use the moveExisting option to be configured as well. [...]
+| *camel.sink.endpoint.flatten* | Flatten is used to flatten the file name path to strip any leading paths, so it's just the file name. This allows you to consume recursively into sub-directories, but when you eg write the files to another directory they will be written in a single directory. Setting this to true on the producer enforces that any file name in CamelFileName header will be stripped for any leading paths. | false | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.jailStartingDirectory* | Used for jailing (restricting) writing files to the starting directory (and sub) only. This is enabled by default to not allow Camel to write files to outside directories (to be more secured out of the box). You can turn this off to allow writing files to directories outside the starting directory, such as parent or root folders. | true | ConfigDef.Importance.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 cre [...]
+| *camel.sink.endpoint.moveExisting* | Expression (such as File Language) used to compute file name to use when fileExist=Move is configured. To move files into a backup subdirectory just enter backup. This option only supports the following File Language tokens: file:name, file:name.ext, file:name.noext, file:onlyname, file:onlyname.noext, file:ext, and file:parent. Notice the file:parent is not supported by the FTP component, as the FTP component can only move any existing files to a r [...]
+| *camel.sink.endpoint.tempFileName* | The same as tempPrefix option but offering a more fine grained control on the naming of the temporary filename as it uses the File Language. The location for tempFilename is relative to the final file location in the option 'fileName', not the target directory in the base uri. For example if option fileName includes a directory prefix: dir/finalFilename then tempFileName is relative to that subdirectory dir. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.tempPrefix* | This option is used to write the file using a temporary name and then, after the write is complete, rename it to the real name. Can be used to identify files being written and also avoid consumers (not using exclusive read locks) reading in progress files. Is often used by FTP when uploading big files. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.allowNullBody* | Used to specify if a null body is allowed during file writing. If set to true then an empty file will be created, when set to false, and attempting to send a null body to the file component, a GenericFileWriteException of 'Cannot write null body to file.' will be thrown. If the fileExist option is set to 'Override', then the file will be truncated, and if set to append the file will remain unchanged. | false | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.chmod* | Specify the file permissions which is sent by the producer, the chmod value must be between 000 and 777; If there is a leading digit like in 0755 we will ignore it. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.chmodDirectory* | Specify the directory permissions used when the producer creates missing directories, the chmod value must be between 000 and 777; If there is a leading digit like in 0755 we will ignore it. | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.eagerDeleteTargetFile* | Whether or not to eagerly delete any existing target file. This option only applies when you use fileExists=Override and the tempFileName option as well. You can use this to disable (set it to false) deleting the target file before the temp file is written. For example you may write big files and want the target file to exists during the temp file is being written. This ensure the target file is only deleted until the very last moment, just [...]
+| *camel.sink.endpoint.forceWrites* | Whether to force syncing writes to the file system. You can turn this off if you do not want this level of guarantee, for example if writing to logs / audit logs etc; this would yield better performance. | true | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.keepLastModified* | Will keep the last modified timestamp from the source file (if any). Will use the Exchange.FILE_LAST_MODIFIED header to located the timestamp. This header can contain either a java.util.Date or long with the timestamp. If the timestamp exists and the option is enabled it will set this timestamp on the written file. Note: This option only applies to the file producer. You cannot use this option with any of the \ftp producers. | false | ConfigDef. [...]
+| *camel.sink.endpoint.moveExistingFileStrategy* | Strategy (Custom Strategy) used to move file with special naming token to use when fileExist=Move is configured. By default, there is an implementation used if no custom strategy is provided | null | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.autoCreate* | Automatically create missing directories in the file's pathname. For the file consumer, that means creating the starting directory. For the file producer, it means the directory the files should be written to. | true | ConfigDef.Importance.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 | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.bufferSize* | Buffer size in bytes used for writing files (or in case of FTP for downloading and uploading files). | 131072 | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.copyAndDeleteOnRenameFail* | Whether to fallback and do a copy and delete file, in case the file could not be renamed directly. This option is not available for the FTP component. | true | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.renameUsingCopy* | Perform rename operations using a copy and delete strategy. This is primarily used in environments where the regular rename operation is unreliable (e.g. across different file systems or networks). This option takes precedence over the copyAndDeleteOnRenameFail parameter that will automatically fall back to the copy and delete strategy, but only after additional delays. | false | ConfigDef.Importance.MEDIUM
+| *camel.sink.endpoint.synchronous* | Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). | false | ConfigDef.Importance.MEDIUM
+| *camel.component.file.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 cr [...]
+| *camel.component.file.basicPropertyBinding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
+|===
+
+
+// kafka-connector options: END
diff --git a/docs/modules/ROOT/pages/connectors/camel-file-kafka-source-connector.adoc b/docs/modules/ROOT/pages/connectors/camel-file-kafka-source-connector.adoc
new file mode 100644
index 0000000..aac40b8
--- /dev/null
+++ b/docs/modules/ROOT/pages/connectors/camel-file-kafka-source-connector.adoc
@@ -0,0 +1,103 @@
+// kafka-connector options: START
+== camel-file-kafka-connector source configuration
+
+When using camel-file-kafka-connector as source make sure to use the following Maven dependency to have support for the connector:
+
+[source,xml]
+----
+<dependency>
+ <groupId>org.apache.camel.kafkaconnector</groupId>
... 19660 lines suppressed ...