Cloud Computing Jobs

Determines the authorization credentials that are used to connect Control-M to AWS Batch.

Rules:

• Characters: 1−30

• Case Sensitive: Yes

• Invalid Characters: Blank spaces.

Determines whether you supply your own JSON parameters.

Defines the parameters for the batch job, in JSON format, that enable you to control how the job runs.

For a description of this JSON syntax, see the description of SubmitJob in the AWS Batch API Reference.

{
   "containerOverrides":
   {
      "command":["echo","Hello, from Control-M"],
         "resourceRequirements":[
         {
            "type":"VCPU",
            "value":"2"
         }
      ]
   }
   "jobDefinition": "ctm-batch-job-definition",
   "jobName": "ctm-batch-job-single",
   "jobQueue": "ctm-batch-job-queue",
   "timeout": 
   {
      "attemptDurationSeconds": 70
   }
}

Defines the name of the batch job.

Determines which predefined job definition and version number (revision) is applied to the job, depending upon how you complete the field, as follows:

• Job Definition Name: When you type only the job definition name in the field, this job definition and its most recent version is applied to the job.

• Job Definition Name:Version Number: When you type the job definition name—followed by a colon (:), followed by a version number—in the field, this job definition and version number is applied to the job.

Determines the job queue, which stores your batch job.

(Optional) Defines a command, in JSON format, that overrides the specified command in the job definition.

(Optional) Determines the number of times to retry a job run, which overrides the retry attempts determined in the job definition.

Valid Values: 1–10

(Optional) Determines the number of seconds to wait before a timeout occurs in a batch job, which overrides the specified timeouts in the job definition.

Determines the authorization credentials that are used to connect Control-M to AWS EC2.

Rules:

• Characters: 1−30

• Case sensitive: Yes

• Invalid characters: Blank spaces.

Determines one of the following operations to perform on the AWS EC2 Virtual Machine:

• Create: Creates a new virtual machine.

• Create from Instance Template: Creates a new virtual machine based on a template.

• Start: Starts an existing virtual machine.

• Stop: Stops a running virtual machine.

• Reboot: Resets a virtual machine.

• Terminate: Deletes an existing virtual machine.

Defines the template to use to create a VM from a template.

Defines the name of the VM instance where you want to run the operation.

This parameter is available for all operations except for the Create operations.

Defines the name of a new VM instance for Create operations.

Determines which AWS EC2 zone to use for a Create operation.

Determines the software requirements of the host computer when you create a new AWS EC2 Virtual Machine.

Defines the Subnet ID that is required to launch the instance in a Create operation.

Defines the security credential key set for a Create operation.

Defines the ID of the Amazon Machine Image (AMI) that is required to launch the instance in a Create operation.

Determines the number of copies of the VM to create in a Create operation.

Default: 1

Determines whether to display logs from the AWS EC2 instance at the end of the job output.

This parameter is available for all operations except for the Terminate operation.

Determines the number of seconds to wait before job status verification.

Default: 15 seconds

Determines the authorization credentials that are used to connect Control-M to AWS ECS.

Rules:

• Characters: 1−30

• Case sensitive: Yes

• Invalid characters: Blank spaces.

Determines one of the following actions to perform on AWS ECS:

• Preset JSON: Runs the task according to the attributes that you define in this job.

• Manual JSON: Runs the task according to the JSON parameters that you supply in the Parameters attribute.

Defines the parameters, in JSON format, that enable you to control how the AWS ECS task runs.

For a description of this JSON syntax, see RunTask in the AWS ECS API Reference.

"Parameters": 
{
   "cluster":"ECSIntegrationCluster",
   "launchType":"FARGATE",
   "networkConfiguration":
   {
      "awsvpcConfiguration":
      {
         "assignPublicIp":"ENABLED",
         "securityGroups":["sg-01e4a5bfac4189d10"],
         "subnets":["subnet-045ddaf41d4852fd7"]
      }
   },
   "overrides":
   {
         "containerOverrides":[
         {
            "command":["/bin/sh -c 'whoami'"],
            "environment":[
            {
               "name":"var1",
               "value":"hello"
            }],
            "name":"IntegrationURI"
            }]
   },
   "taskDefinition":"ECSIntegrationTask"
}

Defines the ECS cluster on the AWS ECS platform where the job runs.

An ECS cluster is a logical group of tasks and services.

Defines the task definition on the AWS ECS platform.

The task definition describes the container image, command, environment variables, and other parameters that run your application.

Determines the type infrastructure where your tasks and services run:

• Fargate: Runs your application on a virtual machine that is automatically provisioned and managed.

• EC2: Runs your application on a predefined AWS EC2 virtual machine that you provision and manage.

