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