Data Integration Connection Profiles

The following topics describe the connection profile parameters for data integration platforms and services:

Airbyte Connection Profile Parameters

Before you can define a job, you must create a connection profile in the Configuration domain. A connection profile contains authorization credentials—such as the username, password, and other plug-in-specific parameters—and enables you to connect to the application server with only the connection profile name. To create a connection profile, see Creating a Centralized Connection Profile.

For more information about this plug-in, see Control-M for Airbyte.

The following table describes the Airbyte connection profile parameters.

Parameter

Description

Airbyte Base URL

Defines the Airbyte authentication endpoint.

Default: https://api.airbyte.com

API Key

Defines the Airbyte account access key, which is available on the Airbyte Developer Portal.

Connection Timeout

Determines the number of seconds to wait after Control-M initiates a connection request to Airbyte before a timeout occurs.

Default: 10

Alteryx Trifacta Connection Profile Parameters

Before you can define a job, you must create a connection profile in the Configuration domain. A connection profile contains authorization credentials—such as the username, password, and other plug-in-specific parameters—and enables you to connect to the application server with only the connection profile name. To create a connection profile, see Creating a Centralized Connection Profile.

For more information about this plug-in, see Control-M for Trifacta.

The following table describes the Alteryx Trifacta connection profile parameters.

Parameter

Description

Trifacta URL

Defines the Trifacta authentication endpoint.

Default: https://cloud.trifacta.com

Username

Defines the registered user name or email address for your Trifacta account.

Password

Defines the registered password for your Username.

Connection Timeout

Determines the number of seconds to wait after Control-M initiates a connection request to Alteryx Trifacta before a timeout occurs.

Default: 10

AWS Glue Connection Profile Parameters

Before you can define a job, you must create a connection profile in the Configuration domain. A connection profile contains authorization credentials—such as the username, password, and other plug-in-specific parameters—and enables you to connect to the application server with only the connection profile name. To create a connection profile, see Creating a Centralized Connection Profile.

For more information about this plug-in, see Control-M for AWS Glue.

The following table describes Control-M for AWS Glue connection profile parameters.

Parameter

Description

Glue URL

Defines the AWS Endpoint.

glue.us-east-2.amazonaws.com

AWS_REGION

Determines the region where the AWS Glue jobs are located.

us-east-2

Authentication

Determines one of the following authentication methods:

  • AWS Key & Secret: Used for services outside the AWS infrastructure.

  • AWS IAM Role: Used for services within the AWS infrastructure.

AWS Access Key ID

Defines a unique string for the Service API to identify the application.

AWS Secret

Authenticates the identity of the application to the Service API when the application requests access to a user account.

IAM Role

Defines the IAM role username on an EC2 instance with the required policies, and is used to acquire a temporary security token.

Connection Timeout

Determines the number of seconds to wait after Control-M initiates a connection request to AWS Glue before a timeout occurs.

AWS Glue DataBrew Connection Profile Parameters

Before you can define a job, you must create a connection profile in the Configuration domain. A connection profile contains authorization credentials—such as the username, password, and other plug-in-specific parameters—and enables you to connect to the application server with only the connection profile name. To create a connection profile, see Creating a Centralized Connection Profile.

For more information about this plug-in, see Control-M for AWS Glue DataBrew.

The following table describes the AWS Glue DataBrew connection profile parameters.

Parameter

Description

AWS API Base URL

Defines the REST API URL for the AWS Glue DataBrew regional endpoint.

https://databrew.us-east-2.amazonaws.com

For more information about regional endpoints available for the AWS Glue DataBrew service, refer to the AWS documentation.

AWS Logs URL

Defines the AWS Logs URL.

https://logs.us-east-2.amazonaws.com

AWS Region

Determines the region where the AWS Glue DataBrew jobs are located.

us-east-2

Authentication

Determines one of the following authentication methods:

  • AWS Key & Secret: Used for services outside the AWS infrastructure.

  • AWS IAM Role: Used for services within the AWS infrastructure.

AWS Access Key ID

Defines the AWS Glue DataBrew account access key.

AWS Secret Key

Defines the AWS Glue DataBrew account secret access key.

IAM Role

Defines the Identity and Access Management (IAM) role for the connection to AWS.

Connection Timeout

Determines the number of seconds to wait after Control-M initiates a connection request to AWS Glue DataBrew before a timeout occurs.

Default: 30

Azure Data Factory Connection Profile Parameters

Before you can define a job, you must create a connection profile in the Configuration domain. A connection profile contains authorization credentials—such as the username, password, and other plug-in-specific parameters—and enables you to connect to the application server with only the connection profile name. To create a connection profile, see Creating a Centralized Connection Profile.

For more information about this plug-in, see Control-M for Azure Data Factory.

