Control-M for Azure Functions

Azure Function job enables you to develop, test, and run applications in the cloud.

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

• Execute Activity, HTTP, and Orchestrator Azure Function Apps.
• Manage Azure Functions credentials in a secure connection profile.
• Connect to any Azure Functions endpoint.
• Integrate Azure Functions jobs with other Control-M jobs into a single scheduling environment.
• Monitor the status, results, and output of Azure Functions jobs in the Monitoring domain.
• Attach an SLA job to your Azure Functions jobs.
• Introduce all Control-M capabilities to Control-M for Azure Functions including advanced scheduling criteria, complex dependencies, Resource Pools, Lock Resources, and variables.
• Run 50 Azure Functions jobs simultaneously per 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: Creating a Job with Azure Functions Job parameters
   • Automation API: Job:AzureFunctions

Change Log

The following table provides details about changes that were introduced in new versions of this plug-in:

Plug-in Version	Details
1.0.09	New Unauthenticated option for the Identity Type in the connection profile. New job attributes Azure Resource and Azure Resource Scope. New API-VERSION job attribute.
1.0.07	Added ability to kill Durable Functions.
1.0.06	Corrected issue in the Function App ID authentication in the Connection Profile.
1.0.05	New Function APP ID authentication. New connection profile fields, Function App Web Site and Custom App Key.
1.0.03	Added ability to trigger Orchestrator functions.
1.0.02	New fields Verification Poll Interval and Failure Tolerance, and a new Durable option in the Function Type attribute.