Data Integration Jobs

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

Rules:

• Characters: 1−30

• Case sensitive: Yes

• Invalid characters: Spaces

Defines the AWS Glue job name that you want to run. After you create an AWS Glue pipeline, it is saved as a jobname and you can run it.

Determines whether to add arguments to the AWS Glue job.

Defines the AWS Glue job runtime parameters

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

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

Rules:

• Characters: 1−30

• Case sensitive: Yes

• Invalid characters: Spaces

• Variable Name: %%AZURE-ACCOUNT

Determines the Azure Resource Group that is associated with a specific data factory. 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.

Determines the name of the Azure Data Factory that contains the pipeline you want to run.

Determines which data pipeline runs when the Control-M job is executed.

Defines specific parameters in JSON format that are passed when the Data Pipeline runs.

Format: {"var1":"value1", "var2":"value2"}

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

Defines the name of a pipeline that you defined in your Azure Synapse workspace.

Defines pipeline parameters to override when the job runs, defined in JSON format as pairs of name and value, as follows::

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

For no parameters, specify {}.

Determines the authorization credentials that are used to connect Control-M to Boomi AtomSphere.

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

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

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

Default: 20 seconds

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

Rules:

• Characters: 1−30

• Case sensitive: Yes

• Invalid characters: Spaces

Variable Name: %%INF-ACCOUNT

Defines the Repository Folder containing the workflow that you want to run.

Variable Name: %%INF-REP_FOLDER

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

Variable Name: %%INF-WORKFLOW

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

Variable Name: %%INF-INSTANCE_NAME

Enables you to specify an OS profile when running or rerunning an Informatica job.

Defines options regarding the workflow task hierarchy.

Determines the number of levels within the workflow task hierarchy that is used to select workflow tasks.

Default: 10

Variable Name: %%INF- DEPTH

Determines whether to run the whole workflow, start from a specific task, or run a single task as follows:

• Run the whole workflow: Runs the whole workflow.

• Start from task: Starts the workflow from the task that you specify.

  Variable Name: %%INF- START_FROM_TASK

• Run single task: Runs the task that you specify.

  Variable Name: %%INF-RUN_SINGLE_TASK

Determines an array of parameters that is passed to the workflow.

Each parameter is comprised of the following:

• Scope: Defines the scope of the parameter in an array definition.

• Name: Defines the parameter name in an array definition.

• Value: Defines the parameter value in an array definition.

Determines whether to include the workflow event log in the job 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 whether to include a detailed error log for a workflow that failed.

Determines whether to retrieve session statistics and log messages.

Determines which operation is executed when the workflow is in a suspended status, as follows:

• Recover: Restarts suspended workflow from point of failure

• Force restart: Restarts a suspended workflow from the beginning.

• Force restart from a specific task: Restarts the suspended workflow that you define

  Variable Name: %%INF- RESTART_FROM_TASK

Determines the authorization credentials that are used to connect Control-M to Informatica Cloud Services.

Rules:

• Characters: 1−30

• Case sensitive: Yes

• Invalid characters: Spaces

Variable Name: %%INF-ACCOUNT

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

• Mapping Task

• Masking Task

• PowerCenter Task

• Replication Task

• Synchronization Task

• Linear Taskflow

• Taskflow

Defines the name of the task to execute on Informatica Cloud.

This parameter is not relevant for a taskflow.

Defines the Service URL of the taskflow to execute on Informatica Cloud.

In Informatica Data Integration, you can obtain this Service URL through the Properties Detail option of the taskflow.

Defines input fields for a taskflow.

Format: input1=value1&input2=value2&input3=value3

(Optional) Defines a publicly available URL to which to post the job status.

Determines the authorization credentials that are used to connect Control-M to Talend Data Management.

Rules:

• Characters: 1−30

• Case sensitive: Yes

• Invalid characters: Spaces

Determines one of the following options for execution in Talend:

• Execute Task

• Execute Plan

Defines the name of the Talend task or plan to execute, as defined in the Tasks and Plans page in the Talend Management Console.

(For a task) Defines specific parameters to pass when the Talend job runs, defined as JSON pairs of parameter name and value. All parameter names must contain the parameter_ prefix.

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

For no parameters, specify {}.

(For a task) Determines one of the following levels of detail in log messages for the triggered task in the Talend Management Console:

• Information — All logs available

• Warning — Only warning logs

• Error — Only Error logs

• Off — No logs

(For a task) Determines whether to show Talend log messages in the job output.

Values: checked|unchecked

Default: unchecked