anchor.diff:  
   endif::community[]
   
  -ifdef::product[]
  -
  -Following is an example of the configuration for a Db2 connector that connects to a Db2 server on port 50000 at 192.168.99.100, whose logical name is `fullfillment`. Typically, you configure a {prodname} Db2 connector in a `.yaml` file using the configuration properties available for the connector.
  -
  -You can choose to produce events for a subset of the schemas and tables. Optionally, ignore, mask, or truncate columns that are sensitive, too large, or not needed.
  -
  -[source,yaml,options="nowrap",subs="+attributes"]
  -----
  -apiVersion: {KafkaConnectApiVersion}
  -  kind: KafkaConnector
  -  metadata:
  -    name: inventory-connector  // <1>
  -    labels: strimzi.io/cluster: my-connect-cluster
  -  spec:
  -    class: io.debezium.connector.db2.Db2Connector
  -    tasksMax: 1  // <2>
  -    config:  // <3>
  -      database.hostname: 192.168.99.100   // <4>
  -      database.port: 50000
  -      database.user: db2inst1
  -      database.password: Password!
  -      database.dbname: mydatabase
  -      database.server.name: fullfillment   // <5>
  -      database.include.list: public.inventory   // <6>
  -----
  -
  -.Descriptions of connector configuration settings
  -[cols="1,7",options="header",subs="+attributes"]
  -|===
  -|Item |Description
  -
  -|1
  -|The name of the connector.
  -
  -|2
  -|Only one task should operate at any one time.
  -
  -|3
  -|The connector’s configuration.
  -
  -|4
  -|The database host, which is the address of the Db2 instance.
  -
  -|5
  -|The logical name of the Db2 instance/cluster, which forms a namespace and is used in the names of the Kafka topics to which the connector writes, the names of Kafka Connect schemas, and the namespaces of the corresponding Avro schema when the {link-prefix}:{link-avro-serialization}[Avro Connector] is used.
  -
  -|6
  -|Changes in only the `public.inventory` database are captured.
  -
  -|===
  -
  -endif::product[]
  -
  -See the {link-prefix}:{link-db2-connector}#db2-connector-properties[complete list of connector properties] that you can specify in these configurations.
  -
  -You can send this configuration with a `POST` command to a running Kafka Connect service. The service records the configuration and starts one connector task that connects to the Db2 database, reads change-data tables for tables in capture mode, and streams change event records to Kafka topics.
  -
  -// Type: procedure
  -// ModuleID: adding-debezium-db2-connector-configuration-to-kafka-connect
  -// Title: Adding {prodname} Db2 connector configuration to Kafka Connect
  +For the complete list of the configuration properties that you can set for the {prodname} Db2 connector, see {link-prefix}:{link-db2-connector}#db2-connector-properties[Db2 connector properties].
  +
  +ifdef::community[]
  +
  +You can send this configuration with a `POST` command to a running Kafka Connect service.
  +The service records the configuration and starts one connector task that performs the following actions:
  +
  +* Connects to the Db2 database.
  +* Reads change-data tables for tables that are in capture mode.
  +* Streams change event records to Kafka topics.
  +
   [[db2-adding-connector-configuration]]
   === Adding connector configuration
   
  -ifdef::community[]
   To start running a Db2 connector, create a connector configuration and add the configuration to your Kafka Connect cluster.
   
   .Prerequisites
   
  -* The {link-prefix}:{link-db2-connector}#setting-up-db2-to-run-a-debezium-connector[Db2 replication] is enabled to expose change-data for tables that are in capture mode
  -
  +* {link-prefix}:{link-db2-connector}#setting-up-db2[Db2 replication is enabled] to expose change data for tables that are in capture mode.
   * The Db2 connector is installed.
   
   .Procedure
  
positive.code: * For more information about capture agent parameters, see the Db2 documentation.
  
  // Type: assembly
  // ModuleID: deploying-debezium-db2-connectors
  // Title: Deploying {prodname} Db2 connectors
  [[db2-deploying-a-connector]]
  == Deployment
  
  ifdef::community[]
  
  With https://zookeeper.apache.org[Zookeeper], http://kafka.apache.org/[Kafka], and {link-kafka-docs}.html#connect[Kafka Connect] installed, the remaining tasks to deploy a {prodname} Db2 connector are:
  
  . Download the link:https://repo1.maven.org/maven2/io/debezium/debezium-connector-db2/{debezium-version}/debezium-connector-db2-{debezium-version}-plugin.tar.gz[connector's plug-in archive].
  
  . Extract the JAR files into your Kafka Connect environment.
  . Add the directory with the JAR files to {link-kafka-docs}/#connectconfigs[Kafka Connect's `plugin.path`].
  . Obtain the link:https://www.ibm.com/support/pages/db2-jdbc-driver-versions-and-downloads[JDBC driver for Db2].
  
negative.code: endif::product[]
  
  // Type: concept
  // Title: How {prodname} Db2 connectors perform database snapshots
  [[db2-snapshots]]
  === Snapshots
  