Connection Profiles

Connection profiles are used to define access methods and security credentials for a specific application. They can be referenced by multiple jobs. To do this, you must deploy the connection profile definition before running the relevant jobs.

Note: For most types of connection profiles (except for File Transfer connection profiles), the name of the connection profile can contain only the following types of characters: uppercase letters, numbers, hyphens, and underscores. The connection profile name can contain up to 30 characters.

ConnectionProfile:Hadoop

These examples show how to use connection profiles for the various types of Hadoop jobs.

Hadoop (all types)

These are the required parameters for all Hadoop job types.

{
"HADOOP_CONNECTION_PROFILE":
{
   "Type" : "ConnectionProfile:Hadoop",
   "TargetAgent" : "edgenode",
   "TargetCTM" : "CTMHost"
}
}

Parameter	Description
TargetAgent	The Control-M/Agent to which to deploy the connection profile.
TargetCTM	The Control-M/Server to which to deploy the connection profile. If there is only one Control-M/Server, that is the default.

These are the optional parameters for defining the user running the Hadoop job types and choosing between a local or centralized connection profile.

{
"HADOOP_CONNECTION_PROFILE":
{
   "Type" : "ConnectionProfile:Hadoop",
   "TargetAgent" : "edgenode",
"TargetCTM" : "CTMHost",
   "RunAs": "",
   "KeyTabPath":"",
   "Centralized":true
}
}

RunAs	Defines the user of the account on which to run Hadoop jobs. Leave this field empty to run Hadoop jobs using the user account where the agent was installed. The Control-M/Agent must run as root, if you define a specific RunAs user.
Centralized	9.0.20.000 Whether to create the connection profile as a centralized connection profile that is stored in the Control-M database and is available to all Control-M/Agents (version 9.0.20 or later). Either true or false. The default is false, that is, the connection profile is created as a local connection profile that is associated with a specific agent and is stored on that agent.

In the case of Kerberos security, the following parameters control security:

RunAs	Principal name of the user
KeyTabPath	Keytab file path for the target user

Apache Spark

The following example shows a connection profile that defines access to a Spark server.

{
"SPARK_CONNECTION_PROFILE" :
{
   "Type" : "ConnectionProfile:Hadoop",
   "TargetAgent" : "docker-hadoop5",
   "Spark" :
   {
     "CustomPath" : "/home"
   }
}
}

The CustomPath parameter is optional.

Apache Oozie

The following example shows a connection profile that defines access to an Oozie server.

{
"OOZIE_CONNECTION_PROFILE" :
{
   "Type" : "ConnectionProfile:Hadoop",
   "TargetAgent" : "hdp-ubuntu",
   "Centralized" : false,
   "Oozie" :
   {
     "SslEnabled"     : false,
     "Host" : "hdp-centos",
     "Port" : "11000",
     "ExtractionRules": [
     {
       "RuleName" : "rule_name1",
       "WorkFlowName" : "work_flow_name1",
       "WorkFlowUserName" : "work_flow_user_name1",
       "FolderName" : "folder_name1",
       "JobName" : "job_name1"
      },
     {
       "RuleName" : "rule_name2",
       "WorkFlowName" : "work_flow_name2",
       "WorkFlowUserName" : "work_flow_user_name2",
       "FolderName" : "folder_name2",
       "JobName" : "job_name2"
      }
      ]
  }
}
}

Parameter	Description
Host	Oozie server host
Port	Oozie server port Default: 11000
SslEnabled	true \| false Default: false
ExtractionRules	9.0.20.010(Optional) Definitions of rules for filtering Oozie workflows. Each rule has the following definitions:
RuleName	Name of the rule
WorkFlowName	Name of the Oozie workflow to get from the Oozie server
WorkFlowUserName	Name of the user that runs the workflows from the Oozie server
FolderName	Name of the folder that contains the Hadoop job of the Oozie Extractor, as defined in the Hadoop job template
JobName	Name of the Hadoop job of the Oozie Extractor, as defined in the Hadoop job template

Apache Sqoop

The following example shows a connection profile that defines a Sqoop data source and access credentials.

{
"SQOOP_CONNECTION_PROFILE" :
{
   "Type" : "ConnectionProfile:Hadoop",
   "TargetAgent" : "edgenode",
   "TargetCTM" : "CTMHost",
   "Centralized" : false,
   "Sqoop" :
   {
     "User"     : "username",
     "Password" : "userpassword",
     "ConnectionString" : "jdbc:mysql://mysql.server/database",
     "DriverClass" : "com.mysql.jdbc.Driver"
   }
}
}

