Replication profile management
Data Control Tower (DCT) version 16.0.0 and above offers comprehensive CRUD (Create, Read, Update, Delete) functionalities for replication specifications directly within the Delphix Engines registered with DCT. This can help streamline the management of replication processes.
Prerequisites
You must have a running instance of DCT, at least one registered Delphix Engine, and one or more dSources or VDBs on the engine to leverage the new replication functionalities.
Feature list
GUI access – Navigate to the Replication Profiles summary page via Data > Replication in the GUI to find all known replication profiles, along with essential details like name, source, target host, and mode. Create a new profile with the guided wizard, accessible from the page's upper right corner.
API support – For direct API interaction, endpoints have been introduced to create, update, delete, and execute replication profiles.
Enhanced visibility and control – The inclusion of previously absent replication spec parameters in the APIs means greater visibility and control over your replication tasks.
Getting started
You can access the Replication Profiles page by navigating to Data > Replication in the DCT GUI.

Use the GUI wizard or API calls to create and setup new replication profiles, specifying all necessary parameters such as source, target, and replication mode. The following points below highlight specifics of each section in the wizard.
Mode – The type of replication profile that is to be created. At present, only the standard Engine Data Replication is supported when creating a new profile.

Details – The Name and Description of the profile correlate to the same parameters on the Delphix Engine, while the Tags are used in the DCT profile (not the objects to be replicated).

Target Engines – When using the GUI, only target engines registered with DCT can be selected.

Replication Objects – Objects to be replicated are chosen relative to the source engine selected from the dropdown menu, only if registered with DCT.
Additionally, users have the option to view only selected or unselected objects by utilizing the display option dropdown. They can also filter the replication objects tree nodes by utilizing the search input provided at the top.

Parameters – Including automated Replication and Traffic options, similar in operation to the Delphix Engine. Tags from the existing source objects can be incorporated onto the replicas by opting for the "Include existing source tags on replicas” option.

Summary – Shows all of the details configured in the wizard for user approval, confirm before pressing Save Profile.

You can view existing profiles through the GUI or API, according to your operational needs.
API endpoints
Create replication profile
POST /v3/replication-profiles
Creates a new replication profile with specified parameters.
Update replication profile
PATCH /v3/replication-profiles/{replicationProfileId}
Updates an existing replication profile based on the provided ID.
Delete replication profile
DELETE /v3/replication-profiles/{replicationProfileId}
Removes a replication profile from the system.
Execute replication profile
POST /v3/replication-profiles/{replicationProfileId}/execute
Initiates the execution of the specified replication profile.
Key parameters
replication_mode
– Defines the profile's replication mode (e.g.,ENGINE_DATA_REPLICATION
).description
– A brief description of the replication profile.schedule
– Defines the schedule on which the replication should occur.targetEngineId
,targetHost
,targetPort
– Specify the target engine's ID, hostname, and port for replication.vdb_ids
,dsource_ids
– Lists of virtual databases (VDBs) and data sources (dSources) to be replicated.tags
– Key-value pairs for categorizing and managing profiles.
Example API calls
Create replication profile
curl -X 'POST' \
'https://localhost/v3/replication-profiles' \
-H 'accept: application/json' \
-H 'Authorization: apk 1.4rJrWuVbB54W53ufEn6f5k8zDM9RUtOH4ciJtLGeVZNO0N6HnFt30WHMyj9WynKD' \
-H 'Content-Type: application/json' \
-d '{
"name": "replication-profile-name",
"replication_mode": "ENGINE_DATA_REPLICATION",
"engine_id": 1,
"target_engine_id": 2,
"target_port": 8415,
"description": "description",
"schedule": "0 0 0 * * ?",
"tags": [
{
"key": "key1",
"value": "value1"
},
{
"key": "key2",
"value": "value2"
}
],
"enable_tag_replication": true,
"bandwidth_limit": 0,
"number_of_connections": 1,
"encrypted": false,
"automatic_replication": false,
"use_system_socks_setting": false,
"group_ids": [
"1-GROUP-1"
]
}'
Update replication profile
curl -X 'PATCH' \
'https://localhost/v3/replication-profiles/1-REPLICATION_SPEC-68' \
-H 'accept: application/json' \
-H 'Authorization: apk 1.4rJrWuVbB54W53ufEn6f5k8zDM9RUtOH4ciJtLGeVZNO0N6HnFt30WHMyj9WynKD' \
-H 'Content-Type: application/json' \
-d '{
"name": "string",
"description": "string",
"target_engine_id": "string",
"target_host": "string",
"target_port": 65535,
"schedule": "string",
"vdb_ids": [
"string"
],
"dsource_ids": [
"string"
],
"cdb_ids": [
"string"
],
"vcdb_ids": [
"string"
],
"group_ids": [
"string"
],
"replicate_entire_engine": false,
"bandwidth_limit": 0,
"number_of_connections": 16,
"encrypted": true,
"automatic_replication": true,
"use_system_socks_setting": true
}'
Delete replication profile
curl -X 'DELETE' \
'https://localhost/v3/replication-profiles/1-REPLICATION_SPEC-68' \
-H 'accept: application/json' \
-H 'Authorization: apk 1.4rJrWuVbB54W53ufEn6f5k8zDM9RUtOH4ciJtLGeVZNO0N6HnFt30WHMyj9WynKD'
Other considerations
Password vaults cannot be used for replication operations. This is because the Continuous Data Engine replication APIs require explicit credentials and do not currently support password vaults.
You can find a list of all existing profiles via the DCT GUI, but replication profile IDs can only be found through the
GET /v3/replication-profiles
endpoint.
Limitations
While the creation of new profiles is supported through the GUI, other operations require API calls. Future updates will expand GUI functionalities to cover these aspects.