• External: Runs your application on a different virtual machine that you define in the AWS ECS platform.

Determines whether the job has a public internet protocol (IP).

• Yes

• No

Defines which network security group your task is connected to, through the elastic network interface, which is a virtual network card that controls inbound and outbound traffic.

Defines the virtual subnet, which determines the IP addresses for the task.

Defines which override container to use that overrides the default container image, command, or other settings specified in the task definition.

Defines the command to run in the container that overrides any command specified in the task definition.

Defines the environment variables for the container, which are used to manage the container and pass information to the application that runs inside it.

Determines whether the logs from the AWS ECS platform appear at the end of the Control-M job output.

• Get Logs

• Don't Get Logs

Determines the number of seconds to wait before checking the status of the job.

Default: 10

Determines the authorization credentials that are used to connect Control-M to Azure Batch Accounts.

Rules:

• Characters: 1−30

• Case sensitive: Yes

• Invalid characters: Blank spaces.

Defines the name of the job that is created in Azure Portal.

Defines a prefix that is added to the task ID.

Defines the commands that the job performs.

Determines the maximum amount of time the job runs, as follows:

• Unlimited

• Custom

Variable name: %%AWS-BATCH_ WALLCLOCK

Defines the Custom maximum number of seconds, minutes, hours, or days the job runs.

Default: 1

Determines the Custom units used to define the maximum amount of time the job runs.

• Seconds

• Minutes

• Hours

• Days

Default: Minutes

Determines the maximum number of times to rerun a failed job, as follows:

• None

• Unlimited

• Custom

Default: None

Determines the Custom maximum number of times to rerun a failed job.

Default: 1

Determines the file retention period, as follows:

• Unlimited: Retains the job directory and its files indefinitely.

• Custom: Determines the number of days, hours, minutes, or seconds to retain the job directory and its files.

Default: Unlimited

Determines the number of seconds, minutes, hours, or days to set the Custom file retention period for.

Default: 1

Determines the unit of time used to set the Custom file retention period for.

• Seconds

• Minutes

• Hours

• Days

Default: Hours

Determines whether to add the job log to the outputA tab in the job properties pane in the Monitoring domain that shows the output of a job, which indicates whether a job ended OK, and used, for example, with jobs that check file location.

Determines the authorization credentials that are used to connect Control-M to Azure Functions.

Rules:

• Characters: 1−30

• Case sensitive: Yes

• Invalid characters: Blank spaces.

Variable name: %%AZURE-ACCOUNT

Defines the name of the Azure function application that you want to run.

Defines the name of the function that you want to run.

Defines the function parameters, in JSON format, that enable you to control the presentation of data.

{ 
  "param1":"value1",
  "param2":"value2"
}

For no parameters, type {}.

Determines which of the following types of Azure functions to run:

• Activity: The basic unit of work in a durable function and that can be called by an orchestrator function.

• HTTP: An HTTP-triggered function that can be used to build serverless APIs and respond to webhooks. You cannot call an orchestrator function from an HTTP function.

• Orchestrator: A type of durable function that enables you to determine how and in what order actions are executed.

Determines the number of times to check the job status before ending Not OK.

Default: 2

Determines the authorization credentials that are used to connect Control-M to Azure VM.

Rules:

• Characters: 1−30

• Case sensitive: Yes

• Invalid characters: Blank spaces.

Defines the name of the Azure Virtual Machine to run the operation.

Determines one of the following operations to perform on the Azure Virtual Machine

• Create\Update: Creates a new virtual machine.

• Delete: Deletes an existing virtual machine.

• Deallocate: Empties a virtual machine.

• Reset: Resets a virtual machine.

• Start: Starts a virtual machine.

• Stop: Stops a running virtual machine.

Defines the input parameters in JSON format for a Create operation.

{"param1":"value1", "param2", "value2", …}

Determines whether to display logs from Azure VM at the end of the job output.

This parameter is available for all operations except for the Delete operation.

Determines whether to delete the Azure Virtual Machine disk when you delete an Azure Virtual Machine.

Determines the number of seconds to wait before job status verification.

Default: 15 seconds

Determines the authorization credentials that are used to connect Control-M to GCP Batch.

Rules:

• Characters: 1−30

• Case sensitive: Yes

• Invalid characters: Blank spaces.

Defines the GCP project ID where the batch job runs.

A project is a set of configuration settings that define the resources your GCP Batch jobs use and how they interact with GCP.

Defines the region that is predefined in the GCP Batch platform where the virtual machine resources are located.

Determines whether to override the predefined region in the GCP Batch platform, as follows:

• Yes

• No

Default: No