The following table describes Azure Data Factory connection profile parameters.

Parameter

Description

Subscription ID

Defines the Azure account subscription ID.

The subscription ID can be retrieved from the Azure portal by selecting the Subscription menu.

Identity Type

Determines one of the following identity types to connect to Azure Data Factory:

  • Managed Identity: Enables you to access other Azure AD-protected resources. The identity is managed by the Azure platform and does not require you to provide credentials within Control-M. Use this option if the Agent is installed on an Azure virtual machine that has an assigned Managed Identity with the required permissions.

  • Service Principal: An Azure service principal, also known as App Registration, is an identity created for use with applications, hosted services, and automated tools to access Azure resources. This access is restricted by the roles assigned to the service principal, which gives the Azure Administrator control over which resources can be accessed and at which level. Use this option if the Agent is installed on-premises or any other cloud vendor.

Specify Managed Identity Client ID

(Managed Identity) Determines whether the client ID for your Managed Identity is specified by the Managed Identity Client ID parameter.

Select this checkbox if you are using the Managed Identity authentication method and you have multiple Managed Identities defined on your Azure virtual machine.

Managed Identity Client ID

(Managed Identity) Determines which client ID to use as the Managed Identity.

This parameter requires a value only if you have multiple Managed Identities defined on your Azure virtual machine and you selected the Specify Managed Identity Client ID checkbox.

If you have only one Managed Identity, it is detected automatically.

Tenant ID

(Service Principal) Defines the ID where the Azure Data Factory is created.

Application ID

(Service Principal) Defines the Azure identity of a Service Principal that is granted access to interact with Azure Data Factory.

Client Secret

(Service Principal) Defines the password of the Service Principal.

REST Login URL

Indicates the Azure AD authentication endpoint base URL:

login.microsoftonline.com

Do not change the default value unless you are required to by your Azure Administrator.

Management URL

Indicates the Azure Management URL:

management.azure.com

Do not change the default value unless you are required to by your Azure Administrator.

Connection Timeout

Determines the number of seconds to wait after Control-M initiates a connection request to Azure Data Factory before a timeout occurs.

Boomi AtomSphere Connection Profile Parameters

Before you can define a job, you must create a connection profile in the Configuration domain. A connection profile contains authorization credentials—such as the username, password, and other plug-in-specific parameters—and enables you to connect to the application server with only the connection profile name. To create a connection profile, see Creating a Centralized Connection Profile.

For more information about this plug-in, see Control-M for Boomi.

The following table describes Boomi AtomSphere connection profile parameters.

Parameter

Description

API Username

Defines the name of a Boomi AtomSphere user in email format.

Default: BOOMI_TOKEN.{Boomi username}

API Token

Defines a Boomi AtomSphere API Token of a Boomi user for connection to the Boomi endpoint.

Endpoint

Defines the Boomi AtomSphere API endpoint:

https://api.boomi.com

Account ID

Defines a unique Boomi AtomSphere account ID.

GCP Data Fusion Connection Profile Parameters

Before you can define a job, you must create a connection profile in the Configuration domain. A connection profile contains authorization credentials—such as the username, password, and other plug-in-specific parameters—and enables you to connect to the application server with only the connection profile name. To create a connection profile, see Creating a Centralized Connection Profile.

For more information about this plug-in, see Control-M for GCP Data Fusion.

The following table describes the GCP Data Fusion connection profile parameters.

Parameter

Description

GCP Data Fusion URL

(Service Account) Defines the Google Cloud Platform (GCP) authentication endpoint for GCP Data Fusion.

https://datafusion.googleapis.com

Identity Type

Determines one of the following authentication types using GCP Data Fusion:

  • Service Account: Authenticates using an application ID (service account) and client secret.

  • IAM: Authenticates based on a detected IAM role, which removes the need to provide additional credentials.

Service Account Key

(Service Account) Defines a service account that is associated with an RSA key pair.

Connection Timeout

Determines the number of seconds to wait after Control-M initiates a connection request to GCP Data Fusion before a timeout occurs.

Default: 20

GCP Dataplex Connection Profile Parameters

Before you can define a job, you must create a connection profile in the Configuration domain. A connection profile contains authorization credentials and enables you to connect to the application server with only the connection profile name. To create a connection profile, see Creating a Centralized Connection Profile.

For more information about this plug-in, see Control-M for GCP Dataplex.

The following table describes the GCP Dataplex connection profile parameters.

Parameter

Description

Identity Type

Determines one of the following GCP Dataplex authentication methods:

  • Service Account: Authenticates using an application ID (service account) and client secret.

  • IAM: Authenticates based on a detected IAM role, which removes the need to provide additional credentials.

GCP Dataplex URL

Defines the Google Cloud Platform (GCP) authentication endpoint for GCP Dataplex.

