Table of Contents

Search

  1. Installation Getting Started
  2. Before You Install the Services
  3. Run the Big Data Suite Installer
  4. After You Install the Services
  5. Install the Developer Tool
  6. Uninstallation
  7. Starting and Stopping Informatica Services
  8. Connecting to Databases
  9. Updating the DynamicSections Parameter of a DB2 Database

Installation and Configuration Guide

Installation and Configuration Guide

Creating the Catalog Service

Creating the Catalog Service

Provide the following details to configure the Catalog Service:
  1. Name of the Catalog Service.
  2. Name of the Model Repository Service that you wan to associate with the Catalog Service.
  3. Name of the node on which the Catalog Service must run.
  4. For Enterprise Data catalog deployed on an embedded cluster, if you had selected the option to associate an Informatica Cluster Service with the Catalog Service, provide the name of the Informatica Cluster Service.
  5. The license that you want to associate with the Catalog Service.
  6. The cluster Hadoop distribution URL.
  7. Username to access the cluster Hadoop distribution URL. Default is admin.
  8. Password to access the cluster Hadoop distribution URL.
  9. Specify the following properties if you deployed Enterprise Data Catalog on an existing cluster:
    Property
    Description
    Name of the cluster
    If you selected Cloudera as the cluster type, you can provide a name for the cluster.
    HDFS Service Name for High Availability
    Applies to highly available existing cluster. Specify the HDFS service name.
    Yarn resource manager scheduler URI
    Scheduler URI value for the Yarn resource manager.
    If you select ClouderaManager or Hortonworks as the Hadoop distribution for an existing cluster, Enterprise Data Catalog automatically identifies the following properties for the Hadoop-distribution type:
    • ZooKeeper Cluster URI
    • HDFS Namenode URI
    • Yarn resource manager URI
    • Yarn resource manager HTTPS or HTTP URI
    • History Server HTTP URI
    • HDFS Service Name for High Availability
    • Yarn resource manager scheduler URI
  10. If you deployed Enterprise Data Catalog on an Azure HDInsight cluster, specify the following properties for the Catalog Service:
    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.
    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.
  11. The service cluster name.
  12. Provide the following properties if you want to enable secure access to the Catalog Service:
    1. Provide the HTTPS port that you want to configure for the Catalog Service. Default is 9124.
    2. Press
      1
      if you want to use the default keystore generated by the installer, else press
      2
      to use a custom keystore file.
      If you do not plan to use the keystore file generated by the installer, verify that you provide SSL certificates in PEM format and in Java Keystore (JKS) files. Informatica requires specific names for the SSL certificate files for the Informatica domain. You must use the same SSL certificates for all nodes in the domain. Store the truststore and keystore files in a directory accessible to all the nodes in the domain and specify the same keystore file directory and truststore file directory for all nodes in the same domain.
      If you selected the option to use a custom keystore file, provide the following details:
      1. Path to the keystore file.
      2. The keystore alias.
      3. Password of the keystore file.
      4. Password of the Solr keystore.
  13. Select the metadata load size that you want to ingest into the catalog from the following options:
    • demo
    • low
    • medium
    • high