An Azure Event Hubs connection stores the information that Oracle GoldenGate uses to connect to an Azure Event Hubs namespace. After the connection is created and validated, you can reuse it when configuring Replicat processes that publish change data to Azure Event Hubs.

The connection stores the Event Hubs bootstrap server information, authentication settings, and optional runtime configuration independently of the Replicat configuration, allowing multiple Replicat processes to use the same validated connection.

Before creating an Azure Event Hubs connection, ensure that you have the following:

• An Oracle GoldenGate deployment.
• Network connectivity between the Oracle GoldenGate deployment and the Azure Event Hubs namespace.
• The Azure Event Hubs bootstrap server information.
• Credentials for the authentication method used by the Azure Event Hubs namespace.
  • For Shared Access Signature (SAS) authentication, the SAS connection information. for more information refer: https://learn.microsoft.com/en-us/azure/event-hubs/azure-event-hubs-apache-kafka-overview#security-and-authentication
  • For Microsoft Entra ID (formerly Azure Active Directory) authentication, the Microsoft Entra tenant ID, client ID, and client secret for the registered application.
• Required Azure Event Hubs client libraries, if additional runtime dependencies are required.
• Common runtime settings, such as the runtime classpath.
• Proxy information if the deployment accesses Azure Event Hubs through an HTTP proxy.

Here's the content reformatted to match the style you've been using for all connection topics:

Create and Validate an Azure Event Hubs Connection

Use the Add Connection page to create an Azure Event Hubs 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 Azure Event Hubs.
5. In the Technology Settings section, provide the Azure Event Hubs connection information.

   Configure the following technology settings:

   Bootstrap Servers – Specifies the Event Hubs bootstrap server list used to establish the initial connection to the Azure Event Hubs namespace.

6. Configure the Authentication Settings section.
7. Configure the following authentication settings:

   • Security Protocol – Specifies the security protocol used to authenticate with Azure Event Hubs.

   • Username – Specifies the user name required by the selected authentication method.

   • Password – Specifies the password or shared access credential required by the selected authentication method. This field is treated as sensitive information and is displayed as a password field.

8. Configure Common Settings, if additional runtime configuration is required.

   Configure the following common settings:

   Classpath – Specifies the runtime classpath used to load the required Azure Event Hubs client libraries. You can use Dependency Downloader to download client libraries.

   Note:

   • Download the supported Azure Event Hubs client libraries by using the Dependency Downloader for Azure Event Hubs.
   • Configure the runtime classpath to reference the downloaded client libraries before starting the Extract or Replicat process.
   • If your Azure Event Hubs deployment uses custom Kafka serializers, deserializers, or message converters, configure them as described in the Azure Event Hubs Handler documentation.
9. (Optional) Configure Proxy Settings if the Oracle GoldenGate for Distributed Applications and Analytics deployment accesses Azure Event Hubs through an HTTP proxy.
   Configure the following proxy settings:

   • Proxy URL – Specifies the URL or host name of the proxy server used to access Azure Event Hubs.

   • 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 Azure Event Hubs through a proxy that requires authentication or TLS. If the deployment has direct network connectivity to Azure Event Hubs, leave the Proxy Settings blank.

10. Click Submit.
11. On the DB Connections page, click DB Login to validate the connection.

    Note:

    A successful DB Login validates only the saved connection information. It does not validate the Extract or Replicat configuration or Azure Event Hubs Handler configuration. After successful validation, the connection is available for selection during Extract or Replicat creation.

After the Azure Event Hubs connection has been successfully validated:

1. Create or edit a Replicat.
2. Select Azure Event Hubs as the target technology.
3. Select the validated Azure Event Hubs connection.
4. Complete the remaining Replicat configuration.
5. Create and start the Replicat.

The selected connection supplies the generated connection reference used by the Replicat during runtime.