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"
  }
}

 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
  }
}

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

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"
       }
      ]
   }
 }
}

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:

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"
    }
  }
}

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, "*****".

_{Back to top}

ConnectionProfile:FileTransfer 

Connection profiles for File Transfers are available for the following types of target servers and communication protocols:

• FTP
• SFTP
• FTPS
• AS2
• Local filesystem
• S3 Storage solutions:
  • Amazon Simple Storage Service (Amazon S3)
  • S3-Compatible Storage
  • AWS PrivateLink for Amazon S3
• Azure Storage solutions:
  • Shared Key authentication using an access key
  • Shared Key authentication using a full connection string
  • Active Directory authentication with user and password
  • Active Directory authentication with client secret
  • Active Directory authentication with a certificate file
  • Shared Access Signature (SAS) authentication
  • Managed Identity authentication
• Google Cloud Storage (GCS)
• Oracle Object Storage

For FTP, SFTP, FTPS, and Local filesystem transfers, you can choose between the following types of connection profiles, depending on the number of hosts for which the connection profile contains connection details:

• Single endpoint: Each connection profile contains the connection details of a single host. Such a connection profile can be used for either the source host or the destination host in a file transfer.
• Dual endpoint: The connection profile contains connection details of two hosts, both the source host and the destination host, in a file transfer.

You can also create group connection profiles for file transfers, which enable you to transfer a file from one host to multiple hosts in one transfer. In each group connection profile, you include a variety of previously defined connection profiles for file transfers.

ConnectionProfile:FileTransfer:FTP

The following examples show a connection profile for a file transfer to a single endpoint using the FTP communication protocol.

Simple ConnectionProfile:FileTransfer:FTP

{
 "FTPConn" : {
   "Type" : "ConnectionProfile:FileTransfer:FTP",
   "TargetAgent" : "AgentHost",
   "TargetCTM" : "CTMHost",
   "HostName": "FTPServer",
   "Port": "21",
   "User" : "FTPUser",
   "Password" : "ftp password",
 }
}

ConnectionProfile:FileTransfer:FTP with optional parameters

{
 "FTPConn" : {
   "Type" : "ConnectionProfile:FileTransfer:FTP",
   "TargetAgent" : "AgentHost",
   "TargetCTM" : "CTMHost",
   "WorkloadAutomationUsers":["john","bob"],
   "HostName": "FTPServer",
   "Port": "21",
   "User" : "FTPUser",
   "Password" : "ftp password",
   "HomeDirectory": "/home/FTPUser",
   "OsType": "Unix",
   "Centralized" : false,
   "AdditionalParameters": [
      {
        "Name": "param1",
        "Value": "1"
      },
      {
        "Name": "param2",
        "Value": "2"
      }
    ]
 }
}

ConnectionProfile:FileTransfer:SFTP

The following examples show a connection profile for a file transfer to a single endpoint using the SFTP (SSH File Transfer Protocol) communication protocol. 

Simple ConnectionProfile:FileTransfer:SFTP

{
 "sFTPconn": {
   "Type": "ConnectionProfile:FileTransfer:SFTP",
   "TargetAgent": "AgentHost",
   "TargetCTM" : "CTMHost",
   "HostName": "SFTPServer",
   "Port": "22",
   "User" : "SFTPUser",
   "Password" : "sftp password"
 }
}

ConnectionProfile:FileTransfer:SFTP with optional parameters

{
 "sFTPconn": {
   "Type": "ConnectionProfile:FileTransfer:SFTP",
   "TargetAgent": "AgentHost",
   "TargetCTM" : "CTMHost",
   "HostName": "SFTPServer",
   "Port": "22",
   "User" : "SFTPUser",
   "HomeDirectory": "/home/SFTPUser",  
   "PrivateKeyName": "/home/controlm/ctm_agent/ctm/cm/AFT/data/Keys/sFTPkey",
   "Passphrase": "passphrase",
   "SSHCompression": true,
   "Centralized" : true,
   "AdditionalParameters": [
      {
        "Name": "param1",
        "Value": "1"
      },
      {
        "Name": "param2",
        "Value": "2"
      }
    ]
 }
}

ConnectionProfile:FileTransfer:FTPS

The following example shows a connection profile for a file transfer to a single endpoint using the FTPS (FTP over SSL) communication protocol.

{
 "FTPSConn": {
    "Type": "ConnectionProfile:FileTransfer:FTPS",
    "HomeDirectory": "/var/home",
    "TargetAgent": "sqa",
    "TargetCTM": "LocalControlM",
    "HostName" : "localhost",
    "User" : "controlm",
    "Password": "ftps_pass",
    "Port": "10021",
    "SSLImplicit": false,
    "ClearDataChannel": true,
    "SSLLevel": "ClientServerAuthentication",
    "ClearCommandChannel": true,
    "Centralized" : true,
    "AdditionalParameters": [
      {
        "Name": "param1",
        "Value": "1"
      },
      {
        "Name": "param2",
        "Value": "2"
      }
    ]
  }
}

ConnectionProfile:FileTransfer:AS2

The following examples show connection profiles for file transfers from a local filesystem to an AS2 server using the AS2 protocol.

Note: File transfers that use the AS2 protocol are supported by Control-M Automation API only in one direction — from a local filesystem to an AS2 server.

Simple ConnectionProfile:FileTransfer:AS2

{
  "AS2_Conn_1": {
    "Type": "ConnectionProfile:FileTransfer:AS2",
    "TargetCTM": "LocalControlM",
    "TargetAgent": "sqa",
    "WorkloadAutomationUsers": [
      "noAi"
    ],
    "PartnerAS2Id": "partner-as2-id",
    "PartnerDestinationUrl": "sqa",
    "PartnerCertificateAlias": "partnerCertAlias",
    "HostName": "sqa",
    "Password": "*****"
  }
}

ConnectionProfile:FileTransfer:AS2 with optional parameters

{
  "AS2_Conn_2": {
    "Type": "ConnectionProfile:FileTransfer:AS2",
    "TargetCTM": "LocalControlM",
    "TargetAgent": "sqa",
    "Centralized": true,
    "WorkloadAutomationUsers": [
      "em_user1"
    ],
    "PartnerAS2Id": "partner-as2-id",
    "PartnerDestinationUrl": "sqa",
    "PartnerCertificateAlias": "partnerCertAlias",
    "HostName": "sqa",
    "Password": "*****",
    "AsyncMdnTimeout": "18120000",
    "User": "basicUser",
    "SendMessageTimeout": "301000",
    "CompressMessage": true,
    "SignMessageParameters": {
      "SignMessage": false,
      "SignatureAlgorithm": "RSA with SHA-384"
    },
    "EncryptMessageParameters": {
      "EncryptMessage": false,
      "EncryptionAlgorithm": "tripleDES (DES EDE3)"
    },
    "RequestReceiptParameters": {
      "RequestReceipt": false,
      "Mode": "Asynchronous",
      "Sign": "Unsigned"
    },
    "AdditionalParameters": [
      {
        "Name": "param1",
        "Value": "1"
      },
      {
        "Name": "param2",
        "Value": "2"
      }
    ]
  }
} 

This connection profile has the following parameters:

ConnectionProfile:FileTransfer:Local

The following example shows a connection profile for a file transfer to a single endpoint on a Local File System. 

{
 "LocalConn" : {
   "Type" : "ConnectionProfile:FileTransfer:Local",
   "TargetAgent" : "AgentHost",
   "TargetCTM" : "CTMHost",
   "User" : "controlm",
   "Password" : "local password",
   "Centralized" : true,
   "AdditionalParameters": [
      {
        "Name": "param1",
        "Value": "1"
      },
      {
        "Name": "param2",
        "Value": "2"
      }
    ]
  }
}

ConnectionProfile:FileTransfer:S3:Amazon

The following example shows a connection profile for file transfers to or from an Amazon S3 storage service.

{
  "testAmazon": {
    "Type": "ConnectionProfile:FileTransfer:S3:Amazon",
    "Region": "us-west-2",
    "AccessKey": "mykey",
    "SecretAccessKey": "mysecret", 
    "VerifyDestination": true,
    "TargetAgent": "sqa",
    "Centralized": true,
    "AdditionalParameters": [
      {
        "Name": "param1",
        "Value": "1"
      },
      {
        "Name": "param2",
        "Value": "2"
      }
    ]
 }
}

This connection profile has the following parameters:

ConnectionProfile:FileTransfer:S3:Compatible

The following example shows a connection profile for file transfers to or from an S3-compatible storage service.

{
  "testCompatible": {
    "Type": "ConnectionProfile:FileTransfer:S3:Compatible",
    "RestEndPoint": "api.com",
    "AccessKey": "mykey",
    "SecretAccessKey": "mysecret",
    "VerifyDestination": true,            
    "TargetAgent": "sqa",
    "Centralized": true,
    "AdditionalParameters": [
      {
        "Name": "param1",
        "Value": "1"
      },
      {
        "Name": "param2",
        "Value": "2"
      }
    ]
  }
}

This connection profile has the following parameters:

ConnectionProfile:FileTransfer:S3:AWSPrivateLink

{
   "PRIVATE_LINK_AMAZON_CP": {
      "Type": "ConnectionProfile:FileTransfer:S3:AWSPrivateLink",
      "Region": "us-west-2",
      "AccessKey": "f392vvrf353422dsfvsd5b",
      "SecretAccessKey": "JXq5+dfsux71t3wee+PdQ2bzGOFpddfsdf",
      "VerifyDestination": true, 
      "RestEndPoint": "apicom",
      "TargetCTM": "CTMHost",
      "TargetAgent": "web",
	  "Centralized": true
   }
}

The following example shows a connection profile for file transfers to or from an AWS PrivateLink for Amazon S3, for storage that resides in the virtual private cloud (VPC) endpoint.

This connection profile has the following parameters:

ConnectionProfile:FileTransfer:Azure:SharedKey

The following example shows a connection profile for file transfers to or from an Azure Storage service with Shared Key authentication using an access key:

{
   "AZURE_CCP1": {
      "Type": "ConnectionProfile:FileTransfer:Azure:SharedKey",
      "AzureAccountName": "mftdevstorage",
      "AzureAccountAccessKey": "44ZHQnMJeIk4hZ4npQMZGfXTuwlciq82lbeYvtBZ+Ig9yCagX4FMOECSg1xDyzr8qO6A==",
      "Centralized": true
   }
}

This connection profile has the following parameters:

ConnectionProfile:FileTransfer:Azure:ConnectionString

The following example shows a connection profile for file transfers to or from an Azure Storage service with Shared Key authentication using a full connection string:

{
   "AZURE_CCP2": {
      "Type": "ConnectionProfile:FileTransfer:Azure:ConnectionString",
      "AzureAccountName": "mftdevstorage",
      "AzureAccountConnectionString": "DefaultEndpointsProtocol=https;AccountName=mftdevstorage;AccountKey=44ZHQnMJeIk4hZ4npQMZGfXTuwlciq82lbeYvtBZ+Ig9yCagX4FMOECSg1xDyzr8qO6A==;EndpointSuffix=core.windows.net",
      "Centralized": true
   }
}

This connection profile has the following parameters:

ConnectionProfile:FileTransfer:Azure:AdUserPass

The following example shows a connection profile for file transfers to or from an Azure Storage service with authentication based on the credentials of a user in the Azure Active Directory (AD).

{
   "AZURE_CCP3": {
      "Type": "ConnectionProfile:FileTransfer:Azure:AdUserPass",
      "AzureAccountName": "mftdevstorage",
      "AzureTenantId": "4092bb37-ebce-8xmi-b6c1-42d0f71c6f5c",
      "AzureClientId": "ce64ad51-yh90-4d01-a73b-7ad58a766741",
      "AzureUserNameAD": "john@mftteamoutlook.onmicrosoft.com",
      "AzureUserPasswordAD": "Abcxyz1234!",
      "Centralized": true
   }
}

This connection profile has the following parameters:

ConnectionProfile:FileTransfer:Azure:AdClientSecret

The following example shows a connection profile for file transfers to or from an Azure Storage service with authentication based on an application secret for the Azure Active Directory (AD) IAM service.

{
   "AZURE_CCP4": {
      "Type": "ConnectionProfile:FileTransfer:Azure:AdClientSecret",
      "AzureAccountName": "mftdevstorage",
      "AzureTenantId": "4092bb37-ebce-8xmi-b6c1-42d0f71c6f5c",
      "AzureClientId": "ce64ad51-yh90-4d01-a73b-7ad58a766741",
      "AzureClientSecret": "rbyHyYH7~pg0fs1pRNMEPuJG-Y.t_fE8yt",
      "Centralized": true
   }
}

This connection profile has the following parameters:

ConnectionProfile:FileTransfer:Azure:AdCertificate

The following example shows a connection profile for file transfers to or from an Azure Storage service with authentication based on a certificate file for the Azure Active Directory (AD) IAM service.

{
   "AZURE_CCP5": {
      "Type": "ConnectionProfile:FileTransfer:Azure:AdCertificate",
      "AzureAccountName": "mftdevstorage",
      "AzureTenantId": "4092bb37-ebce-8xmi-b6c1-42d0f71c6f5c",
      "AzureClientId": "ce64ad51-yh90-4d01-a73b-7ad58a766741",
      "AzureClientCertificateFormat": "PFX",
      "AzureClientCertificatePath": "C:\\as2_keystore.pfx",
      "AzureClientCertificatePassword": "password",
      "Centralized": true
   }
}

This connection profile has the following parameters:

ConnectionProfile:FileTransfer:Azure:SharedAccessSignature

The following example shows a connection profile for file transfers to or from an Azure Storage service using a Shared Access Signature (SAS), which delegates access with specific permissions over a limited time interval.

{
   "AZURE_CCP6": {
      "Type": "ConnectionProfile:FileTransfer:Azure:SharedAccessSignature",
      "AzureAccountName": "mftdevstorage",
      "AzureAccountSaSToken": "?sv=2019-12-12&ss=bfqt&srt=sco&sp=rwdlacupx&se=2022-06-21T16:47:01Z&st=2021-02-10T09:47:01Z&spr=https&sig=YK8ilBPZW2EzKPpfd2SBBrokZQdwepCca4igKJwP0YM%5D",
      "Centralized": true
   }
}

This connection profile has the following parameters:

ConnectionProfile:FileTransfer:Azure:ManagedIdentity

The following example shows a connection profile for file transfers to or from an Azure Storage service using a predefined Managed Identity that does not require credentials.

You can define such a connection profile only when Control-M/Agent is installed on an Azure virtual machine.

{
   "AZURE_CCP7": {
      "Type": "ConnectionProfile:FileTransfer:Azure:ManagedIdentity",
      "AzureAccountName": "mftdevstorage",
      "AzureTenantId": "4092bb37-ebce-8xmi-b6c1-42d0f71c6f5c",
      "Centralized": true
   }
}

This connection profile has the following parameters:

ConnectionProfile:FileTransfer:GCS

The following example shows a connection profile for file transfers to or from a Google Cloud Storage (GCS) service:

{
   "GCS_CCP1": {
      "Type": "ConnectionProfile:FileTransfer:GCS",
      "GCSServiceAccountKey": "{\"type\":\"service_account\",\"project_id\":\"sso-gcp-dba-ctm1-priv-cc30752\",\"private_key_id\":\"5197d05c5b8212bea944985cec74a34d6c1868aa\",\"private_key\":\"-----BEGIN PRIVATE KEY-----\\nprivate-key\\n-----END PRIVATE KEY-----\\n\",\"client_email\":\"bmc-wla-svc-02@sso-gcp-dba-ctm1-priv-cc30752.iam.gserviceaccount.com\",\"client_id\":\"116650586827623521335\",\"auth_uri\":\"https://accounts.google.com/o/oauth2/auth\",\"token_uri\":\"https://oauth2.googleapis.com/token\",  \"auth_provider_x509_cert_url\":\"https://www.googleapis.com/oauth2/v1/certs\",\"client_x509_cert_url\":\"https://www.googleapis.com/robot/v1/metadata/x509/bmc-wla-svc-02%40sso-gcp-dba-ctm1-priv-cc30752.iam.gserviceaccount.com\"}",
      "GCSServiceAccountKeyFileName": "john.json",
      "Centralized": true
   }
}

This connection profile has the following parameters:

ConnectionProfile:FileTransfer:Oracle

The following example shows a connection profile for file transfers to or from an Oracle Object Storage service.

Note: This feature requires Control-M/Enterprise Manager version 9.0.21.100 and Control-M MFT Enterprise B2B version 9.0.21.100.

{
   "ORACLE_CCP1": {
      "Type": "ConnectionProfile:FileTransfer:Oracle",
      "OracleUserId": "ocid1.user.oc1..aaaaaaaaxs7s4xb6mbyvgwkypgcbopm3rexus3vjaiw4zlzbumlxt6blnckq",
      "OracleUserPublicKeyFingerprint": "ae:07:4e:c6:43:17:12:73:0a:70:ed:c7:21:ea:5c:f3",
      "OracleTenancyId": "ocid1.tenancy.oc1..aaaaaaaa5rdw3z2pk23454goj5xeftltlbofnp6moccpe6vtdxa7pp3r7bba",
      "OracleUserPrivateKey": "-----BEGIN PRIVATE KEY-----\\nprivate-key\\n-----END PRIVATE KEY-----",
      "OracleUserPrivateKeyFileName": "john.pem",
      "OracleUserPrivateKeyPassphrase": "",
      "OracleRegion": "il-jerusalem-1",
      "OracleNamespace": "axeictwdjfly",
      "OracleCompartmentId": "ocid1.tenancy.oc1..aaaaaaaa5rdw3z2pk23454goj5xeftltlbofnp6moccpe6vtdxa7pp3r7bba",
      "Centralized": true
   }
}

This connection profile has the following parameters:

ConnectionProfile:FileTransfer:DualEndPoint

In a dual-endpoint connection profile, you specify connection details for the source host and for the destaination host of the file transfer. Connection details can be based on the FTP, SFTP, or FTPS communication protocols or can be to a local file system.

The following example shows a dual-endpoint connection profile. One endpoint uses the FTP communication protocol and the other endpoint uses the SFTP communication protocol.

{
 "DualEpConn" : {
	"Type" : "ConnectionProfile:FileTransfer:DualEndPoint",
	"WorkloadAutomationUsers" : [ "em_user1" ],
	"TargetAgent" : "AgentHost",
    "Centralized" : false,
	"src_endpoint" : {
		"Type" : "Endpoint:Src:FTP",
		"User" : "controlm",
 		"Port" : "10023",
		"HostName" : "localhost",
		"Password" : "password",
		"HomeDirectory" : "/home/controlm/"
	},
	"dest_endpoint" : {
		"Type" : "Endpoint:Dest:SFTP",
		"User" : "controlm",
		"Port" : "10023",
		"HostName" : "host2",
		"Password" : "password",
		"HomeDirectory" : "/home/controlm/"
	}
  }
}

The dual-endpoint connection profile can have the following parameters:

ConnectionProfile:FileTransfer:Group

9.0.20.015The following example shows a group connection profile, which enables you to transfer a file from one host to multiple hosts in one transfer. In each group connection profile, you include a variety of previously defined connection profiles for file transfers.