The following table describes the parameters in the example above, as well as several additional optional parameters:

Parameter	Description
User	The database user connected to the Sqoop server
Password	A password for the specified user If you are updating an existing connection profile and do not want to change the existing password, enter a string of 5 asterisk characters, "*****".
ConnectionString	JDBC-compliant database: The connection string used to connect to the database
DriverClass	JDBC-compliant database: The driver class for the driver .jar file, which indicates the entry-point to the driver
PasswordFile	(Optional) The full path to a file located on the HDFS that contains the password to the database Note: To use a JCEKS file, include the .jceks file extension.
DatabaseVendor	(Optional) The database vendor of an automatically supported database used with Sqoop, one of the following: MySQL Oracle (SID) Oracle (Service Name) PostgreSQL
DatabaseName	(Optional) Name of an automatically supported database used with Sqoop
DatabaseHost	(Optional) The host server of an automatically supported database used with Sqoop
DatabasePort	(Optional) The port number for an automatically supported database used with Sqoop

Apache Tajo

The following example shows a connection profile that defines access to a Tajo server. Tajo is an advanced data warehousing system on top of HDFS.

{
"TAJO_CP" :
{
   "Type" : "ConnectionProfile:Hadoop",
   "TargetAgent" : "edgenode",
   "Tajo":
   {
     "BinaryPath": "$TAJO_HOME/bin/",
     "DatabaseName": "myTajoDB",
     "MasterServerName" : "myTajoServer",
     "MasterServerPort": "26001"
   }
}
}

Parameter	Description
BinaryPath	Path to the bin directory where tsql utility is located
DatabaseName	Name of the Tajo database
MasterServerName	Host name of the server where the Tajo master is running
MasterServerPort	Tajo master port number

Apache Hive

The following example shows a connection profile that defines a Hive beeline endpoint and access credentials. The parameters in the example translate to this beeline command:

beeline -u jdbc:hive2://<Host>:<Port>/<DatabaseName>

{
"HIVE_CONNECTION_PROFILE" :
{
   "Type" : "ConnectionProfile:Hadoop",
   "TargetAgent" : "edgenode",
   "TargetCTM" : "CTMHost",
   "Hive" :
   {
      "Host" : "hive_host_name",
      "Port" : "10000",
      "DatabaseName" : "hive_database",
   }
}
}

The following shows how to use optional parameters for a Hadoop Hive job type connection profile.

The parameters in the example translate to this beeline command:

beeline -u jdbc:hive2://<Host>:<Port>/<DatabaseName>;principal=<Principal> -n <User> -p <Password>

{
  "HIVE_CONNECTION_PROFILE1":
  {
    "Type" : "ConnectionProfile:Hadoop",
    "TargetAgent" : "edgenode",
    "TargetCTM" : "CTMHost",
    "Centralized" : true,
    "Hive" :
    {
       "Host" : "hive_host_name",
       "Port" : "10000",
       "DatabaseName" : "hive_database",
       "User" : "user_name",
       "Password" : "user_password",
       "Principal" : "Server_Principal_of_HiveServer2@Realm"
    }
  }
}

If you are updating an existing connection profile and do not want to change the existing password, enter a string of 5 asterisk characters, "*****".

