Control-M for Azure Functions

Azure Functions is an Azure cloud service for serverless application development .

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

• Connect to any Azure Functions workspace from a single computer with secure login, which eliminates the need to provide authentication.
• Integrate Azure Functions jobs with other Control-M jobs into a single scheduling environment.
• Monitor the Azure Functions workspace status and view the results in the Monitoring domain.
• Attach an SLA job to your entire Azure Functions service.
• Introduce all Control-M capabilities to Azure Functions, including advanced scheduling criteria, complex dependencies, quantitative and control resources, and variables.
• Run 50 Azure Functions jobs simultaneously per Control-M/Agent.

Setting up Control-M for Azure Functions

This procedure describes how to install the Azure Functions plug-in, create a connection profile, and define an Azure Functions 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, use the provision image command:
     • Linux: ctm provision image ZFA_plugin.Linux
     • Windows: ctm provision image ZFA_plugin.Windows
   • For an upgrade, use the following command:
     ctm provision agent::update
3. Create an Azure Functions connection profile in Helix Control-M or Automation API, as follows:
   • Helix Control-M: Creating a Centralized Connection Profile with Azure Functions Connection Profile Parameters
   • Automation API:  ConnectionProfile:AzureFunctions
4. Define an Azure Functions job in Helix Control-M or Automation API, as follows:
   • Helix Control-M: Create a Job and then define specific Azure Functions parameters in Azure Functions Job parameters.
   • Automation API: Job:AzureFunctions