Installation and Upgrade Guide > Part IV: Install and Configure for Cloudera CDH > Hadoop Configuration Manager for Cloudera CDH > Run the Configuration Manager in Silent Mode
  

Run the Configuration Manager in Silent Mode

To configure the Big Data Management without user interaction in silent mode, run the Hadoop Configuration Manager in silent mode. Use the SilentInput.properties file to specify the configuration options. The configuration manager reads the file to determine the configuration options.
To configure the domain for Big Data Management in silent mode, perform the following tasks:
  1. 1. Configure the properties in the SilentInput.properties file.
  2. 2. Run the configuration manager with the SilentInput.properties file.

Configure the Properties File

The SilentInput.properties file includes the properties that are required by the configuration manger. Customize the properties file to specify the options for your configuration and then run the configuration manager in silent mode.
You might want to create connections if you are installing for the first time or if you are upgrading and the changes to the Hadoop environment are significant, such as a different distribution. If you are upgrading and you create connections that you want to use in existing mappings, you need to update mappings to use the new connections after you upgrade.
You might want to skip creating connections if the changes to the Hadoop environment are minimal, such as a change in distribution version. If you are upgrading and you choose not to create connections, you can continue to use the connections in existing mappings. However, you need update any changed properties after you upgrade. Property changes might include host names, URIs, or port numbers.
  1. 1. Find the sample SilentInput.properties file in the following location: <Informatica installation directory>/tools/BDMUtil
  2. 2. Create a backup copy of the SilentInput.properties file.
  3. 3. Use a text editor to open the file and modify the values of the configuration properties.
    4. The following table describes the configuration properties that you can modify:
    Property Name
    Description
    CLOUDERA_SELECTION
    Indicates whether to configure the Informatica domain for the Cloudera CDH cluster. To configure the domain for the Cloudera CDH cluster, set the value of this property to 1.
    HORTONWORKS_SELECTION
    Indicates whether to configure the Informatica domain for the Hortonworks cluster. To configure the domain for the Hortonworks cluster, set the value of this property to 1.
    BIG_INSIGHT
    Indicates whether to configure the Informatica domain for the BigInsights cluster. To configure the domain for the BigInsights cluster, set the value of this property to 1.
    HD_INSIGHT
    Indicates whether to configure the Informatica domain for the HDInsight cluster. To configure the domain for the HDInsight cluster, set the value of this property to 1.
    DIST_FOLDER_NAME
    Indicates the Hadoop distribution folder name present in INFA_HOME/services/shared/hadoop.
    INSTALL_TYPE
    Indicates how to access files on the Hadoop cluster. Set the value depending on the Hadoop distribution.
    To access files on the Cloudera CDH cluster using the Cloudera Manager, set the value of this property to 0.
    To access files on the Hortonworks HDP, IBM BigInsights, or the Azure HDInsight cluster using Apache Ambari, set the value of this property to 3.
    CLOUDERA_HOSTNAME
    Required if you set INSTALL_TYPE=0.
    Indicates the host name of the Cloudera Manager.
    CLOUDERA_USER_NAME
    Required if you set INSTALL_TYPE=0.
    Indicates the user id for the Cloudera Manager.
    CLOUDERA_USER_PASSWD
    Required if you set INSTALL_TYPE=0.
    Indicates the password for the Cloudera Manager.
    CLOUDERA_PORT
    Required if you set INSTALL_TYPE=0.
    Indicates the port of the Cloudera Manager.
    CLOUDERA_SINGLECLUSTER_NAME
    Required if you set INSTALL_TYPE=0.
    Indicates the name of the Cloudera CDH cluster for which you want to configure Big Data Management.
    If the Cloudera Manager manages a single cluster, you do not have to set this property. Retain this property as a comment or remove the property from the file.
    If the Cloudera Manager manages more than one cluster, uncomment and set the property to the name of the cluster for which you want to configure Big Data Management.
    Note: In a multi-cluster environment, the configuration fails if the property is commented or if the property has an invalid cluster name as the value.
    AMBARI_HOSTNAME
    Required if you set INSTALL_TYPE =3.
    Indicates the password for Apache Ambari.
    AMBARI_USER_NAME
    Required if you set INSTALL_TYPE=3.
    Indicates the port number for Apache Ambari.
    AMBARI_USER_PASSWD
    Required if you set INSTALL_TYPE=3.
    Indicates the password for Apache Ambari.
    AMBARI_PORT
    Required if you set INSTALL_TYPE=3.
    Indicates the port number for Apache Ambari.
    TEZ_EXECUTION_MODE
    Required if you set INSTALL_TYPE=3.
    Indicates whether to enable Tez for the Hive engine.
    To enable Tez on the Hortonworks HDP or Azure HDInsight cluster, set the value of this property to 1. Otherwise, set the value to 0.
    CREATE_CONNECTION
    Indicates whether to update the Data Integration Service and create connections for Big Data Management. To update the Data Integration Service and create connections, set the value of this property to 1 and define the connection properties.
    If you are upgrading and you choose not to create connections, you can continue to use the connections in existing mappings. However, you need update any changed properties after you upgrade. Property changes might include host names, URIs, or port numbers.
    If you are upgrading and you create connections that you want to use in existing mappings, you need to update mappings to use the new connections after you upgrade.
    To exit the configuration manager, set the value to 0.
    UPDATE_DIS
    Required if you set CREATE_CONNECTION=1.
    Indicates whether to update the Data Integration Service properties. To update the Data Integration Service, set this property to 1. Otherwise, set the value to 0.
    CREATE_BDM_CONNECTIONS
    Required if you set CREATE_CONNECTION=1.
    Set this property to 1 to create Hadoop, HDFS, HBase, and Hive connections. Otherwise, the configuration manager will not create connections.
    DOMAIN_USER
    Required if you set CREATE_CONNECTION=1.
    Indicates the user name for the domain administrator.
    DOMAIN_PSSWD
    Required if you set CREATE_CONNECTION=1.
    Indicates the password for the domain administrator.
    DIS_SERVICE_NAME
    Required if you set CREATE_CONNECTION=1 and UPDATE_DIS=1.
    Indicates the name of the Data Integration Service.
    CLUSTER_INSTALLATION_DIR
    Required if you set CREATE_CONNECTION=1 and UPDATE_DIS=1.
    Indicates the Informatica home directory on every node on the Hadoop cluster that is created during the Big Data Management installation. Default is /opt/Informatica.
    KERBEROS_PRINCIPAL_NAME
    Required if you set CREATE_CONNECTION=1 and UPDATE_DIS=1 and if the Hadoop cluster uses Kerberos authentication.
    Indicates the Hadoop Kerberos service principal name.
    KERBEROS_KEYTAB
    Required if you set CREATE_CONNECTION=1 and UPDATE_DIS=1 and if the Hadoop cluster uses Kerberos authentication.
    Indicates the Hadoop Kerberos keytab location.
    HIVE_CONNECTION
    Required if you set CREATE_CONNECTION=1 and CREATE_BDM_CONNECTIONS=1.
    Set this property to 1 to create a Hive connection. Otherwise, set the value to 0.
    HDFS_CONNECTION
    Required if you set CREATE_CONNECTION=1 and CREATE_BDM_CONNECTIONS=1.
    Set this property to 1 to create a HDFS connection. Otherwise, set the value to 0.
    HADOOP_CONNECTION
    Required if you set CREATE_CONNECTION=1 and CREATE_BDM_CONNECTIONS=1.
    Set this property to 1 to create a Hadoop connection. You must create a Hadoop connection to run the mappings in the Hadoop environment.
    HBASE_CONNECTION
    Required if you set CREATE_CONNECTION=1 and CREATE_BDM_CONNECTIONS=1.
    Set this property to 1 to create a HBASE connection. Otherwise, set the value to 0.
    SELECT_ALL_CONNECTION
    Required if you set CREATE_CONNECTION=1 and CREATE_BDM_CONNECTIONS=1.
    Set this property to 1 to create all listed connections.
    Also set HIVE_CONNECTION=1, HDFS_CONNECTION=1, HADOOP_CONNECTION=1, and HBASE_CONNECTION=1 .
    SAMPLE_HIVE_CONNECTION
    Required if CREATE_CONNECTION=1, HIVE_CONNECTION=1, and CREATE_BDM_CONNECTIONS=1.
    Indicates connection name for Hive.
    HIVE_EXECUTION_MODE
    Required if you set CREATE_CONNECTION=1, HIVE_CONNECTION=1, and CREATE_BDM_CONNECTIONS=1.
    Indicates the execution mode for Hive. Set this property to either Local or Remote.
    HIVE_USER_NAME
    Required if you set CREATE_CONNECTION=1, HIVE_CONNECTION=1, and CREATE_BDM_CONNECTIONS=1.
    Indicates the user name for Hive. You must set the execution mode to Remote.
    SAMPLE_HDFS_CONNECTION
    Required if you set CREATE_CONNECTION=1, HDFS_CONNECTION=1, and CREATE_BDM_CONNECTIONS=1.
    Indicates the connection name for HDFS.
    HDFS_USER_NAME
    Required if you set CREATE_CONNECTION=1, HDFS_CONNECTION=1, and CREATE_BDM_CONNECTIONS=1.
    Indicates the user name to access HDFS.
    SAMPLE_HADOOP_CONNECTION
    Required if you set CREATE_CONNECTION=1 , HADOOP_CONNECTION=1 and CREATE_BDM_CONNECTIONS=1.
    Indicates the connection name for Hadoop.
    BLAZE_WORKING_DIR
    Required if you set CREATE_CONNECTION=1 , HADOOP_CONNECTION=1, and CREATE_BDM_CONNECTIONS=1.
    Indicates the existing Blaze work directory on HDFS.
    BLAZE_USER
    Required if you set CREATE_CONNECTION=1, HADOOP_CONNECTION=1, and CREATE_BDM_CONNECTIONS=1.
    Indicates the user name for Blaze.
    SPARK_HDFS_STAGING_DIR
    Required if you set CREATE_CONNECTION=1 , HADOOP_CONNECTION=1 and CREATE_BDM_CONNECTIONS=1.
    Indicates the existing Spark HDFS staging directory.
    SPARK_EVENTLOG_DIR
    Required if you set CREATE_CONNECTION=1, HADOOP_CONNECTION=1, and CREATE_BDM_CONNECTIONS=1.
    Optional: Indicates the Spark event log directory
    SPARK_PARAMETER_LIST
    Required if you set CREATE_CONNECTION=1, HADOOP_CONNECTION=1, and CREATE_BDM_CONNECTIONS=1.
    Indicates the Spark execution parameters list.
    IMPERSONATION_USER
    Required if you set CREATE_CONNECTION=1, HADOOP_CONNECTION=1, CREATE_BDM_CONNECTIONS=1, and if the Hadoop cluster uses Kerberos authentication.
    SAMPLE_HBASE_CONNECTION
    Required if you set CREATE_CONNECTION=1 , HBASE_CONNECTION=1 and CREATE_BDM_CONNECTIONS=1.
    Indicates the connection name for HBase.
    ZOOKEEPER_HOSTS
    Required if you set CREATE_CONNECTION=1 , HBASE_CONNECTION=1 and CREATE_BDM_CONNECTIONS=1.
    Indicates the ZooKeeper host.

Run the Configuration Manager

After you configure the properties file, open a command prompt to start the silent configuration.
  1. 1. Go to the following directory: <Informatica installation directory>/tools/BDMUtil
  2. 2. Verify that the directory contains the SilentInput.properties file that you edited.
  3. 3. Run the BDMSilentConfig.sh file.
The installer runs in the background. The process can take a while. The silent configuration is complete when the following log files are created in the <Informatica installation directory>/tools/BDMUtil directory:
The silent configuration fails if you incorrectly configure the properties file or if the installation directory is not accessible. The silenterror.log file is created in the home directory of the UNIX user that runs the configuration manager in silent mode. Correct the errors and then run the silent configuration again.