Connect a Continuous Data Engine in DCT

Connect a Delphix Continuous Data Engine (CD) to DCT before you add PostgreSQL environments or create dSources. After you add a connection, DCT automatically discovers compatible objects on the engine you can use for PostgreSQL ingestion and provisioning tasks.

Procedure

  1. Log in to DCT with an API key or a username and password.

  2. Open the Data tab and go to Data Infrastructure > Data Engines.

  3. Click Connect Engine.

  4. On the Engine Details page, add the following:

    1. Name: a display name for the source environment.

    2. Hostname: the hostname or IP address of the source environment.

    3. Choose Engine Type: select Continuous Data for a Virtualization engine, or Continuous Compliance for a Masking engine.

  5. Click Next.

  6. On the Authentication page, choose an option:

    • Select Username and Password to enter your CD login credentials.

  7. Click Next.

  8. On the Security page, select additional settings. Use these settings only when certificate validation cannot be configured correctly.

    • Insecure SSL: if checked, DCT connects over HTTPS without validating the TLS certificate. Even with HTTPS, enabling this removes protection from man-in-the-middle attacks. If your system allows, configure DCT with proper Certificate Authority certificates instead.

    • Unsafe Hostname: if checked, DCT ignores hostname validation for the TLS certificate when you connect over HTTPS. Enable this only when the engine TLS certificate does not match the hostname and you cannot correct the engine TLS configuration. Ignored if Insecure SSL is set.

  9. Click Next.

  10. On the Tags page, optionally add tags so that DCT can apply predefined tags to objects that are discovered through the engine.

  11. Click Next.

  12. Review details on the Summary page and click Submit.

Your CD Engine is now connected in DCT.

After you connect the engine

The engine appears in the Data > Data Infrastructure > Data Engines list with an Online status.

Click View to open the Engine detail page. On the Engine detail page, click Actions on your top right to perform the following:

  • Rename: Change the engine display name.

  • Auto-tagging configuration: Modify object access. Review permissions carefully after auto-tagging. All new and existing objects from that point automatically receive configured tags which behave like other object tags.

  • Network Performance Test: Test for latency, throughput, and DSP. For details, read Test with Network Performance Tool.

  • Deregister – Removes an engine from DCT and deletes all associated metadata, including dSources, VDBs, and environment connections. This action cannot be undone. Reconnect the engine and rediscover objects if you need to restore access.