A Job Orchestrator manages job placement and execution flow. It maintains a queue of compliance jobs and assigns jobs to available execution nodes.
When a job runs, the Job Orchestrator selects an available compliance node and assigns the operation to that node. This allows masking operations to run efficiently across multiple nodes.
Compliance nodes operate as stateless execution resources, while DCT centrally manages configuration and execution history. Because nodes are stateless, operations can run on any available node associated with the orchestrator. For more information about how operations are executed and managed, see Job Orchestrator Operations.
Each connector in DCT is associated with a Job Orchestrator. All operations related to that connector such as metadata refresh, discovery, and masking jobs; run using the nodes registered with that orchestrator. Independent operations, including test‑connector, ruleset refresh, and job execution, may run on any available node within the orchestrator’s pool.
You can perform the following operations: