Application Workflow Jobs

The following topics describe job attributes that work with application workflow platforms and services:

Airflow Job
AWS Step Functions Job
Azure Logic Apps Job
GCP Workflows Job

Airflow Job

Airflow enables you to monitor and manage DAG workflows in Control-M. You can monitor DAG executions in the Airflow tab in the Monitoring domain. You can also view the specific details of each task, open the DAG in the Airflow web server user interface, and view XCom variables from the Airflow tab.

To create an Airflow job, see Creating a Job. For more information, see Control-M for Airflow.

The following table describes the Airflow job type attributes.

Attribute	Description
Connection Profile	Determines the authorization credentials that are used to connect Control-M to Airflow, as described in Airflow Connection Profile Parameters. Rules: Characters: 1−30 Case Sensitive: Yes Invalid Characters: Blank spaces.
DAG ID	Defines the unique identifier of a DAG. Airflow returns 100 records by default. To increase this limit, you must change the maximum_page_limit parameter in the airflow.cfg file. The Airflow plug-in requests 300 records to be returned by default. To increase this number, you must add or modify the NumberOfRecordsPerRequest parameter in the <Agent_Home>/cm/AFL/data/cm_container_conf.xml file, <NumberOfRecordsPerRequest>400</NumberOfRecordsPerRequest>. You can filter the returned list of DAG IDs by typing one of the following: A partial string such as abcd, which returns all DAG IDs that contain this string. A partial string followed by an asterisk, such as abcd*, which returns all DAG IDs that start with this string.
Configuration JSON	(Optional) Defines the JSON object, which describes additional configuration parameters.
Output Details	Determines whether to include Airflow DAG task logs in the Control-M job output, as follows: No task logs. Include failing task logs. Include all task logs. You can also view all task logs from the Airflow tab in an Airflow job in the Monitoring domain. In addition, you can view the log of each Airflow task execution represented by the Try Number field. If a task executed 3 times during the DAG run, the Try Number shows three options.

AWS Step Functions Job

AWS Step Functions enables you to create visual workflows that can integrate other AWS services.

The following table describes the AWS Step Functions job attributes.

Attribute	Description
Connection Profile	Determines the authorization credentials that are used to connect Control-M to AWS Step Functions. Rules: Characters: 1−30 Case Sensitive: Yes Invalid Characters: Blank spaces.
Execution Name	Defines the name of the Step Function execution. An execution executes a state machine, which is a workflow.
State Machine ARN	Determines the Step Function state machine to use. A state machine is a workflow, and an Amazon Resource Name (ARN) is a standardized AWS resource address. arn:aws:states:us-east-1:155535555553:stateMachine:MyStateMachine
Parameters	Defines the parameters for the Step Function job, in JSON format, which enables you to control how the job executes. Rule: You must type backslashes around the parameter name and value. Copy `{\"parameter1\":\"value1\"}`
Show Execution Logs	Determines whether to append the log to the output A tab in the job properties pane of the Monitoring domain where the job output appears that indicates whether a job ended OK, and is used, for example, with jobs that check file location..
Status Polling Frequency	Determines the number of seconds to wait before checking the job status. Default: 20
Failure Tolerance	Determines the number of times to check the job status before ending Not OK. Default: 2

Azure Logic Apps Job

Azure Logic Apps enables you to design and automate cloud-based workflows and integrations.

The following table describes the Azure Logic Apps job attributes.

Attribute	Description
Connection Profile	Determines the authorization credentials that are used to connect Control-M to Azure Logic Apps. Rules: Characters: 1−30 Case Sensitive: Yes Invalid Characters: Blank spaces.
Workflow	Determines which of the Consumption logic app workflows executes from your predefined set of workflows. This job does not execute Standard logic app workflows.
Parameters	Defines parameters, in JSON format, that enable you to control the presentation of data. Copy `{ "param1":"value1", "param2":"value2" }` Rules: Characters: 2–4,000 For no parameters, type {}.
Get Logs	Determines whether to display the job output when the job ends.
Failure Tolerance	Determines the number of times to check the job status before ending Not OK. Default: 2
Status Polling Frequency	Determines the number of seconds to wait before checking the job status. Default: 20

GCP Workflows Job

GCP Workflows enables you to design and automate cloud-based workflows and integrations.

The following table describes GCP Workflows job attributes.

Attribute	Description
Connection Profile	Determines the authorization credentials that are used to connect Control-M to GCP Workflows. Rules: Characters: 1−30 Case Sensitive: Yes Invalid Characters: Blank spaces.
Project ID	Defines the GCP project ID where the batch job executes. A project is a set of configuration settings that define the resources your GCP Workflows jobs use and how they interact with GCP.
Location	Defines the region where the GCP Workflow job executes. us-central1
Workflow Name	Determines the predefined GCP Workflow that executes.
Parameters JSON Input	Defines the JSON-based body parameters that are passed to the function, in the following format: Copy `"argument" : {\"var1\":\"value1\",\"var2\":\"value2\"}`
Execution Label	Defines a job execution label, which enables you to group similar executions in the GCP Workflows log.
Show Workflow Results	Determines whether the GCP Workflow results appear in the job output.
Status Polling Frequency	Determines the number of seconds to wait before checking the job status. Default: 20
Failure Tolerance	Determines the number of times to check the job status before ending Not OK. Default: 3