anchor.diff:  . Create a configuration for the Db2 connector.
   
   . Use the link:{link-kafka-docs}/#connect_rest[Kafka Connect REST API] to add that connector configuration to your Kafka Connect cluster.
  -
   endif::community[]
   
  -ifdef::product[]
  -You can use a provided {prodname} container to deploy a {prodname} Db2 connector. In this procedure, you build a custom Kafka Connect container image for {prodname}, configure the {prodname} connector as needed, and then add your connector configuration to your Kafka Connect environment.
  -
  -.Prerequisites
  -
  -* Podman or Docker is installed and you have sufficient rights to create and manage containers.
  -* You installed the {prodname} Db2 connector archive.
  -
  -.Procedure
  -
  -. Extract the {prodname} Db2 connector archive to create a directory structure for the connector plug-in, for example:
  -+
  -[subs=+macros]
  -----
  -pass:quotes[*tree ./my-plugins/*]
  -./my-plugins/
  -├── debezium-connector-db2
  -│   ├── ...
  -----
  -
  -. Create and publish a custom image for running your {prodname} connector:
  -
  -.. Create a new `Dockerfile` by using `{DockerKafkaConnect}` as the base image. In the following example, you would replace _my-plugins_ with the name of your plug-ins directory:
  -+
  -[subs="+macros,+attributes"]
  -----
  -FROM {DockerKafkaConnect}
  -USER root:root
  -pass:quotes[COPY _./my-plugins/_ /opt/kafka/plugins/]
  -USER 1001
  -----
  -+
  -Before Kafka Connect starts running the connector, Kafka Connect loads any third-party plug-ins that are in the `/opt/kafka/plugins` directory.
  -
  -.. Build the container image. For example, if you saved the `Dockerfile` that you created in the previous step as `debezium-container-for-db2`, and if the `Dockerfile` is in the current directory, then you would run the following command:
  -+
  -`podman build -t debezium-container-for-db2:latest .`
  -
  -.. Push your custom image to your container registry, for example:
  -+
  -`podman push debezium-container-for-db2:latest`
  -
  -.. Point to the new container image. Do one of the following:
  -+
  -* Edit the `spec.image` property of the `KafkaConnector` custom resource. If set, this property overrides the `STRIMZI_DEFAULT_KAFKA_CONNECT_IMAGE` variable in the Cluster Operator. For example:
  -+
  -[source,yaml,subs="+attributes"]
  -----
  -apiVersion: {KafkaConnectApiVersion}
  -kind: KafkaConnector
  -metadata:
  -  name: my-connect-cluster
  -spec:
  -  #...
  -  image: debezium-container-for-db2
  -----
  -+
  -* In the `install/cluster-operator/050-Deployment-strimzi-cluster-operator.yaml` file, edit the `STRIMZI_DEFAULT_KAFKA_CONNECT_IMAGE` variable to point to the new container image and reinstall the Cluster Operator. If you edit this file you must apply it to your OpenShift cluster.
  -
  -. Create a `KafkaConnector` custom resource that defines your {prodname} Db2 connector instance. See {LinkDebeziumUserGuide}#debezium-db2-connector-configuration-example[the connector configuration example].
  -
  -. Apply the connector instance, for example:
  -+
  -`oc apply -f inventory-connector.yaml`
  -+
  -This registers `inventory-connector` and the connector starts to run against the `inventory` database.
  -
  -. Verify that the connector was created and has started to capture changes in the specified database. You can verify the connector instance by watching the Kafka Connect log output as, for example, `inventory-connector` starts.
  -
  -.. Display the Kafka Connect log output:
  -+
  -[source,shell,options="nowrap"]
  -----
  -oc logs $(oc get pods -o name -l strimzi.io/name=my-connect-cluster-connect)
  -----
  -
  -.. Review the log output to verify that the initial snapshot has been executed. You should see something like the following lines:
  -+
  -[source,shell,options="nowrap"]
  -----
  -... INFO Starting snapshot for ...
  -... INFO Snapshot is using user 'debezium' ...
  -----
  -
  -endif::product[]
  -
   .Results
   
  -When the connector starts, it {link-prefix}:{link-db2-connector}#db2-snapshots[performs a consistent snapshot] of the Db2 database tables that the connector is configured to capture changes for. The connector then starts generating data change events for row-level operations and streaming change event records to Kafka topics.
  +When the connector starts, it {link-prefix}:{link-db2-connector}#db2-snapshots[performs a consistent snapshot] of the Db2 database tables that the connector is configured to capture changes for.
  +The connector then starts generating data change events for row-level operations and streaming change event records to Kafka topics.
   
   // Type: reference
  -// ModuleID: descriptions-of-debezium-db2-connector-configuration-properties
   // Title: Description of {prodname} Db2 connector configuration properties
   [[db2-connector-properties]]
   === Connector properties
  
positive.code: . {link-prefix}:{link-db2-connector}#db2-adding-connector-configuration[Configure the connector and add the configuration to your Kafka Connect cluster.]
  . Restart your Kafka Connect process to pick up the new JAR files.
  
  If you are working with immutable containers, see link:https://hub.docker.com/r/debezium/[{prodname}'s Container images] for Zookeeper, Kafka and Kafka Connect with the Db2 connector already installed and ready to run.
  You can also xref:operations/openshift.adoc[run {prodname} on Kubernetes and OpenShift].
  endif::community[]
  
  ifdef::product[]
  To deploy a {prodname} Db2 connector, install the {prodname} Db2 connector archive, configure the connector, and start the connector by adding its configuration to Kafka Connect. Details are in the following topics:
  
  * xref:steps-for-installing-debezium-db2-connectors[]
  * xref:debezium-db2-connector-configuration-example[]
  * xref:adding-debezium-db2-connector-configuration-to-kafka-connect[]
  * xref:descriptions-of-debezium-db2-connector-configuration-properties[]
  endif::product[]
  
  ifdef::product[]
  // Type: concept
  [id="steps-for-installing-debezium-db2-connectors"]
  === Steps for installing {prodname} Db2 connectors
  
  To install the Db2 connector, follow the procedures in {LinkDebeziumInstallOpenShift}[{NameDebeziumInstallOpenShift}]. The main steps are:
  
  . {LinkDebeziumUserGuide}#setting-up-db2-to-run-a-debezium-connector[Set up Db2 to run a {prodname} connector]. This enables Db2 replication to expose change-data for tables that are in capture mode.
  
  . Use link:https://access.redhat.com/products/red-hat-amq#streams[Red Hat AMQ Streams] to set up Apache Kafka and Kafka Connect on OpenShift. AMQ Streams offers operators and images that bring Kafka to OpenShift.
  
  . Download the {prodname} link:https://access.redhat.com/jbossnetwork/restricted/listSoftware.html?product=red.hat.integration&downloadType=distributions[Db2 connector].
  
  . Extract the files into your Kafka Connect environment.
  . Add the plug-in's parent directory to your Kafka Connect `plugin.path`, for example:
  +
  [source]
  ----
  plugin.path=/kafka/connect
  ----
  +
  The above example assumes that you extracted the {prodname} Db2 connector to the `/kafka/connect/{prodname}-connector-db2` path.
  
  . Restart your Kafka Connect process to ensure that the new JAR files are picked up.
  
  endif::product[]
  
  // Type: concept
  // ModuleID: debezium-db2-connector-configuration-example
  // Title: {prodname} Db2 connector configuration example
  [[db2-example-configuration]]
  === Connector configuration example
  
  ifdef::community[]
  
  [[db2-example]]
  
  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 the {prodname} Db2 connector in a `.json` 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,json]
  ----
  
negative.code: endif::product[]
  
  // Type: concept
  // Title: How {prodname} Db2 connectors perform database snapshots
  [[db2-snapshots]]
  === Snapshots
  