TargetAgent	Which agent computer to deploy the connection profile
TargetCTM	The Control-M/Server to which to deploy the connection profile. If there is only one Control-M/Server, that is the default.
WorkloadAutomationUsers	(Optional) Users that are allowed to access the connection profile. Relevant only for local connection profiles. NOTE : You can use "" as a wildcard. For example, "e" Default: * (all users)
WorkloadAutomationGroups	(Optional) Control-M roles (groups of users) that are allowed to access the connection profile. Relevant only for local connection profiles. NOTE: You can use "" as a wildcard. For example, "e" Default: Empty (no roles specified)
VerifyChecksum	(Optional) Enable or disable error detection on file transfer true \| false Default: false
VerifyDestination	(Optional) Verify the size of the file at the destination after a successful binary-mode transfer. true \| false Default: true
VerifyBytes	(Optional) Verify that the number of bytes sent to the destination during a successful binary-mode transfer is the same as the source file. If it is not the same size, the transfer fails. true \| false Default: false
PrivateKeyName	(Optional) Private key full file path
Passphrase	(Optional) Password for the private key. Use Secrets in code to not expose the password in the code. If you are updating an existing connection profile and do not want to change the existing password, enter a string of 5 asterisk characters, "*****".
Password	(Optional) Password for SFTP Server account. Use Secrets in code to not expose the password in the code. If you are updating an existing connection profile and do not want to change the existing password, enter a string of 5 asterisk characters, "*****".
HomeDirectory	(Optional) User home directory
SSHCompression	(Optional) Whether to compress the file before the transfer. true \| false Default: false
Centralized	9.0.20.000 Whether to create the connection profile as a centralized connection profile that is stored in the Control-M database and is available to all Control-M/Agents (version 9.0.20 or later). Either true or false. The default is false, that is, the connection profile is created as a local connection profile that is associated with a specific agent and is stored on that agent.
AdditionalParameters	9.0.19.220 (Optional) Additional parameters that are specific to your environment and you can add manually. Each parameter is defined by its name and value. For an updated list of parameters that are supported by Control-M for MFT, see Connection Profile Manual Additional Parameters (in the Control-M Online Help).

TargetAgent	The Control-M/Agent to which to deploy the connection profile.
Region	The region in which the Amazon S3 storage bucket is located. Specify one of the following regions: us-gov-west-1 ap-northeast-1 ap-northeast-2 ap-south-1 ap-southeast-1 ap-southeast-2 ca-central-1 eu-central-1 eu-west-1 eu-west-2 eu-west-3 sa-east-1 us-east-1 us-east-2 us-west-1 us-west-2 cn-north-1 cn-northeast-1
AccessKey	The access key to the Amazon S3 storage.
SecretAccessKey	The secret access key to the Amazon S3 storage. Use Secrets in code to not expose this secret access key in the code.
VerifyDestination	(Optional) Verify the size of the file at the destination after a successful binary-mode transfer. true \| false Default: true
Centralized	9.0.20.000 Whether to create the connection profile as a centralized connection profile that is stored in the Control-M database and is available to all Control-M/Agents (version 9.0.20 or later). Either true or false. The default is false, that is, the connection profile is created as a local connection profile that is associated with a specific agent and is stored on that agent.
AdditionalParameters	9.0.19.220 (Optional) Additional parameters that are specific to your environment and you can add manually. Each parameter is defined by its name and value. For an updated list of parameters that are supported by Control-M for MFT, see Connection Profile Manual Additional Parameters (in the Control-M Online Help).

TargetAgent	The Control-M/Agent to which to deploy the connection profile.
RestEndPoint	The network address where the S3 Compatible Storage is located.
AccessKey	The access key to the S3 Compatible storage.
SecretAccessKey	The secret access key to the S3 Compatible storage. Use Secrets in code to not expose this secret access key in the code.
VerifyDestination	(Optional) Verify the size of the file at the destination after a successful binary-mode transfer. true \| false Default: true
Centralized	9.0.20.000 Whether to create the connection profile as a centralized connection profile that is stored in the Control-M database and is available to all Control-M/Agents (version 9.0.20 or later). Either true or false. The default is false, that is, the connection profile is created as a local connection profile that is associated with a specific agent and is stored on that agent.
AdditionalParameters	9.0.19.220 (Optional) Additional parameters that are specific to your environment and you can add manually. Each parameter is defined by its name and value. For an updated list of parameters that are supported by Control-M for MFT, see Connection Profile Manual Additional Parameters (in the Control-M Online Help).

Region	Determines the region in which the Amazon S3 storage bucket is located: us-gov-west-1 ap-northeast-1 ap-northeast-2 ap-south-1 ap-southeast-1 ap-southeast-2 ca-central-1 eu-central-1 eu-west-1 eu-west-2 eu-west-3 sa-east-1 us-east-1 us-east-2 us-west-1 us-west-2 cn-north-1 cn-northeast-1
AccessKey	Defines the access key to the Amazon S3 storage.
SecretAccessKey	Defines the secret access key to the Amazon S3 storage. Use Secrets in code to not expose this secret access key in the code.
VerifyDestination	(Optional) Determines whether to verify the size of the file at the destination after a successful binary-mode transfer. true \| false Default: true
RestEndPoint	Defines the network address where the Amazon S3 storage is located.
TargetCTM	Defines the Control-M/Server to which to deploy the connection profile. If there is only one Control-M/Server, that is the default.
TargetAgent	Defines the Control-M/Agent to which to deploy the connection profile.
Centralized	Determines whether to create the connection profile as a centralized connection profile that is stored in the Control-M database and is available to all Control-M/Agents (version 9.0.20 or later). Either true or false. The default is false, that is, the connection profile is created as a local connection profile that is associated with a specific agent and is stored on that agent.

