This section describes the core components of Hyperscale job execution and how they interact
Key components
Data Control Tower (DCT)
The central control plane for managing compliance logic, jobs, rule sets, connectors, and execution history.
Job orchestrator
A logical grouping that manages Compliance Engines and Hyperscale orchestrators. DCT connects to one or more Hyperscale orchestrators with a one-to-one mapping per job orchestrator.
Hyperscale orchestrator
Executes masking jobs in parallel across multiple Compliance Engines and manages the staging area (mount point) for data operations.
Compliance Engines
Stateless execution nodes that perform masking tasks as assigned by the Hyperscale orchestrator. In a Hyperscale setup, these engines are dedicated to the Hyperscale orchestrator and cannot be used for standard job orchestrator tasks.
Job execution flow — overview
-
Define rule sets, connectors, inventories, and OTF (on-the-flly) jobs in DCT.
-
Register a Hyperscale Orchestrator under a job orchestrator.
-
Enable an Oracle OTF job for Hyperscale execution and configure the required Hyperscale-specific attributes.
-
Execute the job. DCT tracks progress and displays execution details under the Hyperscale orchestrator.