Data Integration Jobs

Defines the ConnectionProfile:Airbyte name that connects Control-M to Airbyte.

Defines the Airbyte Connection ID, which identifies which data pipeline to execute.

In Airbyte, a data pipeline copies data from a source to a destination.

Determines one of the following Airbyte actions to perform:

• Sync: Reads from a source and writes to a destination, depending upon the predefined sync mode in the Airbyte platform.

• Reset: Deletes all the records from your destination and then performs a sync.

Determines whether to append the API REST response to the output.

Valid Values:

• checked

• unchecked

Default: unchecked

(Optional) Determines the number of seconds to wait before checking the status of the job between intervals.

Default: 60

Defines the ConnectionProfile:AWS Glue name that connects Control-M to AWS Glue.

Defines the name of the AWS Glue job that you want to execute.

Determines whether to specify arguments to pass when you run the AWS Glue job, as defined in Arguments.

Valid Values:

• checked

• unchecked

Default: unchecked

(Optional) Defines specific arguments to pass when you run the AWS Glue job, as shown in the following example:

{\"--myArg1\": \"myVal1\", \"--myArg2\": \"myVal2\"}

For more information about the available arguments, see Special Parameters Used by AWS Glue in the AWS documentation.

(Optional) Defines the number of seconds to wait before checking the status of the job.

Default: 30

Defines the ConnectionProfile:AWS Glue DataBrew name that connects Control-M to AWS Glue DataBrew.

Defines the AWS Glue DataBrew job name.

Determines whether the DataBrew job logs are included in the Control-M output.

Valid Values:

• checked

• unchecked

Default: unchecked

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

Default: 10

Defines the ConnectionProfile:ADF (Azure Data Factory) name that connects Control-M to Azure Data Factory.

Defines an Azure Resource Group that is associated with a specific data factory pipeline. A resource group is a container that holds related resources for an Azure solution. The resource group can include all the resources for the solution, or only those resources that you want to manage as a group.

Defines an Azure Data Factory Resource to use to execute the pipeline.

Defines the data pipeline to run when the job is executed.

Defines specific name-and-value-pair parameters to pass when the Data Pipeline runs, as shown in the following example:

 <\"var1\":\"value1\", \"var2\":\"value2\">

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

Default: 45

Defines the ConnectionProfile:Boomi name that connects Control-M to Boomi.

Defines the name of a Boomi Atom associated with the Boomi process.

Defines the name of a Boomi process associated with the Boomi Atom.

(Optional) Number of seconds to wait before checking the status of the job.

Default: 20

Defines the ConnectionProfile:GCPDF (GCP Data Fusion) name that connects Control-M to GCP Data Fusion.

Determines the region where the GCP Data Fusion job executes.

Defines the name of the predefined Google Cloud project that holds your configured APIs, authentication information, billing details, and job resources.

Defines the name of the predefined virtual machine (instance) that executes your job.

Defines the name of the namespace, which contains the job, job data, and metadata.

Valid Characters: A–Z, a–z, 0–9, and _.

Default: default

Defines the name of a predefined ETL or data integration pipeline in GCP Data Fusion.

Defines the JSON-based body parameters that are passed to the function, as follows:

"argument" : {\"var1\":\"value1\",\"var2\":\"value2\"}

Determines whether to append the GCP Data Fusion logs 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..

Valid Values:

• checked

• unchecked

Default: unchecked

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

Default: 10

Defines the ConnectionProfile:GCP Dataplex name that connects Control-M to GCP Dataplex.

Defines the ID of the predefined Google Cloud project that holds your configured APIs, authentication information, billing details, and job resources.

Determines the region where the GCP Dataplex job executes.

Determines one of the following GCP Dataplex actions to perform:

• Data Quality Task: Executes a predefined data quality task in GCP BigQuery or Google Cloud Storage locations and defines data controls in BigQuery environments.

• Custom Spark Task: Executes a predefined, scheduled Apache Spark task to analyze and process your data.

• Data Profiling Scan: Executes a predefined data scan to identify shared statistical characteristics between BigQuery tables.

• Data Quality Scan: Executes a predefined data quality scan that validates your data and logs alerts when the data fails validation.

(Data Quality Task and Custom Spark Task actions only) Defines the name of the Google Cloud Storage data lakes where the job executes its task.

(Data Quality Task and Custom Spark Task actions only) Defines the name of the predefined task that the job executes.

(Data Profiling Scan and Data Quality actions only) Defines the name of the predefined scan that the job executes.

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

Default: 15

Defines the ConnectionProfile:GCP Dataprep name that connects Control-M to GCP Dataprep.

Defines the name of the flow, which is the workspace where you format and prepare your data.

Defines parameters that override the flow or its data sets when the job executes.

For more information on parameter types, see the properties of runFlow service in the GCP Dataprep API documentation.

Determines whether to execute the job with an idempotency token.

Valid Values:

• checked

• unchecked

Default: unchecked

Defines a unique ID (idempotency token), which guarantees that the job executes only once.

Default: Control-M-Idem-%%ORDERID

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

Default: 10

Defines the ConnectionProfile:Informatica name that connects Control-M to Informatica.

Defines the Repository folder that contains the workflow that you want to run.

Defines the workflow that you want to run in Control-M for Informatica.

(Optional) Defines the specific instance of the workflow that you want to run.

(Optional) Defines the operating system profile in Informatica.

Defines the mode for executing the workflow, one of the following:

• RunWholeWorkflow: Runs the whole workflow.

• StartFromTask: Starts running the workflow from a specific task, as specified by the StartFromTask parameter.

• RunSingleTask: Runs a single task in the workflow, as specified by the RunSingleTask parameter.

Defines the task from which to start running the workflow.

This parameter is required only if you set WorkflowExecutionMode to StartFromTask.

Defines the workflow task that you want to run.

This parameter is required only if you set WorkflowExecutionMode to RunSingleTask.

Determines the number of levels within the workflow task hierarchy for the selection of workflow tasks.

Default: 10

Determines whether to include the workflow events log in the job output.

Valid Values:

• true

• false

Default: true

Determines whether to include a detailed error log for a workflow that failed.

Valid Values:

• true

• false

Default: true

Determines one of the following operations to execute when the workflow is in a suspended satus:

• Recover: Recovers the suspended workflow.

• ForceRestart: Forces a restart of the suspended workflow.

• ForceRestartFromSpecificTask: Forces a restart of the suspended workflow from a specific task, as specified by the RestartFromTask parameter.

Defines the task from which to restart a suspended workflow.

This parameter is required only if you set WorkflowRestartMode to ForceRestartFromSpecificTask.

Defines the ConnectionProfile:Informatica CS name that connects Control-M to Informatica Cloud.

Determines one of the following task types to run on Informatica Cloud:

• Mapping Task: A set of instructions that defines how data is transformed and moved from its source to its target system.

• Masking Task: A data security technique that enables you to protect sensitive data while allowing it to be used for non-production purposes.

• PowerCenter Task: A data integration tool that enables you to extract, transform, and load data from different sources into a unified target system.

• Replication Task: A data replication solution that enables you to replicate and synchronize data across different systems and databases in real time.

• Synchronization Task: A data integration solution that enables you to synchronize data between different systems and databases, ensuring that data is consistent and up-to-date across all systems.

• Linear Taskflow: A workflow automation feature that enables you to create and automate a sequence of tasks that are executed in a specific order, which helps streamline data integration and processing tasks.

• Taskflow: A workflow automation feature that enables you to create complex workflows that orchestrate and automate data integration and processing tasks across multiple systems and platforms.

Determines whether to identify the task using a Federated Task ID, which is a unique identifier that is used track and manage tasks across distributed environments in a federated environment. This ID is generated by the Informatica domain and is important for monitoring and troubleshooting tasks. This parameter is not required when you run a taskflow.

Valid Values:

• checked

• unchecked

Default: unchecked

Defines the name of the task that executes on Informatica Cloud.

This parameter is not required when you run a taskflow or use a Federated Task ID.

Defines the folder path of the task that executes on Informatica Cloud.

This parameter is required if you are using a Federated Task ID.

Defines the service URL of the taskflow that executes on Informatica Cloud.

You can find this URL by clicking in the top, right corner of the TaskFlow main page of Informatica Data Integrator and clicking Properties Detail....

Defines input fields for a taskflow, expressed as input=value pairs separated by the & character.

(Optional) Defines a publicly available URL where the job status is posted.

Determines whether to rerun a suspended taskflow.

Valid Values:

• checked

• unchecked

Default: unchecked

Defines the Run ID to rerun a suspended taskflow.

The Run ID is unique to each job run and is available in the job output, next to the variable name RUN-UCM-RUNID.

Determines the Connection Profile:OCI Data Integration name that connects Control-M to OCI Data Integration.

Determines one of the following OCI Data Integration actions:

• Start Workspace: Activates the OCI Data Integration Workspace with the Workspace OCID

• Stop Workspace: Deactivates the OCI Data Integration Workspace with the Workspace OCID.

• Run Task: Executes the Oracle dataflow task on the active OCI Data Integration Workspace and defines the task parameters.

Determines the ID of the OCI Data Integration workspace, which is a logical container for managing pipelines, data flows, and projects.

Defines the Application Key which identifies the project application where the task runs.

Determines the Task Key that is used to run the job.

Defines the unique name for the specific task run.

(Optional) Defines the input parameters for the specific task run, in JSON format.

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

Default: 15

Defines the ConnectionProfile:Talend Data Management name that connects Control-M to Talend Data Management.

Determines one the following operations to perform:

• Execute Task: Executes a Talend job.

• Execute Plan: Executes a Talend workflow.

(Execute Task) Defines the name of the Talend task that is executed, as defined in the Tasks and Plans page in the Talend Management Console.

(Execute Task) Defines the ID of the Talend task that is executed, as defined in the Tasks and Plans page in the Talend Management Console.

(Execute Task) Defines specific parameters, in JSON format, to pass when the Talend job executes.

All parameter names must contain a parameter_ prefix, as appears in the following example:

{"parameter_param1":"value1", "parameter_param2":"value2"}

For no parameters, type {}.

(Execute Task) Determines the amount of log details are recorded in the Talend task logs, as follows:

• Information: Records all task execution details in the logs.

• Warning: Only records warnings.

• Error: Only records errors.

• Off: Records no information in the logs.

(Execute Task) Determines whether to append Talend log messages to the job output.

Valid Values:

• checked

• unchecked

Default: uncheckeds

(Execute Task) Determines the number of seconds to wait before checking the status of the triggered task.

Default: 10

(Execute Plan) Defines the name of the Talend plan that is executed, which is defined in the Tasks and Plans page in the Talend Management Console.

(Execute Plan) Defines the specific parameters, in JSON format, that are passed to Talend when the job executes, as shown in the following example:

{
  "executable": "b91cf8b2-5dd1-4b18-915b-4c447cee5267",
  "rerunOnlyFailedTasks": true,
  "stepId": "09043c9f-02d0-41f6-b3cb-0ea53ffde377"
}

where executable is the Plan ID.

(Execute Plan) Determines whether Talend logs are appended to the output when the plan fails to execute.

Default: Unchecked

Defines the a Connection Profile:Talend OAuth name that connects Control-M to Talend OAuth.

Determines one of the following actions to perform:

• Execute Task by ID: Executes a Talend task (job) by Task Executable (ID).

• Execute Task by Name: Executes a Talend task (job) by Name.

• Execute Plan: Executes a Talend plan (workflow).

Defines the Environment ID where the task is executed.

Defines the name of the predefined Talend task that is executed, as defined in the Tasks and Plans page in the Talend Management Console.

Defines the ID of the predefined Talend task that is executed, as defined in the Tasks and Plans page in the Talend Management Console.

Defines specific parameters, in JSON format, to pass when the Talend job executes.

{"custom_message":"Talend test", "number_of_message": 4, "sleep_time": 100 }

For no parameters, type {}.

Determines the amount of log details that are recorded in the Talend task logs, as follows:

• Information: Records all task execution details in the logs.

• Warning: Records warnings.

• Error: Records errors.

• Off: Records no information in the logs.

(Optional) Determines the number of minutes to wait before the task is executed.

Determines whether to append the Talend logs to the job output when the plan fails during the execution.

Valid Values:

• Checked

• Unchecked

Default: Unchecked

Defines the Plan executable that you want to execute, as defined in the Tasks and Plans page in the Talend Management Console.

Determines whether to append the failed Talend Plan logs in the job output when the plan fails during the execution.

Valid Values:

• Checked

• Unchecked

Default: Unchecked

(Optional) Determines whether to rerun only the failed tasks.

Valid Values:

• Checked

• Unchecked

Default: Unchecked

(Optional) Defines the ID for there-run plan.

(Optional) Defines the step that the task re-runs.

Determines the number of seconds to wait before Control-M checks the status of the job or the job's output.

Default :10

Defines the ConnectionProfile:TRIFACTA name that connects Control-M to Alteryx Trifacta.

Determines which Alteryx Trifacta flow the job runs.

Determines whether to allow rerun of the job in Alteryx Trifacta with a new idempotency token (for example, when the job run times out).

Valid Values:

• checked

• unchecked

Default: unchecked

Defines a unique ID (idempotent token), which guarantees that the job executes only once.

To allow rerun of the job with a new token, replace the default value with a unique ID that has not been used before. Use the RUN_ID, which can be retrieved from the job output.

Default: Control-M-Idem_%%ORDERID

Determines whether to track job run status as the job execution and status changes, for example—from in-progress to failed or to completed.

Valid Values:

• checked

• unchecked

Default: unchecked

Defines the RUN_ID number for the job run to be tracked.

The RUN_ID is unique to each job run and it can be found in the job output.