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
  10. Silent Input Properties File

Installation and Configuration Guide

Installation and Configuration Guide

Silent Input Properties File

Silent Input Properties File

Informatica provides a sample properties file, called
SilentInput.properties
, that includes the parameters that are required by the installer. The following example shows the contents of the file:
# Use the following guidelines when editing this file: # * Use this file to install without user interaction. Save the file # with the following name: SilentInput.properties # * Any error condition that leads to failure, such as an invalid # installation directory, generates a log file in the user home # directory. For example: /home/<user name>/silentErrorLog.log ########################################################## # Informatica Installer Build Details # Copyright (c) 1993-2018 Informatica LLC # This software contains confidential and proprietary # information of Informatica LLC. # All Rights Reserved. ########################################################## ####### # Use this file (SilentInput.properties) to install Informatica domain services without user interaction. # Use this sample properties file to define the parameters for the silent installation. # To upgrade Informatica, use the SilentInput_upgrade.properties or SilentInput_upgrade_NewConfig.properties file. # Use the following guidelines when you edit this file: # Back up the file before you modify it. # Any error condition that causes the installation to fail, such as an installation directory that is not valid, # generates a log file in /home/<user name>. For example: /home/informatica/silentErrorLog.log ####### # Set ENABLE_USAGE_COLLECTION to 1 to accept the product usage toolkit end user license agreement. # You must set the value as 1 to install the Informatica platform. # The product usage toolkit end user license agreement is available at: http://www.informatica.com/us/eula/en-support-eula.aspx. # As further described in the EULA, your use of the Informatica platform will enable the product usage toolkit # to collect certain product usage and failure information. You may disable this feature at any time. # For more information on how to disable this feature refer the Informatica Administrator Guide. ENABLE_USAGE_COLLECTION=0 # The LICENSE_KEY_LOC property represents the absolute path and file name of the license key file. # Set the property if you are installing Informatica domain services. LICENSE_KEY_LOC=/home/license.key # Version 10.2.1 is for big data products only, such as Big Data Management and Big Data Quality. This version does not support non-big data products, such as PowerCenter or Informatica Data Quality. # If you {install / upgrade} this version, the PowerCenter functionality will not be available. # Set UPGRADE_WITHOUT_PC=1 if you want to continue with the {installation | upgrade}. UPGRADE_WITHOUT_PC=0 # The USER_INSTALL_DIR property represents the directory in which to install the new version of Informatica. # Set the property if you are installing or upgrading Informatica. # The property must point to a valid directory with write permissions enabled. USER_INSTALL_DIR=/home/Informatica/10.2.1 # The INSTALL_TYPE property determines whether to install or upgrade Informatica. # Set INSTALL_TYPE=0 to perform a new installation of Informatica. # To upgrade Informatica, use the SilentInput_upgrade.properties file. # To upgrade Informatica to a different node configuration, use the SilentInput_upgrade_NewConfig.properties file. INSTALL_TYPE=0 # The INSTALL_LDM property determines whether to install or upgrade Enterprise Data Catalog too along with Informatica domain services. # Set INSTALL_LDM=0 to perform a new installation of Informatica without Enterprise Data Catalog. # Set INSTALL_LDM=1 to perform a new installation of Informatica with Enterprise Data Catalog. INSTALL_LDM=0 # The INSTALL_IDL property determines whether to install or upgrade Enterprise Data Lake too along with Enterprise Data Catalog. # Set INSTALL_IDL=0 to perform a new installation of Enterprise Data Catalog without Enterprise Data Lake. # Set INSTALL_IDL=1 to perform a new installation of Enterprise Data Catalog with Enterprise Data Lake. INSTALL_IDL=0 # This property determines whether to install standalone Enterprise Data Catalog. # Set INFA_SERVICES_INSTALLED=true, if current version of Informatica is already installed and you want to install only Enterprise Data Catalog on top of it. # Set INFA_SERVICES_INSTALLED=false, if current version of Informatica is not installed and you want to install Enterprise Data Catalog. INFA_SERVICES_INSTALLED=false # This property determines whether to install standalone Enterprise Data Lake. # Set EIC_SERVICES_INSTALLED=true, if current version of Enterprise Data Catalog is already installed and you want to install only Enterprise Data Lake on top of it. # Set EIC_SERVICES_INSTALLED=false, if current version of Enterprise Data Catalog is not installed and you want to install Enterprise Data Lake. EIC_SERVICES_INSTALLED=false # To proceed with the installation, you need to acknowledge that you have read and accepted the terms and conditions for Java SE Development Kit Software. # Open the following URL http://www.oracle.com/technetwork/java/javase/terms/license/index.html in a web browser to read and accept the terms and conditions # Set ACCEPT_ORACLE_LICENSE to 1 to accept the terms and conditions. # Set ACCEPT_ORACLE_LICENSE to 1, if INSTALL_LDM=1 and CLUSTER_TYPE=1 ACCEPT_ORACLE_LICENSE=0 # Set RUN_CLUSTER_PREVALIDATION to 1, if INSTALL_LDM=1 and if you want to run pre validation utility. # Set RUN_CLUSTER_PREVALIDATION to 0, if INFA_SERVICES_INSTALLED=true. RUN_CLUSTER_PREVALIDATION=0 # The installer can tune the application services based on the deployment type in your environment. # If you do not tune now, you can tune the services later through infacmd. # Set TUNE_APPLICATION_SERVICES=true, to tune the application services through installer. # Set TUNE_APPLICATION_SERVICES=false, to tune the services later through infacmd. TUNE_APPLICATION_SERVICES=false # Select the deployment type associated with the Informatica environment: # If TUNE_APPLICATION_SERVICES=true, Set this TUNING_SIZE property to one of the following (case-sensitive): sandbox, basic, standard, or advanced # Sandbox # Set TUNING_SIZE=sandbox, if the environment is used for proof of concepts or as a sandbox environment with minimal users. Sandbox environments are typically configured with 16 cores, 32 GB RAM, and about 50 GB disk space. # Basic (Default) # Set TUNING_SIZE=basic, if the environment is used for low volume processing environments with low levels of concurrency. Basic environments are typically single- or multi-node setups configured with 24 cores, 64 GB RAM, and about 100 GB disk space. # Standard # Set TUNING_SIZE=standard, if the environment is used for high volume processing but with low levels of concurrency. Standard environments are typically multi-node setups configured with 64 GB RAM, more than 100 GB disk space per node, and 48 cores across nodes. # Advanced # Set TUNING_SIZE=advanced, if the environment is used for high volume processing with high levels of concurrency. Advanced environments are typically multi-node setups configured with 128 GB RAM, more than 100 GB disk space per node, and 96 cores across nodes. TUNING_SIZE= # Provide Kerberos Network Authentication parameters: #To configure the Informatica domain to run on a network with Kerberos authentication, set this parameter to 1. #If INSTALL_LDM is set to 1 or INSTALL_IDL is set to 1, then set this parameter to 0. ENABLE_KERBEROS=0 #Name of the Kerberos realm to which the Informatica domain services belong. The service realm name and the user realm name must be the same. SERVICE_REALM_NAME= #Name of the Kerberos realm to which the Informatica domain users belong. The service realm name and the user realm name must be the same. USER_REALM_NAME= #Directory where all keytab files for the Informatica domain are stored. The name of a keytab file in the Informatica domain must follow a format set by Informatica. KEYTAB_LOCATION= #Path and file name of the Kerberos configuration file. Informatica requires the following name for the Kerberos configuration file: krb5.conf KRB5_FILE_LOCATION= # The SPN_SHARE_LEVEL property determines whether the service principal level for the domain is Node or Process. # Value NODE Use Node Level. Configure the domain to share SPNs and keytab files on a node. # Value PROCESS Use Process Level. Configure the domain to use a unique service principal name (SPN) and keytab file for each node and each service on a node. SPN_SHARE_LEVEL= # The HTTPS_ENABLED property determines whether to secure the connection to Informatica Administrator. # Value 0 Use HTTP connection. Set up an unsecure HTTP connection to Informatica Administrator. # Value 1 Use HTTPS connection. Set up a secure HTTPS connection to the Informatica Administrator. HTTPS_ENABLED=0 # The DEFAULT_HTTPS_ENABLED property determines whether the installer creates a keystore file. # Set the property if HTTPS_ENABLED=1 (uses HTTPS connection). # Value 0 Use a keystore file that you specify. # Value 1 Create a keystore and use it for the HTTPS connection. DEFAULT_HTTPS_ENABLED=1 # The CUSTOM_HTTPS_ENABLED property determines whether the installer uses an existing keystore file. # Value 0 Set the property to 0 if DEFAULT_HTTPS_ENABLED=1. # Value 1 Install Informatica using a keystore file that you specify. Set the property to 1 if DEFAULT_HTTPS_ENABLED=0. CUSTOM_HTTPS_ENABLED=0 # The KSTORE_PSSWD property represents the password for the keystore file. # Set the property to the plain text password for the keystore file if CUSTOM_HTTPS_ENABLED=1. KSTORE_PSSWD=MyKeystorePassword # Set the property to the absolute path and file name of the keystore file if CUSTOM_HTTPS_ENABLED=1. KSTORE_FILE_LOCATION=/home/MyKeystoreFile # The HTTPS_PORT property represents the port number to use for the secure connection to Informatica Administrator. HTTPS_PORT=8443 # The CREATE_DOMAIN property determines whether to create an Informatica domain. # Value 0 Create a node and join that node to another domain created in a previous installation. Set the property to 0 if JOIN_DOMAIN=1. # Value 1 Create a node and an Informatica domain. CREATE_DOMAIN=1 # The directory to store the encryption key on the node created during the installation. KEY_DEST_LOCATION=/home/Informatica/10.2.1/isp/config/keys #Keyword to use to create an encryption key to secure sensitive data in the domain. Set the property only when you create a domain. # The keyword must meet the following criteria:- # From 8 to 20 characters long- # Includes at least one uppercase letter- # Includes at least one lowercase letter- # Includes at least one number- # Does not contain spaces PASS_PHRASE_PASSWD= # The JOIN_DOMAIN property determines whether to join the node to another domain created in a previous installation. # Value 0 Create a node and an Informatica domain. Set the property to 0 if CREATE_DOMAIN=1. # Value 1 Create a node and join the node to another domain created in a previous installation. Set the property to 1 if CREATE_DOMAIN=0. JOIN_DOMAIN=0 # Directory that contains the encryption key on the master gateway node of the Informatica domain that you want to join. KEY_SRC_LOCATION=/home/temp/siteKey # The SSL_ENABLED property enables or disables Transport Layer Security (TLS). # Set the property to true to enable secure communication between services within the domain. # Set the property to true or false if CREATE_DOMAIN=1. # If SSL_ENABLED=true, then set HTTPS_ENABLED=1 and set HTTPS_PORT. SSL_ENABLED=false #The property SECURITY_DOMAIN_NAME represents the LDAP name for the Kerberos enabled domain #Set the property if JOIN_DOMAIN=1 and ENABLE_KERBEROS=1 SECURITY_DOMAIN_NAME= ################################################# #Provide TLS information for domain. Set TLS_CUSTOM_SELECTION equals to true if you want domain level TLS option. TLS_CUSTOM_SELECTION=false ################################ #Below fields are only required when you set TLS_CUSTOM_SELECTION=true NODE_KEYSTORE_DIR=/home/<username>/temp NODE_KEYSTORE_PASSWD= NODE_TRUSTSTORE_DIR=/home/<username>/temp NODE_TRUSTSTORE_PASSWD= # The SERVES_AS_GATEWAY property determines whether to create a gateway or worker node. # Set the property if JOIN_DOMAIN=1. # Value 0 The installer configures the node as a worker node. # Value 1 The installer configures the node as a gateway node. SERVES_AS_GATEWAY=0 # Set to true to enable Security Assertion Markup Language (SAML) authentication in the domain. # If ENABLE_KERBEROS=1, then set this value to false. SAML_AUTHENTICATION=false # Set the following properties only if SAML_AUTHENTICATION=true. # Leave the property blank, if JOIN_DOMAIN=1. # The identity provider URL for the domain. IDP_URL= # If a custom truststore file is used for SAML authentication, set to the directory containing the truststore file on gateway nodes within the domain. # Specify the directory only, not the full path to the file. The default Informatica truststore is used if no truststore is specified. SAML_TRUSTSTORE_DIR= # The password for the custom truststore file specified in SAML_TRUSTSTORE_DIR. SAML_TRUSTSTORE_PASSWD= # The alias name specified when the identity provider assertion signing certificate was imported into the truststore file used for SAML authentication. SAML_TRUSTSTORE_ALIAS= # The DB_TYPE property represents the database type for the domain configuration database. # Set the property to one of the following database types (case-sensitive): Oracle, MSSQLServer, DB2, or Sybase DB_TYPE=Oracle/MSSQLServer/DB2/Sybase # The DB_UNAME property represents the database user account name for the domain configuration repository. DB_UNAME=UserName # The DB_PASSWD property represents the database password for the database user account. DB_PASSWD=UserPassword # The DB_SSL_ENABLED property indicates whether the database for the domain # configuration repository is secure. To create the domain configuration repository # in a secure database, set this parameter to True. # If this property is set to True then the DB_CUSTOM_STRING_SELECTION property must be # set to 1 to use the custom string option. The DB_CUSTOM_STRING property must include # the following secure database parameters: # EncryptionMethod=SSL;HostNameInCertificate=;ValidateServerCertificate= DB_SSL_ENABLED=false # The TRUSTSTORE_DB_FILE indicates the path and file name of the truststore file for # the secure domain configuration repository database. If the domain that you create # or join uses a secure domain configuration repository, set this property to the # truststore file of the repository database. TRUSTSTORE_DB_FILE= # TRUSTSTORE_DB_PASSWD to the password for the truststore file for the secure domain # configuration repository database. TRUSTSTORE_DB_PASSWD= # The SQLSERVER_SCHEMA_NAME property represents the name of the schema that will contain domain configuration tables. # Set the property if DB_TYPE=MSSQLServer. # If SQLSERVER_SCHEMA_NAME is empty, the installer creates the tables in the default schema. SQLSERVER_SCHEMA_NAME= # The TRUSTED_CONNECTION property determines whether to connect to the Microsoft SQL Server database through a # trusted connection using the Windows credentials of the current user account. # In Create domain scenario ,when CREATE_DOMAIN=1 # Set the property if DB_TYPE=MSSQLServer and you are installing on Windows. # Set TRUSTED_CONNECTION=0 if DB_TYPE is set to another database type or if you are installing Informatica on Linux or UNIX. # If the property is empty, the installer uses Microsoft SQL Server authentication. # Value 0 Connect to the Microsoft SQL Server database using a Microsoft SQL Server user account. # Value 1 Connect to the Microsoft SQL Server database through a trusted connection using the Windows credentials of the current user account. # If TRUSTED_CONNECTION flag is set to 1, Make sure that DB_CUSTOM_STRING_SELECTION is also set to 1 and provide connection details in DB_CUSTOM_STRING_SELECTION. # In join node scenario, when JOIN_DOMAIN=1 # Set this value to empty,for all cases. TRUSTED_CONNECTION= # The DB2_TABLESPACE property represents the name of the tablespace in which to create the tables. # Set the property if DB_TYPE=DB2. # Specify a tablespace that meets the pageSize requirement of 32768 bytes. # In a single-partition database, if DB2_TABLESPACE is empty, the installer creates the tables in the default tablespace. # In a multi-partition database, define the tablespace in the catalog partition of the database. DB2_TABLESPACE= # The DB_CUSTOM_STRING_SELECTION property determines whether to use a JDBC URL or a custom connection string to connect to the domain configuration database. # Set DB_CUSTOM_STRING_SELECTION=1 if TRUSTED_CONNECTION=1. Also provide the default valid connection string in DB_CUSTOM_STRING. # Value 0 The installer creates a JDBC URL from the database properties you provide # Value 1 The installer uses the custom connection string you provide. DB_CUSTOM_STRING_SELECTION=0 # The DB_SERVICENAME property represents the service name or database name of the database. # Set the property if DB_CUSTOM_STRING_SELECTION=0. # Set the property to the service name for Oracle and IBM DB2 databases. # Set the property to the database name for Microsoft SQL Server and Sybase ASE databases. # Leave the property blank if DB_CUSTOM_STRING_SELECTION=1. DB_SERVICENAME=DBServiceName # The DB_ADDRESS property represents the host name and port number for the database instance. # Set the property if DB_CUSTOM_STRING_SELECTION=0. # Set the property in the format HostName:PortNumber. # Leave the property blank if DB_CUSTOM_STRING_SELECTION=1. DB_ADDRESS=HostName:PortNumber # The ADVANCE_JDBC_PARAM property represents additional parameters in the JDBC URL connection string. # If DB_CUSTOM_STRING_SELECTION=0, you can set the property to include optional parameters in the JDBC URL connection string. # The parameter string must be valid. # If the parameter is empty, the installer creates the JDBC URL without additional parameters. ADVANCE_JDBC_PARAM= # The DB_CUSTOM_STRING property represents a valid custom JDBC connection string. # Set the property if DB_CUSTOM_STRING_SELECTION=1. DB_CUSTOM_STRING= # The DOMAIN_NAME property represents the name of the domain to create. The default domain name is Domain_<MachineName>. # Set the property if CREATE_DOMAIN=1. # The domain name must not exceed 128 characters and must be 7-bit ASCII only. It cannot contain a space or any of the following characters: ` % * + ; " ? , < > \ / DOMAIN_NAME=DomainName # The DOMAIN_HOST_NAME property represents the host name of the machine. # * If you create a domain, this is the host name of the machine on which to create the node. # If the machine has a single network name, use the default host name. # If the machine has multiple network names, you can modify the default host name to use an alternate network name. Optionally, you can use the IP address. # * If you join a domain, this is the host name of the machine that hosts the gateway node of the domain you want to join. # Do not use localhost. The host name must explicitly identify the machine. DOMAIN_HOST_NAME=HostName # The NODE_NAME property represents the node to create on the machine. The node name is not the host name for the machine. NODE_NAME=NodeName # The DOMAIN_PORT property represents the port number. # * If you create a domain, set the property to the port number for the node to create. # The default port number for the node is 6005. # If the default port number is not available on the machine, the installer displays the next available port number. # * If you join a domain, set the property to the port number of the gateway node of the domain you want to join. DOMAIN_PORT=6005 # The DOMAIN_USER property represents the user name for the domain administrator. # If you create a domain, you can use this user name to initially log in to the Informatica Administrator. # If you join a domain, this is the user name to use to log in to the domain that you want to join. DOMAIN_USER=AdminUser #The PASSWORD_COMPLEXITY property is the password you set to secure sensitive data in the domain. # Set the PASSWORD_COMPLEXITY=true if you want the password complexity to be enabled otherwise set it to false. # The password must meet the following complexity requirements: # The password must be at least 8 characters. # The password must contain at least 1 digit character. # The password must contain at least 1 of the following special characters: [!"#$%&'()*+,-./:;<=>?@[]^_`{|}~]. # The password must contain at least 1 character. # Set this property only if ENABLE_KERBEROS=0 PASSWORD_COMPLEXITY=false # The DOMAIN_PSSWD property represents the password for the domain administrator. # The password must be more than 2 characters but cannot exceed 128 characters. # Set this property only if ENABLE_KERBEROS=0. DOMAIN_PSSWD= # The DOMAIN_CNFRM_PSSWD property confirms the password you set for the domain administrator. # Set the property to the password you set in the DOMAIN_PSSWD property to confirm the password. # Set this property only if ENABLE_KERBEROS=0. DOMAIN_CNFRM_PSSWD= # The JOIN_NODE_NAME property represents the name of the node to create on this machine. The node name is not the host name for the machine. # Set the property if JOIN_DOMAIN=1. JOIN_NODE_NAME=NodeName # Host name of the machine on which to create the node that you are joining to the domain. The node host name cannot contain the underscore (_) character. # Set the property if JOIN_DOMAIN=1. JOIN_HOST_NAME=DomainHostName # The JOIN_DOMAIN_PORT property represents the port number of the machine on which to create the node that you are joining to the domain. # Set the property if JOIN_DOMAIN=1. JOIN_DOMAIN_PORT= # The ADVANCE_PORT_CONFIG property determines whether to display the list of port numbers for the domain and node components. # If ADVANCE_PORT_CONFIG=1, set the MIN_PORT, MAX_PORT, TOMCAT_PORT, AC_PORT, SERVER_PORT, and AC_SHUTDWN_PORT properties. # Value 0 The installer assigns default port numbers to the domain and node components. # Value 1 You can manually set the port numbers for the domain and node components. ADVANCE_PORT_CONFIG=0 # The MIN_PORT property represents the lowest port number in the range of port numbers that can be assigned to the application service processes that run on this node. # Set the property if ADVANCE_PORT_CONFIG=1. MIN_PORT= # The MAX_PORT property represents the highest port number in the range of port numbers that can be assigned to the application service processes that run on this node. # Set the property if ADVANCE_PORT_CONFIG=1. MAX_PORT= # The TOMCAT_PORT property represents the port number used by the Service Manager on the node. Default is 6006. # Set the property if ADVANCE_PORT_CONFIG=1. # The Service Manager listens for incoming connection requests on this port. # Client applications use this port to communicate with the services in the domain. # This is the port that the Informatica command line programs use to communicate with the domain. # This is also the port for the SQL data service JDBC/ODBC driver. TOMCAT_PORT= # The AC_PORT property represents the port number used by Informatica Administrator. Default is 6007. # Set the property if CREATE_DOMAIN=1 and ADVANCE_PORT_CONFIG=1. AC_PORT= # The SERVER_PORT property controls the server shutdown for the domain Service Manager. The Service Manager listens for shutdown commands on this port. Default is 6008. # Set the property if ADVANCE_PORT_CONFIG=1. SERVER_PORT= # The AC_SHUTDWN_PORT property represents the port number that controls the server shutdown for Informatica Administrator. Default is 6009. # Set the property if ADVANCE_PORT_CONFIG=1. # Informatica Administrator listens for shutdown commands on this port. AC_SHUTDWN_PORT= #------------------------------------------------------------------------------------------------------------ #Optional parameters to create Model Repository Service, monitoring Model Repository Service, and Data Integration Service from the installer. # Set CREATE_SERVICES=1 and provide the Model repository database parameters, Model Repository Service name, Data Integration Service name, and port. # Use a different database user account for Model repository database instead of using the domain database user or database user. # If JOIN_DOMAIN=1, then set CREATE_SERVICES=0. CREATE_SERVICES=0 # optional parameter to create a separate Model Repository Service to monitor statistics. # Set CREATE_MONITORING_STATS=1 to create a monitoring Model Repository Service to monitor statistics. Otherwise, set CREATE_MONITORING_STATS=0 # set CREATE_MONITORING_STATS value to 0 or 1 only if CREATE_SERVICE=1. Otherwise, leave the field set to 0. CREATE_MONITORING_STATS=0 # Set KERBEROS_SECURITY_DOMAIN_NAME and KERBEROS_DOMAIN_PSSWD only if you chose to use Kerberos authentication for the Model Repository Service and Data Integration Service. (ENABLE_KERBEROS=1 and CREATE_SERVICES=1). #The KERBEROS_SECURITY_DOMAIN_NAME property represents the security domain name. KERBEROS_SECURITY_DOMAIN_NAME= #The KERBEROS_DOMAIN_PSSWD property represents the security domain password. KERBEROS_DOMAIN_PSSWD= # The MRS_DB_TYPE property represents the database type for the domain configuration database. # Set the property to one of the following database types (case-sensitive): Oracle, MSSQLServer, or DB2. MRS_DB_TYPE=Oracle/MSSQLServer/DB2 # The MRS_DB_UNAME property represents the database user account name for the domain configuration repository. MRS_DB_UNAME=UserName # The MRS_DB_PASSWD property represents the database password for the database user account. MRS_DB_PASSWD=UserPassword # The MRS_DB_SSL_ENABLED property represents whether the database is in SSL mode or not. # Set the property to "true" if you want to enable secure communication. # Also, if this property is set to true, then MRS_DB_CUSTOM_STRING_SELECTION property must be set to 1. MRS_DB_SSL_ENABLED=false #Set this property only if MRS_DB_SSL_ENABLED is set to true. #MRS_SSL_DEFAULT_STRING should include the following secure DB parameters: #EncryptionMethod=SSL;HostNameInCertificate=;ValidateServerCertificate= MRS_SSL_DEFAULT_STRING= # The TRUSTSTORE_MRS_DB_FILE and TRUSTSTORE_MRS_DB_PASSWD properties to be set only if you want to enable secure communication. # for the DB property, MRS_DB_SSL_ENABLED=true # Set the TRUSTSTORE_MRS_DB_FILE property to the location of the trust store file for the DB TRUSTSTORE_MRS_DB_FILE= # Set the TRUSTSTORE_MRS_DB_PASSWD as a password of the trust store file for the DB TRUSTSTORE_MRS_DB_PASSWD= # The MRS_SQLSERVER_SCHEMA_NAME property represents the name of the schema that contains domain configuration tables. # Set the property if MRS_DB_TYPE=MSSQLServer. # If MRS_SQLSERVER_SCHEMA_NAME is empty, the installer creates the tables in the default schema. MRS_SQLSERVER_SCHEMA_NAME= # The MRS_DB2_TABLESPACE property represents the name of the tablespace in which to create the tables. # Set the property if MRS_DB_TYPE=DB2. # Specify a tablespace that meets the pageSize requirement of 32768 bytes. # In a single-partition database, if MRS_DB2_TABLESPACE is empty, the installer creates the tables in the default tablespace. # In a multi-partition database, define the tablespace in the catalog partition of the database. MRS_DB2_TABLESPACE= # The MRS_DB_CUSTOM_STRING_SELECTION property determines whether to use a JDBC URL or a custom connection string to connect to the domain configuration database. # Set MRS_DB_CUSTOM_STRING_SELECTION=1 if MRS_TRUSTED_CONNECTION=1. Also provide the default valid connection string in MRS_DB_CUSTOM_STRING. # Value 0 The installer creates a JDBC URL from the database properties you provide # Value 1 The installer uses the custom connection string you provide. MRS_DB_CUSTOM_STRING_SELECTION=0 # The MRS_DB_SERVICENAME property represents the service name or database name of the database. # Set the property if MRS_DB_CUSTOM_STRING_SELECTION=0. # Set the property to the service name for Oracle and IBM DB2 databases. # Set the property to the database name for Microsoft SQL Server. # Leave the property blank if MRS_DB_CUSTOM_STRING_SELECTION=1. MRS_DB_SERVICENAME=DBServiceName # The MRS_DB_ADDRESS property represents the host name and port number for the database instance. # Set the property if MRS_DB_CUSTOM_STRING_SELECTION=0. # Set the property in the format <hostname>:<portnumber>. # Leave the property blank if MRS_DB_CUSTOM_STRING_SELECTION=1. MRS_DB_ADDRESS=HostName:PortNumber # The MRS_ADVANCE_JDBC_PARAM property represents additional parameters in the JDBC URL connection string. # If MRS_DB_CUSTOM_STRING_SELECTION=0, you can set the property to include optional parameters in the JDBC URL connection string. # The parameter string must be valid. # If the parameter is empty, the installer creates the JDBC URL without additional parameters. MRS_ADVANCE_JDBC_PARAM= # The MRS_DB_CUSTOM_STRING property represents a valid custom JDBC connection string. # Set the property if MRS_DB_CUSTOM_STRING_SELECTION=1. MRS_DB_CUSTOM_STRING= # The MONITORING_DB_TYPE property represents the database type for the monitoring Model repository database. # Set the property to one of the following database types (case-sensitive): Oracle, MSSQLServer, or DB2. # Choose the MONITORING_DB_TYPE when CREATE_MONITORING_STATS=1. Otherwise, leave the field blank. MONITORING_DB_TYPE=Oracle/MSSQLServer/DB2 # The MONITORING_DB_UNAME property represents the database user account name for the monitoring Model Repository Service. MONITORING_DB_UNAME=UserName # The MONITORING_DB_PASSWD property represents the database password for the database user account for the monitoring Model Repository Service. MONITORING_DB_PASSWD=UserPassword # The MONITORING_DB_SSL_ENABLED property represents whether the database is in SSL mode or not. #Set the property to "true" if you want to enable secure communication. # Also, if this property is set to true then MONITORING_DB_CUSTOM_STRING_SELECTION property must be set to 1. MONITORING_DB_SSL_ENABLED=false #Set this property only if MONITORING_DB_SSL_ENABLED is set to true. #MONITORING_SSL_DEFAULT_STRING should include the following secure DB parameters: #EncryptionMethod=SSL;HostNameInCertificate=;ValidateServerCertificate= MONITORING_SSL_DEFAULT_STRING= # Set the TRUSTSTORE_MONITORING_DB_FILE and TRUSTSTORE_MONITORING_DB_PASSWD properties if secure communication is enabled. # If the DB property MONITORING_DB_SSL_ENABLED=true? # Set the TRUSTSTORE_MONITORING_DB_FILE property to the location of the truststore file for the monitoring Model repository database. # Set the TRUSTSTORE_MONITORING_DB_PASSWD as a password of the truststore file for the monitoring Model repository database. TRUSTSTORE_MONITORING_DB_FILE= TRUSTSTORE_MONITORING_DB_PASSWD= # The MONITORING_SQLSERVER_SCHEMA_NAME property represents the name of the schema that contains Model repository tables. # Set the property if MONITORING_DB_TYPE=MSSQLServer. # If MONITORING_SQLSERVER_SCHEMA_NAME is empty, the installer creates the tables in the default schema. MONITORING_SQLSERVER_SCHEMA_NAME= # The MONITORING_DB2_TABLESPACE property represents the name of the tablespace in which to create the tables. # Set the property if MONITORING_DB_TYPE=DB2. # Specify a tablespace that meets the pageSize requirement of 32768 bytes. # In a single-partition database, if MONITORING_DB2_TABLESPACE is empty, the installer creates the tables in the default tablespace. # In a multi-partition database, define the tablespace in the catalog partition of the database. MONITORING_DB2_TABLESPACE= # The MONITORING_DB_CUSTOM_STRING_SELECTION property determines whether to use a JDBC URL or a custom connection string to connect to the monitoring Model repository database. # Set MONITORING_DB_CUSTOM_STRING_SELECTION=1 if MONITORING_TRUSTED_CONNECTION=1. Also provide the default connection string in MONITORING_DB_CUSTOM_STRING. # Value 0 The installer creates a JDBC URL from the database properties you provide. # Value 1 The installer uses the custom connection string you provide. MONITORING_DB_CUSTOM_STRING_SELECTION=0 # The MONITORING_DB_SERVICENAME property represents the service name or database name of the database. # Set the property if MONITORING_DB_CUSTOM_STRING_SELECTION=0. # Set the property to the service name for Oracle and IBM DB2 databases. # Set the property to the database name for Microsoft SQL Server. # Leave the property blank if MONITORING_DB_CUSTOM_STRING_SELECTION=1. MONITORING_DB_SERVICENAME=DBServiceName # The MONITORING_DB_ADDRESS property represents the host name and port number for the database instance. # Set the property if MONITORING_DB_CUSTOM_STRING_SELECTION=0. # Set the property in the format <hostname>:<portnumber>. # Leave the property blank if MONITORING_DB_CUSTOM_STRING_SELECTION=1. MONITORING_DB_ADDRESS=HostName:PortNumber # The MONITORING_ADVANCE_JDBC_PARAM property represents additional parameters in the JDBC URL connection string. # If MONITORING_DB_CUSTOM_STRING_SELECTION=0, you can set the property to include optional parameters in the JDBC URL connection string. # The parameter string must be valid. # If the parameter is empty, the installer creates the JDBC URL without additional parameters. MONITORING_ADVANCE_JDBC_PARAM= # The MONITORING_DB_CUSTOM_STRING property represents a valid custom JDBC connection string. # Set the property if MONITORING_DB_CUSTOM_STRING_SELECTION=1. MONITORING_DB_CUSTOM_STRING= # Model Repository Service name MRS_SERVICE_NAME=Model_Repository_Service # Set the property to the absolute path and file name of the keytab file if ENABLE_KERBEROS=1 and SPN_SHARE_LEVEL=PROCESS # Leave the property blank for rest of the cases. MRS_KEYTAB_FILELOC= # Name of the monitoring Model repository database. # Set the MONITORING_SERVICE_NAME if CREATE_MONITORING_STATS=1. Otherwise, leave the field blank. MONITORING_SERVICE_NAME=MRS_Monitoring_Service # Set the property to the absolute path and file name of the keytab file if ENABLE_KERBEROS=1, CREATE_MONITORING_STATS=1 and SPN_SHARE_LEVEL=PROCESS. # Leave the property blank for rest of the cases. MONITORING_KEYTAB_FILELOC= # Data Integration Service name DIS_SERVICE_NAME=Data_Integration_Service # Set the property to the absolute path and file name of the keytab file if ENABLE_KERBEROS=1 and SPN_SHARE_LEVEL=PROCESS # Leave the property blank for rest of the cases. DIS_KEYTAB_FILELOC= # HTTP protocol type # Set the property to one of the following protocol types (case-sensitive): http/https/both DIS_PROTOCOL_TYPE= # HTTP PortNumber # if DIS_PROTOCOL_TYPE=http or DIS_PROTOCOL_TYPE=both, set this property. # Leave this property blank for DIS_PROTOCOL_TYPE=https case. DIS_HTTP_PORT= # HTTPS PortNumber # if DIS_PROTOCOL_TYPE=https or DIS_PROTOCOL_TYPE=both, set this property. # Leave this property blank for DIS_PROTOCOL_TYPE=http case. DIS_HTTPS_PORT= # DIS_CUSTOM_SELECTION is optional. # You can set DIS_CUSTOM_SELECTION value to true only if DIS_PROTOCOL_TYPE=https or DIS_PROTOCOL_TYPE=both DIS_CUSTOM_SELECTION=false #Below fields are only required when you set DIS_CUSTOM_SELECTION=true # Set keystore file location in DIS_KEYSTORE_DIR DIS_KEYSTORE_DIR= DIS_KEYSTORE_PASSWD= # Set truststore file location in DIS_TRUSTSTORE_DIR DIS_TRUSTSTORE_DIR= DIS_TRUSTSTORE_PASSWD= # Set the following property to true if you want to use a user defined JDK for the Data Integration Service. USE_USER_JDK_FOR_DIS=false # Set the following property to a valid JDK path if you set USE_USER_JDK_FOR_DIS to true. DIS_JDK_HOME= # The CLOUD_SUPPORT_ENABLE property is to support the installation on cloud and valid only for silent cases. # Set the property to 1 only for cloud based installations support don't edit this property otherwise. CLOUD_SUPPORT_ENABLE=0 # set ASSOCIATE_PROFILE_CONNECTION=1 to associate a profile warehouse connection and database with the Data Integration Service # and fill the profiling warehouse database fields respectively. ASSOCIATE_PROFILE_CONNECTION=0 # Enter database information for the profiling warehouse. # The PWH_DB_TYPE property represents the database type for the profile warehouse connection. # Set the property to one of the following database types (case-sensitive): Oracle, SQLServer, DB2. PWH_DB_TYPE=Oracle/SQLServer/DB2 # The PWH_DB_UNAME property represents the database user account name for the profiling warehouse repository. PWH_DB_UNAME=UserName # The PWH_DB_PASSWD property represents the database password for the database user account. PWH_DB_PASSWD=UserPassword # The PWH_SQLSERVER_SCHEMA_NAME property represents the name of the schema that will contain profiling warehouse tables. # Set the property if DB_TYPE=SQLServer. # If PWH_SQLSERVER_SCHEMA_NAME is empty, the installer creates the tables in the default schema. PWH_SQLSERVER_SCHEMA_NAME= # The PWH_DB2_TABLESPACE property represents the name of the tablespace in which profiling warehouse tables need to be created. # Set the property if DB_TYPE=DB2. # Specify a tablespace that meets the pageSize requirement of 32768 bytes. # In a single-partition database, if PWH_DB2_TABLESPACE is empty, the installer creates the tables in the default tablespace. # In a multi-partition database, define the tablespace in the catalog partition of the database. PWH_DB2_TABLESPACE= # The PWH_DB_CUSTOM_STRING_SELECTION property determines whether to use a JDBC URL or a custom connection string to connect to the profiling warehouse database. # Set PWH_DB_CUSTOM_STRING_SELECTION=1 if PWH_TRUSTED_CONNECTION=1. Additionally, provide the default valid connection string in PWH_DB_CUSTOM_STRING. # Value 0 The installer creates a JDBC URL from the database properties you provide # Value 1 The installer uses the custom connection string you provide. PWH_DB_CUSTOM_STRING_SELECTION=0 # The PWH_DB_SERVICENAME property represents the service name or database name of the database. # Set the property if PWH_DB_CUSTOM_STRING_SELECTION=0. # Set the property to the service name for Oracle and IBM DB2 databases. # Set the property to the database name for Microsoft SQL Server and Sybase ASE databases. # Leave the property blank if PWH_DB_CUSTOM_STRING_SELECTION=1. PWH_DB_SERVICENAME=DBServiceName # The PWH_DB_ADDRESS property represents the host name and port number for the database instance. # Set the property if PWH_DB_CUSTOM_STRING_SELECTION=0. # Set the property in the format HostName:PortNumber. # Leave the property blank if PWH_DB_CUSTOM_STRING_SELECTION=1. PWH_DB_ADDRESS=HostName:PortNumber # The PWH_ADVANCE_JDBC_PARAM property represents additional parameters in the JDBC URL connection string. # If PWH_DB_CUSTOM_STRING_SELECTION=0, you can set the property to include optional parameters in the JDBC URL connection string. # The parameter string must be valid. # If the parameter is empty, the installer creates the JDBC URL without additional parameters. PWH_ADVANCE_JDBC_PARAM= # The PWH_DB_CUSTOM_STRING property represents a valid custom JDBC connection string. # Set the property if PWH_DB_CUSTOM_STRING_SELECTION=1. PWH_DB_CUSTOM_STRING= # THE PWH_DATA_ACCESS_CONNECT_STRING should be provided if ASSOCIATE_PROFILE_CONNECTION=1 # This property is required for the Data Integration Service to update the profiling warehouse tables when profiles are run PWH_DATA_ACCESS_CONNECT_STRING= # set LOAD_DATA_DOMAIN=1 to create the Content Management Service with a staging database connection # and then, load the out-of-the-box data domains. LOAD_DATA_DOMAIN=0 # Name of the content management service CMS_SERVICE_NAME=CMS # Enter protocol for the Content Management Service. # Set the property to one of the following protocol types (case-sensitive): http/https # If domain is ssl enabled, i.e, if SSL_ENABLED=true, then set CMS_PROTOCOL_TYPE=https. CMS_PROTOCOL_TYPE=http # HTTP PortNumber # if CMS_PROTOCOL_TYPE=http, set this property. # Do not use this property if you set CMS_PROTOCOL_TYPE=https. CMS_HTTP_PORT= # HTTPS PortNumber # if CMS_PROTOCOL_TYPE=https , set this property. #Do not use this property if you set CMS_PROTOCOL_TYPE=http. CMS_HTTPS_PORT= # CMS_CUSTOM_SELECTION is optional. # You can set CMS_CUSTOM_SELECTION value to true only if CMS_PROTOCOL_TYPE=https CMS_CUSTOM_SELECTION=false #Below fields are required only if CMS_CUSTOM_SELECTION=true. # Below fields to be set when CMS_PROTOCOL_TYPE=https # Leave this property blank for CMS_PROTOCOL_TYPE=http case. CMS_KEYSTORE_FILE= CMS_KEYSTORE_PASSWD= # The CMS_DB_TYPE property represents the database type for the content management service staging database connection. # Set the property to one of the following database types (case-sensitive): Oracle, SQLServer, DB2. CMS_DB_TYPE=Oracle/SQLServer/DB2 # The CMS_DB_UNAME property represents the database user account name for the reference table staging database. CMS_DB_UNAME=UserName # The CMS_DB_PASSWD property represents the database password for the database user account. CMS_DB_PASSWD=UserPassword # The CMS_SQLSERVER_SCHEMA_NAME property represents the name of the schema that contains the reference table staging database. # Set the property if DB_TYPE=SQLServer. # If you do not specify a value for CMS_SQLSERVER_SCHEMA_NAME , the installer creates the tables in the default schema. CMS_SQLSERVER_SCHEMA_NAME= # The CMS_DB2_TABLESPACE property represents the name of the tablespace in which to create the tables. # Set the property if DB_TYPE=DB2. # Specify a tablespace that meets the pageSize requirement of 32768 bytes. # In a single-partition database, if CMS_DB2_TABLESPACE is empty, the installer creates the tables in the default tablespace. # In a multi-partition database, define the tablespace in the catalog partition of the database. CMS_DB2_TABLESPACE= # The CMS_DB_CUSTOM_STRING_SELECTION property determines whether to use a JDBC URL or a custom connection string to connect to the reference data warehouse. # Set CMS_DB_CUSTOM_STRING_SELECTION=1 if CMS_TRUSTED_CONNECTION=1. You also need to provide the default valid, connection string for the CMS_DB_CUSTOM_STRING property. # Value 0 The installer creates a JDBC URL from the database properties you provide. # Value 1 The installer uses the custom connection string you provide. CMS_DB_CUSTOM_STRING_SELECTION=0 # The CMS_DB_SERVICENAME property represents the service name or database name of the database. # Set the property if CMS_DB_CUSTOM_STRING_SELECTION=0. # Set the property to the service name for Oracle and IBM DB2 databases. # Set the property to the database name for Microsoft SQL Server and Sybase ASE databases. # Leave the property blank if CMS_DB_CUSTOM_STRING_SELECTION=1. CMS_DB_SERVICENAME=DBServiceName # The CMS_DB_ADDRESS property represents the host name and port number for the database instance. # Set the property if CMS_DB_CUSTOM_STRING_SELECTION=0. # Set the property in the format HostName:PortNumber. # Leave the property blank if CMS_DB_CUSTOM_STRING_SELECTION=1. CMS_DB_ADDRESS=HostName:PortNumber # The CMS_ADVANCE_JDBC_PARAM property represents additional parameters in the JDBC URL connection string. # If CMS_DB_CUSTOM_STRING_SELECTION=0, you can set the property to include optional parameters in the JDBC URL connection string. # The parameter string must be valid. # If the parameter is empty, the installer creates the JDBC URL without additional parameters. CMS_ADVANCE_JDBC_PARAM= # The CMS_DB_CUSTOM_STRING property represents a valid custom JDBC connection string. # Set the property if CMS_DB_CUSTOM_STRING_SELECTION=1. CMS_DB_CUSTOM_STRING= # THE CMS_DATA_ACCESS_CONNECT_STRING should be provided if LOAD_DATA_DOMAIN=1 # This property is required for the Data Integration Service to update the reference table staging database. CMS_DATA_ACCESS_CONNECT_STRING= # Parameters to create Catalog Service and Informatica Cluster Service from installer. # Set CLUSTER_TYPE=1 for embeddedl Hadoop cluster that creates the Informatica Cluster Service, configures Ambari server host and agent, and then creates a Catalog service . # Set CLUSTER_TYPE=2 for an existing Hadoop cluster that creates the Catalog service. CLUSTER_TYPE=2 #Set this field to one of the values if CLUSTER_TYPE=2. Otherwise, do not use the property. #Set this field to HortonWorks or ClouderaManager or HDInsight if you know the cluster URL, username, and Password. #Set this field to HortonWorks or ClouderaManager or HDInsight,if you want the installer to detect ZooKeeper, HDFS, and YARN configurations based on your inputs # Otherwise, set this field value to Others to provide ZooKeeper, HDFS and YARN URIs manually. CLUSTER_HADOOP_DISTRIBUTION_TYPE=HortonWorks/ClouderaManager/HDInsight/Others # Set IS_CLUSTER_HA_ENABLE=true if CLUSTER_TYPE=2 and the Cluster is highly available. Otherwise, do not use this property. # leave this property blank for CLUSTER_HADOOP_DISTRIBUTION_TYP=HortonWorks/ClouderaManager/HDInsight IS_CLUSTER_HA_ENABLE= # Set IS_CLUSTER_SECURE=true if the Hadoop cluster is Kerberos–enabled. # This property applies to both embedded Hadoop cluster managed by Informatica and existing Hadoop cluster that creates the Catalog service in your enterprise. # If the cluster is not Kerberos-enabled, do not use this property. # If CLUSTER_TYPE=2 and CLUSTER_HADOOP_DISTRIBUTION_TYP=HDInsight, do not use this property IS_CLUSTER_SECURE= # Set IS_CLUSTER_SSL_ENABLE=true if you need the Hadoop cluster to be SSL–enabled. Otherwise, do not use this property. # If CLUSTER_TYPE=1, then set this property if you need the Hadoop cluster to be SSL–enabled. # If CLUSTER_TYPE=2, then set this property if you need the Hadoop cluster to be SSL–enabled. # If SSL_ENABLED=false i.e, if domain is not SSL enabled then leav this proper blank or set to false. # if SSL_ENABLED=true i.e, if domain is SSL enabled, set IS_CLUSTER_SSL_ENABLE=true if you need the Hadoop cluster to be SSL–enabled. Otherwise, do not use this property. # If CLUSTER_TYPE=2 and CLUSTER_HADOOP_DISTRIBUTION_TYP=HDInsight, do not use this property IS_CLUSTER_SSL_ENABLE= # GATEWAY_USERNAME field is required only for embedded Hadoop cluster cluster managed by informatica # where you connect to other hosts from the Enterprise Data Catalog domain host without an SSH password. # The default user name is root. If CLUSTER_TYPE=2, do not use this property. GATEWAY_USERNAME=root # HADOOP_SERVICE_NAME parameter is the name of the Informatica Cluster Service. # This property applies to CLUSTER_TYPE=1, which indicates an embedded Hadoop cluster managed by informatica. # Do not use this field if CLUSTER_TYPE=2. HADOOP_SERVICE_NAME= # HADOOP_SERVICE_PORT parameter is required for CLUSTER_TYPE=1 i.e for embedded Hadoop cluster managed by informatica, port for Informatica hadoop service. # leave this property blank for CLUSTER_TYPE=2 i.e for existing Hadoop cluster. # leave this property blank for SSL_ENABLED=true. HADOOP_SERVICE_PORT= # OVERRIDE_HADOOP_AMBARI_PSD parameter is required for CLUSTER_TYPE=1 i.e for embedded Hadoop cluster managed by informatica, port for Informatica hadoop service. # Set OVERRIDE_HADOOP_AMBARI_PSD=true, if you want to override the default Hadoop Ambari password, else set it to false. OVERRIDE_HADOOP_AMBARI_PSD=false # NEW_HADOOP_AMBARI_PASSWD parameter is required for CLUSTER_TYPE=1 i.e for embedded Hadoop cluster managed by informatica, port for Informatica hadoop service. # Set NEW_HADOOP_AMBARI_PASSWD field only if OVERRIDE_HADOOP_AMBARI_PSD=true, else leave this property blank. NEW_HADOOP_AMBARI_PASSWD= # The CONFIRM_HADOOP_AMBARI_PASSWD property confirms the password you set for the hadoop ambari. # Set the property to the password you set in the NEW_HADOOP_AMBARI_PASSWD property to confirm the password. # Set this property only if OVERRIDE_HADOOP_AMBARI_PSD=true. CONFIRM_HADOOP_AMBARI_PASSWD= # HADOOP_TLS_HTTPS_PORT parameter is required only if SSL_ENABLED=true i.e for embedded Hadoop cluster managed by informatica, port for Informatica hadoop service. # leave this property blank for CLUSTER_TYPE=2 i.e for existing Hadoop cluster. HADOOP_TLS_HTTPS_PORT= # HADOOP_CUSTOM_SELECTION is optional. # You can set HADOOP_CUSTOM_SELECTION value to true or false only if SSL_ENABLED=true and CLUSTER_TYPE=1 HADOOP_CUSTOM_SELECTION=false # HADOOP_KEYSTORE_FILE parameter is required only if SSL_ENABLED=true # leave this property blank for CLUSTER_TYPE=2 i.e for existing Hadoop cluster. # Below field is required only if HADOOP_CUSTOM_SELECTION=true. HADOOP_KEYSTORE_FILE= # HADOOP_KEYSTORE_ALIAS parameter is required only if SSL_ENABLED=true # leave this property blank for CLUSTER_TYPE=2 i.e for existing Hadoop cluster. # Below field is required only if HADOOP_CUSTOM_SELECTION=true. HADOOP_KEYSTORE_ALIAS= # HADOOP_KEYSTORE_PASSWD parameter is required only if SSL_ENABLED=true # leave this property blank for CLUSTER_TYPE=2 i.e for existing Hadoop cluster. # Below field is required only if HADOOP_CUSTOM_SELECTION=true. HADOOP_KEYSTORE_PASSWD= # HADOOP_TRUSTSTORE_FILE property is the location of the truststore file. This property is required only if SSL_ENABLED=true , which means the domain is SSL-enabled. # Do not use this field if CLUSTER_TYPE=2. # The location must be a common location present in all the Hadoop Nodes where you can copy the truststore file after the export and import of HADOOP_KEYSTORE_FILE. HADOOP_TRUSTSTORE_FILE= # HADOOP_GATEWAY_HOST parameter is required if you install Enterprise Data Catalog on an embedded Hadoop cluster managed by informatica (CLUSTER_TYPE=1). This is the host where Ambari server is installed. # Do not use this property for the existing Hadoop cluster, which is indicated by CLUSTER_TYPE=2. HADOOP_GATEWAY_HOST= # HADOOP_NODES parameter applies to the embedded Hadoop cluster and refers to the Ambari agent host name. # If you use multiple Ambari agent hosts, specify the comma-separated values of multiple Ambari agent host names. # Do not use this property for installation on an existing Hadoop cluster, which is represented by CLUSTER_TYPE=2. HADOOP_NODES= # HADOOP_GATEWAY_PORT property represents the port number where the Ambari server needs to run. This property applies to embedded Hadoop cluster managed by Informatica. # Do not use this property for an existing Hadoop cluster, which is represented by CLUSTER_TYPE=2. HADOOP_GATEWAY_PORT=8080 # WORKING_DIR is required only if RUN_CLUSTER_PREVALIDATION=1 and CLUSTER_TYPE=1. WORKING_DIR= # HADOOP_LOG_DIR property is required only if CLUSTER_TYPE=1. # Set this property to specific directory if you want to specify directory to point YARN, HDFS and ZOOKEEPER logs and data dirs. # This is optional and if left blank, default directory will used. HADOOP_LOG_DIR= # Applies to Kerberos-enabled, embedded Hadoop cluster managed by Informatica. # This property refers to the type of the Key Distribution Center for the Hadoop cluster. # You can choose either an MIT KDC or a Microsoft Active Directory. Set this property if CLUSTER_TYPE=1 and IS_CLUSTER_SECURE=true. # if the cluster is not Kerberos-enabled, do not use this property. KDC_TYPE=mit-kdc/active-directory # Applies to Kerberos-enabled, embedded Hadoop cluster managed by Informatica. # This property applies to Microsoft Active Directory and represents the loction of the certificate file for KDC. KDC_CERT_FILE_LOC= # Applies to Kerberos-enabled, embedded Hadoop cluster managed by Informatica. # This property applies to Microsoft Active Directory and represents the URL to the LDAP server directory. LDAP_URL= # Applies to Kerberos-enabled, embedded Hadoop cluster managed by Informatica. # This property applies to Microsoft Active Directory and represents the Distinguished Name of the container to which the user belongs. CONTAINER_DN= # Name of the KDC host machine. Set this property if CLUSTER_TYPE=1 and IS_CLUSTER_SECURE=true. # If the CLUSTER_TYPE=2, do not use the property. KDC_HOST= # Name of the Kerberos realm on the machine that hosts the KDC server . Set this property if CLUSTER_TYPE=1 and IS_CLUSTER_SECURE=true. # If the CLUSTER_TYPE=2, do not use the property. IHS_REALM= # The name of the administrator server machine that hosts the KDC server. Set this property if CLUSTER_TYPE=1 and IS_CLUSTER_SECURE=true. # If the CLUSTER_TYPE=2, do not use the property. IHS_ADMINISTRATOR_SERVER_HOST= # Kerberos administrator principal. Set this property if CLUSTER_TYPE=1 and IS_CLUSTER_SECURE=true. # If the CLUSTER_TYPE=2, do not use the property. IHS_ADMINISTRATOR_PRINCIPAL= # Kerberos administrator password. Set this property if CLUSTER_TYPE=1 and IS_CLUSTER_SECURE=true. # If the CLUSTER_TYPE=2, do not use the property. IHS_ADMINISTRATOR_PASSWORD= #KERBEROS_CONF_FILE_LOC property refers to the location of krb5.conf file that you need to provide. # You need to specify this property for Kerberos-enabled embedded Hadoop cluster # or Kerberos-enabled existing Hadoop cluster in your enterprise. KERBEROS_CONF_FILE_LOC= # Set this property only if CLUSTER_TYPE=1. If the CLUSTER_TYPE=2, do not use the property. # Set this property if IS_CLUSTER_SECURE=true. # CATALOGE_SERVICE_KEYTAB_LOCATION property refers to the location of the keytab file that you set for the Catalog Service # if the Catalog Service is configured on embedded Hadoop cluster. CATALOGE_SERVICE_KEYTAB_LOCATION= # set DOMAINMACHINE_PASSWORDLESS_SSH_ENABLED=1 if domain machine has passwordless ssh enabled to all the cluster nodes. # Set these properties only if RUN_CLUSTER_PREVALIDATION=1 # Set this property for both CLUSTER_TYPE=1 and CLUSTER_TYPE=2 DOMAINMACHINE_PASSWORDLESS_SSH_ENABLED=0 # set HOST_SSH_USER to connect to other hosts from the domain host # The default user name is root. # Set these properties only if RUN_CLUSTER_PREVALIDATION=1 # Set this property for both CLUSTER_TYPE=1 and CLUSTER_TYPE=2 HOST_SSH_USER=root # set SSH_HOST_NAMES to all the cluster nodes that you want to connect using passwordless ssh. # If you use multiple hosts, specify the comma-separated values of multiple host names. # Set these properties only if RUN_CLUSTER_PREVALIDATION=1 # Set this property for both CLUSTER_TYPE=1 and CLUSTER_TYPE=2 SSH_HOST_NAMES= #Set CLUSTER_CONFIG_VALIDATION=1, if you want to run configuration validations on the cluster. # Set this property only if RUN_CLUSTER_PREVALIDATION=1 and CLUSTER_TYPE=2. # For CLUSTER_TYPE=1, set CLUSTER_CONFIG_VALIDATION=0. CLUSTER_CONFIG_VALIDATION=0 #CATALOGUE_SERVICE_NAME parameter is required for both embedded Hadoop cluster managed by informatica and existing Hadoop cluster, it's a Catalogue service name. CATALOGUE_SERVICE_NAME= #CATALOGUE_SERVICE_PORT parameter is required for both embedded Hadoop cluster managed by informatica and existing Hadoop cluster, it's a Catalogue service port. #leave this property blank for SSL_ENABLED=true. CATALOGUE_SERVICE_PORT= #CATALOGUE_SERVICE_TLS_HTTPS_PORT parameter is required only if SSL_ENABLED=true i.e for existing Hadoop cluster, port for Informatica hadoop service. CATALOGUE_SERVICE_TLS_HTTPS_PORT= # CATALOGUE_SERVICE_CUSTOM_SELECTION is optional. # You can set CATALOGUE_SERVICE_CUSTOM_SELECTION value to true or false only if SSL_ENABLED=true CATALOGUE_SERVICE_CUSTOM_SELECTION=false #Below fields are required only if CATALOGUE_SERVICE_CUSTOM_SELECTION=true. #CATALOGUE_SERVICE_KEYSTORE_FILE parameter is required only if SSL_ENABLED=true CATALOGUE_SERVICE_KEYSTORE_FILE= #Below fields are required only if CATALOGUE_SERVICE_CUSTOM_SELECTION=true. #CATALOGUE_SERVICE_KEYSTORE_ALIAS parameter is required only if SSL_ENABLED=true CATALOGUE_SERVICE_KEYSTORE_ALIAS= #Below fields are required only if CATALOGUE_SERVICE_CUSTOM_SELECTION=true. #CATALOGUE_SERVICE_KEYSTORE_PASSWD parameter is required only if SSL_ENABLED=true CATALOGUE_SERVICE_KEYSTORE_PASSWD= #DOMAIN_KEYSTORE_ALIAS parameter is required only if SSL_ENABLED=true #This field is required only if domain is created in ssl mode and when you set TLS_CUSTOM_SELECTION=true DOMAIN_KEYSTORE_ALIAS= #CATALOGUE_SERVICE_KEYSTORE_FILE parameter is required only if IS_CLUSTER_SSL_ENABLE=true #If IS_CLUSTER_SSL_ENABLE=true, then set this propoerty for CLUSTER_TYPE=2. #If CLUSTER_TYPE=1, then leave this property blank. CATALOGUE_SERVICE_SOLR_KEYSTORE_FILE= #CATALOGUE_SERVICE_KEYSTORE_PASSWD parameter is required only if IS_CLUSTER_SSL_ENABLE=true #If IS_CLUSTER_SSL_ENABLE=true, then set this propoerty for CLUSTER_TYPE=2. #If CLUSTER_TYPE=1, then leave this property blank. CATALOGUE_SERVICE_SOLR_KEYSTORE_PASSWD= # YARN_QUEUE_NAME is valid YARN queue name where YARN applications would launch # Set this property if CLUSTER_TYPE=2, else leave the field blank # By default the value will be "default" YARN_QUEUE_NAME=default #CLUSTER_HADOOP_DISTRIBUTION_URL field is required if CLUSTER_HADOOP_DISTRIBUTION_TYP=HortonWorks or Cloudera Manager or HDInsight. CLUSTER_HADOOP_DISTRIBUTION_URL= #CLUSTER_HADOOP_DISTRIBUTION_URL_USER field is required if CLUSTER_HADOOP_DISTRIBUTION_TYP=HortonWorks or Cloudera Manager or HDInsight. CLUSTER_HADOOP_DISTRIBUTION_URL_USER= #CLUSTER_HADOOP_DISTRIBUTION_URL_PASSWD field is required if CLUSTER_HADOOP_DISTRIBUTION_TYP=HortonWorks or ClouderaManager or HDInsight CLUSTER_HADOOP_DISTRIBUTION_URL_PASSWD= #YARN_RESOURCE_MANAGER_URI parameter is required for CLUSTER_TYPE=2 i.e for existing Hadoop cluster, value to be given as hostname:port. #leave this property blank for CLUSTER_TYPE=1 i.e for embedded Hadoop cluster managed by informatica. #leave this property blank for CLUSTER_HADOOP_DISTRIBUTION_TYP=HortonWorks/ClouderaManager/HDinsight YARN_RESOURCE_MANAGER_URI= #YARN_RESOURCE_MANAGER_HTTP_URI parameter is required for CLUSTER_TYPE=2 i.e for existing Hadoop cluster, value to be given as hostname:port. #leave this property blank for CLUSTER_TYPE=1 i.e for embedded Hadoop cluster managed by informatica. #leave this property blank for CLUSTER_HADOOP_DISTRIBUTION_TYP=HortonWorks/ClouderaManager/HDinsight YARN_RESOURCE_MANAGER_HTTP_URI= #YARN_RESOURCE_MANAGER_SCHEDULER_URI parameter is required for CLUSTER_TYPE=2 i.e for existing Hadoop cluster, value to be given as hostname:port. #leave this property blank for CLUSTER_TYPE=1 i.e for embedded Hadoop cluster managed by informatica. #leave this property blank for CLUSTER_HADOOP_DISTRIBUTION_TYP=HortonWorks/ClouderaManager/HDinsight YARN_RESOURCE_MANAGER_SCHEDULER_URI= #ZOOKEEPER_URI parameter is required for CLUSTER_TYPE=2 i.e for existing Hadoop cluster, value to be given as zookeeperhost:clientport. #leave this property blank for CLUSTER_TYPE=1 i.e for embedded Hadoop cluster managed by informatica. #leave this property blank for CLUSTER_HADOOP_DISTRIBUTION_TYP=HortonWorks/ClouderaManager/HDinsight ZOOKEEPER_URI= #HDFS_HOST_NAME parameter is required for CLUSTER_TYPE=2 i.e for existing Hadoop cluster, it's a HDFS namenode URI to be given as hostname:port. #leave this property blank for CLUSTER_TYPE=1 i.e for embedded Hadoop cluster managed by informatica. #leave this property blank for CLUSTER_HADOOP_DISTRIBUTION_TYP=HortonWorks/ClouderaManager/HDinsight HDFS_HOST_NAME= #CLUSTER_NAME parameter is required for CLUSTER_TYPE=2 i.e for existing Hadoop cluster, directory under hdfs and CLUSTER_HADOOP_DISTRIBUTION_TYPE=ClouderaManager #if CLUSTER_TYPE=1 i.e for embedded Hadoop cluster managed by informatica, leave this field blank. #if CLUSTER_HADOOP_DISTRIBUTION_TYPE=HortonWorks/HDinsight or Others, then leave this field blank. #Cluster Name applies only to a multi-cluster Cloudera Manager environment. CLUSTER_NAME= #SERVICE_CLUSTER_NAME parameter is required for CLUSTER_TYPE=2 i.e for existing Hadoop cluster, directory under hdfs , dynamic default is #DOMAIN_NAME_CATALOGUE_SERVICE_NAME. #if CLUSTER_TYPE=1 i.e for embedded Hadoop cluster managed by informatica, # if IS_CLUSTER_SECURE=true, then set this property to princlpal user name # else leave this field blank #if CLUSTER_TYPE=2, then Service Cluster Name should be provided mandatorily. SERVICE_CLUSTER_NAME= #HDFS_SERVICE_NAME_HA parameter is required for CLUSTER_TYPE=2 i.e for existing Hadoop cluster, directory under hdfs , if the Cluster is HA enabled i.e, for IS_CLUSTER_HA_ENABLE=true. #leave this property blank for CLUSTER_TYPE=1 i.e for embedded Hadoop cluster managed by informatica. #leave this property blank for CLUSTER_HADOOP_DISTRIBUTION_TYP=HortonWorks/ClouderaManager/HDinsight HDFS_SERVICE_NAME_HA= #HDFS_SERVICE_PRINCIPAL parameter is required for CLUSTER_TYPE=2 i.e for existing Hadoop cluster and IS_CLUSTER_SECURE=true for kerberos enabled cluster else leave this #property blank. #HDFS_SERVICE_PRINCIPAL parameter is required for CLUSTER_HADOOP_DISTRIBUTION_TYP=HortonWorks/ClouderaManager/HDInsight, for CLUSTER_HADOOP_DISTRIBUTION_TYP=others leave the field blank #leave this property blank for CLUSTER_TYPE=1 i.e for embedded Hadoop cluster managed by informatica. HDFS_SERVICE_PRINCIPAL= #YARN_SERVICE_PRINCIPAL parameter is required for CLUSTER_TYPE=2 i.e for existing Hadoop cluster and IS_CLUSTER_SECURE=true for kerberos enabled cluster else leave this #property blank. #leave this property blank for CLUSTER_TYPE=1 i.e for embedded Hadoop cluster managed by informatica. YARN_SERVICE_PRINCIPAL= #KDC_DOMAIN_NAME parameter is required for CLUSTER_TYPE=2 i.e for existing Hadoop cluster and IS_CLUSTER_SECURE=true for kerberos enabled cluster else leave this #property blank. #leave this property blank for CLUSTER_TYPE=1 i.e for embedded Hadoop cluster managed by informatica. KDC_DOMAIN_NAME= #KDC_KEYTAB_LOCATION parameter is required for CLUSTER_TYPE=2 i.e existing Hadoop cluster and IS_CLUSTER_SECURE=true for kerberos enabled cluster else leave this #property blank. #leave this property blank for CLUSTER_TYPE=1 i.e for embedded Hadoop cluster managed by informatica. KDC_KEYTAB_LOCATION= #HISTORY_SERVER_HTTP_URI parameter is required for CLUSTER_TYPE=2 i.e existing Hadoop cluster else leave this property blank. #leave this property blank for CLUSTER_TYPE=1 i.e for embedded Hadoop cluster managed by informatica. #leave this property blank for CLUSTER_HADOOP_DISTRIBUTION_TYP=HortonWorks/ClouderaManager/HDinsight HISTORY_SERVER_HTTP_URI= #Set this property to demo/low/high/medium for both CLUSTER_TYPE=1 and CLUSTER_TYPE=2 #By default the value will be low LOAD_TYPE=low ##################################### # Enterprise Data Lake ##################################### # If the machine on which you are installing Enterprise Data Lake has 16 GB of RAM or less, Informatica recommends that you create the Data Preparation Service and the Enterprise Data Lake Service on different nodes. If you create the services on different nodes, you must create the Data Preparation Service on the master gateway node. You can create the Enterprise Data Lake Service on any other node. # Creates the Data Preparation Service and the Enterprise Data Lake Service during installation. Set the value to 1 to create the services during installation. # If the value is 0, the installer does not create the Data Preparation Service and the Enterprise Data Lake Service. You must create the services in Informatica Administrator. # Default is 1. CREATE_LAKE_SERVICES=1 # Name of the Catalog Service that you want to associate with the Enterprise Data Lake Service. # Default name is Catalog_Service. CATALOGUE_SERVICE_NAME_ASSOCIATED=Catalog_Service # Required if you want to use the profiling feature in Enterprise Data Catalog. Name of the Content Management Service. # Enables or disables the Content Management Service. # If the value is true, the Content Management Service is enabled. # If the value is false, the Content Management Service is disabled. # Default is false. ENABLE_CMS_SERVICE=false # Name of the Content Management Service that you want to associate with the Enterprise Data Lake Service. # Set this value if ENABLE_CMS_SERVICE=true CMS_SERVICE_NAME_ASSOCIATED= # Optional parameters to create Model repository service(MRS) and Data Integration Service(DIS) from installer. # You can create a Model Repository Service and Data Integration Service to associate with the Enterprise Data Lake Service, or you can associate existing services with the Enterprise Data Lake Service. # Set CREATE_IDL_SERVICES=1 to create a Model Repository Service and Data Integration Service on this node and provide the MRS database parameters, MRS service name, DIS service name, and port number.. # Set CREATE_IDL_SERVICES=0 to Associate an existing Model Repository Service and Data Integration Service with the Enterprise Data Lake Service. # Use a different database user account for the Model Repository Service database instead of using the same domain database user or database. CREATE_IDL_SERVICES=0 # Database type for the domain configuration database. # Set this property to one of the following database types (case sensitive): Oracle, MSSQLServer, or DB2. # Set this value if CREATE_IDL_SERVICES=1 IDL_MRS_DB_TYPE=Oracle/MSSQLServer/DB2 # Database user account name for the domain configuration repository. # Set this value if CREATE_IDL_SERVICES=1 IDL_MRS_DB_UNAME=UserName # Database password for the database user account. # Set this value if CREATE_IDL_SERVICES=1 IDL_MRS_DB_PASSWD=UserPassword # Represents whether the database is in SSL mode or not. # Set this property to true if you want to enable secure communication. # If this property is set to true then IDL_MRS_DB_CUSTOM_STRING_SELECTION property must be set to 1. # Set this value if CREATE_IDL_SERVICES=1 IDL_MRS_DB_SSL_ENABLED=false # Set this property only if IDL_MRS_DB_SSL_ENABLED is set to true. # Include the following secure database parameters: # EncryptionMethod=SSL;HostNameInCertificate=;ValidateServerCertificate= # Set this value if CREATE_IDL_SERVICES=1 IDL_MRS_SSL_DEFAULT_STRING= # Set the IDL_TRUSTSTORE_MRS_DB_FILE and IDL_TRUSTSTORE_MRS_DB_PASSWD properties if the database property IDL_MRS_DB_SSL_ENABLED=true. # Set the IDL_TRUSTSTORE_MRS_DB_FILE property to the location of the trust store file for the database. # Set the IDL_TRUSTSTORE_MRS_DB_PASSWD as the password of the trust store file for the database. # Set this value if CREATE_IDL_SERVICES=1 IDL_TRUSTSTORE_MRS_DB_FILE= IDL_TRUSTSTORE_MRS_DB_PASSWD= # Name of the schema that will contain the domain configuration tables. # Set this property if IDL_MRS_DB_TYPE=MSSQLServer. # If IDL_MRS_SQLSERVER_SCHEMA_NAME is empty, the installer creates the tables in the default schema. # Set this value if CREATE_IDL_SERVICES=1 IDL_MRS_SQLSERVER_SCHEMA_NAME= # Name of the tablespace in which to create the tables. # Set this property if IDL_MRS_DB_TYPE=DB2. # Specify a tablespace that meets the pageSize requirement of 32768 bytes. # In a single-partition database, if IDL_MRS_DB2_TABLESPACE is empty, the installer creates the tables in the default tablespace. # In a multi-partition database, define the tablespace in the catalog partition of the database. # Set this value if CREATE_IDL_SERVICES=1 IDL_MRS_DB2_TABLESPACE= # Determines whether to use a JDBC URL or a custom connection string to connect to the domain configuration database. # Set IDL_MRS_DB_CUSTOM_STRING_SELECTION=1 if MRS_TRUSTED_CONNECTION=1. Also provide the default valid connection string in MRS_DB_CUSTOM_STRING. # If the value is 0, the installer creates a JDBC URL from the database properties you provide # If the value is 1, the installer uses the custom connection string you provide. # Set this value if CREATE_IDL_SERVICES=1 IDL_MRS_DB_CUSTOM_STRING_SELECTION=0 # Represents the service name or database name of the database. # Set this property if IDL_MRS_DB_CUSTOM_STRING_SELECTION=0. # Set this property to the service name for Oracle and IBM DB2 databases. # Set this property to the database name for Microsoft SQL Server and Sybase ASE databases. # Leave the property blank if IDL_MRS_DB_CUSTOM_STRING_SELECTION=1. # Set this value if CREATE_IDL_SERVICES=1 IDL_MRS_DB_SERVICENAME=DBServiceName # Represents the host name and port number for the database instance. # Set this property if IDL_MRS_DB_CUSTOM_STRING_SELECTION=0. # Set this property in the format HostName:PortNumber. # Leave the property blank if IDL_MRS_DB_CUSTOM_STRING_SELECTION=1. # Set this value if CREATE_IDL_SERVICES=1 IDL_MRS_DB_ADDRESS=HostName:PortNumber # Represents additional parameters in the JDBC URL connection string. # If IDL_MRS_DB_CUSTOM_STRING_SELECTION=0, you can Set this property to include optional parameters in the JDBC URL connection string. # The parameter string must be valid. # If the parameter is empty, the installer creates the JDBC URL without additional parameters. # Set this value if CREATE_IDL_SERVICES=1 IDL_MRS_ADVANCE_JDBC_PARAM= # Represents a valid custom JDBC connection string. # Set this property if IDL_MRS_DB_CUSTOM_STRING_SELECTION=1. # Set this value if CREATE_IDL_SERVICES=1 IDL_MRS_DB_CUSTOM_STRING= # Name of the Model Repository Service that you want to use for the Enterprise Data Lake Service. # Set this value if CREATE_IDL_SERVICES=1 MRS_SERVICE_NAME_IDL=Model_Repository_Service_EDL # Name of the Data Integration Service that you want to use for the Enterprise Data Lake Service. # Set this value if CREATE_IDL_SERVICES=1 DIS_SERVICE_NAME_IDL=Data_Integration_Service_EDL # Select the HTTP protocol to use for the Data Integration Service. # Set this property to one of the following protocol types (case-sensitive): http/https/both. # Set this value if CREATE_IDL_SERVICES=1 IDL_DIS_PROTOCOL_TYPE= # Number of the HTTP port of the Data Integration Service. # Set this property if IDL_DIS_PROTOCOL_TYPE=http or IDL_DIS_PROTOCOL_TYPE=both. # Leave this property blank if IDL_DIS_PROTOCOL_TYPE=https. # Set this value if CREATE_IDL_SERVICES=1 IDL_DIS_HTTP_PORT= # Number of the HTTPS Port of the Data Integration Service. # Set this property if IDL_DIS_PROTOCOL_TYPE=https or IDL_DIS_PROTOCOL_TYPE=both. # Leave this property blank if IDL_DIS_PROTOCOL_TYPE=http. # Set this value if CREATE_IDL_SERVICES=1 IDL_DIS_HTTPS_PORT= # IDL_DIS_CUSTOM_SELECTION is optional. # Set IDL_DIS_CUSTOM_SELECTION value to true if IDL_DIS_PROTOCOL_TYPE=https or IDL_DIS_PROTOCOL_TYPE=both. # Set this value if CREATE_IDL_SERVICES=1 IDL_DIS_CUSTOM_SELECTION=false # The following fields are required when you set IDL_DIS_CUSTOM_SELECTION=true. # Set keystore file location in IDL_DIS_KEYSTORE_DIR. # Set this value if CREATE_IDL_SERVICES=1 IDL_DIS_KEYSTORE_DIR= IDL_DIS_KEYSTORE_PASSWD= # Set truststore file location in IDL_DIS_TRUSTSTORE_DIR. # Set this value if CREATE_IDL_SERVICES=1 IDL_DIS_TRUSTSTORE_DIR= IDL_DIS_TRUSTSTORE_PASSWD= # Cluster Configuration Details # Cluster configuration required to push processing to the Hadoop environment. The cluster configuration contains configuration information about the Hadoop cluster, and enables the Data Integration Service to push mapping logic to the Hadoop engine. # Enter the following details to create the CCO connections. #Name of the cluster to be created and configured. CLUSTER_CONFIG_NAME= #Name of the cluster distribution type. #Set this property to one of the following values according to the Distribution types #Cloudera=cdh #Hortonworks=hdp #Azure HDInsight=hdi #MapR=mapr #Amazon EMR=emr DISTRIBUTION_TYPE= #Method to import the cluster configuration. #Set this property to 1 to import from archive file. #Set this property to 2 to import from cluster. IMPORT_METHOD= #Set this property if IMPORT_METHOD=1. #Path of the archive file to import the cluster configuration. ARCHIVE_FILE= #Set this property if IMPORT_METHOD=2. #Host name of the cluster. CLUSTER_HOST= #Set this property if IMPORT_METHOD=2. #Port number of the cluster. CLUSTER_PORT= #Set this property if IMPORT_METHOD=2. #User ID of the cluster. CLUSTER_USERID= #Set this property if IMPORT_METHOD=2. #Password for the user log in Id of the cluster. CLUSTER_PASSWORD= #Set this property to true or false to create Hadoop, HDFS, Hive, and HBase connections. The installer appends the connection type to the cluster connection name to create each connection name. #Default is true. CREATE_CONNECTION=true #Name of the cluster. CLUSTER_NAME_CCO= # Data Preparation Repository Database Details # Enter repository database information for the Data Preparation Service: # Type of the database for the Data Preparation repository. # Set this property to one of the following database types (case-sensitive): Oracle or MySQL. DPS_DB_TYPE=Oracle/MySQL # Database user account that you want to use to create the Data Preparation repository. DPS_DB_USER= # Password for the Data Preparation repository database user account. DPS_DB_PSSWD= # The DPS_DB_CUSTOM_STRING_SELECTION property determines whether to use a JDBC URL or a custom connection string to connect to the domain configuration database. # Set this property to "true" if you want the installer to use the custom connection string you provide. DPS_DB_CUSTOM_STRING_SELECTION=false # Port number of the database. # Required if DPS_DB_CUSTOM_STRING_SELECTION=false for Oracle or if DPS_DB_TYPE=MySQL. # Leave the property blank if DPS_DB_CUSTOM_STRING_SELECTION=true. DPS_DB_PORT= # Host name of the machine that hosts the Data Preparation repository database. # Required if DPS_DB_CUSTOM_STRING_SELECTION=false for Oracle or if DPS_DB_TYPE=MySQL. # Leave the property blank if DPS_DB_CUSTOM_STRING_SELECTION=true. DPS_DB_HOST= # The DPS_DB_SERVICENAME property represents the service name or database name of the database. # Set this property if DPS_DB_CUSTOM_STRING_SELECTION=false. # Required if DPS_DB_CUSTOM_STRING_SELECTION=false for Oracle. # Leave the property blank if DPS_DB_CUSTOM_STRING_SELECTION=true. DPS_DB_SERVICENAME= # Schema or database name of the Data Preparation repository database. # Required if DPS_DB_TYPE=MySQL. DPS_DB_SCHEMA= # The ENABLE_DB_SSL property represents whether the database is in SSL mode or not. # The ENABLE_DB_SSL property is valid only if DPS_DB_TYPE=Oracle. # Set this property to "true" if you want to enable secure communication. ENABLE_DB_SSL=false # Set this property if DPS_DB_CUSTOM_STRING_SELECTION=true. # Represents a valid custom JDBC connection string. DPS_DB_CUSTOM_STRING=false # Set this property only if ENABLE_DB_SSL is set to true and if DPS_DB_TYPE=Oracle. # Set the DPS_DB_TRUSTSTORE_FILE property to the location of the trust store file for the database. DPS_DB_TRUSTSTORE_FILE= # Set this property only if ENABLE_DB_SSL is set to true and if DPS_DB_TYPE=Oracle # Set the DPS_DB_TRUSTSTORE_PASSWD as the password of the trust store file for the database. DPS_DB_TRUSTSTORE_PASSWD= # Set this property only if ENABLE_DB_SSL is set to true and if DPS_DB_TYPE=Oracle. # DPS_SSL_DEFAULT_STRING should include the following secure database parameters: # EncryptionMethod=SSL;HostNameInCertificate=;ValidateServerCertificate= DPS_SSL_DEFAULT_STRING= # Data Preparation Service Details # Name of the Data Preparation Service associated with the Enterprise Data Lake Service. Default is Data_Preparation_Service. DPS_SERVICE_NAME=Data_Preparation_Service # Set the value to true, if user wants to configure MRS/DIS for the Data Preparation Service. Default is false. DPS_CONFIGURE_SERVICES=false # Required if DPS_CONFIGURE_SERVICES=true. # Name of the MRS Service name which user wants to associate with the Data Preparation Service. DPS_MRS_SERVICE_NAME= # Required if DPS_CONFIGURE_SERVICES=true. # Name of the DIS Service name which user wants to associate with the Data Preparation Service. DPS_DIS_SERVICE_NAME= # Set the value to true, to enable the Data Preparation Service immediately after creation. # Set the value to false, to enable the Data Preparation Service from the Administrator tool. Default is false. ENABLE_DPS_SERVICE=false # Name of the node where you want to run the Data Preparation Service. DPS_NODE_NAME= # Enable Secure Communication # To enable secure communication for the Data Preparation Service, set DPS_PROTOCOL_TYPE to https. # To disable secure communication for the Data Preparation Service, set DPS_PROTOCOL_TYPE to http. DPS_PROTOCOL_TYPE=http # Required if DPS_PROTOCOL_TYPE=http. # Keep this field blank if DPS_PROTOCOL_TYPE=https. # Number of the HTTP port of the Data Preparation Service. DPS_HTTP_PORT=8099 # Required if DPS_PROTOCOL_TYPE=https. # Keep this field blank if DPS_PROTOCOL_TYPE=http. # Number of the HTTPS port number of the Data Preparation Service. DPS_HTTPS_PORT= # To use the default Informatica SSL certificate files, set DPS_CUSTOM_HTTPS_ENABLED to false. # To use the custom SSL certificate files, set DPS_CUSTOM_HTTPS_ENABLED to true. # Default is false. DPS_CUSTOM_HTTPS_ENABLED=false # Required if DPS_CUSTOM_HTTPS_ENABLED=true. # Path and the file name of keystore file that contains key and certificates required for the HTTPS communication. DPS_KEYSTORE_DIR= # Required if DPS_CUSTOM_HTTPS_ENABLED=true. # Password for the keystore file. DPS_KEYSTORE_PSSWD= # Required if DPS_CUSTOM_HTTPS_ENABLED=true. # Path and the file name of truststore file that contains authentication certificates for the HTTPS connection. DPS_TRUSTSTORE_DIR= # Required if DPS_CUSTOM_HTTPS_ENABLED=true. # Password for the truststore file. DPS_TRUSTSTORE_PSSWD= # Data Preparation Storage Options # HDFS location for data preparation file storage. If the connection to the local storage fails, the Data Preparation Service recovers data preparation files from the HDFS location. HDFS_LOCATION= # Directory for data preparation file storage on the node on which the Data Preparation Service runs. LOCAL_STORAGE_DIR= # Port number for the Apache Solr server used to provide data preparation recommendations. # Default is 8983. SOLR_PORT=8983 # Hadoop Authentication Mode # Set the Hadoop Authentication Mode to NonSecure or Kerberos. # Default is NonSecure AUTH_MODE=NonSecure # Required if AUTH_MODE=Kerberos. # User name to use in Hadoop impersonation as set in core-site.xml. HADOOP_IMPERSONATION_USER= # Required if AUTH_MODE=Kerberos. # Service Principal Name (SPN) for the data preparation Hadoop cluster. Specify the service principal name in the following format: user/_HOST@REALM. HDFS_PRINCIPAL_NAME= # Required if AUTH_MODE=Kerberos. # Path and file name of the SPN keytab file for the user account to impersonate when connecting to the Hadoop cluster. The keytab file must be in a directory on the machine where the Data Preparation Service runs. KERBEROS_KEYTAB_FILE= # Enterprise Data Lake Service Details # Enterprise Data Lake Service Name. Default is Enterprise_Data_Lake_Service. IDL_SERVICE_NAME=Enterprise_Data_Lake_Service # Name of the node where you want to run the Enterprise Data Lake Service. IDL_NODE_NAME= # Name of the Data Preparation Service. Set the IDL_DPS_SERVICE_NAME property to the name of the Data Preparation Service to associate with the Enterprise Data Lake Service specified in the IDL_SERVICE_NAME property. IDL_DPS_SERVICE_NAME= # Name of the Model Repository Service. Set the IDL_MRS_SERVICE_NAME property to the name of the Model Repository Service to associate with the Enterprise Data Lake Service specified in the IDL_SERVICE_NAME property. IDL_MRS_SERVICE_NAME= # Name of the Data Integration Service. Set the IDL_DIS_SERVICE_NAME property to the name of the Data Integration Service to associate with the Enterprise Data Lake Service specified in the IDL_SERVICE_NAME property. IDL_DIS_SERVICE_NAME= # If the value is true, the Enterprise Data Lake Service is enabled immediately after creation. # If the value is false, you must enable the Enterprise Data Lake Service from the Administrator tool. # Default is false. ENABLE_IDL_SERVICE=true # Enable Secure Communication # Indicates whether the Enterprise Data Lake Services uses secure communication. # To enable secure communication for the Enterprise Data Lake Service, set IDL_PROTOCOL_TYPE to https. # To disable secure communication for the Data Preparation Service, set IDL_PROTOCOL_TYPE to http. IDL_PROTOCOL_TYPE=http # Required if IDL_PROTOCOL_TYPE=http. # HTTP port number of the Enterprise Data Lake Service. # Leave this field blank if IDL_PROTOCOL_TYPE=https. IDL_HTTP_PORT=7099 # Required if IDL_PROTOCOL_TYPE=https. # HTTPS port number of the Enterprise Data Lake Service. # Leave this field blank if IDL_PROTOCOL_TYPE=http. IDL_HTTPS_PORT= # Required if IDL_PROTOCOL_TYPE=https. # Indicates whether the Enterprise Data Lake Service uses the default or custom Informatica SSL certificate files. # To use the default Informatica SSL certificate files, set IDL_CUSTOM_HTTPS_ENABLED to false. # To use the custom Informatica SSL certificate files, set IDL_CUSTOM_HTTPS_ENABLED to true. # Default is false. IDL_CUSTOM_HTTPS_ENABLED=false # Required if IDL_CUSTOM_HTTPS_ENABLED=true. # Path and the file name of keystore file that contains key and certificates required for the HTTPS communication. IDL_KEYSTORE_DIR= #Required if IDL_CUSTOM_HTTPS_ENABLED=true. Password for the keystore file. IDL_KEYSTORE_PSSWD= # Required if IDL_CUSTOM_HTTPS_ENABLED=true. # Path and the file name of truststore file that contains authentication certificates for the HTTPS connection. IDL_TRUSTSTORE_DIR= # Required if IDL_CUSTOM_HTTPS_ENABLED=true. # Password for the truststore file. IDL_TRUSTSTORE_PSSWD= # Data Lake Options # HDFS directory where the Enterprise Data Lake Service copies temporary data and files necessary for the service to run. HDFS_SYSTEM_DIR= # Data storage format for the Hive tables. Values are DefaultFormat, Parquet, ORC. # Default is DefaultFormat. HIVE_LOCALSTORAGE_FORMAT=DefaultFormat LOCAL_SYSTEM_DIR= # Indicates whether the security mode is NonSecure or Kerberos. # Set the SECURITY_MODE to NonSecure or Kerberos. # Default is NonSecure. SECURITY_MODE=NonSecure # Required if SECURITY_MODE=Kerberos. # Service principal name (SPN) of the user account to impersonate when connecting to the data lake Hadoop cluster. The user account for impersonation must be set in the <Informatica installation directory>/services/shared/hadoop/<hadoop distribution name>/conf/core-site.xml file. IDL_KERBEROS_PRINCIPAL= # Required if SECURITY_MODE=Kerberos. # Path and file name of the SPN keytab file for the user account to impersonate when connecting to the Hadoop cluster. The keytab file must be in a directory on the machine where the Enterprise Data Lake Service runs. IDL_KERBEROS_KEYTAB_FILE= ####### # After you create the properties file, save the file with the name SilentInput.properties and # run the silent installer to perform the Informatica domain services installation. #######