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:
- Connect to any Azure Functions endpoint 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.
- Execute Activity, HTTP, and Orchestrator Azure Function Apps.
- 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
- 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>"
- Linux:
- 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
- For a fresh installation, use the provision image command:
- 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
- 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
Was this page helpful? Yes No
Submitting...
Thank you
Comments
Log in or register to comment.