Table of Contents

Search

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

Installation and Configuration Guide

Installation and Configuration Guide

Common Operating System Prerequisites for Red Hat Enterprise Linux and SUSE Linux Enterprise Server

Common Operating System Prerequisites for Red Hat Enterprise Linux and SUSE Linux Enterprise Server

You can install Enterprise Data Catalog on a machine that runs on Red Hat Enterprise Linux Server or SUSE Linux Enterprise Server.
Verify the following common prerequisites for both SUSE and Red Hat Enterprise Linux Servers:
  • Ensure that the operating system is 64-bit.
  • Make sure that you install
    file
    .
  • Ensure that
    Bash
    is the default shell.
  • If you use a user account without root privileges and if you want to remove sudo access, ensure that
    defaults requiretty
    is commented in
    /etc/sudoers
    .
  • If you use a user account without root privileges, make sure that the Hadoop user has sudo privileges.
  • Make sure that you disable the password prompt for the Hadoop user.
  • Make sure that you install python-devel.
  • Make sure that you set UMASK to 022 (0022) or 027 (0027).
  • Ensure that you set Fully Qualified Domain Name (FQDN) for hostname -f.
  • Make sure that the
    /var
    location does not have write privilege for everyone.
  • Ensure that you configure the Linux base repositories.
  • Make sure that you install the netstat command line network utility tool.
  • Verify that the root directory (
    /
    ) has a minimum of 10 GB of free disk space.
  • If you plan to install Enterprise Data Catalog on an embedded cluster and you want to mount Informatica Cluster Service on a separate mount location, verify that the mount location has a minimum of 50 GB of free disk space.
  • Make sure that the
    NOEXEC
    flag is not set for the file system mounted on the
    /tmp
    directory.
  • You might want to ensure that the
    /tmp
    directory has a minimum of 20 GB of free disk space to enhance performance.
  • Make sure that you install the scp, curl, unzip, wget and tar utilities.
  • Ensure that you configure the
    home
    directory with write permission.
  • Make sure that the configured
    /etc/hosts
    file of all machines include the FQDN for the machines.
  • Ensure that the Network Time Protocol (NTP) daemon is synchronized and running.
  • Make sure that the
    /tmp
    directory has chmod 777 permission configured for the directory.
  • Make sure that the
    /
    and
    /var
    directories do not have
    chmod 777
    permission configured.
  • Make sure that the
    /var
    directory has a minimum of 2 GB of free disk space.
  • Make sure that the
    /usr
    directory has a minimum of 2 GB of free disk space.
  • Ensure that you disable Selinux or set Selinux to permissive mode.
  • Make sure that the
    /etc/hosts
    has an entry for the loopback address,
    127.0.0.1 localhost localhost.domain.com
  • Make sure that you set the core limit to
    unlimited
    for a user without root privileges.
  • If you configure the workingDir to
    /
    , validate if the file system mounted on
    /tmp
    and
    /var
    directories have the EXEC flag set.
  • If the workingDir is not configured to
    /
    , validate if the workingDir directory has Read, Write, and Execute permissions configured. Validate if the EXEC flag is also set for the directory.
  • Verify that you have the write permission on the
    /home
    directory. You can configure the permission in the
    /etc/default/useradd
    file.
  • Make sure that each machine in the cluster includes the
    127.0.0.1 localhost localhost.localdomain
    entry in the
    /etc/hosts
    file.
  • Verify that the
    /etc/hosts
    file includes the fully-qualified host names for all the cluster nodes. Alternatively, make sure that reverse DNS lookup returns the fully-qualified host names for all the cluster nodes.
  • Verify that the Linux repository includes postgresql version 8.14.18, release 1.el6_4 or later versions.
  • Ensure that you set the soft limit for max user processes to 32000 or more.
  • Ensure that you set the hard limit for max user processes to 32000 or more.
  • Ensure that you set the soft limit for max user processes to 10000 or more for the cluster nodes.
  • Ensure that you set the hard limit for max user processes to 10000 or more for the cluster nodes.​
  • On each host machine, verify that you have the following tools and applications available:
    • YUM and RPM (RHEL/CentOS/Oracle Linux)
    • Zypper
    • scp, curl, unzip, tar, and wget
    • awk
    • OpenSSL version 1.0.1e-30.el6_6.5.x86_64 or later.
      Make sure that the $PATH variable points to the
      /usr/bin
      directory to use the correct version of Linux OpenSSL.
  • For Enterprise Data Catalog installed on an embedded cluster, if you have not configured the Linux base repository or if you do not have an Internet connection, install the following packages:
    - The following RPMs on the Ambari Server host:
    • postgresql-libs
    • postgresql-server
    • postgresql
    -The following RPMs on all cluster nodes:
    • nc
    • redhat-lsb
    • psmisc
    • python-devel