Registering a Hyperscale orchestrator allows DCT to delegate job execution to a Hyperscale cluster.
When to use this task
Perform this task to add a Hyperscale orchestrator to DCT and enable Compliance jobs to run on Hyperscale
Steps
Registration is a two-stage process: validation followed by registration. In the DCT UI, this is presented as a multi-step wizard.
-
Navigate to Compliance > Delphix Infrastructure > Hyperscale Orchestrators in the left sidebar.
-
Click + Hyperscale Orchestrator to open the Create Hyperscale Orchestrator wizard.
-
On the Details step, provide a name for the orchestrator and optionally add tags. Click Next.
-
On the Configuration step, select the parent Compliance Orchestrator (job orchestrator) from the dropdown, enter the Host/IP Address and API Key for the Hyperscale instance, and configure the Security settings (Insecure SSL, Unsafe SSL Hostname Check) as needed. Click Next. DCT validates connectivity and retrieves the connector type (for example, ORACLE) automatically from the Hyperscale instance — the connector type is no longer a manual input.
-
On the Default Settings step, review and configure the Hyperscale-specific default values. This step is organized into the following sections:
Global Target Assignments — Set defaults for Unload Split, Stream Size, and Column Array Rows.
Job Settings — Configure Consider Continuous Compliance Warning Event As, Retain Execution Data, and toggle options such as Create All Indexes With Nologging, Disable Parallel Index Creation, Enable All Constraints With Novalidate, and Auto Calculate Unload Split.
Source Configuration — Set Max Concurrent Source Connections, Max Records per Split, Max Split per Connection, and Max Parallel Connections per Table.
Target Configuration — Set Max Concurrent Target Connections and Parallelism Degree.
Click Next.
-
On the Summary step, review all settings and click Submit to register the orchestrator.
After successful registration, the new Hyperscale orchestrator appears in the Hyperscale Orchestrators list with its Connection Status, Name, associated Compliance Orchestrator, Data Type, and Number of Nodes.
What's next
Move Compliance Engines from a job orchestrator to the Hyperscale orchestrator