Data Engineering Integration 10.5.1
- Data Engineering Integration 10.5.1
- All Products
Name of the cloud provisioning configuration.
ID of the cloud provisioning configuration. Default: Same as the cloud provisioning configuration name.
Optional. Description of the cloud provisioning configuration.
ID of the Azure account to use in the cluster creation process.
A GUID string associated with the Azure Active Directory.
A GUID string that is the same as the Application ID associated with the Service Principal. The Service Principal must be assigned to a role that has permission to create resources in the subscription that you identified in the Subscription ID property.
An octet string that provides a key associated with the client ID.
Azure Data Lake Store Name
Name of the ADLS storage to access. The ADLS storage and the cluster to create must reside in the same region.
Data Lake Service Principal Client ID
A credential that enables programmatic access to ADLS storage. Enables the Informatica domain to communicate with ADLS and run commands and mappings on the HDInsight cluster.
The service principal is an Azure user that meets the following requirements:
Data Lake Service Principal Certificate Contents
The Base64 encoded text of the public certificate used with the service principal.
Leave this property blank when you create the cloud provisioning configuration. After you save the cloud provisioning configuration, log in to the VM where the Informatica domain is installed and run
infacmd ccps updateADLSCertificateto populate this property.
Data Lake Service Principal Certificate Password
Private key for the service principal. This private key must be associated with the service principal certificate.
Data Lake Service Principal Client Secret
An octet string that provides a key associated with the service principal.
Data Lake Service Principal OAUTH Token Endpoint
Endpoint for OAUTH token based authentication.
Azure Storage Account Name
Name of the storage account to access. Get the value from the Storage Accounts node in the Azure web console. The storage and the cluster to create must reside in the same region.
Azure Storage Account Key
A key to authenticate access to the storage account. To get the value from the Azure web console, select the storage account, then Access Keys. The console displays the account keys.
Resource group in which to create the cluster. A resource group is a logical set of Azure resources.
Virtual Network Resource Group
Optional. Resource group to which the virtual network belongs.
If you do not specify a resource group, the Data Integration Service assumes that the virtual network is a member of the same resource group as the cluster.
Name of the virtual network or vnet where you want to create the cluster. Specify a vnet that resides in the resource group that you specified in the Virtual Network Resource Group property.
The vnet must be in the same region as the region in which to create the cluster.
Subnet in which to create the cluster. The subnet must be a part of the vnet that you designated in the previous property.
Each vnet can have one or more subnets. The Azure administrator can choose an existing subnet or create one for the cluster.
Name of the Hive metastore database.
Database Server Name
Server on which the database resides.
The database server name on the Azure web console commonly includes the suffix
database.windows.net. For example:
server123xyz.database.windows.net. You can specify the database server name without the suffix and Informatica will automatically append the suffix. For example, you can specify
Database User Name
User name of the account for the domain to use to access the database.
Password for the user account.
Updated April 21, 2022