Skip to Content

Control-M for Azure Container Instances

Azure Container Instances enables you to run an isolated container in Azure, without having to manage any virtual machines and without having to adopt a higher-level service. 

Control-M for Azure Container Instances enables you to do the following:

  • Execute Azure Container Instances jobs that run specified versions of predefined Azure Container Instances tasks and plans.
  • Manage Azure Container Instances credentials in a secure connection profile.
  • Connect to any Azure Container Instances endpoint.
  • Introduce all Control-M capabilities to Control-M for Azure Container Instances, including advanced scheduling criteria, complex dependencies, Resource Pools, Lock Resources, and variables.
  • Integrate Azure Container Instances jobs with other Control-M jobs into a single scheduling environment.
  • Monitor the job status, results, and output of Azure Container Instances jobs.
  • Attach an SLA job to the Azure Container Instances jobs.

Control-M for Azure Container Instances Compatibility

The following table lists the prerequisites that are required to use the Azure Container Instances plug-in, each with its minimum required version.

Component

Version

Control-M/EM

9.0.21.200

Control-M/Agent

9.0.21.200

Control-M Application Integrator

9.0.21.200

Control-M Automation API

9.0.21.310

Control-M for Azure Container Instances is supported on Control-M Web and Control-M Automation API, but not on the Control-M client.

To download the required installation files for each prerequisite, see Obtaining-Control-M-Installation-Files.

Setting up Control-M for Azure Container Instances

This procedure describes how to deploy the Azure Container Instances plug-in, create a connection profile, and define an Azure Container Instances job in Control-M Web and Automation API.

Warning

Note

Integration plug-ins released by BMC require an Application Integrator installation. However, these plug-ins are not editable and you cannot import them into Application Integrator. To deploy these integrations to your Control-M environment, import them directly into Control-M using Control-M Automation API.

Before You Begin

Verify that Automation API is installed, as described in Automation API Installation.

Begin

  1. Create a temporary directory to save the downloaded files.
  2. Download the Azure Container Instances plug-in from the Control-M for Azure Container Instances download page in the EPD site.
  3. Install the Azure Container Instances plug-in using the Automation API Provision service:
    1. Log in to the Control-M/EM Server machine as an Administrator and store the downloaded zip file in the one of the following locations (within several minutes, the job type appears in Control-M Web):
      • Linux: $HOME/ctm_em/AUTO_DEPLOY
      • Windows: <EM_HOME>\AUTO_DEPLOY
    2. Log in to the Control-M/Agent machine and run the provision image command, as follows:
      • Linux: ctm provision image Azure_Container_Instances_plugin.Linux
      • Windows: ctm provision image Azure_Container_Instances_plugin.Windows
  4. Create an Azure Container Instances connection profile in Control-M Web or Automation API, as follows:
  5. Define an Azure Container Instances job in Control-M Web or Automation API, as follows:
Warning

Note

To remove this plug-in from an Agent, see Removing a Plug-in. The plug-in ID is ZCI062024.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*

Control-M