Table of Contents

Search

  1. Preface
  2. Analyst Service
  3. Catalog Service
  4. Content Management Service
  5. Data Integration Service
  6. Data Integration Service Architecture
  7. Data Integration Service Management
  8. Data Integration Service Grid
  9. Data Integration Service Applications
  10. Data Preparation Service
  11. Enterprise Data Lake Service
  12. Informatica Cluster Service
  13. Mass Ingestion Service
  14. Metadata Access Service
  15. Metadata Manager Service
  16. Model Repository Service
  17. PowerCenter Integration Service
  18. PowerCenter Integration Service Architecture
  19. High Availability for the PowerCenter Integration Service
  20. PowerCenter Repository Service
  21. PowerCenter Repository Management
  22. PowerExchange Listener Service
  23. PowerExchange Logger Service
  24. SAP BW Service
  25. Search Service
  26. System Services
  27. Test Data Manager Service
  28. Test Data Warehouse Service
  29. Web Services Hub
  30. Application Service Upgrade
  31. Appendix A: Application Service Databases
  32. Appendix B: Connecting to Databases from Windows
  33. Appendix C: Connecting to Databases
  34. Appendix D: Updating the DynamicSections Parameter of a DB2 Database

Configuring the Catalog Service for Azure HDInsight

Configuring the Catalog Service for Azure HDInsight

Perform the following steps to configure the Catalog Service for an Azure HDInsight cluster:
  1. Specify the following properties and values in the
    New Catalog Service - Step 4of 4
    dialog box :
    Property
    Description
    Cluster Type
    External Cluster
    Hadoop Distribution
    HDInsight
    Cluster URL
    Fully qualified host name to access the cluster.
    Cluster URL username
    User name to access the cluster.
    Cluster URL password
    Password for the Cluster URL username.
  2. After you create the Catalog Service, configure the following custom properties in Informatica Administrator for the Catalog Service:
    Custom Property
    Description
    LdmCustomOptions.deployment.azure.account.key
    The key to authenticate the Catalog Service to connect to Azure storage account . The value of the Azure storage account key might be encrypted or non encrypted. You can retrieve the value from
    fs.azure.account.key.<storage account name>
    property in
    core-site.xml
    file present in the Azure HDInsight cluster.
    LdmCustomOptions.deployment.azure.key.decryption.script.path
    If the key specified in the
    LdmCustomOptions.deployment.azure.account.key
    property is in encrypted format, you can use the decrypt shell script to decrypt the key using the key certificate. You must verify that you copy the decrypt shell script and key certificate file to the (same path as cluster machine) domain machine before enabling Catalog Service. Make sure that you maintain the path in the Azure HDInsight cluster machine for the copied files in the domain machine. The value for the property is the location of the decrypt shell script. For example,
    /usr/lib/python2.7/dist-packages/hdinsight_common/decrypt.sh
    . The key certificate file, key_decryption_cert.prv, is present in the
    /usr/lib/hdinsight-common/certs/key_decryption_cert.prv
    directory of Azure HDInsight cluster.
    LdmCustomOptions.deployment.hdfs.default.fs
    Address of the WASB storage account to which the Catalog Service must connect. The address includes the WASB storage container name with the storage account name. The value for the property is the complete WASB address with the container and storage account names. You can retrieve the value for the property from the
    fs.defaultFS
    property in the
    core-site.xml
    file present in the Azure HDInsight cluster.

0 COMMENTS

We’d like to hear from you!