Data Control Tower 2.0.0
  • 08 Mar 2023
  • Dark
    Light
  • PDF

Data Control Tower 2.0.0

  • Dark
    Light
  • PDF

Overview

Data Control Tower (DCT) is a unified data management platform used to enable API-driven DevOps workflows with continuous data and centrally manage the entire data estate for all Delphix customers. DCT 2.0.0.0introduces a centralized, container-based deployment architecture with a robust API library that enables automation and management across multiple Delphix Continuous Data engines. The DCT container form factor allows customers to self-host on their preferred public or private cloud environment.

Supported APIs

  • Engines - List engines connected to DCT
  • Environments - List environments across Engines
  • Datasets - List sources, dsources and vdbs across Engines
  • Snapshots - List Timeflow Snapshots for a dataset
  • Bookmarks - Bookmark a point in time in a VDB to ease the process of restoring the VDB later to that point in time
  • VDB Provisioning - Provision Oracle single instance, MSSql or Sybase ASE databases
  • VDB operations - Enable, Disable, Start, Stop, Delete, Refresh, Rewind VDBs
  • VDB Groups - A new grouping mechanism used in conjunction with bookmarks that was previously supported by VDB Templates in the Self Service module
  • Jobs - Monitor progress of aynschronous tasks
  • Reporting - Query across multiple engines to list storage capability, VDB inventory and dsource inventory
  • Connectivity - Checks connectivity between an engine and a remote host machine

Features

  • Automation APIs to enable automating complaint data within DevOps pipelines (NEW in DCT 2.0.0.0)
  • Reporting APIs to provide central reporting across many Delphix engines (NEW in DCT 2.0.0.0)
  • Terraform Provider for Delphix support for data infrastructure automation (NEW in DCT 2.0.0.0)
  • Engines versions 6.0.0.1 + supported (Virtualization only - masking support will be a future addition)
  • Connections to engine over HTTPs (self-provided certificate authority when necessary)
  • Username/password to authenticate with engines stored in the API Gateway or provided via password vault
  • Hashicorp vault supported
  • Audit logging via Nginx access log, self-configured Docker logging to go to fluentd, splunk, etc.
  • Native APIs keys supported for MCAPIGW authentication, OAuth2.0 provided via nginx module
  • OpenAPI 3.0 spec (self-generated client libraries with open source tooling)

Was this article helpful?

What's Next