Continuous Data end-of-life notice

Action required: The Continuous Data UI, API, and CLI are scheduled for end of life. Review the latest migration guidance and start planning your transition to Data Control Tower.

On new engine installations of 2026.5.0.0 and later, the Admin UI opens directly to the Performance Dashboard, and the Manage, Resources, and System menus are unavailable. Engines upgraded from an earlier version keep full Admin UI access. This restriction cannot be changed by customers; contact Delphix Support if you need it lifted temporarily.

Learn more about the Continuous Data end-of-life announcement.

This topic describes the steps for adding a Yugabyte staging and target environment.

Prerequisites

  • A Yugabyte staging environment must be set up with the requirements as described in Yugabyte requirements and prerequisites.

  • Installation of the Yugabyte connector is required before the discovery operation.

  • Install Yugabyte binaries on staging and target servers.

  • The connector identifies the Yugabyte repository in the following cases:

    • Default installation in /usr/bin such that yb-master returns the binary path.

    • Environment variable $YUGABYTE_REPO set on the staging/target host, which contains the binary path of yb-master on the host for the user with which the environment is added (in our case, delphix_os).

    • Running yb-master or yb-tserver running on the host.

Procedure

Perform the following steps to add an environment(staging/target) to the Delphix Continuous Data Engine:

  1. Login to the Delphix Management application.

  2. Navigate to the Manage > Environments page.

  3. Click the Actions ... menu and select Add Environment.

  4. From the Add Environment dialog window, select Unix/Linux.

  5. Select Standalone Host.

  6. Click Next.

  7. Provide the name of the environment.

  8. Provide the Host IP address or host FQDN.

  9. Provide the SSH port. The default value is 22.

  10. Provide an Environment Username for the environment. 

  11. Choose the Login Type that fits your setup. 

  • Username and Password – provide the environment username and password.

  • Username and Public Key – provide the environment username.

  • Password Vault – select from an existing Enterprise Password Vault.

Using Public Key Authentication
If you want to use public-key authentication for logging into your Unix-based environment, you have two options: 

  1. For Password, enter the password associated with the user in step 11.

  2. If you want to use Public Key Encryption for logging into your environment:

    1. Select Public Key for the Login Type.

    2. Click View Public Key.

    3. Copy the public key that is displayed, and append it to the end of your ~/.ssh/authorized_keys file. If this file does not exist, it must be created.

The addition of the public key is a one-time requirement per user and per environment. Additionally, you have the option to add public key authentication to an environment user's profile via CLI (For more information, refer to the CLI Cookbook: Setting up SSH key authentication for UNIX environment users topic).

  1. For Password Login, click Verify Credentials to test the username and password.

  2. Enter Toolkit Path (ensure that the toolkit path does not have any spaces).

  3. To provide your own Oracle Java Development Kit, select the Provide my own JDK checkbox and click Next.

    1. On the Java Development Kit page, provide an absolute path to your Oracle JDK and click Next. 

  4. Click Submit.

After successfully adding and discovering the environment, you should be able to view the newly added environment listed under the Environments tab. If it does not appear, click the refresh icon in your browser.

After the environment has been successfully discovered if you wish to establish further links, add a source configuration to the previously discovered installation.

Perform the following steps to access the information about any environment you have created:

  1. Navigate to Manage > Environments.

  2. Select the environment name.

Last updated
Oct 22, 2026