10.5.10 Apache Pulsar

10.5.10.1 About Apache Pulsar Connections

An Apache Pulsar connection stores the information that Oracle GoldenGate for Distributed Applications and Analytics uses to connect to an Apache Pulsar deployment.

You can use the connection with Replicat to deliver transactional changes to Apache Pulsar. 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 Apache Pulsar producer configuration and optional runtime settings independently of the process configuration.

10.5.10.2 Before You Begin

Before creating an Apache Pulsar 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 Apache Pulsar cluster.
  • A Pulsar producer configuration properties file containing the required client configuration, including the
    serviceUrl
    .
  • The required Apache Pulsar client libraries. Download the supported client libraries by using the Dependency Downloader for Apache Pulsar.
  • 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 Apache Pulsar cluster through an HTTP proxy.

10.5.10.3 Create and Validate an Apache Pulsar Connection

Use the Add Connection page to create an Apache Pulsar 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 Apache Pulsar.
  5. In the Technology Settings section, provide the Apache Pulsar connection information.
    Configure the following technology settings:
    • Producer Configuration File – Upload the Pulsar producer configuration properties file. The file must contain the Apache Pulsar client configuration, including the serviceUrl. This field is required.
  6. Configure Common Settings, if additional runtime configuration is required.
    Configure the following common settings:
    • Classpath – Specifies the runtime classpath used to load the required Apache Pulsar client libraries. You can use Dependency Downloader to download client libraries.

    Note:

    • Download the supported Apache Pulsar client libraries by using the Dependency Downloader for Apache Pulsar.
    • Configure the runtime classpath to reference the downloaded client libraries before starting the Replicat process.
  7. (Optional) Configure Proxy Settings if the Oracle GoldenGate for Distributed Applications and Analytics deployment accesses the Apache Pulsar cluster 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 Apache Pulsar cluster.
    • 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 Apache Pulsar cluster through a proxy that requires authentication or TLS. If the deployment has direct network connectivity to the Apache Pulsar cluster, leave the Proxy Settings blank
  8. Click Submit.
  9. 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 Replicat configuration or Apache Pulsar Handler configuration. After successful validation, the connection is available for selection during Replicat creation.

10.5.10.4 Use an Apache Pulsar Connection in Replicat

After the Apache Pulsar connection has been successfully validated:

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