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.
Control-M for Azure Functions Compatibility
The following table lists the prerequisites that are required to use the Azure Functions plug-in, each with its minimum required version.
|Control-M Application Integrator||220.127.116.11|
|Control-M Automation API||18.104.22.168|
Control-M for Azure Functions is supported on Control-M Web and Control-M Automation API, but not on Control-M client.
To download the required installation files for each prerequisite, see Obtaining Control-M Installation Files via EPD.
Setting up Control-M for Azure Functions
This procedure describes how to deploy the Azure Functions plug-in, create a connection profile, and define an Azure Functions job in Control-M Web and Automation API.
NOTE: Integration plug-ins released by BMC require an Application Integrator installation at your site. However, these plug-ins are not editable and you cannot import them into Application Integrator. To deploy these integrations to your Control-M environment, you 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.
Create a temporary directory to save the downloaded files.
- Deploy the Azure Functions job via Automation API, as described in deploy jobtype.
- Create an Azure Functions connection profile in Control-M Web or Automation API, as follows:
- Define an Azure Functions job in Control-M Web or Automation API, as follows: