Connect to Confluent Schema Registry

Learn to create a connection to Confluent Schema Registry that is used in conjunction with the Confluent Kafka connection to serve as a source or target for a OCI GoldenGate Big Data deployment.

Related Topics

Before you begin

Before you create the connection, ensure that you review how OCI GoldenGate connects to your source and targets.

Create the connection

To create a Confluent Schema Registry connection:
  1. From the OCI GoldenGate Overview page, click Connections.
    You can also click Create Connection under the Get started section and skip to step 3.
  2. On the Connections page, click Create Connection.
  3. On the Create Connection page, complete the fields as follows:
    1. For Name, enter a name for the connection.
    2. (Optional) For Description, enter a description that helps you distinguish this connection from others.
    3. For Compartment, select the compartment in which to create the connection.
    4. From the Type dropdown, select Confluent Schema Registry.
    5. For URL, enter the Confluent Schema Registry URL.
    6. From the Authentication type dropdown, select one of the following:
      • None
      • Basic authentication, if selected, enter the following:
        1. For Username, enter the username to connect to the database with.
        2. (Optional) Select the Truststore secret. If located in a different compartment, use the dropdown to change compartments.
        3. (Optional) Select the Truststore password secret. If located in a different compartment, use the dropdown to change compartments.

          Note:

          To use password secrets, ensure that you select Use secrets in vault in the Settings tab under Advanced Options, located at the bottom of this form.
      • Mutual authentication, if selected, enter the following:
        1. (Optional) Select the Truststore secret. If located in a different compartment, use the dropdown to change compartments.
        2. (Optional) Select the Truststore password secret. If located in a different compartment, use the dropdown to change compartments.
        3. Select the Keystore secret. If located in a different compartment, use the dropdown to change compartments.
        4. Select the Keystore password secret. If located in a different compartment, use the dropdown to change compartments.
        5. Select the SSL key password secret. If located in a different compartment, use the dropdown to change compartments.

          Note:

          To use password secrets, ensure that you select Use secrets in vault in the Settings tab under Advanced Options, located at the bottom of this form.
    7. Expand Show advanced options. You can configure the following options:
      • Security
        • Select Use Oracle-managed encryption key to leave all encryption key management to Oracle.
        • Select Use customer-managed encryption key to select a specific encryption key stored in your OCI Vault to encrypt your connection credentials.
      • Network connectivity
        • Shared endpoint, to share an endpoint with the assigned deployment. You must allow connectivity from the deployment's ingress IP.
        • Dedicated endpoint, for network traffic through a dedicated endpoint in the assigned subnet in your VCN. You must allow connectivity from this connection's ingress IPs.

          Note:

          • If a dedicated connection remains unassigned for seven days, then the service converts it to a shared connection.
          • Learn more about Oracle GoldenGate connectivity.
      • Settings
        • Deselect Use vault secrets you prefer not to use password secrets for this connection.
        • If using this connection for Extract, then drag and drop or select the Consumer or Producer properties file under Additional properties.
        • To use Snappy compression in Kafka replication, drag and drop or select Producer properties, and change replication settings as discussed in Using Compression OCI GoldenGate (Confluent) Kafka Replication.
        • To capture from Kafka, create a Kafka Consumer properties file with one of the following deserializers or converters:
          • Kafka Consumer properties for JSON deserializer:
            key.deserializer=org.apache.kafka.common.serialization.ByteArrayDeserializer
value.deserializer=org.apache.kafka.common.serialization.ByteArrayDeserializer
          • Kafka Consumer properties for JSON converter:
            key.converter=org.apache.kafka.connect.json.JsonConverter
value.converter=org.apache.kafka.connect.json.JsonConverter
          • Kafka Consumer properties for Avro converter:
            key.converter=io.confluent.connect.avro.AvroConverter
value.converter=io.confluent.connect.avro.AvroConverter
      • Tags: Add tags to organize your resources.
  4. Click Create.
After the connection is created, it appears in the Connections list. Ensure that you assign the connection to a deployment to use it as a source or target in a replication.