An Oracle JSON Collection connection stores the information that Oracle GoldenGate for Distributed Applications and Analytics uses to connect to an Oracle JSON Collection.

You can use the connection with Extract to capture transactional changes from an Oracle JSON Collection as a source and with Replicat to deliver transactional changes to an Oracle JSON Collection as a target. 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 MongoDB-compatible connection string, authentication settings, security configuration, and optional runtime settings independently of the process configuration.

Before creating an Oracle JSON Collection 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 Oracle JSON Collection.
• A valid MongoDB-compatible connection string for the Oracle JSON Collection.
• Authentication credentials or security artifacts required for the selected security protocol.
• The required MongoDB client libraries. Download the supported client libraries by using the Dependency Downloader for MongoDB.
• 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 Oracle JSON Collection through an HTTP proxy.

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

   Configure the following technology settings:

   Connection String – Specifies the connection string used to connect to the Oracle JSON Collection. This field is required.

6. Configure the Security Settings section.

   Configure the following security settings.

   PLAIN Authentication

   Configure the following settings when Security Protocol is PLAIN:

   • Username – Specifies the user name used to connect to the Oracle JSON Collection.
   • Password – Specifies the password associated with the user name. This field is treated as sensitive information.

   Note: The Password property is deprecated and will be replaced by passwordSecretId. This property will be removed after February 15, 2026.

   TLS Settings

   Configure the following settings when Security Protocol is TLS:

   • Username – Specifies the user name used to connect to the Oracle JSON Collection.
   • Password – Specifies the password associated with the user name.
   • TLS CA Certificate – Upload the Base64-encoded CA certificate used to validate the Oracle JSON Collection server certificate.
   Mutual TLS (mTLS) Settings

   Configure the following settings when Security Protocol is MTLS:

   • Username – Specifies the user name used to connect to the Oracle JSON Collection.
   • Password – Specifies the password associated with the user name.
   • TLS CA Certificate – Upload the Base64-encoded CA certificate used to validate the Oracle JSON Collection server certificate.
   • Client Certificate and Private Key – Upload the client certificate and private key used for mutual TLS authentication.
   • Client Key Password – Specifies the password protecting the client private key, when applicable.
   Kerberos Authentication

   Configure the following settings when Security Protocol is KERBEROS:

   • KRB5 Configuration File – Upload the Kerberos

     krb5.conf

     configuration file.
   • Kerberos Credential Cache – Upload the Kerberos credential cache file.
   • JAAS Configuration File – Upload the JAAS configuration file used for Kerberos authentication.
   X.509 Authentication

   Configure the following settings when Security Protocol is X509:

   • TLS CA Certificate – Upload the Base64-encoded CA certificate used to validate the Oracle JSON Collection server certificate.
   • Client Certificate and Private Key – Upload the client certificate and private key used for X.509 authentication.
   • Client Key Password – Specifies the password protecting the client private key, when applicable.

   Note: The client certificate and private key must not be encrypted.

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 client libraries. You can use Dependency Downloader to download client libraries.

   Note:

   • Download the supported client libraries by using the Dependency Downloader for Oracle JSON Collection.
   • 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 Oracle JSON Collection 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 Oracle JSON Collection.
   • 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 Oracle JSON Collection through a proxy that requires authentication or TLS. If the deployment has direct network connectivity to the Oracle JSON Collection, 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 creation.

Use the Connection with Extract

1. Create or edit an Extract.
2. Select Oracle JSON Collection as the source technology.
3. Select the validated Oracle JSON Collection connection.
4. Complete the remaining Extract configuration.
5. Create and start the Extract.

Use the Connection with Replicat

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