Control-M for Databricks

Databricks is a cloud-based data analytics platform that enables you to process large workloads of data.

Control-M for Databricks enables you to do the following:

  • Connect to any Databricks workspace using a Databricks Personal Access Token (PAT) for authentication. You can generate the PAT in your Databricks workspace without dependence on the cloud vendor.
  • Integrate Databricks jobs with other Control-M jobs into a single scheduling environment.
  • Monitor the Databricks workspace status and view the results in the Monitoring domain.
  • Attach an SLA job to your entire Databricks data service.
  • Introduce all Control-M capabilities to Databricks, including advanced scheduling criteria, complex dependencies, quantitative and control resources, and variables.
  • Run 50 Databricks jobs simultaneously per Control-M/Agent.

Setting up Control-M for Databricks

This procedure describes how to install the Databricks plug-in, create a connection profile, and define a Databricks job in Helix Control-M and Automation API.

Before you Begin

  • Verify that Automation API is installed, as described in Setting up the API.
  • Verify that Agent version or later is installed.


  1. On the Agent host, set the Java environment variable by running one of the following commands through a command line:
    • Linux:
      • Bourne shell/bash: export BMC_INST_JAVA_HOME=<java_11_directory>
      • csh/tcsh: setenv BMC_INST_JAVA_HOME <java_11_directory>
    • Windows: set BMC_INST_JAVA_HOME="<java_11_directory>"
  2. Run one of the following API commands:
    • For a fresh installation, use the provision image command:
      • Linux: ctm provision image DBX_plugin.Linux
      • Windows: ctm provision image DBX_plugin.Windows
    • For an upgrade, use the following command:
      ctm provision agent::update
  3. Create a Databricks connection profile in Helix Control-M or Automation API, as follows:
  4. Define a Databricks job in Helix Control-M or Automation API, as follows:


To remove this plug-in from an Agent, follow the instructions in Removing a Plug-in. The plug-in ID is DBX032022.

Was this page helpful? Yes No Submitting... Thank you