AzureAccountName	Defines the name of the Azure Storage account.
AzureAccountAccessKey	Defines the account access key that is used to connect to Azure.
Centralized	Determines whether to create the connection profile as a centralized connection profile that is stored in the Control-M database and is available to all Control-M/Agents (version 9.0.20 or later). Either true or false. The default is false, that is, the connection profile is created as a local connection profile that is associated with a specific agent and is stored on that agent.

AzureAccountName	Defines the name of the Azure Storage account.
AzureAccountConnectionString	Defines the entire connection string used to connect to Azure.
Centralized	Determines whether to create the connection profile as a centralized connection profile that is stored in the Control-M database and is available to all Control-M/Agents (version 9.0.20 or later). Either true or false. The default is false, that is, the connection profile is created as a local connection profile that is associated with a specific agent and is stored on that agent.

AzureAccountName	Defines the name of the Azure Storage account.
AzureTenantId	Defines the ID of the Azure Active Directory instance where your application is located.
AzureClientId	Defines the ID of your application in Azure Active Directory.
AzureUserNameAD	Defines the name of the Azure AD user to use for authentication.
AzureUserPasswordAD	Defines the password of the Azure AD user.
Centralized	Determines whether to create the connection profile as a centralized connection profile that is stored in the Control-M database and is available to all Control-M/Agents (version 9.0.20 or later). Either true or false. The default is false, that is, the connection profile is created as a local connection profile that is associated with a specific agent and is stored on that agent.

AzureAccountName	Defines the name of the Azure Storage account.
AzureAccountSaSToken	Defines the SAS token that is created for Azure limited access.
Centralized	Determines whether to create the connection profile as a centralized connection profile that is stored in the Control-M database and is available to all Control-M/Agents (version 9.0.20 or later). Either true or false. The default is false, that is, the connection profile is created as a local connection profile that is associated with a specific agent and is stored on that agent.

GCSServiceAccountKey	Defines a JSON body that contains the required service account credentials to access the Google Cloud Storage account.
GCSServiceAccountKeyFileName	Defines the name of the file that contains the service account credentials.
Centralized	Determines whether to create the connection profile as a centralized connection profile that is stored in the Control-M database and is available to all Control-M/Agents (version 9.0.20 or later). Either true or false. The default is false, that is, the connection profile is created as a local connection profile that is associated with a specific agent and is stored on that agent.

TargetAgent	The Control-M/Agent to which to deploy the connection profile.
GroupAccounts	A list of file transfer connection profiles included in the group
WorkloadAutomationUsers	(Optional) Control-M users that are allowed to access the connection profile. Relevant only for local connection profiles. NOTE: You can use "" as a wildcard. For example, "e" Default: * (all users)
WorkloadAutomationGroups	(Optional) Control-M roles (groups of users) that are allowed to access the connection profile. Relevant only for local connection profiles. NOTE: You can use "" as a wildcard. For example, "e" Default: Empty (no roles specified)

