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 REST API
  10. Data Integration Service Applications
  11. Data Privacy Management Service
  12. Enterprise Data Preparation Service
  13. Interactive Data Preparation Service
  14. Informatica Cluster Service
  15. Mass Ingestion Service
  16. Metadata Access Service
  17. Metadata Manager Service
  18. Model Repository Service
  19. PowerCenter Integration Service
  20. PowerCenter Integration Service Architecture
  21. High Availability for the PowerCenter Integration Service
  22. PowerCenter Repository Service
  23. PowerCenter Repository Management
  24. PowerExchange Listener Service
  25. PowerExchange Logger Service
  26. SAP BW Service
  27. Search Service
  28. System Services
  29. Test Data Manager Service
  30. Test Data Warehouse Service
  31. Web Services Hub
  32. Application Service Upgrade
  33. Appendix A: Application Service Databases
  34. Appendix B: Connecting to Databases from Windows
  35. Appendix C: Connecting to Databases from UNIX or Linux
  36. Appendix D: Updating the DynamicSections Parameter of a DB2 Database

Configuring the Catalog Service for Azure HDInsight

Configuring the Catalog Service for Azure HDInsight

If the cluster type is HDInsight, configure the following custom properties in Informatica Administrator for the Catalog Service:
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.