Skip to Content
Information

This site will undergo maintenance on Friday, 26 September at 2:00 AM CDT / 12:30 PM IST and may experience a short period of instability during that time.

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.

Setting up Control-M for Azure Container Instances

This procedure describes how to install the Azure Container Instances plug-in, create a connection profile, and define an Azure Container Instances 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 9.0.21.080 or later is installed.

Begin

  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, run the following provision image command:
      • Linux: ctm provision image Azure_Container_Instances_plugin.Linux
      • Windows: ctm provision image Azure_Container_Instances_plugin.Windows
    • To upgrade, run the following command:
      ctm provision agent::update
  3. Create an Azure Container Instances connection profile in Helix Control-M or Automation API, as follows:
  4. Define an Azure Container Instances job in Helix Control-M 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