Parameter	Description
User	SAP user name
Password	Password for the SAP user If you are updating an existing connection profile and do not want to change the existing password, enter a string of 5 asterisk characters, "*****".
SapClient	SAP client number, a three-digit number
Language	The SAP language. The default is English.
XBPVersion	SAP XBP interface version installed on the SAP server Valid values are: XBP 1.0 XBP 2.0 XBP 3.0 (Default)
AppVersion	Version of the SAP application, one of the following: R3 BW 2.<X> BW 3.<X> or later
GroupLogon	Parameters for defining an SAP logon group
SystemID	SAP system ID, three alpha-numeric characters
MessageServerHostName	Host name of the computer on which the SAP System Message Server is running
GroupName	SAP logon group name The Group name is defined in the SAP SMLG transaction.
ApplicationServerLogon	Parameters for defining a specific SAP Application Server
Host	The host name of the computer that runs the SAP Application Server
SystemNumber	SAP instance number, a two-digit number
SecuredNetworkConnection	Parameters that you can use to activate a secured network connection
SncLib	Client full path and file name to SAP crypto lib For example: /home1/agsapfp/SNC/libsapcrypto.sl
SncPartnerName	SNC name of the application server For example: p:CN=LE1, OU=BPM, O=BMC, C=US
QualityOfProtection	Quality of the protection Valid values: 1, 2, 3, 8 (default), 9
SncMyName	SNC name of the user sending the RFC Default: The name provided by the security product for the user who is logged on.
SapResponseTimeOut	Number of seconds that the program waits for an RFC request to be handled by the SAP system before returning a timeout error Default: 180
UseExtended	Whether the extended functionality of Control-M for SAP should be used, either false (default) or true NOTE: If you select this option, the Control-M Function Modules must be installed on your SAP server, as described in Control-M for SAP XBP Interface and Control-M Function Modules in the Control-M for SAP online help.
SolutionManagerConnectionProfile	Solution Manager connection profile for retrieval of SAP job Documentation This parameter is relevant only if the current connection profile is not a Solution Manager connection profile, as discussed in the next parameter.
IsSolutionManagerConnectionProfile	Whether the current connection profile is a Solution Manager connection profile, either true or false (the default)

Parameter	Description
Authentication	Type of authentication to use for the connection with AWS Glue, one of the following: SECRET — authentication using an AWS access key and secret NOSECRET — authentication using an AWS IAM role from inside an EC2 instance
AWS Access key ID	(For SECRET authentication) Access key ID for connection to AWS
AWS Secret	(For SECRET authentication) Secret access key for connection to AWS
IAM Role	(For NOSECRET authentication) Identity and Access Management (IAM) role for connection to AWS
AWS Region	AWS Glue service region
Glue url	URL of an AWS Glue service regional endpoint For more information about regional endpoints available for the AWS Glue service, refer to the AWS documentation.
Connection Timeout	A timeout value, in seconds, for the trigger call made by Control-M to AWS Glue The default is 40 seconds.
Centralized	Whether to create the connection profile as a centralized connection profile that is stored in the Control-M database and is available to all Control-M/Agents (version 9.0.20 or later).Values: true\|false Default: false The AWS Glue job requires a centralized connection profile. Set this parameter to true.

Parameter	Description
Port	The database port number. If the port is not specified, the following default values are used for each database type: MSSQL - 1433 Oracle - 1521 DB2 - 50000 Sybase - 4100 PostgreSQL - 5432
Password	Password to the database account. Use Secrets in code to not expose the password in the code. If you are updating an existing connection profile and do not want to change the existing password, enter a string of 5 asterisk characters, "*****".
DatabaseName	The name of the database
DatabaseVersion	The version of the database. For a list of databases and versions supported by your version of Control-M for Databases, open the Product Availability & Compatibility page at https://customerapps.bmc.com/spac/o/welcome.html. In the Product Name field enter Control-M for Databases, and in the Product Version field select the relevant version. The default version for each database is the earliest version that is supported.
MaxConcurrentConnections	The maximum number of connections that the database can process at the same time. Allowed values: 1–512 Default value: 100
ConnectionRetryTimeOut	The number of seconds to wait before attempting to connect again. Allowed values: 1–300 Default value: 5 seconds
ConnectionIdleTime	The number of seconds that the database connection profile can remain idle before disconnecting. Default value: 300 seconds
ConnectionRetryNum	The number of times to attempt to reconnect after a connection failure. Allowed values: 1–24 Default value: 5

Parmeter	Description
Driver	JDBC driver name as defined in Control-M or as defined using the Driver object

Parameter	Description
TargetAgent	The Control-M/Agent to which to deploy the driver.
StringTemplate	The structure according to which a connection profile string is created.
DriversJarsFolder	The path to the folder where the database driver jars are located.
ClassName	Name of driver class
LineComment	The syntax used for line comments in the scripts that run on the database.
StatementSeparator	The syntax used for statement separator in the scripts that run on the database.

