A target connector identifies a destination database where generated synthetic data is written. Target connectors are always associated with a reference connector.

Use this task to add a target connector to an application in Synthetic Data.

Prerequisites

  • An application with at least one reference connector must already exist.

  • You must have the connection details for the target database.

Steps

  1. From the top navigation bar, click Synthetic, then click Applications in the left navigation pane.

  2. On the Applications page, click View for the application.

  3. Click the Connectors tab.

  4. In the Connector Mappings section, locate the reference connector.

  5. On the reference connector card, click + Add Target Connector.

    The Add Synthetic Connector wizard opens.

  6. On the Details page, provide the following information:

    1. Name: Enter a name to identify the connector.

    2. Description (optional): Enter a description of the connector.

    3. Under Connector Capabilities, the Target capability is pre-selected for this connector type. No changes are required.

      Target connectors are used as destinations for generated synthetic data. They do not participate in metadata discovery.

    4. Click Next.

  7. On the Connection Details page:

    1. From Source Type, select the database platform (for example, Database – Oracle).

      Ensure that all JDBC driver JAR files are obtained from authentic and trusted sources. Verify that the files have not been modified or tampered with before use.

    2. Under Connection Method, select one of the following:

      1. Hostname/IP (Basic) — Connect using a hostname or IP address, port, and database identifier.

      2. JDBC URL (Advanced) — Connect using a full JDBC connection string.

      The target connectors inherit schema names from the associated reference connector.

    3. If you selected Hostname/IP (Basic), complete the following fields:

      1. Host — the hostname or IP address of the source database server.

      2. Port — the port number for the database connection.

      3. Database Identifier — select SID or Service Name, then enter the corresponding value.

      4. Authentication Method — select the method used to authenticate (for example, Username/Password).

      5. Username — the database username.

      6. Password — the password for the specified username.

    4. If you selected JDBC URL (Advanced), complete the following fields:

      1. JDBC URL — Enter the full JDBC connection string used to connect to the source database. This option allows you to specify advanced connection parameters that are not available in the basic hostname‑based configuration.

      2. Authentication Method — Select the method used to authenticate to the database (for example, Username/Password).

      3. Username — The database username used for authentication.

      4. Password — The password for the specified username.

    5. (Optional) Under Advanced Settings, expand this section to view Custom Properties and click Select Properties File... to upload a .properties file that contains custom JDBC settings, such as SSL options or connection timeouts.

      For a .properties file, provide one key=value pair per line. Lines beginning with # or ! are treated as comments.

    6. (Optional) Click Test Connection to verify the connection to the target database.

    7. Click Next.

  8. On the Summary page, review the connector details.

  9. Click Submit.

Connection properties are encrypted when stored on the connector and are applied when DCT tests the connector and runs a data-generation job. Secret-shaped values are masked as ******** in the connector details returned by the API and displayed in the UI.

Target connectors inherit the schemas configured on their associated reference connector. You cannot configure schema_names independently on a target connector. The target database must have schemas with the same names as those configured on its associated reference connector. A data-generation job fails if a schema with the same name is not found on the target database.

The target connector appears under its associated reference connector in the Connector Mappings section, indented below the reference and counted in the target destinations total. You can add additional target connectors to the same reference connector by clicking + Add Target Connector again.

Last updated
Oct 8, 2026