Control-M for Azure Functions

Azure Functions jobs enable 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 Functions apps.

• Manage Azure Functions credentials in a secure connection profile.

• Connect to any Azure Functions endpoint.

• Introduce all Control-M capabilities to Control-M for Azure Functions, including advanced scheduling criteria, complex dependencies, Resource Pools, Lock Resources, and variables.

• Integrate Azure Functions jobs with other Control-M jobs into a single scheduling environment.

• Monitor the status, results, and output of Azure Functions jobs.

• Attach an SLA job to the Azure Functions jobs.

• Run 50 Azure Functions jobs simultaneously per Agent.

Setting up Control-M for Azure FunctionsLink copied to clipboard

This procedure describes how to deploy the Azure Functions plug-in, create a connection profile, and define an Azure Functions job in Control-M SaaS 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.

1. On the Agent host, run one of the following commands to set the Java environment variable:

   • 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:

   • To install, type one of the following provision image commands:

     • Linux: ctm provision image ZFA_plugin.Linux

     • Windows: ctm provision image ZFA_plugin.Windows

   • To upgrade, type the following command:

     ctm provision agent::update

3. Create an Azure Functions connection profile in Control-M SaaS or Automation API, as follows:

   • Control-M SaaS: Create a Centralized Connection Profile with Azure Functions Connection Profile Parameters

   • Automation API: ConnectionProfile:AzureFunctions

4. Define an Azure Functions job in Control-M SaaS or Automation API, as follows:

   • Control-M SaaS: Create a Job with Azure Functions Job parameters

   • Automation API: Job:AzureFunctions

Change LogLink copied to clipboard

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

Plug-in Version	Details
1.0.09	Added new Unauthenticated option for the Identity Type in the connection profile Added new job attributes Azure Resource and Azure Resource Scope Added 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	Added new Function APP ID authentication Added new connection profile fields Function App Web Site and Custom App Key
1.0.03	Added ability to trigger Orchestrator functions.
1.0.02	Added new fields Verification Poll Interval and Failure Tolerance Added a new Durable option in the Function Type attribute
1.0.00	Initial version