Parameter	Description
SkipPackageTest	Whether to skip validation of SSIS packages when testing the connection profile, either true or false
SSIS	Connection details for all associated SSIS Packages
Source	Source location of the SSIS Package — SQL Server, File System, or SSIS Package Store
Name	Name of the SSIS Package
Password	Password required for accessing the SSIS Package If you are updating an existing connection profile and do not want to change the existing password, enter a string of 5 asterisk characters, "*****".

Parameter	Description
Login URL	The URL for login calls to Informatica Cloud
Base URL	The instance name of the Informatica Cloud server
Username	Username for the account to connect to Informatica Cloud
Password	A password for the login to Informatica Cloud Use Secrets in code to not expose the password in the code. If you are updating an existing connection profile and do not want to change the existing password, enter a string of 5 asterisk characters, "*****".
Request Timeout	A timeout value, in seconds, for the requests sent to Informatica Cloud The default is 3 seconds.
Centralized	Whether to create the connection profile as a centralized connection profile that is stored in the Control-M database and is available to all Control-M/Agents (version 9.0.20 or later). Values: true\|false Default: false The Informatica Cloud Services job requires a centralized connection profile. Set this parameter to true.

Parameter	Description
Identity Type	Type of authentication to use for the connection with the Azure Data Factory, one of the following: PRINCIPAL — authentication using a service principal MANAGEDID — authentication using managed identities
Tenant ID	(For service principal authentication) The Azure Tenant ID where the Azure Data Factory was created
Client Secret	(For service principal authentication) The client secret associated with the service principal
Application ID	(For service principal authentication) ID of the Azure-registered application that is used to interact with the Azure Data Factory
Subscription ID	Azure account subscription ID The subscription ID can be retrieved from the Azure portal by selecting the Subscription menu.
Connection Timeout	A timeout value, in seconds, for the trigger call made by Control-M to the Azure Data Factory The default is 40 seconds.
Centralized	Whether to create the connection profile as a centralized connection profile that is stored in the Control-M database and is available to all Control-M/Agents (version 9.0.20 or later).Values: true\|false Default: false The ADF job requires a centralized connection profile. Set this parameter to true.

Parameter	Description
Tenant ID	The Azure Tenant ID in Azure AD
Application ID	The application (service principal) ID of the registered application. The service principal must meet the following requirements: The service principal must be an Azure Databricks workspace user and an admin. In the Databricks Admin Console, it must appear under users and also under admins. The service principal must be associated with a Contributor or Owner role.
Client Secret	The client secret (password) associated with the Azure user and the application
Databricks url	The URL of your Databricks workspace
Azure Login url	The Azure AD authentication e ndpoint base URL
Connection Timeout	A timeout value, in seconds, for the trigger call made by Control-M to Azure Databricks The default is 50 seconds.
Centralized	Whether to create the connection profile as a centralized connection profile that is stored in the Control-M database and is available to all Control-M/Agents (version 9.0.20 or later).Values: true\|false Default: false The Azure Databricks job requires a centralized connection profile. Set this parameter to true.

Parameter	Description
Authentication Method	Defines one of the following types of authentication to use for the connection with Azure Batch: PRINCIPAL — authentication using a service principal MANAGEDID — authentication using managed identities
Tenant ID	(For service principal authentication) Defines the Azure Tenant ID in Azure AD
Azure AD url	(For service principal authentication) Defines the Azure AD authentication e ndpoint base URL
App ID	Defines the application (service principal) ID of the registered application for the Azure Batch service. The service principal must be for an Azure Batch account with a Contributor role.
Batch Account Name	Defines the name of the Batch account created in Azure Portal.
Batch Region ID	Defines the region ID associated with the Batch account in Azure Portal.
Batch Resource url	Defines the identifier for the Azure Batch account for login via Azure AD. This identifier is a constant value set to https://batch.core.windows.net/
Client Secret	(For service principal authentication) Defines the client secret (password) associated with the Azure user and the application.
Connection Timeout	Defines a timeout value, in seconds, for the trigger call made by Control-M to Azure Batch Accounts. The default is 50 seconds.
Centralized	Determines whether to create the connection profile as a centralized connection profile that is stored in the Control-M database and is available to all Control-M/Agents (version 9.0.20 or later).Values: true\|false Default: false The Azure Batch job requires a centralized connection profile. Set this parameter to true.