https://dataplex.googleapis.com

Service Account Key

(Service Account) Defines a service account that is associated with an RSA key pair.

Connection Timeout

Determines the number of seconds to wait after Control-M initiates a connection request to GCP Dataplex before a timeout occurs.

Default: 20

GCP Dataprep Connection Profile Parameters

Before you can define a job, you must create a connection profile in the Configuration domain. A connection profile contains authorization credentials—such as the username, password, and other plug-in-specific parameters—and enables you to connect to the application server with only the connection profile name. To create a connection profile, see Creating a Centralized Connection Profile.

For more information about this plug-in, see Control-M for GCP Dataprep.

The following table describes the GCP Dataprep connection profile parameters.

Parameter

Description

GCP Dataprep URL

Defines the GCP Dataprep API authentication endpoint for Dataprep.

Default: https://api.clouddataprep.com

User Access Token

Defines a token that enables you to authenticate Control-M and connect to your GCP Dataprep account.

Connection Timeout

Determines the number of seconds to wait after Control-M initiates a connection request to GCP Dataprep before a timeout occurs.

Default: 30

IBM InfoSphere DataStage Connection Profile Parameters

Before you can define a job, you must create a connection profile in the Configuration domain. A connection profile contains authorization credentials—such as the username, password, and other plug-in-specific parameters—and enables you to connect to the application server with only the connection profile name. To create a connection profile, see Creating a Centralized Connection Profile.

For more information about this plug-in, see Control-M for IBM InfoSphere DataStage.

The following table describes the IBM InfoSphere DataStage connection profile parameters.

Field

Description

Server Name

Defines the name of the IBM InfoSphere DataStage engine.

Domain Name

(optional) Defines the domain of the IBM InfoSphere DataStage engine.

User Name

Defines the user name for the IBM InfoSphere DataStage server.

Password

Defines the password for the IBM InfoSphere DataStage server.

Confirm Password

Confirms the password for the IBM InfoSphere DataStage server.

Authentication File

Defines the full path, including the authentication filename of the local credentials file for the IBM InfoSphere DataStage engine.

Informatica Connection Profile Parameters

Before you can define a job, you must create a connection profile in the Configuration domain. A connection profile contains authorization credentials—such as the username, password, and other plug-in-specific parameters—and enables you to connect to the application server with only the connection profile name. To create a connection profile, see Creating a Centralized Connection Profile.

For more information about this plug-in, see Control-M for Informatica.

The following table describes the Informatica connection profile parameters.

Parameter

Description

Hub Host Name

Defines the name of the Informatica web services server

Hub Port Number

Defines the port number of the Informatica web services server

Power Center Domain

Defines the name of the Informatica server that contains the Repository service

Repository

Determines the name of the repository where the repository Folders and workflows are located

Integration Service

Determines which Integration Service is used to execute the workflows

Security Domain

Defines a collection of user accounts and groups in a Power Center Domain.

If the username belongs to the native security domain, this field can remain empty. If the username belongs to an LDAP security domain, the security domain must be specified.

User Name

Defines the username that is used to log into the Repository

Password

Defines the password that is used to log into the Repository

Connection Type

Determines whether to use HTTP or HTTPS to connect to the Informatica server.

Maximum Concurrent Workflows

Determines the the maximum number of allowed concurrent workflows in the connection profile

Informatica CS Connection Profile Parameters

Before you can define a job, you must create a connection profile in the Configuration domain. A connection profile contains authorization credentials—such as the username, password, and other plug-in-specific parameters—and enables you to connect to the application server with only the connection profile name. To create a connection profile, see Creating a Centralized Connection Profile.

For more information about this plug-in, see Control-M for Informatica CS.

The following table describes the Informatica Cloud Services (CS) connection profile parameters.

Parameter

Description

Login URL

Defines the URL to connect to Informatica Cloud Services.

https://dm-us.informaticacloud.com

Base URL

Defines the instance name of the Informatica Cloud Services server.

https://usw5.dm-us.informaticalcloud.com

Username

Defines a username for the account to connect to Informatica Cloud Services.

Password

Defines a password for the login to Informatica Cloud Services.

Request Timeout

Determines the number of seconds to wait after Control-M initiates a connection request to Informatica Cloud Services before a timeout occurs.

Default: 3

OCI Data Integration Connection Profile Parameters

Before you can define a job, you must create a connection profile in the Configuration domain. A connection profile contains authorization credentials—such as the username, password, and other plug-in-specific parameters—and enables you to connect to the application server with only the connection profile name. To create a connection profile, see Creating a Centralized Connection Profile.

For more information about this plug-in, see Control-M for OCI Data Integration.

The following table describes the OCI Data Integration connection profile parameters.

Parameter

Authentication Method

Description

OCI Instances URL

All methods

