You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+41Lines changed: 41 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -155,13 +155,54 @@ The configuration options for the Kafka Connect source connector for IBM MQ are
155
155
| mq.queue | The name of the source MQ queue | string || MQ queue name |
156
156
| mq.user.name | The user name for authenticating with the queue manager | string || User name |
157
157
| mq.password | The password for authenticating with the queue manager | string || Password |
158
+
| mq.ccdt.url | The URL for the CCDT file containing MQ connection details | string || URL for obtaining a CCDT file |
158
159
| mq.record.builder | The class used to build the Kafka Connect record | string || Class implementing RecordBuilder |
159
160
| mq.message.body.jms | Whether to interpret the message body as a JMS message type | boolean | false ||
160
161
| mq.record.builder.key.header | The JMS message header to use as the Kafka record key | string || JMSMessageID, JMSCorrelationID, JMSCorrelationIDAsBytes |
161
162
| mq.ssl.cipher.suite | The name of the cipher suite for TLS (SSL) connection | string || Blank or valid cipher suite |
162
163
| mq.ssl.peer.name | The distinguished name pattern of the TLS (SSL) peer | string || Blank or DN pattern |
163
164
| topic | The name of the target Kafka topic | string || Topic name |
164
165
166
+
### Using a CCDT file
167
+
Some of the connection details for MQ can be provided in a [CCDT file](https://www.ibm.com/support/knowledgecenter/en/SSFKSJ_9.0.0/com.ibm.mq.con.doc/q016730_.htm) by setting `mq.ccdt.url` in the Kafka Connect source connector configuration file. If using a CCDT file the `mq.connection.name.list` and `mq.channel.name` configuration options are not required.
168
+
169
+
### Externalizing secrets
170
+
[KIP 297](https://cwiki.apache.org/confluence/display/KAFKA/KIP-297%3A+Externalizing+Secrets+for+Connect+Configurations) introduced a mechanism to externalize secrets to be used as configuration for Kafka connectors.
171
+
172
+
#### Example: externalizing secrets with FileConfigProvider
173
+
174
+
Given a file `secrets.properties` with the contents:
175
+
```
176
+
secret-key=password
177
+
```
178
+
179
+
Update the worker configuration file to specify the FileConfigProvider which is included by default:
180
+
181
+
```
182
+
# Additional properties for the worker configuration to enable use of ConfigProviders
183
+
# multiple comma-separated provider types can be specified here
0 commit comments