Parameter	Description
Application ID	Defines the application ID of the registered application.
Client Secret	Defines the client secret (password) associated with the user and the application.
User Name	Defines the name of a user for logging on to the Power BI platform, typically an email address.
Password	Defines the password for the specified Power BI user.
Resource Group	Defines the URL of the resource group that holds your application: https://analysis.windows.net/powerbi/api
API URL	Defines the Azure AD authentication e ndpoint base URL for Power BI: https://api.powerbi.com/v1.0/myorg/
Centralized	Whether to create the connection profile as a centralized connection profile that is stored in the Control-M database and is available to all Control-M/Agents (version 9.0.20 or later).Values: true\|false Default: false The Power BI job requires a centralized connection profile. Set this parameter to true.

Parameter	Description
Host	Defines the Airflow hostname.
Port	Defines the Airflow port number of the Airflow web server.
User	Defines the username that is used to log in to the Airflow server.
Password	Defines the password to log in to the Airflow server.
SecuredConnection	Determines whether a secure connection to the Airflow server is established. Values: true\|false
Centralized	Whether to create the connection profile as a centralized connection profile that is stored in the Control-M database and is available to all Control-M/Agents (version 9.0.20 or later).Values: true\|false Default: false The Airflow job requires a centralized connection profile. Set this parameter to true.

Connection Profiles

ConnectionProfile:Hadoop

Hadoop (all types)

Apache Spark

Apache Oozie

Apache Sqoop

Apache Tajo

Apache Hive

ConnectionProfile:FileTransfer

ConnectionProfile:FileTransfer:FTP

ConnectionProfile:FileTransfer:SFTP

ConnectionProfile:FileTransfer:FTPS

ConnectionProfile:FileTransfer:AS2

ConnectionProfile:FileTransfer:Local

ConnectionProfile:FileTransfer:S3:Amazon

ConnectionProfile:FileTransfer:S3:Compatible

ConnectionProfile:FileTransfer:S3:AWSPrivateLink

ConnectionProfile:FileTransfer:Azure:SharedKey

ConnectionProfile:FileTransfer:Azure:ConnectionString

ConnectionProfile:FileTransfer:Azure:AdUserPass

ConnectionProfile:FileTransfer:Azure:AdClientSecret

ConnectionProfile:FileTransfer:Azure:AdCertificate

ConnectionProfile:FileTransfer:Azure:SharedAccessSignature

ConnectionProfile:FileTransfer:Azure:ManagedIdentity

ConnectionProfile:FileTransfer:GCS

ConnectionProfile:FileTransfer:DualEndPoint

ConnectionProfile:FileTransfer:Group

ConnectionProfile:Database

ConnectionProfile:Database:DB2

ConnectionProfile:Database:JDBC

Driver:JDBC:Database

ConnectionProfile:Database:MSSQL

ConnectionProfile:Database:MSSQL:SSIS

ConnectionProfile:Database:Oracle

ConnectionProfile:Database:Oracle:SID

ConnectionProfile:Database:Oracle:ServiceName

ConnectionProfile:Database:Oracle:ConnectionString

ConnectionProfile:Database:PostgreSQL

ConnectionProfile:Database:Sybase

ConnectionProfile:SAP

ConnectionProfile:ApplicationIntegrator

ConnectionProfile:Informatica

ConnectionProfile:Informatica CS

ConnectionProfile:AWS

ConnectionProfile:AWS Glue

ConnectionProfile:Azure

ConnectionProfile:ADF

ConnectionProfile:Azure Databricks

ConnectionProfile:AzureFunctions

ConnectionProfile:Azure Batch Accounts

ConnectionProfile:Power BI

ConnectionProfile:PeopleSoft

ConnectionProfile:Airflow

ConnectionProfile:WebServices

ConnectionProfile:UI Path

ConnectionProfile:GCP DataFlow

ConnectionProfile:GCP Dataproc

ConnectionProfile:Boomi

ConnectionProfile:Databricks

ConnectionProfile:Talend Data Management

On this page

Parameter	Description
ServiceAccountKey	Defines a JSON body that contains the required service account credentials to access the Google Cloud Composer account.
ServiceAccountKeyFilename	Defines the name of the file that contains the service account credentials.
BaseURL	Defines the Airflow web UI URL in Google Composer.
TargetAudience	Defines the JWT (JSON Web Token) audience for the IAP (Identity-Aware Proxy) Google Cloud service. Note: If you do not know the target audience value, define any text value and test the connection profile. The error message indicates the required target audience value.
Centralized	Whether to create the connection profile as a centralized connection profile that is stored in the Control-M database and is available to all Control-M/Agents (version 9.0.20 or later).Values: true\|false Default: false The Airflow job requires a centralized connection profile. Set this parameter to true.

