A Confluent Schema Registry connection stores the information that Oracle GoldenGate for Distributed Applications and Analytics uses to connect to a Confluent Schema Registry.

A Confluent Schema Registry connection is used by Kafka-based Extract and Replicat processes that require access to schemas stored in the Schema Registry. After you create and validate the connection, you can reuse it across multiple Oracle GoldenGate for Distributed Applications and Analytics processes.

The connection stores the Schema Registry endpoint, authentication settings, security configuration, and optional runtime settings independently of the process configuration.

Before creating a Confluent Schema Registry connection, ensure that you have the following:

• An Oracle GoldenGate for Distributed Applications and Analytics deployment.
• Network connectivity between the Oracle GoldenGate for Distributed Applications and Analytics deployment and the Confluent Schema Registry.
• The Confluent Schema Registry URL.
• Authentication credentials for the selected authentication method, if required.
• Truststore and keystore files if TLS or mutual TLS authentication is used.
• The required Confluent Schema Registry client libraries. Download the supported client libraries by using the Dependency Downloader for Kafka.
• Common runtime settings, such as the runtime classpath, configured to reference the downloaded client libraries.
• Proxy information if the Oracle GoldenGate for Distributed Applications and Analytics deployment accesses the Confluent Schema Registry through an HTTP proxy.

Use the Add Connection page to create a Confluent Schema Registry connection.

Procedure

1. In the navigation menu, select DB Connections.
2. Click Add Connection.
3. In Connection Alias, enter a unique name for the connection.
4. From Technology Type, select Confluent Schema Registry.
5. In the Technology Settings section, provide the Confluent Schema Registry connection information.

   Configure the following technology settings:

   URL – Specifies the Confluent Schema Registry URL. This field is required.

6. Configure the Security Settings section.

   Configure the following security settings.

   No Authentication

   Configure Authentication Type as NONE when the Confluent Schema Registry does not require authentication.

   TLS Authentication
   Configure the following settings when Authentication Type is TLS:

   • Username – Specifies the user name used to authenticate with the Confluent Schema Registry.
   • Password – Specifies the password associated with the user name. This field is treated as sensitive information.
   • Truststore – Upload the Base64-encoded truststore used to validate the Confluent Schema Registry server certificate.
   • Truststore Password – Specifies the password associated with the truststore.

   Mutual TLS Authentication
   Configure the following settings when Authentication Type is MUTUAL:

   • Truststore – Upload the Base64-encoded truststore used to validate the Confluent Schema Registry server certificate.
   • Truststore Password – Specifies the password associated with the truststore.
   • Keystore – Upload the Base64-encoded keystore containing the client certificate and private key.
   • Keystore Password – Specifies the password associated with the keystore.
   • SSL Key Password – Specifies the password protecting the private key stored in the keystore when it differs from the keystore password.

   Note:

   The SSL Key Password property is deprecated and will be replaced by sslKeyPasswordSecretId. This property will be removed after February 15, 2026.
7. Configure Common Settings, if additional runtime configuration is required.

   Configure the following common settings:

   Classpath – Specifies the runtime classpath used to load the required Confluent Schema Registry client libraries. You can use Dependency Downloader to download client libraries.

   Note:

   • Download the supported Kafka client libraries by using the Dependency Downloader for Kafka.
   • Configure the runtime classpath to reference the downloaded libraries before starting the Extract or Replicat process.
8. (Optional) Configure Proxy Settings if the Oracle GoldenGate for Distributed Applications and Analytics deployment accesses the Confluent Schema Registry through an HTTP proxy.
   Configure the following proxy settings:

   • Proxy URL – Specifies the URL or host name of the proxy server used to access the Confluent Schema Registry.
   • Proxy Port – Specifies the port number of the proxy server.
   • Proxy Username – Specifies the user name for proxy authentication, if required.
   • Proxy Password – Specifies the password for proxy authentication. This field is treated as sensitive information.
   • Truststore – Specifies the Java truststore file that contains the certificate authority (CA) certificates used to validate the proxy server certificate, when required.
   • Truststore Password – Specifies the password associated with the truststore.
   • Keystore – Specifies the Java keystore file containing the client certificate and private key used for client authentication, when required.
   • Keystore Password – Specifies the password associated with the keystore.
   • SSL Key Password – Specifies the password protecting the private key stored in the keystore when it differs from the keystore password.

   Note:

   Configure the proxy and SSL settings only if the Oracle GoldenGate for Distributed Applications and Analytics deployment accesses the Confluent Schema Registry through a proxy that requires authentication or TLS. If the deployment has direct network connectivity to the Confluent Schema Registry, leave the Proxy Settings blank.
9. Click Submit.
10. On the DB Connections page, click DBLOGIN to validate the connection.

    Note:

    A successful DBLOGIN validates only the saved connection information. It does not validate the Extract or Replicat configuration. After successful validation, the connection is available for selection during Extract or Replicat configuration.

After the Confluent Schema Registry connection has been successfully validated:

1. Create or edit an Extract or Replicat that uses Kafka serialization.
2. Select the validated Confluent Schema Registry connection where applicable.
3. Complete the remaining process configuration.
4. Create and start the Extract or Replicat.