Control-M for GCP Deployment Manager

The Google Cloud Platform (GCP) Deployment Manager service automates the creation and management of Google Cloud resources. It enables you to write flexible templates and configuration files and use them to create deployments that have a variety of Google Cloud services, such as Cloud Storage, Compute Engine, and Cloud SQL, configured to work together

Control-M for GCP Deployment Manager enables you to do the following:

  • Connect to any GCP Deployment Manager endpoint from a single computer with secure login, which eliminates the need to provide authentication.
  • Integrate GCP Deployment Manager jobs with other Control-M jobs into a single scheduling environment.
  • Monitor the status, results, and output of GCP Deployment Manager jobs in the Monitoring domain.
  • Attach an SLA job to your GCP Deployment Manager jobs.
  • Introduce all Control-M capabilities to Control-M for GCP Deployment Manager including advanced scheduling criteria, complex dependencies, Resource Pools, Lock Resources, and variables.

Setting up Control-M for GCP Deployment Manager

This procedure describes how to install the GCP Deployment Manager plug-in, create a connection profile, and define an GCP Deployment Manager 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 GCP_Deployment_Manager_plugin.Linux
      • Windows: ctm provision image GCP_Deployment_Manager_plugin.Windows
    • For an upgrade, use the following command:
      ctm provision agent::update
  3. Create an GCP Deployment Manager connection profile in Helix Control-M or Automation API, as follows:
  4. Define an GCP Deployment Manager 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 GDM082023.

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