Defines the new region, or zones in a region, where the virtual machine resources are located.

Defines a unique name for the batch job.

Determines the run priority of the batch job.

Larger numbers indicate higher priority.

Valid Values: Any number between 1 and 99.

Default: 99

Determines one of the following types of batch jobs:

• Script: Runs a UNIX shell scripting language.

• Container: Creates a Docker container from an image.

Defines the shell script that the batch job runs.

Defines the Uniform Resource Identifier (URI) that points to the container image.

Defines the entry point (ENTRYPOINT) for the Docker container, which overrides the entry point defined in the original image.

An entry point is the location in the container where the program begins its execution.

"/bin/project"

Determines whether to override the Docker command (CMD), which is the executable container application code that is defined in the original image, as follows.

• Yes

• No

Default: No

Defines the Docker command (CMD) that executes when a Docker container runs.

If the container image contains an entry point or if an entry point is defined in the Entry Point attribute above, the command is appended as an argument.

Defines the file or directory to copy (mount) onto a container volume, which is a virtual hard drive, inside the Docker container.

/home/usr:/app/

Determines the number of millicores of virtual CPU resources that are reserved for the batch job.

Virtual machines measure CPU resources in millicores (m), which are thousandths of a CPU core. For example, 2000m equals 2 cores.

Determines the number of mebibytes (MiB; mega binary bytes) of virtual memory resources that are reserved for the batch job.

Determines the number of times to retry a job run when it fails.

Valid Values: Any number between 0 and 10.

Default: 0

Determines which kind of virtual machine (instance) runs the job.

• Machine Type: Runs the job on one of the virtual machine types available in the Google Compute Engine (GCE), which is the infrastructure-as-a-service component of GCP.

• Machine Template: Runs the job on a custom-made virtual machine, based on a predefined template in the GCE.

Defines the virtual machine type that runs the job.

Defines the virtual machine template that runs the job.

Determines the price and availability of virtual machine resources, as follows:

• Standard: Allocates virtual machine resources to the user and is used for production-level jobs.

• Spot: Allocates virtual machine resources only when there is excess capacity in the Google Compute Engine (GCE). These resources disappear when they are needed by other users, which might prevent a job from running or cause it to fail.

Default: Standard

Determines whether save the batch job logs and where they appear.

• No Logs: The batch job logs are not saved in the GCP Batch platform or in the Control-M Log in the Monitoring domain.

• Cloud Logging: The batch job logs are saved in both the GCP Batch platform and the Control-M Log in the Monitoring domain.

Determines whether you supply your own JSON parameters.

Defines the parameters for the batch job, in JSON format, that enable you to control how the job runs.

For a description of this JSON syntax, see the description of Resource:Job in the GCP Batch Job API Reference.

{
"priority": "99",
"taskGroups": [
		{
"taskSpec": {
"computeResource": {
"cpuMilli": "1000",
"memoryMib": "1000"
				},
"runnables": [
					{
"script": {
"text": "Total tasks: ${BATCH_TASK_COUNT}"
						}
					}
				]
			},
"taskCount": "1",
"parallelism": "1"
		}
	],
"allocationPolicy": {
"location": {
"allowedLocations": [
"regions/us-east1",
"zones/us-east1-b",
"zones/us-east1-c",
"zones/us-east1-d"
			]
		},
"labels": {
"batch-job-id": "guy3"
		},
"instances": [
			{
"policy": {
"machineType": "e2-micro",
"provisioningModel": "STANDARD"
				}
			}
		]
	},
"logsPolicy": {
"destination": "CLOUD_LOGGING"
	}
}

Determines the authorization credentials that are used to connect Control-M to GCP VM.

Rules:

• Characters: 1−30

• Case sensitive: Yes

• Invalid characters: Blank spaces.

Defines the project ID of the Google Cloud Project Virtual Machine.

Defines the name of the zone for the request.

Example: us-central1-f

Determines one of the following operations to perform on the Google Virtual Machine:

• Create: Creates a virtual machine

• Create from template: Creates a new virtual machine based on a template.

• Start: Starts an existing virtual machine.

• Stop: Stops a running virtual machine.

• Reset: Resets a virtual machine.

• Delete: Deletes an existing virtual machine.

Defines the name of a template for creation of a new Google Virtual Machine from a template.

Defines the name of the VM instance where you want to run the operation.

This parameter is available for all operations except for the Create operations.

Defines the input parameters in JSON format for a Create operation.

{"param1":"value1", "param2", "value2", …}

Determines whether to display logs from Google VM at the end of the job output.

This parameter is available for all operations except for the Delete operation.

Determines the number of seconds to wait before job status verification.

Default: 15