Defines the OCI Instances URL in the following format:

https://dataintegration.<region>.oci.oraclecloud.com

OCI Region

All methods

Determines the region where the OCI Data Integration is located.

https://dataintegration.us-phoenix-1.oci.oraclecloud.com

Authentication

All methods

Determines one of the following authentication methods:

  • Defined Parameters: Defines authentication parameters in the connection profile.

  • Configuration File: Uses a Control-M/Agent configuration file that contains authentication information.

    The following example of a configuration file defines the DEFAULT profile for Linux and the PROFILE2 profile for Windows.

    Copy
    [DEFAULT] 
    user=ocid1.user.oc1..aaaaaaaa4vcihdfhrdtyry457245636cqqcljd6yrcukszg7gzoymoyvkyupivpjfnq
    tenancy=ocid1.tenancy.oc1..aaa456y4e3yrtyue9f8djfihhwp2cu4e6t2b7lttna7rcgnhrdi4qzika
    fingerprint=9f:af:df:f5:5g:95:92:7c:34:ab:46:d3:b4:30:e6:9e
    region=us-phoenix-1
    key_file=/home/dbauser/key.pem 

    [PROFILE2] 
    user=ocid1.user.oc1..aaaaaaaa4v768679dfhrd8989JHGJG36cqqcljd6yrcukszg7gzoymoyvkyupivpjfnq
    tenancy=ocid1.tenancy.oc1..aaa456y4e3yrtyue987erum,gfwp2cu4e6t2b7lttna7rcgnhrdi4qzika
    fingerprint=9f:af:c0:f5:7b:95:92:7c:03:a5:46:g3:b4:38:e6:9e
    region=us-phoenix-1
    key_file=C:\\Users\\dbauser\\key.pem

User OCID

All methods

Defines an individual user within the OCI environment.

Tenancy OCID

Defined Parameters

Defines the OCI Tenacy ID in the OCI Data Integration, which is a global unique identifier for this account within the OCI environment.

Fingerprint

Defined Parameters

Defines a fingerprint to uniquely identify and verify the integrity of the associated certificate or key.

Private Key

Defined Parameters

Defines the Private key within a set of API signing keys that are used for authentication and secure access to OCI resources.

Config File Path

Configuration File

Defines the path to the Control-M/Agent configuration file that contains authentication information.

UNIX: home/user/config/pem.pem

Windows: C:\Users\user1\config\\pem.pem

Profile

Configuration File

Defines the name of a specific section in the configuration file, such as DEFAULT and PROFILE2 in the Configuration File code sample.

Connection Timeout

All methods

Determines the number of seconds to wait after Control-M initiates a connection request to OCI Data Integration before a timeout occurs.

Default: 20

Talend Data Management Connection Profile Parameters

Before you can define a job, you must create a connection profile in the Configuration domain. A connection profile contains authorization credentials—such as the username, password, and other plug-in-specific parameters—and enables you to connect to the application server with only the connection profile name. To create a connection profile, see Creating a Centralized Connection Profile.

For more information about this plug-in, see Control-M for Talend Data Management.

The following table describes the Talend connection profile parameters.

Parameter

Description

API URL

Defines the authentication endpoint base URL for the Talend Cloud Management Console.

This field is automatically populated with the correct URL when you select a region from the Region drop-down list.

https://api.eu.cloud.talend.com/tmc/v2.6

Personal access token authorization

Defines a Talend token to authenticate connections to Talend.

You generate this token through your Talend profile.

Region

Determines one of the following regions where the Talend jobs are located:

  • Eastern United States

  • Europe

  • Western United States

  • Australia

  • Asia

Talend OAuth Connection Profile Parameters

Before you can define a job, you must create a connection profile in the Configuration domain. A connection profile contains authorization credentials—such as the username, password, and other plug-in-specific parameters—and enables you to connect to the application server with only the connection profile name. To create a connection profile, see Creating a Centralized Connection Profile.

For more information about this plug-in, see Control-M for Talend OAuth .

The following table describes the Talend OAuth connection profile parameters.

Parameter

Description

Talend API URL

Defines the authentication endpoint base URL for the Talend OAuth Console.

This field is automatically populated with the correct URL when you select a region from the Region drop-down list, in the following format:

https://api.<region>.cloud.talend.com

Region

Determines one of the following regions where the Talend jobs are located:

  • Europe

  • Eastern United States

  • Western United States

  • Australia

  • Asia

Default: Europe

Client ID

Defines the Client ID that is used to get an OAuth2 JWT access token through the Client ID Grant flow.

Client Secret

Defines the Client Secret (password) that is used to get an OAuth2 JWT access token through the Client Secret Grant flow.

Connection Timeout

Determines the number of seconds to wait after Control-M initiates a connection request to Talend before a timeout occurs.

Default: 30