anchor.diff:  [[postgresql-example-configuration]]
   === Connector configuration example
   
  -Following is an example of the configuration for a PostgreSQL connector that connects to a PostgreSQL server on port 5432 at 192.168.99.100, whose logical name is `fullfillment`. Typically, you configure the {prodname} PostgreSQL connector in a `.json` file using the configuration properties available for the connector.
  +Following is an example of the configuration for a PostgreSQL connector that connects to a PostgreSQL server on port 5432 at 192.168.99.100, whose logical name is `fulfillment`. Typically, you configure the {prodname} PostgreSQL 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]
   ----
   {
  -  "name": "inventory-connector",  // <1>
  +  "name": "fulfillment-connector",  // <1>
     "config": {
       "connector.class": "io.debezium.connector.postgresql.PostgresConnector", // <2>
       "database.hostname": "192.168.99.100", // <3>
  
positive.code: If any of the services stop or crash,
  those tasks will be redistributed to running services.
  <3> The connector’s configuration.
  <4> The database host, which is the name of the container that is running the PostgreSQL server (`postgresqldb`).
  <5> A unique server name.
  The server name is the logical identifier for the PostgreSQL server or cluster of servers.
  This name is used as the prefix for all Kafka topics that receive change event records.
  <6> Changes in only the `public.inventory` schema are captured.
  
  . Register your connector instance with Kafka Connect. For example, if you saved your `KafkaConnector` resource in the `inventory-connector.yaml` file, you would run the following command: 
  +
  [source,shell,options="nowrap"]
  ----
  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: 
  .. Display the Kafka Connect log output to verify that the connector was created and has started to capture changes in the specified database:
  
negative.code: [[postgresql-deploying-a-connector]]
  === Deploying connectors
  
  To deploy a {prodname} PostgreSQL connector, you need to build a custom Kafka Connect container image that contains the {prodname} connector archive and push this container image to a container registry.You then need to create two custom resources (CRs):
  
  * A `KafkaConnect` CR that configures your Kafka Connector and that specifies the name of the image that you created to run your {prodname} connector. You apply this CR to the OpenShift Kafka instance. 
  
  * A `KafkaConnector` CR that configures your {prodname} PostgreSQL connector. You apply this CR to the OpenShift instance where Red Hat AMQ Streams is deployed. 
  
  .Prerequisites
  
  