Control Center Commandline

CCC.exe – The dbWatch Command Line Interface

The Control Center Commandline (CCC.exe) is a utility provided by dbWatch to enable scripting, automation, and system integration via the Unified Scripting Language (USL).

CCC is designed for use in headless environments (e.g., terminal, automation frameworks, CI/CD pipelines) and offers a powerful way to interact with dbWatch without the graphical user interface.

Use Cases

Automating instance provisioning or metadata tagging
Running Farm Data Language (FDL) queries
Installing job packages across groups
Retrieving or registering instance configurations
Integrating dbWatch into external platforms or scripts

Downloading Scripts

dbWatch provides a curated bundle of scripts for CCC.

Download:
https://download.dbwatch.com/download/misc/ccc/ccc_script.zip

This zip contains scripts tailored for setup, monitoring, and instance lifecycle automation.

Script Overview

Script File	Description
setup.script	Perform initial setup on a CCC node
add_instance.script	Add new instances to Control Center
fdl.script	Run Farm Data Language queries and retrieve output
get_instance.script	Export instance config to XML
register_instance.script	Register instances based on XML files
metadata.script	Assign metadata (e.g., environment, location) to instances
jobs.script	Install monitoring or maintenance jobs
instance_action.script	Connect or disconnect instances

Running CCC Scripts

Use the following pattern to execute scripts:

CCC.exe <script_file> [parameters]

Example:

CCC.exe add_instance.script --host 192.168.1.20 --type mysql --name analytics-db

Each script accepts command-line arguments and can be queried with `--help` to show available parameters.

---

CCC in the Network Layout and Domain Security

In a distributed dbWatch Control Center architecture, nodes can be securely interconnected. CCC is **not limited to but is well-suited for use on dedicated scripting nodes**—typically command-line-only machines operating within your automation or orchestration layer.

These scripting nodes can be configured in the Domain Configuration interface where you can:

Define node-specific privileges (e.g., view-only, install-jobs only)
Limit access to instance groups or job types
Centrally manage certificates and routing rules for each node
Control what CCC scripts executed from that node are authorized to access or change

This allows for fine-grained access control and centralized enforcement of operational boundaries, aligning with DevOps or security models.

Best Practices

Always test scripts in non-production before applying in live environments
Use the built-in `setup.script` only during initial configuration of CCC nodes
Restrict CCC node access using Domain Configuration and certificate-based routing
Combine `get_instance.script` and `register_instance.script` for backup/restore or migration
Store CCC logs and scripts in a version-controlled, secured repository