Connect to Oracle JSON Collection

Learn to create a connection to Oracle JSON Collection in OCI GoldenGate.

Before you begin

Before you create the connection, ensure to have the following:
  1. Oracle Database 23ai or Oracle Database23ai Free:
  2. An ORDS which allows to connect to the Oracle JSON Database using Oracle Database MongoDB API:
    1. Generate SSL certificates for ORDS.

      Note:

      Ensure you configure the certificates with FQDN.
    2. Install ORDS and configure with SSL.
  3. Configure the required policies to enable secure Vault and Secrets access, such as use secrets, use vaults, and read secret-bundles. For more information, see Minimum recommended policies.

Create the connection

To create the 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 GoldenGate on Multicloud only) Select your Subscription, and then complete the following fields.
      1. From the Compartment dropdown, select the compartment in which the Resource Anchor resides.
      2. Select the Multicloud partner region.
      3. Select your Partner availability zone. The available options populate based on the selected Multicloud partner region.
    4. For Compartment, select the compartment in which to create the connection.
    5. For Type, select Oracle JSON Collection from the dropdown.
    6. For Connection string, enter a valid MongoDB connection string URI without the username and password. For example, mongodb://mongodb1.example.com:27017. Ensure that FQDN is used in the connection to establish SSL connections.
    7. For Username, enter the username for this database.
    8. Select the Password secret. If located in a different compartment, use the dropdown to change compartments.

      Note:

      • Secrets are credentials such as passwords, certificates, SSH keys, or authentication tokens that you use with OCI services. To create a secret, see Creating a secret. Ensure that you:
        • Select Manual secret generation.
        • Paste the credentials into Secret contents.
      • If you prefer not to use password secrets, ensure that you deselect Use secrets in vault in the Security section under Advanced Options, located at the bottom of this form.

      When you need to update the Secret content, ensure that you:

    9. For Security Settings, select a Security Protocol, and then upload an SSL certificate authority.
    10. Expand Show advanced options. You can configure the following options:
      • Security
        • Deselect Use vault secrets you prefer not to use password secrets for this connection. If not selected:
          • 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.
      • Security attributes: Add security attributes to control access to this connection using Zero Trust Packet Routing (ZPR).
      • 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 target in a replication.