Parameter	Description
Tenant Url	UiPath Account Logical Name, a unique URL for your site
Tenant Name	The display name of the UiPath tenant
App ID	ID of an external application registered in UiPath The specified external application must be assigned the following required Application Scope rights (through the UiPath Orchestrator, Admin > External Applications > Application Scopes): OR.Folders OR.Robots OR.Jobs OR.Execution
App Secret	Application secret generated in UiPath for the external application
Connection Timeout	A timeout value, in seconds, for the trigger call made by Control-M to UiPath The default is 30 seconds.
Centralized	Whether to create the connection profile as a centralized connection profile that is stored in the Control-M database and is available to all Control-M/Agents (version 9.0.20 or later).Values: true\|false Default: false The UI Path job requires a centralized connection profile. Set this parameter to true.

Parameter	Description
Identity Type	Defines one of the following types of authentication to perform using GCP Access Control. service_account – authenticates using an application ID (service account) and client secret managed_identity – does not require credentials; available on GCP VMs only
DataFlow URL	Defines the Google Cloud Platform (GCP) authentication endpoint. Required only for Service Account authentication. For example, https://dataflow.googleapis.com
Service Account Key	Defines a JSON body that contains the required service account credentials to access GCP. Required only for Service Account authentication.
Centralized	Determines whether to create the connection profile as a centralized connection profile that is stored in the Control-M database and is available to all Control-M/Agents (version 9.0.20 or later).Values: true\|false Default: false The GCP Dataflow job requires a centralized connection profile. Set this parameter to true.

Parameter	Description
Identity Type	Defines one of the following types of authentication to perform using GCP Access Control. service_account – authenticates using an application ID (service account) and client secret managed_identity – does not require credentials; available on GCP VMs only
Dataproc URL	Defines the Google Cloud Platform (GCP) authentication endpoint. Required only for Service Account authentication. For example, https://dataproc.googleapis.com
Service Account Key	Defines a JSON body that contains the required service account credentials to access GCP. Required only for Service Account authentication.
Connection timeout	Defines a timeout value, in seconds, for the trigger call to the Google Cloud Platform. Default: 20 seconds
Centralized	Determines whether to create the connection profile as a centralized connection profile that is stored in the Control-M database and is available to all Control-M/Agents (version 9.0.20 or later).Values: true\|false Default: false The GCP Dataproc job requires a centralized connection profile. Set this parameter to true.

Parameter	Description
AccountId	Defines a unique Boomi account ID.
API Token	Defines a Boomi API Token of a Boomi user for connection to the Boomi endpoint.
End Point	Defines the Boomi API endpoint: https://api.boomi.com
API Username	Defines the name of a Boomi user in email format. Default: BOOMI_TOKEN.{Boomi username} Example: BOOMI_TOKEN.user@example.com
Centralized	Determines whether to create the connection profile as a centralized connection profile that is stored in the Control-M database and is available to all Control-M/Agents (version 9.0.20 or later).Values: true\|false Default: false The Boomi job requires a centralized connection profile. Set this parameter to true.

Parameter	Description
Databricks workspace url	Defines the URL of your Databricks workspace.
Databricks personal access token	Defines a Databricks token for authentication of connections to the Databricks workspace.
Connection Timeout	A timeout value, in seconds, for the REST calls made to Databricks. Default: 50 seconds
Centralized	Determines whether to create the connection profile as a centralized connection profile that is stored in the Control-M database and is available to all Control-M/Agents (version 9.0.20 or later).Values: true\|false Default: false The Databricks job requires a centralized connection profile. Set this parameter to true.

Parameter	Description
API URL	Defines the authentication e ndpoint base URL for the Talend Cloud Management Console: https://api.eu.cloud.talend.com/tmc/v2.6
Personal access token authorization	Defines a Talend token for authentication of connections to Talend. You generate this token through your Talend profile.
Centralized	Determines whether to create the connection profile as a centralized connection profile that is stored in the Control-M database and is available to all Control-M/Agents (version 9.0.20 or later).Values: true\|false Default: false The Talend job requires a centralized connection profile. Set this parameter to true.