{
  "GROUP_CP": {
    "Type": "ConnectionProfile:FileTransfer:Group",
    "TargetAgent": "docker_aft_app_centos1",
    "GroupAccounts": ["FTPConn", "sFTPconn", "LocalConn", "AS2_Conn_1"],
    "WorkloadAutomationUsers":["john","bob"] 
  }

This connection profile has the following parameters:

_{Back to top}

ConnectionProfile:Database

The connection profile for database allows you to connect to the following database types:

• ConnectionProfile:Database:DB2
• ConnectionProfile:Database:JDBC
• ConnectionProfile:Database:MSSQL
• ConnectionProfile:Database:Oracle
• ConnectionProfile:Database:PostgreSQL
• ConnectionProfile:Database:Sybase

ConnectionProfile:Database:DB2

The following example shows how to define a connection profile for DB2:

{
  "DB2_CONNECTION_PROFILE": {
    "Type": "ConnectionProfile:Database:DB2",
	"TargetCTM":"CTMHost",
    "TargetAgent": "AgentHost",
    "Host": "DB2Host",
    "Port":"50000",
    "User": "db user",
    "Password": "db password",
    "DatabaseName": "db2"
  }
} 

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

ConnectionProfile:Database:JDBC

The following example shows how to define a connection profile using a custom defined database type created using JDBC. Parameters are described in the table above.

{
	"JDBC_CONNECTION_PROFILE": {
		"Type": "ConnectionProfile:Database:JDBC",
		"User":"db user",
		"TargetCTM":"CTMHost",
		"Host": "PGSQLHost",
		"Driver":"PGDRV",
		"Port":"5432",
		"TargetAgent": "AgentHost",
		"Password": "db password",
		"DatabaseName":"dbname"
	}
}

The following parameter is unique to JDBC connection profiles:

Driver:JDBC:Database

You can define a driver to be used by a connection profile. The following example shows the parameters that you use to define a driver:

{
  "MyDriver": {
    "Type": "Driver:Jdbc:Database",
    "TargetAgent":"app-redhat",
    "StringTemplate":"jdbc:sqlserver://<HOST>:<PORT>/<DATABASE>",
    "DriverJarsFolder":"/home/controlm/ctm/cm/DB/JDBCDrivers/PostgreSQL/9.4/",
    "ClassName":"org.postgresql.Driver",
    "LineComment" : "--",
    "StatementSeparator" : ";"
 }
}

ConnectionProfile:Database:MSSQL

The following example shows how to define an MSSQL database connection profile. Parameters are described in the table above.

 {
	"MSSQL_CONNECTION_PROFILE": {
		"Type": "ConnectionProfile:Database:MSSQL",
		"TargetCTM":"CTMHost",
		"TargetAgent": "AgentHost",
		"Host": "MSSQLHost",
		"User": "db user",
		"Port":"1433",
		"Password": "db password",
		"DatabaseName": "master",
		"DatabaseVersion": "2005",
		"MaxConcurrentConnections": "9",
		"ConnectionRetryTimeOut": "34",
		"ConnectionIdleTime": "45"
	}
}

The following parameter is unique to MSSQL connection profiles:

ConnectionProfile:Database:MSSQL:SSIS

9.0.19.220 The following example shows how to define a connection profile for SQL Server Integration Services (SSIS) packages:

{
    "SSIS_CONNECTION_PROFILE": {
        "Type": "ConnectionProfile:Database:MSSQL:SSIS",
        "TargetAgent": "AgentHost",
        "TargetCTM": "LocalControlM",
        "Host": "localhost",
        "User": "administrator",
        "Port": "1433",
        "Password": "db password",
        "DatabaseName": "testdb",
        "DatabaseVersion": "2016",
        "AuthenticationType": "Windows Authentication",
        "SkipPackagesTest" : false,
        "SSIS": [
            {
                "Source": "File System",
                "Name": "file_system_package",
                "Password": "password"
            },
            {
                "Source": "SSIS Package Store",
                "Name": "ssis_package",
                "Password": "password"
            },
            {
                "Source": "SQL Server",
                "Name": "sql_server_package",
                "Password": "password"
            }
        ]
    }
}

Most of the parameters are the same as for the basic MSSQL connection profile (including those described in the table above). The following parameters are unique to the MSSQL SSIS connection profile:

ConnectionProfile:Database:Oracle

Oracle connection profiles are available for three types of database definitions:

• SID
• ServiceName
• ConnectionString

ConnectionProfile:Database:Oracle:SID

The following example shows how to define a connection profile for an Oracle database using the SID identifier. Additional available parameters are described in the table above.

{
  "ORACLE_CONNECTION_PROFILE": {   
	"Type": "ConnectionProfile:Database:Oracle:SID",   
	"TargetCTM": "controlm",   
	"Port": "1521",   
	"TargetAgent": "AgentHost",
	"Host": "OracleHost",
	"User": "db user",   
	"Password": "db password",
	"SID": "ORCL" 
  }
}

ConnectionProfile:Database:Oracle:ServiceName

The following example shows how to define a connection profile for an Oracle database using a single service name. Additional available parameters are described in the table above.

{
  "ORACLE_CONNECTION_PROFILE": {   
	"Type": "ConnectionProfile:Database:Oracle:ServiceName",   
	"TargetCTM": "controlm",   
	"Port": "1521",   
	"TargetAgent": "AgentHost",
	"Host": "OracleHost",
	"User": "db user",   
	"Password": "db password",
	"ServiceName": "ORCL" 
  }
}

ConnectionProfile:Database:Oracle:ConnectionString

The following example shows how to define a connection profile for an Oracle database using a connection string that contains text from your tnsname.ora file. Additional available parameters are described in the table above.

{
	"ORACLE_CONNECTION_PROFILE": {
		"Type": "ConnectionProfile:Database:Oracle:ConnectionString",
		"TargetCTM":"CTMHost",
		"ConnectionString":"OracleHost:1521:ORCL",
		"TargetAgent": "AgentHost",
		"User": "db user",
		"Password": "db password"
	}
}

ConnectionProfile:Database:PostgreSQL

The following example shows how to define a connection profile for PostgreSQL. Parameters are described in the table above.

{
  "POSTGRESQL_CONNECTION_PROFILE": {
    "Type": "ConnectionProfile:Database:PostgreSQL",
	"TargetCTM":"CTMHost",
    "TargetAgent": "AgentHost",
    "Host": "PostgreSQLHost",
    "Port":"5432",
    "User": "db user",
    "Password": "db password",
    "DatabaseName": "postgres"
  }
} 

ConnectionProfile:Database:Sybase

The following example shows how to define a connection profile for Sybase. Parameters are described in the table above.

{
  "SYBASE_CONNECTION_PROFILE": {
    "Type": "ConnectionProfile:Database:Sybase",
	"TargetCTM":"CTMHost",
    "TargetAgent": "AgentHost",
    "Host": "SybaseHost",
    "Port":"4100",
    "User": "db user",
    "Password": "db password",
    "DatabaseName": "Master"
  }
} 

_{Back to top}

ConnectionProfile:SAP

SAP connection profiles that you create for use by your SAP jobs can be defined for logon to a specific SAP Application Server or for an SAP logon group.

The following example is for a connection profile for a specific SAP Application Server:

{
  "SAP-SERVER-CONN" : {
    "Type" : "ConnectionProfile:SAP",
            "User" : "my-user",
            "Password" : "123456",
            "SapClient" : "100",
            "Language" : "",
            "XBPVersion": "XBP3.0",
            "AppVersion": "R3",
            "ApplicationServerLogon" : {
                "Host" : "localhost",
                "SystemNumber" : "12"
            },
            "SecuredNetworkConnection": {
                "SncLib": " " ,
                "SncPartnerName": "",
                "QualityOfProtection": "2",
                "SncMyName":""
            },
            "SapResponseTimeOut" : "180",
            "UseExtended": true,
            "SolutionManagerConnectionProfile" : "IP4-GROUP",
            "IsSolutionManagerConnectionProfile": true
  }
}

The following example is for a connection profile for an SAP logon group:

{
  "SAP-GROUP-CONN" : {
    "Type" : "ConnectionProfile:SAP",
            "User" : "my-user",
            "Password" : "123456",
            "SapClient" : "100",
            "Language" : "",
            "XBPVersion": "XBP3.0",
            "AppVersion": "R3",
            "GroupLogon": {
                "SystemID": "123",
                "MessageServerHostName": "msgsv",
                "GroupName": "group1"
            },
            "SecuredNetworkConnection": {
                "SncLib": " " ,
                "SncPartnerName": "",
                "QualityOfProtection": "2",
                "SncMyName":""
            },
            "SapResponseTimeOut" : "180",
            "UseExtended": true,
            "SolutionManagerConnectionProfile" : "IP4-GROUP",
            "IsSolutionManagerConnectionProfile": true
  }
}

_{Back to top}

ConnectionProfile:ApplicationIntegrator

The following example shows how to define a connection profile for a job type defined in the Control-M Application Integrator. For information about the Control-M Application Integrator, see Application Integrator.

Properties defined for the connection profile in Control-M Application Integrator are all prefixed with "AI-" in the .json code, as shown in the following example.

{
    "AI_CONNECTION_PROFILE": {
		"Type": "ConnectionProfile:ApplicationIntegrator:<JobType>",
		"TargetAgent": "AgentHost",
		"TargetCTM":"CTMHost",
		"AI-Param03": "45",
		"AI-Param04": "group",
        "Centralized": true
    }
} 

_{Back to top}

ConnectionProfile:Informatica

The following example shows how to define a connection profile for an Informatica job:

{
  "INFORMATICA_CONNECTION": {
    "Type": "ConnectionProfile:Informatica",
    "TargetAgent": "AgentHost",
    "TargetCTM": "CTMHost",
    "Host": "InformaticaHost",
    "Port": "7333",
    "User": "UserName",
    "Password": "Password",
    "PowerCenterDomain": "DomainName",
    "Repository": "RepositoryName",
    "IntegrationService": "ServiceName",
    "SecurityDomain": "Native",
    "ConnectionType": "HTTP",
    "MaxConcurrentConnections": "100",
    "Centralized": false
  }
}

_{Back to top}

ConnectionProfile:Informatica CS

The following example shows how to define a connection profile for an Informatica Cloud Services job:

 {
  "INFORMATICA_CS_CONNECTION": {
     "Type": "ConnectionProfile:Informatica CS",
     "Login URL": "https://dm-us.informaticacloud.com",
     "Base URL": "https://usw5.dm-us.informaticacloud.com", 
     "Username": "UserName",  
     "Password": "Password", 
     "Request Timeout": "3", 
     "Description": "", 
     "Centralized": true 
	} 
 }

_{Back to top}

ConnectionProfile:AWS

Note: This feature requires Control-M/Enterprise Manager version 9.0.21.

The following examples show how to define a connection profile for an AWS job.

The following example is based on authentication with an access key and a secret key:

{
  "AWS_CONNECTION_ACCESSKEY": {
    "Type": "ConnectionProfile:AWS",
    "Centralized": true,
    "TargetAgent": "AgentHost",
    "TargetCTM": "CTMHost",
    "AuthenticationMethod": "AccessKey", 
    "AccessKey": "1234",
    "SecretAccessKey": "00-200340109003001100044011700580-29001301000-410-520-250-880029",
    "Region": "ap-northeast-1",
  }
}

The following example is based on authentication with an IAM role:

{
  "AWS_CONNECTION_IAMROLE": {
    "Type": "ConnectionProfile:AWS",
    "Centralized": true,
    "TargetAgent": "AgentHost",
    "TargetCTM": "CTMHost",
    "AuthenticationMethod": "IAMRole", 
    "IAMRole": "myRole",
    "Region": "ap-northeast-1",
    "ProxySettings": {
      "Host": "host",
      "Port": "12345",
      "Username": "username",
      "Password": "password"
    }
  }
}

_{Back to top}

ConnectionProfile:AWS Batch

The following examples show how to define a connection profile for an AWS Batch job, which enables you to manage and run batch computing workloads in AWS.

The following example is based on authentication using an AWS access key and secret.

{
   "AWS_BATCH": {
      "Type": "ConnectionProfile:AWS Batch",
      "Authentication": "SECRET", 
      "AWS Secret": "myAwsSecret12345",
      "AWS Access Key": "MYAWSACCESSKEY1234",
      "AWS Region": "eu-west-2",
      "Batch URL": " https://batch.{{region}}.amazonaws.com",
      "Connection Timeout": "20",
      "Description": "",
      "Centralized": true
   }
}

The following example is based on authentication using an AWS IAM role from inside an EC2 instance.

{
   "AWS_BATCH": {
      "Type": "ConnectionProfile:AWS Batch",
      "Authentication": "NOSECRET", 
      "IAM Role": "BATCHIAMROLE", 
      "AWS Region": "eu-west-2",
      "Batch URL": " https://batch.{{region}}.amazonaws.com",
      "Connection Timeout": "20",
      "Description": "",
      "Centralized": true
   }
}

_{Back to top}

ConnectionProfile:AWS Step Functions 

The following examples show how to define a connection profile for an AWS Step Functions job, which enables you to create visual workflows that can integrate other AWS services.

The following example is based on authentication using an AWS access key and secret.

{
   "STEPFUNCTIONSCCP": {
      "Type": "ConnectionProfile:AWS Step Functions",
      "Authentication": "SECRET",
      "AWS Secret": "myAwsSecret12345",
      "AWS Access Key": "MYAWSACCESSKEY1234",
      "AWS Region": "eu-west-2", 
      "Step Functions URL": "https://states.AWSRegion.amazonaws.com",
      "Connection Timeout": "20",
      "Description": "",
      "Centralized": true
   }
} 

The following example is based on authentication using an AWS IAM role from inside an EC2 instance.

{
   "STEPFUNCTIONSCCP": {
      "Type": "ConnectionProfile:AWS Step Functions",
      "Authentication": "NOSECRET", 
      "IAM Role": "STEPFXIAMROLE", 
      "AWS Region": "eu-west-2",
      "Step Functions URL": "https://states.AWSRegion.amazonaws.com",
      "Connection Timeout": "20",
      "Description": "",
      "Centralized": true
   }
}

_{Back to top}

ConnectionProfile:AWS Glue

The following examples show how to define a connection profile for an AWS Glue job, which executes Amazon Web Services (AWS) Glue, a serverless data integration service.

The following example is based on authentication using an AWS access key and secret.

{
  "GLUECONNECTION": {
    "Type": "ConnectionProfile:AWS Glue",
    "AWS Access key ID": "MYAWSACCESSKEY1234",
    "AWS Secret": "myAwsSecret12345",
    "Authentication": "SECRET",
    "AWS Region": "eu-west-2",
    "Glue url": "glue.eu-west-2.amazonaws.com",
    "Connection Timeout": "40",
    "Description": "",
    "Centralized": true
  }  
}

The following example is based on authentication using an AWS IAM role from inside an EC2 instance.

{
  "GLUECONNECTIONIAM": {
    "Type": "ConnectionProfile:AWS Glue",
    "IAM Role": "GLUEEC2IAMROLE",
    "Authentication": "NOSECRET",
    "AWS Region": "eu-west-2",
    "Glue url": "glue.eu-west-2.amazonaws.com",
    "Connection Timeout": "40",
    "Description": "",
    "Centralized": true
  }
}

_{Back to top}

ConnectionProfile:AWS Glue DataBrew

The following examples show how to define a connection profile for an AWS DataBrew job, which executes Amazon Web Services (AWS) Glue DataBrew, a cloud-based ETL service that enables you to visualize your data and publish it to the Amazon S3 Data Lake. 

The following example is based on authentication using an AWS access key and secret.

{
	"AWSDATABREW": {
		"Type": "ConnectionProfile:AWS Glue DataBrew",
 		"Authentication": "SECRET", 
		"AWS Access Key": "MYAWSACCESSKEY1234",
		"AWS Secret": "myAwsSecret12345",
		"AWS Region": "us-east-1",
		"AWS Logs URL": "https://logs.{{AWSRegion}}.amazonaws.com",
  		"AWS API Base URL": "https://databrew.{{AWSRegion}}.amazonaws.com",
		"Connection Timeout": "30",
		"Description": "",
		"Centralized": true
	}
}

The following example is based on authentication using an AWS IAM role from inside an EC2 instance.

{
	"AWSDATABREW": {
		"Type": "ConnectionProfile:AWS Glue DataBrew",
		"Authentication": "NOSECRET", 
		"IAM Role": "IAMROLE", 
		"AWS Region": "us-east-1",
		"AWS API Base URL": "https://databrew.{{AWSRegion}}.amazonaws.com",
		"AWS Logs URL": "https://logs.{{AWSRegion}}.amazonaws.com",
		"Connection Timeout": "30",
		"Description": "",
		"Centralized": true
	}
}

_{Back to top}

ConnectionProfile:AWS Data Pipeline 

The following examples show how to define a connection profile for an AWS Data Pipeline job. This job executes an AWS Data Pipeline, a cloud-based ETL service that enables you to automate the transfer, processing, and storage of your data.

The following example is based on authentication using an AWS access key and secret.

{
	"AWSDATAPIPELINESECRET ": {
		"Type": "ConnectionProfile:AWS Data Pipeline",
		"Authentication": "SECRET",
		"AWS Access Key": "MYAWSACCESSKEY1234",
		"AWS Secret": "myAwsSecret12345",
		"AWS Region": "us-east-1",
		"Data Pipeline URL": "https://datapipeline.{{AWSRegion}}.amazonaws.com",
		"Connection Timeout": "30",
		"Description": "",
		"Centralized": true
	}
}

The following example is based on authentication using an AWS IAM role from inside an EC2 instance.

{
	"AWSDATAPIPELINEIAM": {
		"Type": "ConnectionProfile:AWS Data Pipeline",
		"Authentication": "NOSECRET",
		"IAM Role": "IAMROLENAME",
		"AWS Region": "us-east-1",
		"Data Pipeline URL": "https://datapipeline.{{AWSRegion}}.amazonaws.com",
		"Connection Timeout": "30",
		"Description": "",
		"Centralized": true
	}
}

_{Back to top}

ConnectionProfile:AWS EMR

The following examples show how to define a connection profile for an AWS EMR job, which executes Amazon Web Services (AWS) EMR to run big data frameworks.

{
  "AWS_EMR": {
     "Type": "ConnectionProfile:AWS EMR",
     "AWSRegion": "us-east-1",
     "EMRAccessKey": “ABCDEF",
     "EMRSecretKey": "****",
     "Description": "",
     "Centralized": true
  }
}

_{Back to top}

ConnectionProfile:AWSEC2

The following examples show how to define a connection profile for an AWS EC2 job for the integration of AWS EC2 operations into Control-M.

The following example is based on authentication using an AWS access key and secret.

{
  "AWSEC2": {
    "Type": "ConnectionProfile:AWSEC2",
    "Authentication": "SECRET", 
    "AWS Access key ID": "AK***************************",
    "AWS Secret": "nw*****************************",
    "EC2 Region": "us-west-2",
    "Connection timeout": "20",
    "Description": "",
    "Centralized": true
  }
}

The following example is based on authentication using an AWS IAM role from inside an EC2 instance.

{
  "AWSEC2": {
    "Type": "ConnectionProfile:AWSEC2",
    "Authentication": "NOSECRET",
    "IAM Role": "GLUEEC2IAMROLE", 
    "EC2 Region": "us-west-2",
    "Connection timeout": "20",
    "Description": "",
    "Centralized": true
  }
}

_{Back to top}

ConnectionProfile:AWS ECS

The following examples show how to define a connection profile for an AWS ECS job. AWS Elastic Container Service (ECS) is a container management service that enables you to run, stop, manage, and monitor containerized applications in a cluster.

The following example is based on authentication using an AWS access key and secret.

{
   "AWS ECS": {
      "Type": "ConnectionProfile:AWS ECS",
      "AWS ECS URL": "https://ecs.us-east-1.amazonaws.com",
      "Cloud Watch URL": "https://logs.us-east-1.amazonaws.com",
      "AWS Region": "us-east-1",
      "Authentication Method": "Secret",
      "AWS Access Key": "<Access Key>",
      "AWS Secret": "*****",
      "Connection Timeout": "30",
      "Description": "",
      "Centralized": true
   }
}

The following example is based on authentication using an AWS IAM role from inside an EC2 instance.

{
   "AWS ECS": {
      "Type": "ConnectionProfile:AWS ECS",
      "AWS ECS URL": "https://ecs.us-east-1.amazonaws.com",
      "Cloud Watch URL": "https://logs.us-east-1.amazonaws.com",
      "AWS Region": "us-east-1",
      "Authentication Method": "IAM",
      "AWS IAM Role": "IAM ROLE",
      "Connection Timeout": "30",
      "Description": "",
      "Centralized": true
   }
}

_{Back to top}

ConnectionProfile:AWS QuickSight 

The following examples show how to define a connection profile for an AWS QuickSight job, which enables you to visualize, analyze, and share large workloads of data.

The following example is based on authentication using an AWS access key and secret.

{
   "AWS_QUICKSIGHT": {
      "Type": "ConnectionProfile:AWS QuickSight",
      "Authentication Method": "SECRET",
      "AWS Access Key": "MYAWSACCESSKEY1234", 
      "AWS Secret": "myAwsSecret12345",
      "AWS Region": "us-east-1", 
      "AWS Account ID": "12345678",
      "AWS QuickSight URL": "https://quicksight.us-east-1.amazonaws.com",
      "Connection Timeout": "30",
      "Description": "",
      "Centralized": true
   }
}

The following example is based on authentication using an AWS IAM role from inside an EC2 instance.

{
   "AWS_QUICKSIGHT": {
      "Type": "ConnectionProfile:AWS QuickSight",
      "Authentication Method": "NOSECRET",
      "IAM Role": "QUICKSIGHTIAMROLE",  
      "AWS Region": "us-east-1", 
      "AWS Account ID": "12345678",
      "AWS QuickSight URL": "https://quicksight.us-east-1.amazonaws.com",
      "Connection Timeout": "30",
      "Description": "",
      "Centralized": true
   }
}

_{Back to top}

ConnectionProfile:AWS Sagemaker 

The following examples show how to define a connection profile for an AWS SageMaker job, which enables you to create and manage machine learning models.

The following example is based on authentication using an AWS access key and secret.

{
    "AWS_SAGEMAKER": {
       "Type": "ConnectionProfile:AWS Sagemaker",
       "SageMaker URL": "https://sagemaker.us-east-1.amazonaws.com",
       "AWS Region": "us-east-1",
       "Authentication": "SECRET",
       "AWS Access key": "MYAWSACCESSKEY1234",
       "AWS Secret": "myAwsSecret12345",
       "Connection Timeout": "100",
       "Description": "",
       "Centralized": true
   }
}

The following example is based on authentication using an AWS IAM role from inside an EC2 instance.

{
    "AWS_SAGEMAKER_IAM": {
       "Type": "ConnectionProfile:AWS Sagemaker",
       "SageMaker URL": "https://sagemaker.us-east-1.amazonaws.com",
       "AWS Region": "us-east-1",
       "Authentication": "NOSECRET",
       "IAM Role": "SAGEMAKERIAMROLE",
       "Connection Timeout": "100",
       "Description": "",
       "Centralized": true
   }
}     

_{Back to top}

ConnectionProfile:AWS Athena 

The following examples show how to define a connection profile for an AWS Athena job, which you can use for data processing, analysis, and storage.

The following example is based on authentication using an AWS access key and secret.

{
    "AWS_ATHENA": {
        "Type": "ConnectionProfile:AWS Athena",
        "AWS API Base URL": "https://athena.us-east-1.amazonaws.com",
        "AWS Region": "us-east-1",
        "Authentication": "SECRET",
        "AWS Access Key": "ABCDEF",
        "AWS Secret Key": "******",
        "Description": "",
        "Centralized": true
    }
}

The following example is based on authentication using an AWS IAM role from inside an EC2 instance.

{
    "AWS_ATHENA": {
        "Type": "ConnectionProfile:AWS Athena",
        "AWS API Base URL": "https://athena.us-east-1.amazonaws.com",
        "AWS Region": "us-east-1",
        "Authentication": "NOSECRET",
        "IAM Role": "ATHENAIAMROLE",
        "Description": "",
        "Centralized": true
    }
}

_{Back to top}

ConnectionProfile:Azure

9.0.19.220 The following example shows how to define a connection profile for an Azure job:

{
  "AZURE_CONNECTION": {
    "Type": "ConnectionProfile:Azure",
    "TargetAgent": "AgentHost",
    "TargetCTM": "CTMHost",
    "ActiveDirectoryDomainName": "bmc.onmicrosoft.com",
    "SubscriptionID": "bcde-fgh-ijk-lmnopq",
    "ApplicationID": "abcd-efg-hij-klmnop",
    "User": "user1@bmc.onmicrosoft.com",
    "Password": "*****"
    "Batch": {
      "BatchAccountName": "myFirstBatch",
      "BatchAccountKey": "aaaaaabbbbbbbccccccc",
      "Location": "centralus"
    }
  }    
}

_{Back to top}

ConnectionProfile:ADF

The following examples show how to define a connection profile for an ADF job, which executes an Azure Data Factory (ADF) service and allows you to automate the movement and transformation of data.

The following example is based on authentication using an Azure service principal.

{
  "ADF_SERVPRINC": {
    "Type": "ConnectionProfile:ADF",
    "Tenant ID": "tenantId",
    "Identity Type": "PRINCIPAL",
    "Client Secret": "*****",
    "Application ID": "applicationId",
    "Subscription ID": "subscriptionId",
    "Connection Timeout": "40",
    "Description": "",
    "Centralized": true
  }
}

The following example is based on authentication using a managed identity.

{
"ADF_MANID": {
    "Type": "ConnectionProfile:ADF",
    "Identity Type": "MANAGEDID",
    "Specify Managed Identity Client ID": "&client_id=",
    "Managed Identity Client ID": "72d448f0-ac32-45ea-9158-f8653e4ee16",  
    "Subscription ID": "subscriptionId",
    "Connection Timeout": "40",
    "Description": "",
    "Centralized": true
  }
}

_{Back to top}

ConnectionProfile:Azure Databricks

The following example shows how to define a connection profile for an Azure Databricks job, which performs big data analytics .

{
  "ADF_SERVPRINC": {
    "Type": "ConnectionProfile:Azure Databricks",
    "Tenant ID": "tenantId",
    "Application ID": "4f477fa3-1a1g-4877-ca92-f39bb563f3b1",
    "Client Secret": "*****", 
    "Databricks url": "https://adb-1111211144444680.0.azuredatabricks.net",
    "Azure Login url": "https://login.microsoftonline.com",
    "Connection Timeout": "50",
    "Description": "",
    "Centralized": true
  }
}

_{Back to top}

ConnectionProfile:AzureFunctions

The following examples show how to define a connection profile for an Azure Functions job, which executes an Azure cloud service for serverless application development.

The following example is based on authentication using an Azure service principal.

{ 
  "AZUREFUNCTIONS": { 
    "Type": "ConnectionProfile:AzureFunctions", 
    "Subscription ID": "bcde-fgh-ijk-lmnopq", 
    "Identity Type": "PRINCIPAL", 
    "Tenant ID": "tenantId", 
    "Application ID": "4f477fa3-1a1g-4877-ca92-f39bb563f3b1", 
    "Client Secret": "*********", 
    "Azure Login url": "https://login.microsoftonline.com", 
    "Resource Group": "resourceGroup",  
    "Description": "", 
    "Centralized": true 
   } 
}

The following example is based on authentication using a managed identity.

Note: Managed Identity authentication is based on an Azure token that is valid, by default, for 24 hours. Token lifetime can be extended by Azure.  

{ 
  "AZUREFUNCTIONS": { 
    "Type": "ConnectionProfile:AzureFunctions", 
    "Subscription ID": "bcde-fgh-ijk-lmnopq", 
    "Identity Type": "MANAGEDID", 
    "Specify Managed Identity Client ID": "&client_id=",
    "Managed Identity Client ID": "72d448f0-ac32-45ea-9158-f8653e4ee16", 
    "Resource Group": "resourceGroup",  
    "Description": "", 
    "Centralized": true 
   } 
}

_{Back to top}

ConnectionProfile:Azure Batch Accounts

The following examples show how to define a connection profile for execution of an Azure Batch Accounts service, which runs large-scale parallel and batch compute jobs.

The following example is based on authentication using an Azure service principal.

{ 
  "AZURE_BATCH": { 
    "Type": "ConnectionProfile:Azure Batch Accounts",
    "Authentication Method": "PRINCIPAL", 
    "Tenant ID": "tenantId", 
    "Azure AD url": "https://login.microsoftonline.com",
    "App ID": "4f477fa3-1a1g-4877-ca92-f39bb563f3b1",  
    "Batch Account Name": "abc_batch",
    "Batch Region ID": "uksouth",
    "Batch Resource url": "https://batch.core.windows.net/", 
    "Client Secret": "*********",   
    "Connection Timeout": "50", 
    "Description": "", 
    "Centralized": true 
   } 
}

The following example is based on authentication using a managed identity.

Note: Managed Identity authentication is based on an Azure token that is valid, by default, for 24 hours. Token lifetime can be extended by Azure.  

{ 
  "AZURE_BATCH": { 
    "Type": "ConnectionProfile:Azure Batch Accounts",
    "Authentication Method": "MANAGEDID",  
    "Specify Managed Identity Client ID": "&client_id=",
    "Managed Identity Client ID": "72d448f0-ac32-45ea-9158-f8653e4ee16", 
    "Batch Account Name": "abc_batch",
    "Batch Region ID": "uksouth",
    "Batch Resource url": "https://batch.core.windows.net/", 
    "Connection Timeout": "50",
    "Description": "", 
    "Centralized": true 
   } 
}

_{Back to top}

ConnectionProfile:Azure Logic Apps

The following examples show how to define a connection profile for execution of an Azure Logic Apps service, which enables you to design and automate cloud-based workflows and integrations.

The following example is based on authentication using an Azure service principal.

{
	"AZURE_LOGIC_APPS": {
		"Type": "ConnectionProfile:Azure Logic Apps",
		"Subscription ID": "e76056e0-70de-4da8-b02e-61263a150b1f", 
		"Authentication Method": "PRINCIPAL",
 		"Resource Group": "tb-resourcegroup", 
		"Tenant ID": "92b796c5-5839-40a6-8dd9-c1fad320c69b", 
		"Azure Login url": "https://login.microsoftonline.com", 
		"Application ID": "7f477fa3-1a1f-4877-ba80-f39bb563f1b5", 
		"Client Secret": "*****", 
		"Connection timeout": "20", 
 		"Description": "",
		"Centralized": true
	}
} 

The following example is based on authentication using a managed identity.

Note: Managed Identity authentication is based on an Azure token that is valid, by default, for 24 hours. Token lifetime can be extended by Azure.  

{
	"AZURE_LOGIC_APPS": {
		"Type": "ConnectionProfile:Azure Logic Apps",
		"Subscription ID": "e76056e0-70de-4da8-b02e-61263a150b1f", 
		"Authentication Method": "MANAGEDID",
 		"Resource Group": "tb-resourcegroup", 
		"Specify Managed Identity Client ID": "&client_id=",
		"Managed Identity Client ID": "72d448f0-ac32-45ea-9158-f8653e4ee16",  
		"Connection timeout": "20", 
 		"Description": "",
		"Centralized": true
	}
} 

_{Back to top}

ConnectionProfile:Azure Machine Learning

The following examples show how to define a connection profile for an Azure Machine Learning job, which enables you to create and manage machine learning models.

The following example is based on authentication using an Azure service principal.

{
   "AZURE_ML_SERVICE_PRINCIPAL": {
      "Type": "ConnectionProfile:Azure Machine Learning",
      "Authentication Method": "PRINCIPAL",
      "Tenant ID": "82b34c5-5839-40f6-8pd9-c1fad320c69b",
      "Azure Login URL": "https://login.microsoftonline.com", 
      "Azure ML  URL": "https://{{location}}.api.azureml.ms/",
      "Azure Management URL": "https://management.azure.com/",
      "Subscription ID": "e76056e0-70de-4da8-b02e-61263a150b1f",
      "Location Name": "centralus",
      "Application ID": "4f477fa3-1a1g-4877-ca92-f39bb563f3b1",
      "Client Secret": "*****",
      "Connection Timeout": "50",
      "Description": "",
      "Centralized": true
   }
}

The following example is based on authentication using a managed identity.

Note: Managed Identity authentication is based on an Azure token that is valid, by default, for 24 hours. Token lifetime can be extended by Azure.  

{
   "AZURE_ML_SERVICE_IDENTITY": {
       "Type": "ConnectionProfile:Azure Machine Learning", 
       "Authentication Method": "MANAGEDID",
       "Specify Managed Identity Client ID": "&client_id=",
       "Managed Identity Client ID": "72d448f0-ac32-45ea-9158-f8653e4ee16", 
       "Azure ML  URL": "https://{{location}}.api.azureml.ms/",
       "Azure Management URL": "https://management.azure.com/",
       "Subscription ID": "e76056e0-70de-4da8-b02e-61263a150b1f",
       "Location Name": "centralus",
       "Connection Timeout": "50",
       "Description": "",
       "Centralized": true
   }
}

_{Back to top}

 ConnectionProfile:Azure Synapse

The following examples show how to define a connection profile for an Azure Synapse job, which performs data integration and big data analytics.

The following example is based on authentication using an Azure service principal.

{ 
  "AZURE_SYNAPSE_1": { 
    "Type": "ConnectionProfile:Azure Synapse", 
    "Authentication Method": "PRINCIPAL", 
    "Tenant ID": "tenantId", 
    "Azure AD url": "https://login.microsoftonline.com",
    "Synapse url": "https://ncu-if-synapse.dev.azuresynapse.net",
    "Synapse Resource": "https://dev.azuresynapse.net/",
    "App ID": "4f477fa3-1a1g-4877-ca92-f39bb563f3b1", 
    "Client Secret": "*****", 
    "Connection Timeout": "50",
    "Description": "", 
    "Centralized": true 
   } 
}

The following example is based on authentication using a managed identity.

Note: Managed Identity authentication is based on an Azure token that is valid, by default, for 24 hours. Token lifetime can be extended by Azure.  

{ 
  "AZURE_SYNAPSE_2": { 
    "Type": "ConnectionProfile:Azure Synapse", 
    "Authentication Method": "MANAGEDID", 
    "Specify Managed Identity Client ID": "&client_id=",
    "Managed Identity Client ID": "72d448f0-ac32-45ea-9158-f8653e4ee16", 
    "Synapse url": "https://ncu-if-synapse.dev.azuresynapse.net",
    "Synapse Resource": "https://dev.azuresynapse.net/",
    "Connection Timeout": "50",
    "Description": "", 
    "Centralized": true 
   } 
}

_{Back to top}

ConnectionProfile:Azure HDInsight

The following example shows how to define a connection profile for Azure HDInsight jobs.

{
  "AZUREHDINSIGHT": {
    "Type": "ConnectionProfile:Azure HDInsight",     
    "Cluster Name": "hdcluster", 
    "Cluster Username": "admin",  
    "Cluster Password": "*****", 
    "Description": "",
    "Centralized": true
  }
}

_{Back to top}

ConnectionProfile:Azure VM

The following examples show how to define a connection profile for an Azure Virtual Machine (VM) job for the integration of Azure VM operations into Control-M.

The following example is based on authentication using an Azure service principal.

{
  "AZUREVM": {
    "Type": "ConnectionProfile:Azure VM",
    "Subscription ID": "e76056e0-70de-4da8-b02e-61263a150b1f", 
    "Auth_Method": "service_account", 
    "Resource Group": "tb-resourcegroup",
    "Tenant ID": "81b796g5-5839-40a6-8dd9-c1fam320c69b",
    "Client Secret": "*****",
    "Application ID": "7f499fc3-1a1f-4847-ba80-f39bb563f1b5",
    "Azure Login url": "https://login.microsoftonline.com",
    "Connection timeout": "20",
    "Description": "",
    "Centralized": true
  }
}

The following example is based on authentication using a managed identity.

Note: Managed Identity authentication is based on an Azure token that is valid, by default, for 24 hours. Token lifetime can be extended by Azure.  

{
  "AZUREVM": {
    "Type": "ConnectionProfile:Azure VM",
    "Subscription ID": "e76056e0-70de-4da8-b02e-61263a150b1f",
    "Auth_Method": "managed_id", 
    "Specify Managed Identity Client ID": "&client_id=",
    "Managed Identity Client ID": "72d448f0-ac32-45ea-9158-f8653e4ee16",
    "Resource Group": "tb-resourcegroup", 
    "Connection timeout": "20",
    "Description": "Azure VM connection profile",
    "Centralized": true
  }
}

_{Back to top}

ConnectionProfile:Azure Backup 

The following examples show how to define a connection profile for an Azure Backup job, which enables you to back up and restore your data in the Microsoft Azure cloud.

The following example is based on authentication using an Azure service principal.

{
   "ABK_CCP_SERVICE_PRINCIPAL": {
      "Type": "ConnectionProfile:Azure Backup",
	  "Subscription ID": "e76056e0-70de-4da8-b02e-61263a150b1j",
	  "Authentication Method": "service",
	  "Azure Management URL": "https://management.azure.com",
      "Azure Login URL": "https://login.microsoftonline.com", 
      "Tenant ID": "92b796c5-5839-40a6-8dd9-c1fad320c68c",
      "Client Secret": "*****",
      "Application ID": "7f477fa3-1a1f-4877-ba80-f39bb563f1b8",
      "Connection Timeout": "50",
      "Description": "",
      "Centralized": true
   }
}

The following example is based on authentication using a managed identity.

Note: Managed Identity authentication is based on an Azure token that is valid, by default, for 24 hours. Token lifetime can be extended by Azure.  

{
   "ABK_CCP_MANAGED_IDENTITY ": {
      "Type": "ConnectionProfile:Azure Backup",
	  "Subscription ID": "e76056e0-70de-4da8-b02e-61263a150b1j",
	  "Authentication Method": "identity",
	  "Azure Management URL": "https://management.azure.com",
      "Specify Managed Identity Client ID": "&client_id=",
      "Managed Identity Client ID": "7f477fa3-1a1f-4877-ba80-f39bb563f1b8",
      "Connection Timeout": "50",
      "Description": "",
      "Centralized": true
   }
}

_{Back to top}

ConnectionProfile:Power BI

The following example shows how to define a connection profile for a Power BI job, which enables integration of Power BI workflows with your existing Control-M workflows.

{ 
  "POWERBI": { 
    "Type": "ConnectionProfile:Power BI", 
    "Application ID": "77538c66-d7fp-4ca4-8cwa-120ed404fe8c",  
    "Client Secret": "*****", 
    "User Name": "user1@Elearningace.onmicrosoft.com", 
    "Password": "*****",  
    "Resource Group": "https://analysis.windows.net/powerbi/api", 
    "API URL": "https://api.powerbi.com/v1.0/myorg/",  
    "Description": "Power BI connection profile", 
    "Centralized": true 
  } 
}

_{Back to top}

ConnectionProfile:Qlik Cloud

The following example shows how to define a connection profile for a Qlik Cloud job, which enables integration with Qlik Cloud Data Services for data visualization through Qlik Sense.

{
  "QLIK_connection": {
    "Type": "ConnectionProfile:Qlik Cloud",
    "Tenant ID": "******",
    "Qlik API URL": "qlikcloud.com/api/v1",
    "Region": "sg",
    "Connection Timeout": "10",
    "API Key": "******",
    "Description": "Qlik Cloud connection profile",
    "Centralized": true
  }
}

_{Back to top}

ConnectionProfile:Tableau

The following example shows how to define a connection profile for a Tableau job, which enables you to visualize, analyze, and share large workloads of data.

{
    "TABLEAU_CP": {
        "Type": "ConnectionProfile:Tableau",
        "Tableau URL": "https://prod-useast-b.online.tableau.com",
        "Token Name": "myToken",
        "Token Secret": "*****",
        "Site Name": "bmctest",
        "API Version": "3.19",
        "Connection timeout": "50",
        "Description": "",
        "Centralized": true
    }
}

_{Back to top}

ConnectionProfile:PeopleSoft

The following example shows how to define a connection profile for a PeopleSoft job:

{
  "PS_CONNECT": {
      "Type": "ConnectionProfile:PeopleSoft",
      "TargetAgent": "AgentHost",
      "TargetCTM": "CTMHost",
      "Centralized": true,
      "User": "User_Name",
      "Password": "Password",
      "DomainPassword": "****",
      "PeopleToolsVersion": "8.52",
      "ApplicationServers": [
        {
          "ApplicationServer": "ApplicationServer1",
          "JoltPort": "1024"
        },
        {
          "ApplicationServer": "ApplicationServer2",
          "JoltPort": "65535"
        }

      ]
  }
}

_{Back to top}

ConnectionProfile:Airflow

The following examples show how to define a connection profile for an Airflow Job, which enables you to monitor and manage DAG workflows.

The following example is for a standalone instance of Airflow:

{
   "AIRFLOW_CONNECTION_PROFILE": {
      "Type": "ConnectionProfile:Airflow:Standalone",
      "Host": "dba-airflow-12",
      "Port": "8080",
      "User": "admin",
      "Password": "password",
      "SecuredConnection": true,
      "Centralized": true
   }
}

The following example is for a Google Cloud Composer instance of Airflow:

{ 
   "AIRFLOW_GC_CONNECTION_PROFILE": {
      "Type": "ConnectionProfile:Airflow:GoogleComposer",
      "ServiceAccountKey": "{\"type\":\"service_account\",\"project_id\":\"sso-gcp-dba-ctm1-priv-cc30752\",\"private_key_id\":\"5197d05c5b8212bea944985cec74a34d6c1868aa\",\"private_key\":\"-----BEGIN PRIVATE KEY-----\\nprivate-key\\n-----END PRIVATE KEY-----\\n\",\"client_email\":\"bmc-wla-svc-02@sso-gcp-dba-ctm1-priv-cc30752.iam.gserviceaccount.com\",\"client_id\":\"116650586827623521335\",\"auth_uri\":\"https://accounts.google.com/o/oauth2/auth\",\"token_uri\":\"https://oauth2.googleapis.com/token\",  \"auth_provider_x509_cert_url\":\"https://www.googleapis.com/oauth2/v1/certs\",\"client_x509_cert_url\":\"https://www.googleapis.com/robot/v1/metadata/x509/bmc-wla-svc-02%40sso-gcp-dba-ctm1-priv-cc30752.iam.gserviceaccount.com\"}",
      "ServiceAccountKeyFilename": "1234.log",
      "BaseURL": "http://akjsdlksajdksad",
      "TargetAudience": "153767957930-mq2qc9l7p5i8liqvf19d77fku5nrcd1k.apps.googleusercontent.com",
      "Centralized": true
   } 
}

_{Back to top}

ConnectionProfile:WebServices

The following example shows how to define a connection profile for a job to a web service:

{
  "WSDL_CONNECT": {
    "Type": "ConnectionProfile:WebServices",
    "TargetAgent": "AgentHost",
    "TargetCTM": "CTMHost",
    "ServiceType": "WebServices",
    "Location": http://example.com/serverpolicy/Request.asmx?wsdl,
    "HttpAuthentication": "user1:password@realm1;"
  }
}

The following example shows how to define a connection profile for a job to a RESTful web service:

{
  "WSDL_CONNECT": {
    "Type": "ConnectionProfile:WebServices",
    "TargetAgent": "AgentHost",
    "TargetCTM": "CTMHost",
    "ServiceType": "Rest",
    "Location": http://example.com/serverpolicy/Request.asmx?wsdl,
    "HttpAuthentication": "user1:password@realm1;user2:password@realm2",
    "LoginUrl": "http://abc.xyz.com/login",
    "LoginHeader": "Accept:*/*",
    "LoginBody": "{}",
    "JobPreset": "@SessionId:@Token"
  }
}

_{Back to top}

ConnectionProfile:Web Services REST

The following examples show how to define a connection profile for a Web Services REST job.

• Basic Authentication:

  {
       "REST_BASIC_AUTH": {
           "Type": "ConnectionProfile:Web Services REST",
           "Description": "",
           "Centralized": true,
           "WebServiceAuthenticationBasic": {
                "UsePreemptiveAuth": true,
                "User": "User Name",
                "Password": "Password"
           }
       }
  }

• OAuth2 Authentication:

  {
      "REST_OAUTH2": {
          "Type": "ConnectionProfile:Web Services REST",
          "Description": "",
          "Centralized": true,
          "WebServiceAuthenticationOauth2": {
              "Body": [{
                  "resource": "2ff814a6-3304-4ab8-85cb-cd0e6f879c1d"
              }],
              "ContentType": "application/x-www-form-urlencoded",
              "ClientId": "7f477fa3-1a1f-4877-ba80-f39bb563f1b5",
              "ClientSecret": "****",
              "ApiUrl": "https://login.microsoftonline.com/tenantId/oauth2/token"
          }
      }
  }

• AWS Authentication:

  {
      "REST_AWS": {
          "Type": "ConnectionProfile:Web Services REST",
          "Description": "",
          "Centralized": true,
          "WebServiceAuthenticationAws": {
               "CustomServiceName": "batch",
               "Region": "eu-west-2",
               "AuthMethodAccessAndSecretKeys": {
                   "AccessKey": "MYAWSACCESSKEY1234",
                   "SecretAccessKey": "myAwsSecret12345"
               }
          }
      }
  }

• Google Authentication:

  {
      "REST_GCP": {
          "Type": "ConnectionProfile:Web Services REST",
          "Description": "",
          "Centralized": true,
          "WebServiceAuthenticationGoogle": {
              "TokenType": "Access",
              "ServiceAccountKey": "{\"type\":\"service_account\",\"project_id\":\"sso-gcp-dba-ctm1-priv-cc30752\",\"private_key_id\":\"5197d05c5b8212bea944985cec74a34d6c1868aa\",\"private_key\":\"-----BEGIN PRIVATE KEY-----\\nprivate-key\\n-----END PRIVATE KEY-----\\n\",\"client_email\":\bmc-wla-svc-02@sso-gcp-dba-ctm1-priv-cc30752.iam.gserviceaccount.com\,\"client_id\":\"116650586827623521335\",\"auth_uri\":\https://accounts.google.com/o/oauth2/auth\,\"token_uri\":\https://oauth2.googleapis.com/token\,  \"auth_provider_x509_cert_url\":\https://www.googleapis.com/oauth2/v1/certs\,\"client_x509_cert_url\":\https://www.googleapis.com/robot/v1/metadata/x509/bmc-wla-svc-02%40sso-gcp-dba-ctm1-priv-cc30752.iam.gserviceaccount.com\}"
          }
      }
  }

The following table describes the Web Services REST connection profile parameters.

_{Back to top}

ConnectionProfile:Web Services SOAP

The following examples show how to define a connection profile for a Web Services SOAP job.

• Basic Authentication:

  {
       "SOAP_BASIC_AUTH": {
           "Type": "ConnectionProfile:Web Services SOAP",
           "Description": "",
           "Centralized": true,
           "WebServiceAuthenticationBasic": {
                "UsePreemptiveAuth": true,
                "User": "User Name",
                "Password": "Password"
           }
       }
  }

• No Authentication:

  {
       "SOAP_NO_AUTH": {
           "Type": "ConnectionProfile:Web Services SOAP",
           "Description": "",
           "Centralized": true
       }
  }

_{Back to top}

ConnectionProfile:UI Path

The following examples show how to define a connection profile for a UiPath job, which performs robotic process automation (RPA) .

{
  "UIPATH_Connect": {
    "Type": "ConnectionProfile:UI Path",
    "Tenant Url": "devabcdexample/DevDefault",
    "Tenant Name": "DevDefaultexample",
    "App ID": "caaabc57-v8ad-30e5-ah3b0-25am5jf361c3",
    "App Secret": "L!Mh4o#0nv1odf#f",
    "Connection Timeout": "30",
    "Description": "",
    "Centralized": true
  }
}

_{Back to top}

ConnectionProfile:GCP DataFlow

The following example shows how to define a connection profile for a Google Cloud Platform (GCP) Dataflow job, which performs cloud-based data processing for batch and real-time data streaming applications .

{ 
  "GCPDATAFLOW": { 
    "Type": "ConnectionProfile:GCP DataFlow", 
    "Identity Type": "service_account", 
    "DataFlow URL": "https://dataflow.googleapis.com", 
    "Service Account Key": "{\"type\":\"service_account\",\"project_id\":\"sso-gcp-dba-ctm1-priv-cc30752\",\"private_key_id\":\"5197d05c5b8212bea944985cec74a34d6c1868aa\",\"private_key\":\"-----BEGIN PRIVATE KEY-----\\nprivate-key\\n-----END PRIVATE KEY-----\\n\",\"client_email\":\"bmc-wla-svc-02@sso-gcp-dba-ctm1-priv-cc30752.iam.gserviceaccount.com\",\"client_id\":\"116650586827623521335\",\"auth_uri\":\"https://accounts.google.com/o/oauth2/auth\",\"token_uri\":\"https://oauth2.googleapis.com/token\",  \"auth_provider_x509_cert_url\":\"https://www.googleapis.com/oauth2/v1/certs\",\"client_x509_cert_url\":\"https://www.googleapis.com/robot/v1/metadata/x509/bmc-wla-svc-02%40sso-gcp-dba-ctm1-priv-cc30752.iam.gserviceaccount.com\"}",
    "Description": "", 
    "Centralized": true 
  } 
}

_{Back to top}

ConnectionProfile:GCP Dataproc

The following example shows how to define a connection profile for a Google Cloud Platform (GCP) Dataproc job, which performs cloud-based big data processing and machine learning.

{ 
  "GCPDATAPROC": { 
    "Type": "ConnectionProfile:GCP Dataproc", 
    "Identity Type": "service_account", 
    "Dataproc URL": "https://dataproc.googleapis.com", 
    "Service Account Key": "{\"type\":\"service_account\",\"project_id\":\"sso-gcp-dba-ctm1-priv-cc30752\",\"private_key_id\":\"5197d05c5b8212bea944985cec74a34d6c1868aa\",\"private_key\":\"-----BEGIN PRIVATE KEY-----\\nprivate-key\\n-----END PRIVATE KEY-----\\n\",\"client_email\":\"bmc-wla-svc-02@sso-gcp-dba-ctm1-priv-cc30752.iam.gserviceaccount.com\",\"client_id\":\"116650586827623521335\",\"auth_uri\":\"https://accounts.google.com/o/oauth2/auth\",\"token_uri\":\"https://oauth2.googleapis.com/token\",  \"auth_provider_x509_cert_url\":\"https://www.googleapis.com/oauth2/v1/certs\",\"client_x509_cert_url\":\"https://www.googleapis.com/robot/v1/metadata/x509/bmc-wla-svc-02%40sso-gcp-dba-ctm1-priv-cc30752.iam.gserviceaccount.com\"}",
    "Connection timeout": "20",
    "Description": "", 
    "Centralized": true 
  } 
} 

_{Back to top}

ConnectionProfile:GCP BigQuery

The following example shows how to define a connection profile for a GCP BigQuery job for data storage, processing, and analysis.

In this example, authentication is based on a service account.

{
	"BIGQSA": {
		"Type": "ConnectionProfile:GCP BigQuery",
		"Identity Type": "service_account",
		"Service Account Key": "*****",
		"BigQuery URL": "https://bigquery.googleapis.com",
		"Description": "",
		"Centralized": true
	}
}

_{Back to top}

ConnectionProfile:GCP VM

The following example shows how to define a connection profile for a Google Virtual Machine (VM) job for the integration of Google VM operations into Control-M.

In this example, authentication is based on a service account.

{
  "GCPVM": {
    "Type": "ConnectionProfile:GCP VM",
    "Identity Type": "service_account",
    "GCP API URL": "https://compute.googleapis.com/compute", 
    "Service Account Key": "*****",
    "Connection timeout": "20",
    "Description": "",
    "Centralized": true
  }
}

_{Back to top}

ConnectionProfile:GCP Batch

The following example shows how to define a connection profile for a Google Batch job for batch computing workloads on a virtual machine.

In this example, authentication is based on a service account.

{
  "GCP_BATCH": {
      "Type": "ConnectionProfile:GCP Batch",
      "Identity Type": "service_account",
      "Batch URL": "https://batch.googleapis.com",
      "Service Account Key": "*****",
      "Connection Timeout": "20",
      "Description": "",
      "Centralized": true
  }
}

_{Back to top}

ConnectionProfile:GCP Functions

The following example shows how to define a connection profile for a Google Functions job, which enables you to develop, test, and run applications in the cloud.

In this example, authentication is based on a service account.

{
    "GCPFUNCTIONS": {
        "Type": "ConnectionProfile:GCP Functions",
        "Identity Type": "service_account",
        "GCP API URL": "https://cloudfunctions.googleapis.com",
        "Service Account Key": "*****",
        "Connection Timeout": "60",
        "Description": "",
        "Centralized": true
    }
}

_{Back to top}

ConnectionProfile:GCP Dataprep

The following example shows how to define a connection profile for a Google Dataprep job, which enables you to visualize, format, and prepare your data for analysis.

{
    "GCP_DATAPREP": {
        "Type": "ConnectionProfile:GCP Dataprep",
        "GCP Dataprep URL": "https://api.clouddataprep.com",
        "User Access Token": "*****",
        "Connection Timeout": "30",
        "Description": "",
        "Centralized": true
    }
}

_{Back to top}

ConnectionProfile:Boomi

The following example shows how to define a connection profile for a Boomi job, which enables integration of Boomi processes with your existing Control-M workflows.

{
  "BOOMICCP": {
    "Type": "ConnectionProfile:Boomi",
    "AccountId": "*****",
    "API Token": "*****",
    "End Point": "https://api.boomi.com",
    "API Username": "BOOMI_TOKEN.BoomiUsername",
    "Description": "",
    "Centralized": true
  }
}

_{Back to top}

ConnectionProfile:Databricks

The following example shows how to define a connection profile for a Databricks job, which enables integration of jobs created in the Databricks environment with your existing Control-M workflows.

"DATABRICKS": {
    "Type": "ConnectionProfile:Databricks",
    "Databricks workspace url": "https://dbc-7b944b32-faf0.cloud.databricks.com",
    "Databricks personal access token": "*****", 
    "Connection Timeout": "50",
    "Description": "",
    "Centralized": true
}

_{Back to top}

ConnectionProfile:DBT

The following example shows how to define a connection profile for a DBT job. DBT (Data Build Tool) is a cloud-based computing platform that enables you to develop, test, schedule, document, and analyze data models.

"DBT_CP": { 
   "Type": "ConnectionProfile:DBT", 
   "DBT URL": "https://cloud.getdbt.com",  
   "DBT Token": "*****", 
   "Account ID": "123456", 
   "Connection Timeout": "60",
   "Description": "", 
   "Centralized": true 
} 

_{Back to top}

ConnectionProfile:Snowflake

The following example shows how to define a connection profile for a Snowflake job. Snowflake is a cloud computing platform that you can use for data storage, processing, and analysis. 

"SNOWFLAKE_CONNECTION_PROFILE": { 
    "Type": "ConnectionProfile:Snowflake", 
	"Account Identifier": "{Account_ID}",  
    "Region": "us-east-1",
    "Client ID": "DuHj****************",
	"Client Secret": "*****",
    "Refresh Token": "ver%******************",   
    "Redirect URI": "https%****************", 
    "Description": "", 
    "Centralized": true 
}

_{Back to top}

ConnectionProfile:Talend Data Management

The following example shows how to define a connection profile for a Talend job, for data management and integration.

"TALENDDATA": {
    "Type": "ConnectionProfile:Talend Data Management",
    "API URL": "https://api.eu.cloud.talend.com/tmc/v2.6",
    "Region": "eu",
    "Personal access token authorization": "*****", 
    "Description": "Talend Data Management",
    "Centralized": true
}

_{Back to top}

ConnectionProfile:Automation Anywhere

The following example shows how to define a connection profile for an Automation Anywhere job, which performs robotic process automation (RPA) .

{
  "AA_CON": {
    "Type": "ConnectionProfile:Automation Anywhere",
    "Host": "https://trial.cloud.automationanywhere.digital", 
    "User Name": "JohnSmith@abc.onmicrosoft.com",
    "Password": "*****", 
    "Description": "",
    "Centralized": true
  }
}

_{Back to top}

ConnectionProfile:TRIFACTA

The following example shows how to define a connection profile for a Trifacta job, for data processing.

{
	" TRIFACTA": {
		"Type": "ConnectionProfile:TRIFACTA",
		"Trifacta URL": "https://cloud.trifacta.com",
		"User Name": "User Name",
		"Password": "Password",
		"Connection Timeout": "10",
		"Description": " ",
		"Centralized": true
	}
}

_{Back to top}

ConnectionProfile:Micro Focus Windows and ConnectionProfile:Micro Focus Linux

The following examples show how to define a connection profile for a Micro Focus job, for mainframe modernization.

The following connection profile is for Micro Focus on Windows: 

{
   "MICROFWINDOWS": {
      "Type": "ConnectionProfile:Micro Focus Windows",
      "MFBSI Directory Path": "C:\\MicroFocus\\ES\\mfbsi\\ESBMC",
      "MFBSI Config Path": "C:\\Workspace\\system\\config\\MFBSI.cfg",
      "Runtime Environment": "\"C:\\Program Files (x86)\\Micro Focus\\Enterprise Developer\\createenv.bat\"", 
      "Additional Micro Focus Settings Script": "C:\\MicroFocus\\ES\mfbsi\\ESBMC\\settings\\options.bat",
      "Run As": "microuser",
      "Password": "*****", 
      "Description": "Centralized Connection Profile for Micro Focus Windows",
      "Centralized": true
   }
}

The following connection profile is for Micro Focus on UNIX or Linux: 

{
   "MICROFLINUX": {
      "Type": "ConnectionProfile:Micro Focus Linux",
      "MFBSI Directory Path": "/home/esuser/ES/mfbsi/ESBMC1", 
      "MFBSI Config Path": "/home/user/config/mfbsi.cfg", 
      "Runtime Environment": ". /opt/microfocus/EnterpriseDeveloper/bin/cobsetenv", 
      "Additional Micro Focus Settings Script": "/home/esuser/bmc/configuration/mfexports.sh", 
      "Run As": "microuser", 
      "Password": "*****",
      "Description": "Centralised Connection Profile for Micro Focus Linux", 
      "Centralized": true
   }
}

_{Back to top}

ConnectionProfile:Communication Suite

The following example shows how to define a connection profile for a Communication Suite job, which enables you to automate business messaging and communication over Microsoft Teams, Slack, Telegram, and WhatsApp.

{
   "COMM_SUITE": {
      "Type": "ConnectionProfile: Communication Suite",
      "Microsoft Teams Webhook URL": "https://x3dmj.webhook.office.com/webhookb2/5dbb288-138d-428d-ade7-478f727d93f3@edc0dae-4a7f-ac1e-91cb8a656e/IncomingWebhook/ba207b3181d9ede7c9ad1251141/05f0a54e-cec1-4df4-893b-8e61d84516a"
      "Slack Webhook URL": "https://hooks.slack.com/services/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",
      "Telegram URL": "https://api.telegram.org/bot",
      "Telegram Bot Token": "*****",
      "Telegram Chat ID": "207397578157",
      "WhatsApp URL": "https://graph.facebook.com/Version/PhoneNumberID/messages",
      "WhatsApp Business ID": "142913904062636",
      "Phone Number ID": "790951673835859",
      "Recipient Phone Number": "17185551212",
      "User Access Token": "*****",
      "Version": "v15.0",
      "Connection Timeout": "30",
      "Description": "",
      "Centralized": true
   }
}

_{Back to top}

ConnectionProfile:Kubernetes

The following example shows how to define a connection profile for a Kubernetes job, which enables you to run a pod to completion in a Kubernetes-based cluster.

{
    "KBN_CCP": {
        "Type": "ConnectionProfile:Kubernetes",
        "Description": "Profile for agent running in the Kubernetes cluster",
        "Namespace": "jobspace",
        "Kubernetes Cluster URL": "https://kubernetes.default.svc",
        "Service Token File": "/var/run/secrets/kubernetes.io/serviceaccount/token",
        "Connection Timeout": "20",
        "Centralized": true
    }
}

_{Back to top}